{"id":"MAL-2026-12315","revision":"fa1f5a18af1d4cf6a54d934ab9f8364b","records":[{"revision":"fa1f5a18af1d4cf6a54d934ab9f8364b","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-12315","aliases":[],"title":"Malicious code in @cryptosrvc/no-brainer-sdk (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (7955af180bb00f4f97b5dee0c7020f9e43f4c35aa84c5ef5446dd95646eb333b)\nOn 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.\n","state":0,"publishedAt":"2026-08-05T13:01:29+00:00","modifiedAt":"2026-08-05T13:35:08.3414506+00:00","affected":[{"ecosystem":"npm","name":"@cryptosrvc/no-brainer-sdk","ranges":[],"versions":["1.0.18"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@cryptosrvc/no-brainer-sdk/v/1.0.18"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-12315","license":"OSV · upstream source license applies","key":"osv:MAL-2026-12315","identifiers":["MAL-2026-12315"]},"retained":false,"historicalAffected":[]}],"coverage":[]}