Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Exposes a synchronous `if (!fs.existsSync(...))` check around an `fs.writeFileSync` or `fs.mkdirSync` call, depending on whether `filetouch.dir` or `filetouch.file` is called.
Exposes a synchronous if (!fs.existsSync(...))
check around an
fs.writeFileSync
or fs.mkdirSync
call, depending on whether filetouch.dir
or filetouch.file
is called.
Files are not modified if they already exist.
const filetouch = require('filetouch');
// create test.txt if doesn't exist
filetouch.file('test.txt');
// create test2.txt and write into it, if doesn't exist
filetouch.file('test2.txt', 'test text goes here');
// create test3 directory if doesn't exist
filetouch.dir('test3');
FAQs
Exposes a synchronous `if (!fs.existsSync(...))` check around an `fs.writeFileSync` or `fs.mkdirSync` call, depending on whether `filetouch.dir` or `filetouch.file` is called.
The npm package filetouch receives a total of 1 weekly downloads. As such, filetouch popularity was classified as not popular.
We found that filetouch demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.