Which versions of working_tests are malicious?

The following npm versions of working_tests are flagged malicious: 1.1.1. Treat any of these as compromised.

How do I remediate working_tests if I installed it?

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

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

Yes — working_tests is associated with the GHSA-m4m9-6qhv-prrh, RLMA-2025-05200, RLUA-2026-01652 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 working_tests 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 working_tests (version 1.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging working_tests across your stack and pipelines.

Malicious package

working_testsnpm

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

Malicious code in working_tests (npm)

MAL-2025-47362

Immediate action

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

npm uninstall working_tests

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.1.1

Indicators of compromise (SHA-256)

49c21a63c0a80ed6817e5b19617e29f869d463d77843ef462ec7f9f177abe0aa

6d04047f66346ce0af87bc17d38c8f080f50a1abb9c8710d0435f96a24520ff6

92c930ec5057d1acfea2355599508e22ee1b2e22bc2809c2ed2773920c94814a

0869f720048a868afb3cbdba298e3c54b71691351da30d40777652af8f18c45c

5ad7db9745c6e1393f7de07db937d8787ef481b8b62d874069b71d4e11bd14bb

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

Campaign

GHSA-m4m9-6qhv-prrhRLMA-2025-05200RLUA-2026-01652

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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