Which versions of lightsequ are malicious?

The following PyPI versions of lightsequ are flagged malicious: 98.7, 99.7. Treat any of these as compromised.

How do I remediate lightsequ if I installed it?

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

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

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

Search your lockfiles and build artifacts for lightsequ (2 malicious versions).

Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →

Malicious package

lightsequPyPI

Advisory published Nov 5, 2024Updated Dec 12, 2025

lightsequ is a confirmed malicious PyPI package (MAL-2024-10360) that steals credentials and exfiltrates sensitive data (malicious versions 98.7, 99.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lightsequ (PyPI)

MAL-2024-10360

Immediate action

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

pip uninstall lightsequ

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'lightsequ' @ 99.7 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

98.799.7

Indicators of compromise (SHA-256)

a4c4b37a0d225964d4bc4e2c4047d3b2625aac7653c21c4da48ac827c2ddac4e

834311eb84b4aa9f5bad2669b380ecac9a15fc298d228d09cfa1d81463165cc6

982a9ec66c32a78f5829a04aa08e2f9d29f03f317b6a69b6ae0cc1e2d8b02c17

cbe77ff4fda3fb23b23ae7b589a1e23af5c57a06b70e46059d1c3b4ec6bac18b

Detection & response playbook

Credential / info stealer

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

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

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