Which versions of apachelicense are malicious?

The following PyPI versions of apachelicense are flagged malicious: 0.1a1. Treat any of these as compromised.

How do I remediate apachelicense if I installed it?

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

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

Yes — apachelicense is associated with the 2026-03-license-utils-kit 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 apachelicense 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 apachelicense (version 0.1a1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging apachelicense across your stack and pipelines.

Malicious package

apachelicensePyPI

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

MAL-2026-2119

Immediate action

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

pip uninstall apachelicense

What this malware does

Malicious clone of legitimate "license" package. When using the find_by_key function, the malicious code from strongly obfuscated files is loaded. It then at least collects data from cryptowallets and password managers and exfiltrate them to a hardcoded remote location.

Prior version 0.1b2, the malicious code was hosted externally and downloaded when triggered.

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

Campaign: 2026-03-license-utils-kit

Reasons (based on the campaign):

infostealer
obfuscation
crypto-related
action-hidden-in-lib-usage
exfiltration-credentials
clones-real-package

Malicious versions

1 flagged

0.1a1

Indicators of compromise (SHA-256)

9d96d45a87e117e72107d6d6dfbe8c4e94323323bc28ce9accd8ccba39a0a46c

8cb3d989a52bed71e3c0c981edf8cf82632c1fc6e3a0ea9c39f812e7967848a7

031eef30ab036b21c588c2057db7591f222501d19364223cc502b09d63811c6f

9860722a2a2aed103df780cb27b4c599301607ba92d3827a8e7fd1aabcd4fe55

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

Campaign

2026-03-license-utils-kit

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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