Which versions of lapnet are malicious?

The following PyPI versions of lapnet are flagged malicious: 99.6. Treat any of these as compromised.

How do I remediate lapnet if I installed it?

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

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

Yes — lapnet 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 lapnet across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lapnet (version 99.6).

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

Malicious package

lapnetPyPI

Advisory published Nov 6, 2024Updated Dec 12, 2025

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

Malicious code in lapnet (PyPI)

MAL-2024-10825

Immediate action

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

pip uninstall lapnet

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 'lapnet' @ 99.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.6

Indicators of compromise (SHA-256)

69ff02f232477086b1ae259795f5f1b70e930633613330e005b3984b79f8457b

c0fcb08c13bedf91cc56ceaac12a760284e953381e799fd3f1016d5b564b4751

307a1f48007c80dd0a32f9487bc91bd1d12602c53b4942e5826724e659929f44

d257ba6e07678a3c89d336f4f4bcd0ddfb8b3d2643ecf51a531970c847cd39af

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for lapnet (version 99.6).
If you installed it — respond
lapnet 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 lapnet 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. lapnet on PyPI has been identified as a malicious package (version 99.6 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 lapnet-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