prism-registrynpm
Advisory published Updated
prism-registry is a confirmed malicious npm package (MAL-2026-14139) that opens a backdoor for remote access (malicious versions 1.0.1, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in prism-registry (npm)
What this malware does
The package declares preinstall: "node index.js", which fires automatically on npm install. index.js collects host identifiers (os.hostname, os.userInfo, home directory, DNS servers, __dirname, package.json contents) and reads the local files /etc/passwd and /etc/hosts, then POSTs the aggregated JSON over HTTPS to the hardcoded Burp Collaborator subdomain zjmjb1b5mnwtdcmzrsq6uj4bj2ptdj18.oastify.com. There is no legitimate functionality in the package beyond this beacon.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for prism-registry (2 malicious versions).
If you installed it — respond
prism-registry establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If prism-registry was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks prism-registry-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.