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