Which versions of @louisle2/cortex-js are malicious?

The following npm versions of @louisle2/cortex-js are flagged malicious: 0.1.6. Treat any of these as compromised.

How do I remediate @louisle2/cortex-js if I installed it?

@louisle2/cortex-js 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 @louisle2/cortex-js — how do I know if it already compromised me?

If @louisle2/cortex-js 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 @louisle2/cortex-js part of a known attack campaign?

Yes — @louisle2/cortex-js is associated with the GHSA-jvhp-wxfw-v9j5 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 @louisle2/cortex-js 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 @louisle2/cortex-js (version 0.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @louisle2/cortex-js across your stack and pipelines.

Malicious package

@louisle2/cortex-jsnpm

Malicious code in @louisle2/cortex-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190817

Immediate action

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

npm uninstall @louisle2/cortex-js

What this malware does

The package @louisle2/cortex-js was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.1.6

Indicators of compromise (SHA-256)

174ad745e5cf3348d3f49b8423ce849882002841a37af3fd4f27a749441336b9

c444e50876d5f75647d843c02c0b22a893e1129c31baca504e57985a07a2f5bb

9eaffc1a1b6b060c8a0670e7ce6ab022f2ed2fb5d109c8d5562f1c8da2b57d9e

9ffcd90455df34f4ee69297c6d6ebbaa1915b73d7b2ebcd810bd4097a11a69ab

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

Campaign

GHSA-jvhp-wxfw-v9j5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @louisle2/cortex-js-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