Which versions of shift-sdk-v5 are malicious?

The following npm versions of shift-sdk-v5 are flagged malicious: 5.0.1. Treat any of these as compromised.

How do I remediate shift-sdk-v5 if I installed it?

shift-sdk-v5 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.

I already installed shift-sdk-v5 — how do I know if it already compromised me?

If shift-sdk-v5 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.

Is shift-sdk-v5 part of a known attack campaign?

Yes — shift-sdk-v5 is associated with the IN-MAL-2026-014826 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find shift-sdk-v5 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shift-sdk-v5 (version 5.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shift-sdk-v5 across your stack and pipelines.

Malicious package

shift-sdk-v5npm

shift-sdk-v5 is a confirmed malicious npm package (MAL-2026-12436) that steals credentials and exfiltrates sensitive data (malicious version 5.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in shift-sdk-v5 (npm)

MAL-2026-12436

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall shift-sdk-v5

What this malware does

[email protected] registers a postinstall script that runs dist/recon.js on npm install. The script collects hostname, username, SUDO_USER, home directory, working directory, internal network interface addresses, DNS domain (via dnsdomainname), CI provider indicators, the full list of environment variable names, and a filtered subset of environment variable names matching AWS, GCP, AZURE, NPM, TOKEN, SECRET, KEY, PASS, CRED, GITHUB, GITLAB, and SSH patterns. The collected data is POSTed over plain HTTP to the hardcoded bare IP 138.68.108.20 at path /cb. The package's main file self-identifies as @shiftforex/shift-sdk-v4 — trading API client (scoped build) while being published unscoped as shift-sdk-v5, impersonating the legitimate scoped SDK to attract installs. A NON-SENSITIVE telemetry comment accompanies code that explicitly enumerates sudo state, internal IPs, CI context, and credential-shaped env var names — pre-attack host and credential-surface fingerprinting against installer/CI environments.

Malicious versions

1 flagged

5.0.1

Indicators of compromise (SHA-256)

2aca555e012d36b30d9ffe3d0f8acdca7ba67298a87ea02ea9d32731e8f2a748

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for shift-sdk-v5 (version 5.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shift-sdk-v5 across your stack and pipelines.
If you installed it — respond
shift-sdk-v5 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 shift-sdk-v5 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 shift-sdk-v5 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. shift-sdk-v5 on npm has been identified as a malicious package (version 5.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014826

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks shift-sdk-v5-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database