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.
leaked-handles
Advanced tools
Detect any handles leaked in node
require("leaked-handles");
Add this to the TOP of your tests as the very first require.
This will now print any handles that keep your process open.
It has pretty printing of some handles including
When you see a timer, it will print the file, so go fix it!
When you see a child process it prints the pid. Run ps -p {pid}
and figure out what kind of child process it is.
When you see a stream it prints the fd. Run lsof -p {process.pid}
to see what fds your test process has open and see if you can
figure out what the hell it is.
When you see a child process stream, go find the child process
that leaked. If no child process leaked then again, use lsof
to lookup up the fd.
npm install leaked-handles
npm test
FAQs
Detect any handles leaked in node
The npm package leaked-handles receives a total of 11,664 weekly downloads. As such, leaked-handles popularity was classified as popular.
We found that leaked-handles 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.