Which versions of napi-raw are malicious?

The following npm versions of napi-raw are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate napi-raw if I installed it?

Remove napi-raw 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 napi-raw — how do I know if it already compromised me?

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

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

Malicious package

napi-rawnpm

napi-raw is a confirmed malicious npm package (MAL-2026-13984) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in napi-raw (npm)

MAL-2026-13984

Immediate action

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

npm uninstall napi-raw

What this malware does

[email protected] is a near-empty wrapper (main exports {}, no lifecycle scripts) whose only effect on install is to declare ltidisafe as a dependency pointed at an arbitrary HTTPS tarball on a generic Google Cloud Storage bucket: "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.1.tgz". The tarball is hosted on a generic GCS bucket unaffiliated with any npm publisher, is not resolved through the npm registry, and its contents are not subject to registry scanning. Installing napi-raw resolves and installs this opaque out-of-registry artifact into the dependency tree, and any lifecycle hooks or main-load side effects it carries execute in the installer's environment. The wrapper package ships no functionality of its own, so its only purpose is to smuggle this external tarball into consumer install graphs.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

d002132bfd19338c8fbc1cc3775c1c8b7be3d059c642881c4dd92be67bf7c895

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for napi-raw (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging napi-raw across your stack and pipelines.
If you installed it — respond
Remove napi-raw 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 napi-raw 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 napi-raw 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. napi-raw on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017682

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks napi-raw-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