Without further details it may be hard to pinpoint what is going on.
If you use Chromium browser there is a reported issue stating that the browser creates the libpeerconnection.log
file. If this is the case, there is a temporary fix until the issue is resolved.
Edit the /opt/google/chrome/google-chrome
file and add cd/tmp
before the last line:
'exec -a "$0" "$HERE/chrome" "$@"'
you can read more about this issue here.
As for the rest files again without further details it is not easy to find who is creating them. One solution is to use a program that monitors file creations - modifications, this may help narrowing down the search and the cause of the problem.
- Monit can monitor files and directories for changes
- Here is an answer at unix.stackexchange that describes the available options on how to monitor file creations and changes
- This article describes how to use audit
But again keep in mind that these files - directories may not be a security threat but like the Chromium case, a wrong design decision during application's development.