@shiftmarkets/shift-exchange-rootnpm
@shiftmarkets/shift-exchange-root is a confirmed malicious npm package (MAL-2026-12509) 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 @shiftmarkets/shift-exchange-root (npm)
What this malware does
On npm install, the package's postinstall hook (scripts.postinstall: 'node dist/recon.js || true') automatically runs dist/recon.js, which collects the installer's hostname, username, SUDO_USER, home directory, current working directory, internal IPv4 addresses for each network interface, DNS domain (via execSync of dnsdomainname), the full sorted list of process.env variable names, CI indicators, and the npm user-agent/cache, and POSTs this JSON payload to http://138.68.108.20:80/cb over cleartext HTTP. The env-var name list is additionally filtered by a credential regex (AWS|GCP|GOOGLE|AZURE|NPM|NODE_AUTH|DOCKER|KUBE|VAULT|TOKEN|SECRET|KEY|PASS|CRED|GITHUB|GITLAB|SSH) and shipped as a separate credential-shaped-name inventory. The destination is a bare IP unaffiliated with the @shiftmarkets scope's publisher, contacted over plain HTTP. The package's main entry (dist/index.js) exports only trivial math helpers (sum/subtract/multiply/divide) that do not match the @shiftmarkets/shift-exchange-root name, and a header comment in the recon script labels the collection as 'NON-SENSITIVE telemetry only... env var NAMES (never values)' — a cover story that contradicts the actual collection of host identity, internal network topology, sudo user, and credential-shaped env key inventory.
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 @shiftmarkets/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 @shiftmarkets/shift-exchange-root across your stack and pipelines.
If you installed it — respond
@shiftmarkets/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 @shiftmarkets/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 @shiftmarkets/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 @shiftmarkets/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.