Which versions of nintendo-test are malicious?

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

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

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

If nintendo-test 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.

Is nintendo-test part of a known attack campaign?

Yes — nintendo-test is associated with the RLMA-2025-06402 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 nintendo-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nintendo-test (version 1.0.0).

Malicious package

nintendo-testnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

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

Malicious code in nintendo-test (npm)

MAL-2025-192823

Immediate action

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

npm uninstall nintendo-test

What this malware does

The package nintendo-test was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7758932966558f65dcb8d16d04c78742413c9e072c6c3f75e7419b4c1e9b254d

cda34da72431c60b59efa32942146b3a3608477e9eead83ede6f5bb662ed82a0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nintendo-test (version 1.0.0).
If you installed it — respond
Remove nintendo-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 nintendo-test 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. nintendo-test on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06402

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nintendo-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