{"id":"MAL-2026-17179","revision":"e52c9c979c7a4e99a49fd4efc642508f","records":[{"revision":"e52c9c979c7a4e99a49fd4efc642508f","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-17179","aliases":[],"title":"Malicious code in wallet-connect-adapter (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (4135dd91724bdca6fc36f3a49906d219acc67afde7802cb1bd114d128984ca3d)\nThe package's postinstall hook runs `node./loader.js`, which base64-decodes an ~8 KB embedded blob, XOR-decrypts it with a hardcoded 32-byte key, and pipes the resulting bytes into a detached, window-hidden `python -c -` child process via stdin. The loader also silently `pip install`s `requests` if missing. The advertised library surface in `index.js` is an explicit stub whose `connect()` throws, and `package.json` restricts installation to `os: [\"win32\"]`, so the tarball has no functional wallet-adapter behavior — its only effect on install is to execute the obfuscated Python payload on a Windows developer's machine. The combination of a hidden opaque payload, XOR-obfuscated delivery, detached hidden Python execution at `npm install` time, an inert cover-story main module, and OS pinning to Windows is a targeted install-time dropper.\n","state":0,"publishedAt":"2026-09-25T02:38:56+00:00","modifiedAt":"2026-09-25T03:00:07.5340259+00:00","affected":[{"ecosystem":"npm","name":"wallet-connect-adapter","ranges":[],"versions":["1.4.2"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/wallet-connect-adapter/v/1.4.2"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-17179","license":"OSV · upstream source license applies","key":"osv:MAL-2026-17179","identifiers":["MAL-2026-17179"]},"retained":false,"historicalAffected":[]}],"coverage":[]}