{"id":"MAL-2026-13211","revision":"383f4643b4a54ec3ab566c2e45841d77","records":[{"revision":"383f4643b4a54ec3ab566c2e45841d77","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13211","aliases":[],"title":"Malicious code in @zzzcrypto/bitcoin-lib (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (f9d633d3efb27db376be57d77ebbd808db458d088503adebe2f7ad7501281dd1)\nOn require(), index.js serializes process.env together with hostname, username, homedir, platform, cwd, and a timestamp, base64-encodes the JSON, and sends it via HTTPS GET to api.telegram.org using a hardcoded bot token and chat_id. A tmp flag file gates re-execution to reduce noise. The package name @zzzcrypto/bitcoin-lib and its README present it as a drop-in for bitcoinjs-lib, and the code attempts require('bitcoinjs-lib') to transparently proxy the real library's API when present so callers observe normal behavior; the internal identifier in the exfil payload is @wethenorth12/bitcoin-lib, and identifier names in the harvester are scrambled (kffr, xqyv, qzph, _h). Environment variables in developer and CI processes routinely contain credentials, API tokens, and cloud keys, so this constitutes credential and host-identity theft against any process that imports the package.\n","state":0,"publishedAt":"2026-08-05T15:32:11+00:00","modifiedAt":"2026-08-05T16:50:16.3326242+00:00","affected":[{"ecosystem":"npm","name":"@zzzcrypto/bitcoin-lib","ranges":[],"versions":["6.1.7"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@zzzcrypto/bitcoin-lib/v/6.1.7"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13211","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13211","identifiers":["MAL-2026-13211"]},"retained":false,"historicalAffected":[]}],"coverage":[]}