Which versions of @cawraytestorg/packagetest2 are malicious?

The following npm versions of @cawraytestorg/packagetest2 are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate @cawraytestorg/packagetest2 if I installed it?

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

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

Yes — @cawraytestorg/packagetest2 is associated with the RLMA-2026-05840 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 @cawraytestorg/packagetest2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @cawraytestorg/packagetest2 (version 9.9.9).

Malicious package

@cawraytestorg/packagetest2npm

Advisory published Aug 24, 2026Updated Sep 1, 2026

@cawraytestorg/packagetest2 is a confirmed malicious npm package (MAL-2026-15680) that executes malicious code on install (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @cawraytestorg/packagetest2 (npm)

MAL-2026-15680

Immediate action

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

npm uninstall @cawraytestorg/packagetest2

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

2b77d9a990b369d77f8d0614cf80b99ed9bed1e82e685d02aae8aad65fd5bed3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05840

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @cawraytestorg/packagetest2-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