What does the amazon-test malware do?

The OpenSSF Package Analysis project identified 'amazon-test' @ 1.0.0 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of amazon-test are malicious?

The following npm versions of amazon-test are flagged malicious: 1.0.0, 999.9.9. Treat any of these as compromised.

How do I remediate amazon-test if I installed it?

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

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

Yes — amazon-test is associated with the RLMA-2025-00620, RLUA-2025-06057 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 amazon-test 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 amazon-test (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging amazon-test across your stack and pipelines.

Malicious package

amazon-testnpm

amazon-test is a confirmed malicious npm package (MAL-2025-1721) that executes malicious code on install (malicious versions 1.0.0, 999.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in amazon-test (npm)

MAL-2025-1721

Immediate action

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

npm uninstall amazon-test

What this malware does

The OpenSSF Package Analysis project identified 'amazon-test' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

1.0.0999.9.9

Indicators of compromise (SHA-256)

12a25b9609c05e7a20a3b69216d641abfabd917506f23b2b9325b54b50868485

7e065ee96bedcccbc1d717b33f9111467a598d6dd2b02fe1fdc4447ffee42a2f

699f1b1cb1508055b5389ad61de59ad470d170fab9f628abc648c5f30f6a245e

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for amazon-test (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging amazon-test across your stack and pipelines.
If you installed it — respond
Remove amazon-test 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 amazon-test 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 amazon-test 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. amazon-test on npm has been identified as a malicious package (versions 1.0.0, 999.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-00620RLUA-2025-06057

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks amazon-test-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