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

rio-design-tokensnpm

rio-design-tokens is a confirmed malicious npm package (MAL-2026-6956) that steals credentials and exfiltrates sensitive data (malicious versions 99.99.99, 99.99.100). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rio-design-tokens (npm)

MAL-2026-6956
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rio-design-tokens

What this malware does

[email protected] is a dependency-confusion attack package. package.json declares preinstall: node index.js, so npm install auto-executes index.js, which harvests installer secrets and system data and POSTs them to an attacker-controlled oastify.com (Burp Collaborator) subdomain. Specifically, index.js collects os.hostname(), os.userInfo(), output of whoami/id/pwd (via execSync with curl and other commands), the contents of ~/.npmrc and ~/.yarnrc (which contain npm auth tokens), package-lock.json, yarn.lock, /etc/os-release, /etc/hosts, probes AWS IMDS, and reads a targeted env-var list including NPM_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, GITLAB_CI, and CODEARTIFACT_AUTH_TOKEN, then sends the aggregated payload via https.request(... POST) to 7v343wmb7yqwapwew87n2p4stjzbn4bt.oastify.com. The package's own metadata self-identifies as "Dependency Confusion POC" with version 99.99.100 and author "YourName" — the canonical shape of a public-registry package intended to shadow a private internal package name during resolution. Installing this package on a developer workstation, CI runner, or build system will exfiltrate registry auth tokens, cloud credentials, and CI secrets to an external collaborator host.

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 'rio-design-tokens' @ 99.99.100 (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

2 flagged
99.99.9999.99.100

Indicators of compromise (SHA-256)

e83e18c7c88cb4c0e488342a49e4d0733087fa7e7ea7e833f1fbb6e8fbf5a35e
f953c7dfe25e2d7da488167fee4e47d465f58bb2e45a0e52ccdba8f0ae267109
089069734ecd333dcf73b5549ed0aeb3dc6f1d882b2df64583e9bd6360d75c3d
ed72d8256a1831ef61f01d101c9b9de21db822516cb3b61d1fffd1ef7b3bb0c7

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 rio-design-tokens (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rio-design-tokens across your stack and pipelines.

  2. If you installed it — respond

    rio-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 rio-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 rio-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. rio-design-tokens on npm has been identified as a malicious package (versions 99.99.99, 99.99.100 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-53fp-9cgx-r5rgIN-MAL-2026-009241IN-MAL-2026-009108

References

Credits

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

Detect & block this

O3 blocks rio-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.

Explore