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

@nxt-costco-com/forge-design-tokensnpm

Malicious code in @nxt-costco-com/forge-design-tokens (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1632
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @nxt-costco-com/forge-design-tokens

What this malware does

The package @nxt-costco-com/forge-design-tokens was found to contain malicious code.

Malicious versions

1 flagged
9.9.9

Indicators of compromise (SHA-256)

980f1641d88130fe59696711cfd89252b0027134f1f8ca135dea5409307c6651
86e4556dfaa2a30079bf31edd7c9a378deacc22b763f547a4b825d57945debef

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nxt-costco-com/forge-design-tokens (version 9.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nxt-costco-com/forge-design-tokens across your stack and pipelines.

  2. If you installed it — respond

    @nxt-costco-com/forge-design-tokens is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @nxt-costco-com/forge-design-tokens 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 @nxt-costco-com/forge-design-tokens 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. @nxt-costco-com/forge-design-tokens on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01040

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @nxt-costco-com/forge-design-tokens-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

@nxt-costco-com/forge-design-tokens (npm) malicious package — MAL-2026-1632 | O3 Security