Which versions of looopiw are malicious?

The following PyPI versions of looopiw are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate looopiw if I installed it?

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

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

Yes — looopiw is associated with the 2026-04-sher-net 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 looopiw across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for looopiw (version 0.0.1).

Malicious package

looopiwPyPI

Advisory published Apr 17, 2026Updated Apr 17, 2026

looopiw is a confirmed malicious PyPI package (MAL-2026-2842) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in looopiw (PyPI)

MAL-2026-2842

Immediate action

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

pip uninstall looopiw

What this malware does

Starting the module activates a hardcoded telegram bot allowing remote code execution, data exfiltration, collecting webcam photos, clipboard data, etc.

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

Campaign: 2026-04-sher-net

Reasons (based on the campaign):

The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
rat
spyware-like

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9d2af7de30ed37363dcd3ac8e41e0ff2987d97ec742dd973a2f95158c6f0f185

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for looopiw (version 0.0.1).
If you installed it — respond
looopiw 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 looopiw 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. looopiw on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-sher-net

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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