What does the alicenpmpackage13 malware do?

The package alicenpmpackage13 was found to contain malicious code. The OpenSSF Package Analysis project identified 'alicenpmpackage13' @ 9.7.11 (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 alicenpmpackage13 are malicious?

The following npm versions of alicenpmpackage13 are flagged malicious: 9.7.11. Treat any of these as compromised.

How do I remediate alicenpmpackage13 if I installed it?

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

If alicenpmpackage13 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 alicenpmpackage13 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for alicenpmpackage13 (version 9.7.11).

Malicious package

alicenpmpackage13npm

Advisory published Nov 19, 2025Updated Nov 24, 2025

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

Malicious code in alicenpmpackage13 (npm)

MAL-2025-190577

Immediate action

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

npm uninstall alicenpmpackage13

What this malware does

The package alicenpmpackage13 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'alicenpmpackage13' @ 9.7.11 (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.7.11

Indicators of compromise (SHA-256)

0cc228d0f305f22b2323c3c546470b1b4630ef8cff3778281e0776040d16efc2

c4183158dd9ab68784bc126821795cf166b7f2c828d67f46efc533d3859a4342

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for alicenpmpackage13 (version 9.7.11).
If you installed it — respond
Remove alicenpmpackage13 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 alicenpmpackage13 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. alicenpmpackage13 on npm has been identified as a malicious package (version 9.7.11 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 alicenpmpackage13-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