Which versions of wbe3-py are malicious?

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

How do I remediate wbe3-py if I installed it?

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

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

Yes — wbe3-py is associated with the RLMA-2024-09494, funcaptcha-ru 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 wbe3-py 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 wbe3-py (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 wbe3-py across your stack and pipelines.

Malicious package

wbe3-pyPyPI

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

MAL-2024-10195

Immediate action

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

pip uninstall wbe3-py

What this malware does

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: funcaptcha-ru

Reasons (based on the campaign):

infostealer

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

282f55f997df4ed9eeb89f6cef38d27a86d6d60520a652b9ca81dadabceb455f

acd7d752ada1df8f3780e830eae8ae619b6383501dc67eb06a346b6bf43d3f32

a4d6bcb8e980e38ab05f8d8b34ffd4e6920e4a6c8fe5f1bd52bfe711178eadd5

4ff00f77ce8280bbd311e852a20c92cb109d642b99ac246f4d36df0a5ad58d49

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 wbe3-py (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 wbe3-py across your stack and pipelines.
If you installed it — respond
wbe3-py 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 wbe3-py 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 wbe3-py 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. wbe3-py 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-2024-09494funcaptcha-ru

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks wbe3-py-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