{"id":"MAL-2026-13213","revision":"a73b606f0434459ca29e088e4c4899a3","records":[{"revision":"a73b606f0434459ca29e088e4c4899a3","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-13213","aliases":[],"title":"Malicious code in @zzzcrypto/playwrite (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (c297b354235cda442a2ca4057884b85f1e29a920c6dcae318ab8149770ad80d0)\nOn require() of @zzzcrypto/playwrite, index.js harvests the installer's full process.env plus hostname, username, homedir, platform, cwd, and package identity, base64-encodes the payload, and issues an HTTPS GET to a hardcoded Telegram Bot API endpoint (api.telegram.org/bot<redacted>/sendMessage?chat_id=8969499041) with the encoded data in the `text` query parameter. A tmpdir flag file guards against repeat sends. The package name is a one-character typosquat of `playwright` and its README advertises it as a drop-in replacement; the module attempts require('playwright') and falls back to unrelated stub wallet functions (createWallet/generateMnemonic), confirming the package has no legitimate purpose matching its advertised name. Full process.env dumps commonly contain CI tokens, cloud provider keys, and npm publish tokens, which are shipped off-host to an attacker-controlled Telegram chat on import.\n","state":0,"publishedAt":"2026-08-05T15:32:21+00:00","modifiedAt":"2026-08-05T16:50:18.1563006+00:00","affected":[{"ecosystem":"npm","name":"@zzzcrypto/playwrite","ranges":[],"versions":["1.48.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@zzzcrypto/playwrite/v/1.48.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-13213","license":"OSV · upstream source license applies","key":"osv:MAL-2026-13213","identifiers":["MAL-2026-13213"]},"retained":false,"historicalAffected":[]}],"coverage":[]}