What does the npmamzs malware do?

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

The following npm versions of npmamzs are flagged malicious: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4. Treat any of these as compromised.

How do I remediate npmamzs if I installed it?

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

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

Search your lockfiles and build artifacts for npmamzs (5 malicious versions).

Malicious package

npmamzsnpm

Advisory published Mar 28, 2026Updated Mar 31, 2026

npmamzs is a confirmed malicious npm package (MAL-2026-2275) that executes malicious code on install (malicious versions 1.1.0, 1.1.1, 1.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in npmamzs (npm)

MAL-2026-2275

Immediate action

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

npm uninstall npmamzs

What this malware does

The package npmamzs was found to contain malicious code.

The OpenSSF Package Analysis project identified 'npmamzs' @ 1.1.4 (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

5 flagged

1.1.01.1.11.1.21.1.31.1.4

Indicators of compromise (SHA-256)

f520e8fb348c5d8d4db0d95e952437b99aaf4c441436c46145f3bf64d59f1453

7ad3433c3c454343a65a76ac9ca5e161c3bff6ffba2c649d254004aba0084abc

65b6746b4927091d3d1827f9f705bd8c4b1cf8438da5200ffd95ed19a67f0702

1d2b15c6f825f71e19202129f46874419bcc99ad5ad818d225ae75a13f1b6c5f

d494475ee013b73bb0df9b1f0533b2f169fb6feff4b7c3c282c3629588be4e2d

25a8c88c6c60c588983806906169ffad0a2a863d45482ac8e2740f320f7cb2ea

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for npmamzs (5 malicious versions).
If you installed it — respond
Remove npmamzs 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 npmamzs 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. npmamzs on npm has been identified as a malicious package (versions 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4 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 npmamzs-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