Which versions of @testcarrot/supply are malicious?

The following npm versions of @testcarrot/supply are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @testcarrot/supply if I installed it?

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

If @testcarrot/supply 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 @testcarrot/supply part of a known attack campaign?

Yes — @testcarrot/supply is associated with the GHSA-mhrx-j3w2-wvx4, RLMA-2025-05263, RLUA-2025-05666 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 @testcarrot/supply 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 @testcarrot/supply (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @testcarrot/supply across your stack and pipelines.

Malicious package

@testcarrot/supplynpm

@testcarrot/supply is a confirmed malicious npm package (MAL-2025-48094) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @testcarrot/supply (npm)

MAL-2025-48094

Immediate action

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

npm uninstall @testcarrot/supply

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

27e1f69fb6202f5542f7e1a2def95407b079bad5dd22d4ef58c3f243c794000d

844b74d8a09b36bfa2fcfe21556b44ca5bd4566300bc644f84b5ace70e25c7b3

b0fb059bcb32f3d5a78b0b08a6e094b4982483f278a75de8a28aed560b3a1765

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

Campaign

GHSA-mhrx-j3w2-wvx4RLMA-2025-05263RLUA-2025-05666

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @testcarrot/supply-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