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

@shiftmarkets/no-brainer-sdknpm

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

Malicious code in @shiftmarkets/no-brainer-sdk (npm)

MAL-2026-12508
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @shiftmarkets/no-brainer-sdk

What this malware does

The package runs node dist/recon.js as a postinstall lifecycle script on every npm install. The script collects host reconnaissance from the installer machine — hostname, username, SUDO_USER, homedir, cwd, network interface addresses (including internal/private IPs), CI indicators, npm lifecycle metadata, and the full list of environment variable names — and additionally filters those names against a credential-focused regex (AWS, GCP, GOOGLE, AZURE, NPM, NODE_AUTH, DOCKER, KUBE, VAULT, TOKEN, SECRET, KEY, PASS, CRED, GITHUB, GITLAB, SSH) to produce a secretish_names list. The JSON payload is POSTed over plain HTTP to the hardcoded bare-IPv4 endpoint http://138.68.108.20:80/cb, which is not a Shift Markets domain. The code labels itself as 'NON-SENSITIVE telemetry' but the destination is an unrelated bare IP and the installer never opted in. Enumerating which cloud/CI secret names exist on the host maps the target's credential inventory for follow-up attacks.

Malicious versions

1 flagged
1.0.18

Indicators of compromise (SHA-256)

3149c40a7290d16b0247a1128a3e25ba1614e87e5c7261e486ce2e826ac66987

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 @shiftmarkets/no-brainer-sdk (version 1.0.18). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @shiftmarkets/no-brainer-sdk across your stack and pipelines.

  2. If you installed it — respond

    @shiftmarkets/no-brainer-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.

  3. Did it already run?

    If @shiftmarkets/no-brainer-sdk 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 @shiftmarkets/no-brainer-sdk 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. @shiftmarkets/no-brainer-sdk on npm has been identified as a malicious package (version 1.0.18 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014907

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @shiftmarkets/no-brainer-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.

Explore

@shiftmarkets/no-brainer-sdk (npm) malicious package — MAL-2026-12508 | O3 Security