{"id":"MAL-2026-5787","revision":"3e31bdfeda43457dacbd147331d3ed95","records":[{"revision":"3e31bdfeda43457dacbd147331d3ed95","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-5787","aliases":["GHSA-6465-92w6-mgp8"],"title":"Malicious code in @solana-labs/spl-toke (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (8e2ec34996ab8cff20d9ba12cd9f5a8a75346c4e5e25d7c3fd5adc7bb7045f64)\nPackage name `@solana-labs/spl-toke` is a likely confusion-attack against the well-known `@solana/spl-token` SPL token client (missing trailing `n`, different scope). The shipped `lib/index.cjs.js` and `lib/index.esm.js` bundles contain the keyword combinations `fetch(` / `POST` / `https.get` / `ping` that pattern-matched as potential C2 / exfiltration shapes, but tracing of the minified bundle did not complete and the literal destination URLs and trigger paths could not be confirmed in this run. The `ping` token may be benign (e.g. a websocket keepalive method or solana RPC ping helper) and the `fetch` calls may be ordinary RPC traffic — but neither has been verified, and combined with the typosquat-shaped name on a high-value scope (`@solana-labs/*` mimicking the official `solana-labs` GitHub org and the canonical `@solana/spl-token` package), this needs human review before installer use.\n","state":0,"publishedAt":"2026-06-15T17:15:36+00:00","modifiedAt":"2026-09-01T11:30:53.2367241+00:00","affected":[{"ecosystem":"npm","name":"@solana-labs/spl-toke","ranges":[],"versions":["1.0.0","1.98.112","1.0.8","1.98.111","1.0.10","1.0.5","1.0.6","1.0.7","1.0.2","1.0.3","1.0.4","1.98.103","1.98.105","1.98.107","1.98.108","1.98.109","1.98.110"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.0.10","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.98.112","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.0.5","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.0.6","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.0.7","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.0.0","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.98.111","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.0.8","https://research.jfrog.com/post/solana-fakefix","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.98.103","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.98.108","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.0.4","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.0.2","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.98.107","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.98.105","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.98.110","https://www.npmjs.com/package/@solana-labs/spl-toke/v/1.98.109","https://github.com/advisories/GHSA-6465-92w6-mgp8"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-5787","license":"OSV · upstream source license applies","key":"osv:MAL-2026-5787","identifiers":["MAL-2026-5787","GHSA-6465-92w6-mgp8"]},"retained":false,"historicalAffected":[]}],"coverage":[]}