Which versions of @toprimitive/nif are malicious?

The following npm versions of @toprimitive/nif are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate @toprimitive/nif if I installed it?

Remove @toprimitive/nif from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @toprimitive/nif — how do I know if it already compromised me?

If @toprimitive/nif 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.

Is @toprimitive/nif part of a known attack campaign?

Yes — @toprimitive/nif is associated with the RLMA-2026-04790, RLUA-2026-05935 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 @toprimitive/nif across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @toprimitive/nif (version 99.9.9).

Malicious package

@toprimitive/nifnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@toprimitive/nif is a confirmed malicious npm package (MAL-2026-7096) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @toprimitive/nif (npm)

MAL-2026-7096

Immediate action

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

npm uninstall @toprimitive/nif

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

a1da1c8da9901947a0baa8f4742fc0570bec0eff96392a9caf813709eefaa6b7

ebdb9245f0f1f1e8910ba0da5ddf25192cd9b89fae1aae2b2384b2fea53c84ce

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @toprimitive/nif (version 99.9.9).
If you installed it — respond
Remove @toprimitive/nif from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @toprimitive/nif 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

No. @toprimitive/nif on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04790RLUA-2026-05935

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @toprimitive/nif-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database