Which versions of testcatplzignore2 are malicious?

The following npm versions of testcatplzignore2 are flagged malicious: 1.0.15, 1.0.16, 1.0.17. Treat any of these as compromised.

How do I remediate testcatplzignore2 if I installed it?

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

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

Yes — testcatplzignore2 is associated with the GHSA-mxwq-qffg-76c4, RLMA-2025-05529, RLUA-2025-05967 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 testcatplzignore2 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 testcatplzignore2 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testcatplzignore2 across your stack and pipelines.

Malicious package

testcatplzignore2npm

testcatplzignore2 is a confirmed malicious npm package (MAL-2025-48016) that executes malicious code on install (malicious versions 1.0.15, 1.0.16, 1.0.17). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testcatplzignore2 (npm)

MAL-2025-48016

Immediate action

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

npm uninstall testcatplzignore2

What this malware does

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

3 flagged

1.0.151.0.161.0.17

Indicators of compromise (SHA-256)

2a8b1d8bd766d3c76c7e4ebb5e2f9226c1b7ae4cfe0c8ffcfd41ec2ad8916520

bf961eb5934af5b7ed44f28a7f4c7fb40289f1f09036dd63c31e74efe2af521c

85b87975742711f00f1bb611e00dc6b02c525c8cda891b01bc759074b48f4b64

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

Campaign

GHSA-mxwq-qffg-76c4RLMA-2025-05529RLUA-2025-05967

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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