rio-design-tokens

rio-design-tokens@99.99.100 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. ## Source: ghsa-malware (f953c7dfe25e2d7da488167fee4e47d465f58bb2e45a0e52ccdba8f0ae267109) 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. ## Source: ossf-package-analysis (e83e18c7c88cb4c0e488342a49e4d0733087fa7e7ea7e833f1fbb6e8fbf5a35e) 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.