Which versions of @testcarrot/supply1 are malicious?

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

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

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

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

Yes — @testcarrot/supply1 is associated with the GHSA-5g39-q48c-37w6, RLMA-2025-05264, RLUA-2025-05667 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/supply1 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/supply1 (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @testcarrot/supply1 across your stack and pipelines.

Malicious package

@testcarrot/supply1npm

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

Malicious code in @testcarrot/supply1 (npm)

MAL-2025-48095

Immediate action

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

npm uninstall @testcarrot/supply1

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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

517d985985f415a1c4c91f10bdfc1757c72f7331c1f00d61ef96d902603783e1

7066103052f34ca2e4311fb1e5a332d07d10cc5d11211208c63ff92f6e18d71a

18dae0d074890874c2fa2cb80bd0c5a926b0c0367de2cad1d1bc743920e62979

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

Campaign

GHSA-5g39-q48c-37w6RLMA-2025-05264RLUA-2025-05667

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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