Which versions of backwwi are malicious?

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

How do I remediate backwwi if I installed it?

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

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

Yes — backwwi is associated with the RLMA-2024-10979, 2024-11-backwwii, RLUA-2026-00134 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 backwwi 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 backwwi (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging backwwi across your stack and pipelines.

Malicious package

backwwiPyPI

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

MAL-2024-11534

Immediate action

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

pip uninstall backwwi

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)

5e751a3b11ab4cc563188a703192a7fb37bdd51a55c444700a4832b8f70640ca

cdad397596ab7452502fc6ec75fe96e5f653899f29cb723ef873965936a3484e

23f7db675ae2d9beeb90ac31070aeb2a2ca9902ae348f92b30f828c200cc3441

80f061d5d0281995d6fabaf8ce68a7bfaa2ed0798b66241b4ebd22631adfe5ce

7525d1f4f2c2598cc983ea8f9e5303a3da72491c1cfa078ff0394e416c6388a5

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 backwwi (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging backwwi across your stack and pipelines.
If you installed it — respond
backwwi 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 backwwi 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 backwwi 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. backwwi 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

RLMA-2024-109792024-11-backwwiiRLUA-2026-00134

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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