Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

nintendoamerica-ncomnpm

Malicious code in nintendoamerica-ncom (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2008
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall nintendoamerica-ncom

What this malware does

The package nintendoamerica-ncom was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified 'nintendoamerica-ncom' @ 99.0.16 (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

4 flagged
1.0.599.0.799.0.1699.0.19

Indicators of compromise (SHA-256)

7b638ac33d4412bfc3c7d3bc1d5f935f1966b743badfe353e134ff907d3e1b8f
e77b311f9b7e9e9303cab9b4b2a926d9dd50cbd5cc8196be52e888925f36bb89
404cf56f80c8532deb2b12f0dc7a884c5281aee45645a1450c9b2628326fd150
04dfed169f575f5274192d08a28c1df31c54b0ef0f28fba875021dd96db58599
6bd460f8f84945495991b78c3eaf7d639b5b9be34dbe78af64373c222e8cd245
3bcdc242782d57d92c749d378cb6ba01d5a6112c7cbabf280dd0072c51c1c566

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nintendoamerica-ncom (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nintendoamerica-ncom across your stack and pipelines.

  2. If you installed it — respond

    Remove nintendoamerica-ncom 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.

  3. Did it already run?

    If nintendoamerica-ncom 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.

  4. How O3 protects you

    O3 blocks nintendoamerica-ncom 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. nintendoamerica-ncom on npm has been identified as a malicious package (versions 1.0.5, 99.0.7, 99.0.16, 99.0.19 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j836-pcqv-w9c9

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks nintendoamerica-ncom-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.

nintendoamerica-ncom (npm) malicious package — MAL-2026-2008 | O3 Security