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.
@apify/ps-tree
Advanced tools
NOTE: This is a fork of ps-tree NPM package, with some fixes and extras.
Sometimes you cannot kill child processes like you would expect, this a feature of UNIX.
in UNIX, a process may terminate by using the exit call, and it's parent process may wait for that event by using the wait system call. the wait system call returns the process identifier of a terminated child, so that the parent tell which of the possibly many children has terminated. If the parent terminates, however, all it's children have assigned as their new parent the init process. Thus, the children still have a parent to collect their status and execution statistics. (from "operating system concepts")
Solution: use ps-tree
to get all processes that a child_process
may have started, so that they may all be terminated.
var cp = require('child_process'),
psTree = require('ps-tree');
var child = cp.exec("node -e 'while (true);'", function () {...});
// This will not actually kill the child it will kill the `sh` process.
child.kill();
wtf? it's because exec actually works like this:
function exec (cmd, cb) {
spawn('sh', ['-c', cmd]);
...
}
sh
starts parses the command string and starts processes, and waits for them to terminate, but exec
returns a process object with the pid of the sh
process.
However, since it is in wait
mode killing it does not kill the children.
Use ps-tree
like this:
var cp = require('child_process'),
psTree = require('ps-tree');
var child = cp.exec("node -e 'while (true);'", function () { /*...*/ });
psTree(child.pid, function (err, children) {
cp.spawn('kill', ['-9'].concat(children.map(function (p) { return p.PID })));
});
If you prefer to run psTree from the command line, use: node ./bin/ps-tree.js
The ps-tree
module behaves differently on *nix vs. Windows by spawning different programs and parsing their output. This is based on process.platform
and not on checking to see if a ps
compatible program exists on the system.
$ ps -A -o comm,ppid,pid,stat
COMMAND PPID PID STAT
bbsd 2899 16958 Ss
watch <defunct> 1914 16964 Z
ps 20688 16965 R+
wmic PROCESS WHERE ParentProcessId=4604 GET Name,ParentProcessId,ProcessId,Status)
> wmic PROCESS GET Name,ProcessId,ParentProcessId,Status
Name ParentProcessId ProcessId Status
System Idle Process 0 0
System 0 4
smss.exe 4 228
FAQs
Get all children of a pid
We found that @apify/ps-tree demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 9 open source maintainers 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.