Which versions of catwrestlinghuman are malicious?

The following npm versions of catwrestlinghuman are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate catwrestlinghuman if I installed it?

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

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

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

Malicious package

catwrestlinghumannpm

catwrestlinghuman is a confirmed malicious npm package (MAL-2026-16328) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in catwrestlinghuman (npm)

MAL-2026-16328

Immediate action

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

npm uninstall catwrestlinghuman

What this malware does

package.json declares a postinstall hook node index.js. index.js is a 111KB blob composed exclusively of the JSFuck character set ([]()!+), which decodes at runtime via Function(<decoded string>)() to arbitrary JavaScript. A sibling file extension.js (126KB) uses the same JSFuck encoding, indicating a multi-stage opaque payload. The package has no description, no author, and no dependencies, and ships no readable source — the JSFuck encoding is exclusively an obfuscation technique used to hide executable code from scanners and reviewers. Installing this package causes automatic execution of the opaque payload on the installer's machine during npm install.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

6c4045339387526c5db90832687d1691c2caddba3b9cb05006022704bf094653

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

Campaign

IN-MAL-2026-020227

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks catwrestlinghuman-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

Explore

All malware advisories How O3 detects malware Vulnerability database