{"id":"MAL-2026-17327","revision":"ef3ee419566c46f396e0d4d3e425020d","records":[{"revision":"ef3ee419566c46f396e0d4d3e425020d","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-17327","aliases":[],"title":"Malicious code in exiouss (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (43ce408818d0222061c3b6ed499d77a245aae78e30e4f57c8e6e77ee52705805)\nmain.js in exiouss@5.0.1 imports child_process and issues POST requests to hardcoded endpoints, including https://gemini.google.com and https://ipc.shadxino.internal (main.js around lines 368-386). The presence of an `ipc.shadxino.internal` destination alongside a public Google host, combined with child_process usage and repeated `ping` invocations across the file (lines 202, 340, 420, 583, 611), fits an active-exfiltration/reconnaissance shape rather than any documented HTTP-client behavior. The `.internal` host is not a resolvable public destination and its appearance in a published npm module is consistent with an attacker-side collector or a leaked internal C2 name.\n","state":0,"publishedAt":"2026-09-30T04:50:53+00:00","modifiedAt":"2026-09-30T05:30:05.3301476+00:00","affected":[{"ecosystem":"npm","name":"exiouss","ranges":[],"versions":["5.0.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/exiouss/v/5.0.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-17327","license":"OSV · upstream source license applies","key":"osv:MAL-2026-17327","identifiers":["MAL-2026-17327"]},"retained":false,"historicalAffected":[]}],"coverage":[]}