Which versions of w722-poc are malicious?

The following PyPI versions of w722-poc are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate w722-poc if I installed it?

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

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

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

Malicious package

w722-pocPyPI

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

MAL-2025-1003

Immediate action

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

pip uninstall w722-poc

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

1 flagged

0.1

Indicators of compromise (SHA-256)

1936f12dd2812906f4b0200782b0169cd01e9a54ec0d3e3a551e162763580512

012dd3d349184489402a60cf280c95f9d43915c503409807671c911e463134b7

74cbe1029791e4751e8b8c53fda75aa07cd3a6ca974a239c87867db522c2ee8e

60a849d151dd0d27cc4cde83cbeefe2511656f990b8ad61062aecf3a3d45921c

2660f9ef8c887b58d8788568b17261d281633d5e6b90cba35ea93b8af74349f9

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

Campaign

RLMA-2025-00544GENERIC-standard-pypi-install-pentestRLUA-2026-00901

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks w722-poc-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