Which versions of backwwii are malicious?

The following PyPI versions of backwwii are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate backwwii if I installed it?

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

If backwwii was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is backwwii part of a known attack campaign?

Yes — backwwii is associated with the 2024-11-backwwii 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 backwwii across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for backwwii (version 0.1.0).

Malicious package

backwwiiPyPI

Advisory published Nov 12, 2024Updated Dec 12, 2025

backwwii is a confirmed malicious PyPI package (MAL-2024-12212) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in backwwii (PyPI)

MAL-2024-12212

Immediate action

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

pip uninstall backwwii

What this malware does

When importing the module, the obfuscated code downloads and runs a remote executable

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

Campaign: 2024-11-backwwii

Reasons (based on the campaign):

Downloads and executes a remote executable.
clones-real-package

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

309b793eea00b74f13d9fe5015483ed73a2c2b807acb98a589df05c792232825

cf5e7427061483e779c53f125b5792b2e650261bcdca0a9f4d90e9ca883c04d0

24a7fb4f4004bf9dc5cc3747a1eb878bfb45fa5f22f1e6f6b1a39624bdd03018

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for backwwii (version 0.1.0).
If you installed it — respond
backwwii 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 backwwii was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. backwwii on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-backwwii

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database