Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@cryptosrvc/shift-sdk-v4npm

@cryptosrvc/shift-sdk-v4 is a confirmed malicious npm package (MAL-2026-12317) 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 @cryptosrvc/shift-sdk-v4 (npm)

MAL-2026-12317
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @cryptosrvc/shift-sdk-v4

What this malware does

package.json declares a postinstall script node dist/recon.js || true that runs automatically on npm install. dist/recon.js collects installer host identity (hostname, username, SUDO_USER, homedir, cwd, platform/arch/release, node version), all internal and external IPv4 addresses from every network interface, the DNS domain via dnsdomainname, CI-provider indicators, and the full list of process.env variable names with a subset matching AWS|NPM|TOKEN|SECRET|KEY|GITHUB|SSH flagged as secret-shaped. The data is POSTed as JSON over plain HTTP to the hardcoded bare IP http://138.68.108.20:80/cb with a 4-second timeout and errors silently swallowed to preserve install success. A source comment frames the behavior as 'NON-SENSITIVE telemetry only', contradicting the actual enumeration of sudo user, network topology, and env-var names. The destination is an unattributed DigitalOcean IP with no relationship to any legitimate SDK publisher.

Malicious versions

1 flagged
1.0.77

Indicators of compromise (SHA-256)

bbcb95c5f9f9305e86cbeb749787dc845933c6273e91ab2d69138dee6fc2900a

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @cryptosrvc/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 @cryptosrvc/shift-sdk-v4 across your stack and pipelines.

  2. If you installed it — respond

    @cryptosrvc/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.

  3. Did it already run?

    If @cryptosrvc/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.

  4. How O3 protects you

    O3 blocks @cryptosrvc/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

No. @cryptosrvc/shift-sdk-v4 on npm has been identified as a malicious package (version 1.0.77 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014851

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @cryptosrvc/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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@cryptosrvc/shift-sdk-v4 (npm) malicious package — MAL-2026-12317 | O3 Security