Which versions of prism-registry are malicious?

The following npm versions of prism-registry are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate prism-registry if I installed it?

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.

I already installed prism-registry — how do I know if it already compromised me?

If prism-registry was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is prism-registry part of a known attack campaign?

Yes — prism-registry is associated with the IN-MAL-2026-018173 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find prism-registry across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for prism-registry (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prism-registry across your stack and pipelines.

Malicious package

prism-registrynpm

prism-registry is a confirmed malicious npm package (MAL-2026-14139) that opens a backdoor for remote access (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in prism-registry (npm)

MAL-2026-14139

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall prism-registry

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.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

f6570c9056bf020fdada0366045c4e91a0f5cb21171fe27df9fcea82259e7809

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for prism-registry (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prism-registry across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks prism-registry before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. prism-registry on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018173

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database