Which versions of wr-test are malicious?

The following PyPI versions of wr-test are flagged malicious: 100.1337, 101.1337. Treat any of these as compromised.

How do I remediate wr-test if I installed it?

wr-test is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed wr-test — how do I know if it already compromised me?

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

Yes — wr-test is associated with the RLMA-2025-00549, GENERIC-standard-pypi-install-pentest, RLUA-2026-00935 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 wr-test 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 wr-test (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wr-test across your stack and pipelines.

Malicious package

wr-testPyPI

Malicious code in wr-test (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-1008

Immediate action

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

pip uninstall wr-test

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

100.1337101.1337

Indicators of compromise (SHA-256)

0f881f015eb09cdd8461fccdfca701638e1e39b121eb08d119c1b0a712965355

0226ba113a95eba5c5935a4c65548e0441a4ff9385d42362c54d871f397713fa

3e752a2e84135761f1cf5319ed23d3a78b994ea011df850c87938442ad249180

b13d01b97f0197912cf29a7d1f210944139caceda9baa44300aef27ed97d521e

4bc3598747ad0c008d3a5753e061b282d03f93c7969e144b1a8b1303f62fef97

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for wr-test (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging wr-test across your stack and pipelines.
If you installed it — respond
wr-test is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If wr-test 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 wr-test 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. wr-test on PyPI has been identified as a malicious package (versions 100.1337, 101.1337 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-00549GENERIC-standard-pypi-install-pentestRLUA-2026-00935

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks wr-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring