Which versions of license-o-matic are malicious?

The following npm versions of license-o-matic are flagged malicious: 1.2.1, 1.2.2. Treat any of these as compromised.

How do I remediate license-o-matic if I installed it?

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

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

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

Malicious package

license-o-maticnpm

Malicious code in license-o-matic (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191123

Immediate action

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

npm uninstall license-o-matic

What this malware does

The package license-o-matic was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.2.11.2.2

Indicators of compromise (SHA-256)

49c52a247d555acb52bb022b38b85269d3d53c968f4702b205402846d92a18b2

b3fd129a621d2b0301bfbf34bd85c53356c530875a9934cf27d640358a20cd81

7ce44db24a3d6b239882af3df83b529d0110d58680c77d244af2553ac9436085

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

Campaign

GHSA-x23c-fr3f-x5gv

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks license-o-matic-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