@shiftmarkets/shift-sdk-v4npm
@shiftmarkets/shift-sdk-v4 is a confirmed malicious npm package (MAL-2026-12329) that steals credentials and exfiltrates sensitive data (malicious version 1.0.77). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @shiftmarkets/shift-sdk-v4 (npm)
What this malware does
The package declares a postinstall script node dist/recon.js that runs automatically on npm install. The script collects installer-side reconnaissance data — hostname, username, SUDO_USER, home directory, current working directory, all local IPv4 addresses (including internal interfaces), DNS domain (via dnsdomainname), CI-provider flags, the full sorted list of process.env variable names, and a filtered subset of environment variable names matching secret/credential regex patterns — and POSTs the JSON payload over plain HTTP to the hardcoded bare IPv4 endpoint http://138.68.108.20:80/cb. An in-file comment frames the beacon as 'NON-SENSITIVE telemetry', but the destination is a bare IP with no publisher affiliation and the payload includes internal network topology and credential-shaped env variable names. The package presents itself as a scoped Shift Forex build compatible with the public shift-sdk-v4 package and ships a minimal API-compatible stub in dist/index.js, consistent with a dependency-confusion lure against consumers who reference shift-sdk-v4 from an internal registry.
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-sdk-v4 (version 1.0.77). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @shiftmarkets/shift-sdk-v4 across your stack and pipelines.
If you installed it — respond
@shiftmarkets/shift-sdk-v4 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-sdk-v4 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-sdk-v4 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-sdk-v4-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.