Which versions of confirmedbywaseem are malicious?

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

How do I remediate confirmedbywaseem if I installed it?

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

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

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

Malicious package

confirmedbywaseemPyPI

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

MAL-2025-911

Immediate action

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

pip uninstall confirmedbywaseem

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)

b408e39e1208b43fa5bbd09e53d0a3075af81ca870f62d3a4f8f7c5aff7f1688

68c744c70d22d897999d98639a8832b7c96329851211d4fc67b21b762abce26b

b73d94e4cfd78613adcbcaba3b19fdfbafc44593382f6ab4b9238b263fd30403

fdbaa6dd50881789e896cd08d0ca8e05fd7978e9055303a2f6df6a2a54b2a148

1b01a7908b6fb7d3d60d26c457d8643b8c3ca32f91fe62f836a548e7ee5fc087

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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