Which versions of waseem4321 are malicious?

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

How do I remediate waseem4321 if I installed it?

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

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

Yes — waseem4321 is associated with the RLMA-2025-01256, GENERIC-standard-pypi-install-pentest, RLUA-2026-00910 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 waseem4321 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 waseem4321 (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 waseem4321 across your stack and pipelines.

Malicious package

waseem4321PyPI

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

MAL-2025-2010

Immediate action

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

pip uninstall waseem4321

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)

925b461331958e22589a26ae9ad1336292c002b1f47e0197fed990c8185f7ce5

6c007ac1ed0418483867ab8d6538ad920672dfec8484701b6915f68d162fd440

0dcb404c741672d9f6880b0a41c2b45ed01d3e25e13b512c6d16a51b1899fcc7

64bd8fa63b5da2304780b03be65f2d3c21a624dbd315fd723b20c0eaddffb9c0

36e3ee72913cc4c6465a3b025dde7da40c2716a89382eb1641494c9c7da96375

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 waseem4321 (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 waseem4321 across your stack and pipelines.
If you installed it — respond
waseem4321 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 waseem4321 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 waseem4321 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. waseem4321 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-01256GENERIC-standard-pypi-install-pentestRLUA-2026-00910

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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