Which versions of nullrift are malicious?

The following npm versions of nullrift are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate nullrift if I installed it?

nullrift is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed nullrift — how do I know if it already compromised me?

If nullrift 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 nullrift part of a known attack campaign?

Yes — nullrift is associated with the IN-MAL-2026-009763 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 nullrift 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 nullrift (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nullrift across your stack and pipelines.

Malicious package

nullriftnpm

Malicious code in nullrift (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10206

Immediate action

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

npm uninstall nullrift

What this malware does

Package advertises itself as an SVG fetcher/sanitizer but its main module also exports an undocumented getPlugin() function. The returned function performs an HTTP request to https://www.jsonkeeper.com/b/3P9BF with a custom 'bearrtoken' header, parses the JSON response, and passes the 'model' field directly to eval(). jsonkeeper.com is a public, mutable, anonymous paste host — whoever controls the paste can change its contents at any time and thereby execute arbitrary JavaScript inside any consumer process that invokes the exported function. The hidden code path is inconsistent with the package's declared SVG-utility purpose and is the canonical shape of a supply-chain backdoor giving the paste operator remote code execution on downstream consumers.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

29ebce322ac712405bfd29254cbd8f820c20ddc083587693a982b75ef6f3039a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nullrift (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nullrift across your stack and pipelines.
If you installed it — respond
nullrift is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If nullrift 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 nullrift 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. nullrift on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009763

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nullrift-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring