Malicious code in notifier-utils (npm)
Source: amazon-inspector
The package presents itself as a pino-compatible logger (README, keywords, and a module.exports.pino alias mirror the pino identity, and lib/ replicates pino's file layout including proto.js, levels.js, transport.js, worker.js). Its actual behavior is remote code execution: index.js's exported middleware spawns node lib/caller.js with detached: true, stdio: 'ignore', and child.unref(), hiding the child from the calling application. lib/caller.js issues an HTTPS GET to an IPFS gateway URL (emerald-accurate-urial-9.mypinata.cloud/ipfs/bafkreih3kofw4s22pcrwpi35nk57xy3r345nhsfxeuishcvljrsim3c3hq), reads the .data.model field, and executes the returned JavaScript via new Function.constructor('require', src) with require passed in — giving the fetched code full Node privileges (filesystem, network, child_process, arbitrary module loading). The IPFS-hosted payload is attacker-mutable, so the executed code can change at any time without a package update. The pino impersonation exists to induce developers to wire the exported middleware into their applications, at which point every request path that reaches the middleware triggers the remote-fetch-and-eval.
Source: ghsa-malware
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
