Which versions of path-addon-extend are malicious?

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

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

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

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

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

Malicious package

path-addon-extendnpm

Malicious code in path-addon-extend (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10420

Immediate action

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

npm uninstall path-addon-extend

What this malware does

path-addon-extend presents itself as a copy of Node's built-in path module. On module load, path.js issues an HTTPS GET to a base64-obscured URL that decodes to https://json.extendsclass.com/bin/567893d4e220 and passes the response's .content field directly to eval(). The destination is a public JSON-bin service whose contents can be mutated at any time by the publisher (or anyone in possession of the bin token), giving arbitrary remote code execution in any process that requires this package. The endpoint is stored as a base64 literal decoded via atob(...) at call time rather than as a plain string, concealing the destination in a package that otherwise mirrors the Node core path module.

Malicious versions

2 flagged

1.0.71.0.8

Indicators of compromise (SHA-256)

60906e93ae3b838d259b7ebdb6874779e3c2f83d652488cf3b0039a4844a4db3

b383636076e2701a372675c281ee82463d97529ed7d8db027276aa8a8b68b966

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 path-addon-extend (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging path-addon-extend across your stack and pipelines.
If you installed it — respond
path-addon-extend 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 path-addon-extend 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 path-addon-extend 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. path-addon-extend 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-009851IN-MAL-2026-009850

References

Credits

Amazon Inspector · finder

Detect & block this

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