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

@cryptosrvc/no-brainer-sdknpm

@cryptosrvc/no-brainer-sdk is a confirmed malicious npm package (MAL-2026-12315) 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 @cryptosrvc/no-brainer-sdk (npm)

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

What this malware does

On npm install, the package's postinstall script (dist/recon.js) collects installer-side host reconnaissance — hostname, username, SUDO_USER, home directory, cwd, network interfaces including internal IPs, DNS domain via dnsdomainname, and npm lifecycle context — and enumerates process.env, filtering the key names against a regex targeting AWS, GCP, AZURE, NPM, NODE_AUTH, DOCKER, KUBE, VAULT, TOKEN, SECRET, KEY, PASS, CRED, GITHUB, GITLAB, and SSH. Both the full env-name list and the credential-shaped subset are serialized and POSTed as JSON over plain HTTP to hardcoded bare IP 138.68.108.20:80/cb, with a npm-install-telemetry/1.0 User-Agent and an inline comment framing the payload as 'NON-SENSITIVE telemetry only' despite including sudo_user, internal network layout, and credential env-var name inventory. Behavior fires automatically as a postinstall lifecycle hook.

Malicious versions

1 flagged
1.0.18

Indicators of compromise (SHA-256)

7955af180bb00f4f97b5dee0c7020f9e43f4c35aa84c5ef5446dd95646eb333b

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/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 @cryptosrvc/no-brainer-sdk across your stack and pipelines.

  2. If you installed it — respond

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@cryptosrvc/no-brainer-sdk (npm) malicious package — MAL-2026-12315 | O3 Security