Which versions of testhaus are malicious?

The following npm versions of testhaus are flagged malicious: 99.9.8. Treat any of these as compromised.

How do I remediate testhaus if I installed it?

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

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

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

Search your lockfiles and build artifacts for testhaus (version 99.9.8).

Malicious package

testhausnpm

Advisory published Dec 1, 2025Updated Dec 24, 2025

testhaus is a confirmed malicious npm package (MAL-2025-191504) that executes malicious code on install (malicious version 99.9.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testhaus (npm)

MAL-2025-191504

Immediate action

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

npm uninstall testhaus

What this malware does

The package testhaus was found to contain malicious code.

Malicious versions

1 flagged

99.9.8

Indicators of compromise (SHA-256)

b9f0d8de5427f60c269fe53d3a876a67c03dc5c393599a5ca2b35d538fce9c3a

b1dcc09c4d9b29cf81e2bb408ad8b84712700dc220b0608a140c52b8c9e8fd9a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06517

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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