Which versions of testtestsharp are malicious?

The following npm versions of testtestsharp are flagged malicious: 0.34.5. Treat any of these as compromised.

How do I remediate testtestsharp if I installed it?

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

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

Yes — testtestsharp is associated with the GHSA-7g34-jxp7-g7r3, RLMA-2026-02049 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 testtestsharp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for testtestsharp (version 0.34.5).

Malicious package

testtestsharpnpm

Advisory published Mar 27, 2026Updated Apr 16, 2026

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

Malicious code in testtestsharp (npm)

MAL-2026-2251

Immediate action

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

npm uninstall testtestsharp

What this malware does

The package testtestsharp was found to contain malicious code.

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

0.34.5

Indicators of compromise (SHA-256)

a60a14bbd40854d1657cc0976cb3cd48a5cf74e75ed0be4db3d263ccbb782392

d76d90d4c0413d045792eb3caf31ab7aa89d88854a891b2327107997b39eef91

f7edcee3a8853979e8c7e7073e8d36da08067d6b1c56127ca28d68e966ba2c7b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for testtestsharp (version 0.34.5).
If you installed it — respond
Remove testtestsharp 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 testtestsharp 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. testtestsharp on npm has been identified as a malicious package (version 0.34.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7g34-jxp7-g7r3RLMA-2026-02049

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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