Which versions of licensemonitor are malicious?

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

How do I remediate licensemonitor if I installed it?

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

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

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

Malicious package

licensemonitorPyPI

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

MAL-2024-10826

Immediate action

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

pip uninstall licensemonitor

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 'licensemonitor' @ 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)

761ac6cb8b3ca1d6ffbcc427e91393f25f2a2971105e7fea6429073ac083eef6

42495af3f3f187b901b16e7bbe9ffbbdf6c0e8f02ac7723d587d89ecfa7d3fd5

6bf006c4d28ae3036555f2c7255de1d0f672d7992acb46f2a89b4068b86f8754

83696e3f0a2841d66b3bfd42c8c6147be9f85cb41fe16b54b519155f346341db

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