Which versions of import-license-checker are malicious?

The following PyPI versions of import-license-checker are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate import-license-checker if I installed it?

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

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

Yes — import-license-checker is associated with the 2025-08-import-license-checker 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 import-license-checker 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 import-license-checker (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging import-license-checker across your stack and pipelines.

Malicious package

import-license-checkerPyPI

Malicious code in import-license-checker (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191765

Immediate action

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

pip uninstall import-license-checker

What this malware does

Package exfiltrates content of .env files to a remote target

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

Campaign: 2025-08-import-license-checker

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.

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

43f202ff0da53abc63a19cc284b63f1016ef13e5eb1d8cd5a9290c8f596ff520

c41ca4c8119fa20f7f5915b34de59f879b77fedf237cbbf5a69e46ddbeded428

39b7f1ee5d5030eedaadae9271a89ba1f37e1a9ed27de272ba80594ce4017ca9

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 import-license-checker (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging import-license-checker across your stack and pipelines.
If you installed it — respond
import-license-checker 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 import-license-checker 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 import-license-checker 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. import-license-checker on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-08-import-license-checker

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks import-license-checker-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