Which versions of wasig4321 are malicious?

The following PyPI versions of wasig4321 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate wasig4321 if I installed it?

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

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

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

Malicious package

wasig4321PyPI

Malicious code in wasig4321 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2011

Immediate action

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

pip uninstall wasig4321

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

1.0.0

Indicators of compromise (SHA-256)

ba036d1063cdd7c1ccd46dbf29efc6ab26d8933a115d8b358d60e2664e687eaa

b4d7b6b826e76ea17bc47909b8d43d343f207b30c628ada717c7326e94a621df

a95ae4f8a374465b956acda50b3860ce59e7784cfa0ecb5c2b48157fcc41d326

d1814aebd87e9965cf29ad11b6c85143cb74b34fd32658a52e9c70dd600ffe3b

6e407f03923be816f5a573fade28afa89f59c15f003c707064a72cf30c4a71ae

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

Campaign

RLMA-2025-01257GENERIC-standard-pypi-install-pentestRLUA-2026-00912

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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