Which versions of node-path-addon are malicious?

The following npm versions of node-path-addon are flagged malicious: 1.0.7, 1.0.8. Treat any of these as compromised.

How do I remediate node-path-addon if I installed it?

node-path-addon 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 node-path-addon — how do I know if it already compromised me?

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

Yes — node-path-addon is associated with the IN-MAL-2026-010269, GHSA-87rj-7vj7-vxgg, IN-MAL-2026-010630 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 node-path-addon 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 node-path-addon (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-path-addon across your stack and pipelines.

Malicious package

node-path-addonnpm

node-path-addon is a confirmed malicious npm package (MAL-2026-10463) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.7, 1.0.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-path-addon (npm)

MAL-2026-10463

Immediate action

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

npm uninstall node-path-addon

What this malware does

node-path-addon presents itself as an extension of the Node.js built-in 'path' module. Its main entry (path.js) delegates by executing require('path-addon-extend') at module load, and package.json declares that dependency at wildcard version '*', so importing node-path-addon unconditionally resolves and executes the latest published version of path-addon-extend — whose contents are controlled by whoever owns that separate npm name. The shim also imports the 'https' module without using it, and the README instructs users to run 'npm install --save path-addon' rather than the actual published name 'node-path-addon', a naming mismatch consistent with typosquat lure behavior. The package itself contains no direct exfiltration or shell execution, but the wildcard-pinned require on import is a loader that grants an external, mutable dependency arbitrary code execution in the consumer's process on every install and require.

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

2 flagged

1.0.71.0.8

Indicators of compromise (SHA-256)

5dbc52a88818bccd5602eb556ea4bf089dac66c44a2bb1ecbd6fddd6723e9d1d

6b9d31ad60810b0ec7e48b0a716595cc64021531ef9711fab0dd6b7ccfb2cd07

11641d204c4db5042d4e4ce53ad30e2e4afd31f0a439dcc2470d2776048f6803

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 node-path-addon (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-path-addon across your stack and pipelines.
If you installed it — respond
node-path-addon 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 node-path-addon 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 node-path-addon 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. node-path-addon on npm has been identified as a malicious package (versions 1.0.7, 1.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010269GHSA-87rj-7vj7-vxggIN-MAL-2026-010630

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks node-path-addon-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

Explore

All malware advisories How O3 detects malware Vulnerability database