Which versions of normalize-path-seq are malicious?

The following npm versions of normalize-path-seq are flagged malicious: 3.8.9. Treat any of these as compromised.

How do I remediate normalize-path-seq if I installed it?

normalize-path-seq is a typosquat — you almost certainly intended a legitimately-named package. Remove normalize-path-seq, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed normalize-path-seq — how do I know if it already compromised me?

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

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

Malicious package

normalize-path-seqnpm

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

MAL-2026-4622

Immediate action

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

npm uninstall normalize-path-seq

What this malware does

On require, index.js invokes initPlugin() at the module top level, which performs an HTTPS GET to https://jsonkeeper.com/b/VL3WY, parses the response JSON, and passes the 'cookie' field to new Function.constructor('require', body)(require). This compiles attacker-controlled JavaScript and invokes it with the installer's require, granting arbitrary code execution with full Node.js privileges on every import. The payload host (jsonkeeper.com) is an anonymous paste service whose contents are mutable, so the executed code can change at any time without a package update. The package is also a typosquat of the widely-installed normalize-path: it impersonates the original author (Jon Schlinkert) in package.json and mimics the normalizePath API surface to lure consumers who mistype the dependency name.

Malicious versions

1 flagged

3.8.9

Indicators of compromise (SHA-256)

048493f47bc6a8b0a61c93d14a9bfbbe5edd77baff2d2423870e3cc8b7099b0a

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for normalize-path-seq (version 3.8.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging normalize-path-seq across your stack and pipelines.
If you installed it — respond
normalize-path-seq is a typosquat — you almost certainly intended a legitimately-named package. Remove normalize-path-seq, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If normalize-path-seq 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 normalize-path-seq 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. normalize-path-seq on npm has been identified as a malicious package (version 3.8.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004738

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks normalize-path-seq-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