Which versions of lwplugin are malicious?

The following PyPI versions of lwplugin are flagged malicious: 0.0.5. Treat any of these as compromised.

How do I remediate lwplugin if I installed it?

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

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

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

Search your lockfiles and build artifacts for lwplugin (version 0.0.5).

Malicious package

lwpluginPyPI

Advisory published Oct 14, 2024Updated Dec 12, 2025

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

Malicious code in lwplugin (PyPI)

MAL-2024-12301

Immediate action

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

pip uninstall lwplugin

What this malware does

The attached DLL is infected with a very high detection rate

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

Campaign: 2024-10-old-lwplugin

Reasons (based on the campaign):

other

Malicious versions

1 flagged

0.0.5

Indicators of compromise (SHA-256)

b3dc7e66e833135fe0bc581d2880bb8347f1334d9d62fb9a064118c8bf5e40a4

c6d463791b2f4dc4cdb8a0b3961dbb9b956fc3f0e0ad974fc407211ae9d2e3a8

e8fce70e75b5d8eeba8e1236a86625fbd9df074545d305d2122549a4b3c7faf5

Detection & response playbook

Credential / info stealer

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

Campaign

2024-10-old-lwplugin

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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