Which versions of js-nodecat are malicious?

The following npm versions of js-nodecat are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate js-nodecat if I installed it?

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

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

Yes — js-nodecat is associated with the GHSA-m3qj-483q-v65m, RLMA-2026-01363, RLUA-2026-01771 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 js-nodecat 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 js-nodecat (version 1.0.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging js-nodecat across your stack and pipelines.

Malicious package

js-nodecatnpm

Malicious code in js-nodecat (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1116

Immediate action

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

npm uninstall js-nodecat

What this malware does

The package js-nodecat 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.

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

1f19647e158d2037b4d4d79e931211560b4b7c72e33defc94f8c4552775f601b

38c204576b5f5aefba60246b88360a50e23f958c2023883088bdf6a151ccb7d9

112222e8c04c33fcf0ec84f15a5fcb4e1a05fdfe0ebed974084a9012396d11c4

51186f0e278592c64bf71d9291884a5013c5ea66a2985ebf96aa08bd3f21efce

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

Campaign

GHSA-m3qj-483q-v65mRLMA-2026-01363RLUA-2026-01771

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks js-nodecat-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