Which versions of petco-test are malicious?

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

How do I remediate petco-test if I installed it?

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

If petco-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is petco-test part of a known attack campaign?

Yes — petco-test is associated with the RLMA-2025-06447 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 petco-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for petco-test (version 1.0.0).

Malicious package

petco-testnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

petco-test is a confirmed malicious npm package (MAL-2025-192851) 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 petco-test (npm)

MAL-2025-192851

Immediate action

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

npm uninstall petco-test

What this malware does

The package petco-test was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a269df5857aed3ab26f6c0257dd72767ff990a79a5e0a938df8fa83a122c4501

196bf178785bd7d40b4330c618187893cdc8876d342d8eb9a81b104146552961

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for petco-test (version 1.0.0).
If you installed it — respond
Remove petco-test 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 petco-test was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. petco-test 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

RLMA-2025-06447

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks petco-test-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