Which versions of shiftmarkets-sdk are malicious?

The following npm versions of shiftmarkets-sdk are flagged malicious: 2.1.0. Treat any of these as compromised.

How do I remediate shiftmarkets-sdk if I installed it?

shiftmarkets-sdk 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 shiftmarkets-sdk — how do I know if it already compromised me?

If shiftmarkets-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is shiftmarkets-sdk part of a known attack campaign?

Yes — shiftmarkets-sdk is associated with the IN-MAL-2026-014929 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 shiftmarkets-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for shiftmarkets-sdk (version 2.1.0).

Malicious package

shiftmarkets-sdknpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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

Malicious code in shiftmarkets-sdk (npm)

MAL-2026-12803

Immediate action

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

npm uninstall shiftmarkets-sdk

What this malware does

The package declares a postinstall hook that runs dist/recon.js on npm install. The script collects hostname, username, sudo_user, homedir, cwd, internal IPv4 addresses of all network interfaces, DNS domain, CI indicators, and the full list of process.env variable names — including a subset filtered against a regex matching AWS/GCP/AZURE/NPM/TOKEN/SECRET/KEY/PASS/CRED/GITHUB/SSH keywords — and POSTs the JSON payload over plain HTTP to http://138.68.108.20/cb, a hardcoded bare IP unrelated to the package's stated SDK purpose. A docstring header labels the collection as 'NON-SENSITIVE telemetry only' while the code simultaneously enumerates and filters environment variable names for credential-shaped keywords, indicating deliberate mislabeling of pre-attack reconnaissance as benign telemetry.

Malicious versions

1 flagged

2.1.0

Indicators of compromise (SHA-256)

b1628a8b4e8b6c4c117f2a38f7d69664950c1d5758772c64c2225f296f681c29

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for shiftmarkets-sdk (version 2.1.0).
If you installed it — respond
shiftmarkets-sdk 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-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-014929

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks shiftmarkets-sdk-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