What does the alicenpmpackage1 malware do?

The package alicenpmpackage1 was found to contain malicious code. The OpenSSF Package Analysis project identified 'alicenpmpackage1' @ 9.9.10 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of alicenpmpackage1 are malicious?

The following npm versions of alicenpmpackage1 are flagged malicious: 9.9.10. Treat any of these as compromised.

How do I remediate alicenpmpackage1 if I installed it?

Remove alicenpmpackage1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed alicenpmpackage1 — how do I know if it already compromised me?

If alicenpmpackage1 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.

How do I find alicenpmpackage1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for alicenpmpackage1 (version 9.9.10).

Malicious package

alicenpmpackage1npm

Advisory published Nov 19, 2025Updated Nov 24, 2025

alicenpmpackage1 is a confirmed malicious npm package (MAL-2025-190576) that executes malicious code on install (malicious version 9.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in alicenpmpackage1 (npm)

MAL-2025-190576

Immediate action

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

npm uninstall alicenpmpackage1

What this malware does

The package alicenpmpackage1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'alicenpmpackage1' @ 9.9.10 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

9.9.10

Indicators of compromise (SHA-256)

87f288f60579766c600e6528a38e357035269fbbbf2c4f57d64f44187fbfde54

cc6f807461a8da92854705819f1e63af5d1951c52d255a565e6d70c4b5a21fd3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for alicenpmpackage1 (version 9.9.10).
If you installed it — respond
Remove alicenpmpackage1 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If alicenpmpackage1 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. alicenpmpackage1 on npm has been identified as a malicious package (version 9.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks alicenpmpackage1-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database