@cryptosrvc/shift-exchange-rootnpm
@cryptosrvc/shift-exchange-root is a confirmed malicious npm package (MAL-2026-12316) that steals credentials and exfiltrates sensitive data (malicious versions 1.9.9, 2.9.9, 3.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @cryptosrvc/shift-exchange-root (npm)
What this malware does
On npm install, the package runs dist/recon.js as a postinstall script that collects the installer's hostname, username, SUDO_USER, home directory, current working directory, all local network interface IPs (including internal addresses), DNS domain, the full list of environment variable names, a filtered subset of env var names matching credential keywords (AWS, GCP, AZURE, NPM, TOKEN, SECRET, KEY, PASS, GITHUB, SSH), and CI indicators, and POSTs the JSON payload over plain HTTP to the hardcoded DigitalOcean address 138.68.108.20:80/cb. The file's header comment labels the collection as 'NON-SENSITIVE telemetry only' and the outgoing User-Agent is 'npm-install-telemetry/1.0', while the package's declared main entry (dist/index.js) is a math-utility stub unrelated to any telemetry function. The scope @cryptosrvc/shift-exchange-root resembles the legitimate @shiftforex/shift-exchange-root, consistent with a dependency-confusion or typosquat lure. Host identity plus internal network topology plus enumerated credential-shaped env var names constitute reconnaissance data suitable for follow-on targeted attacks against the installing environment.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @cryptosrvc/shift-exchange-root (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @cryptosrvc/shift-exchange-root across your stack and pipelines.
If you installed it — respond
@cryptosrvc/shift-exchange-root 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.
Did it already run?
If @cryptosrvc/shift-exchange-root 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.
How O3 protects you
O3 blocks @cryptosrvc/shift-exchange-root 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @cryptosrvc/shift-exchange-root-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.