{"id":"MAL-2026-4418","revision":"db3afc9a2080428184a33c16e9b02f46","records":[{"revision":"db3afc9a2080428184a33c16e9b02f46","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-4418","aliases":["GHSA-wpmr-hxhp-4h27"],"title":"Malicious code in @pluxee-connect/api-client (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (0f5056dda18e9a9f440db7379d09fa1f9f7ff087ac00d6684170cddd40c240e9)\nOn `npm install`, postinstall.js collects `os.hostname()`, `os.userInfo()`, and `process.version` and transmits them over plain HTTP to `716bw4e4k31qif2nc1v658fb62ct0soh.oastify.com` (a Burp Collaborator out-of-band interaction subdomain), with DNS resolution providing a second exfil channel via subdomain encoding. The package itself is a near-empty shell — `index.js` exports only a `ConsentsStatus` enum — and is published at version 99.0.1, far above any plausible legitimate release for the `@pluxee-connect` scope. The structural shape (high-bumped version + trivial functional surface + lifecycle-time OOB beacon to oastify.com) is the canonical dependency-confusion attack against an internal scope. Any developer or CI system that resolves `@pluxee-connect/api-client` from public npm will leak machine identifiers to the attacker.\n","state":0,"publishedAt":"2026-05-20T03:57:26+00:00","modifiedAt":"2026-09-01T11:30:52.1426343+00:00","affected":[{"ecosystem":"npm","name":"@pluxee-connect/api-client","ranges":[],"versions":["99.0.1","99.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@pluxee-connect/api-client/v/99.0.1","https://www.npmjs.com/package/@pluxee-connect/api-client/v/99.0.0","https://github.com/advisories/GHSA-wpmr-hxhp-4h27"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-4418","license":"OSV · upstream source license applies","key":"osv:MAL-2026-4418","identifiers":["MAL-2026-4418","GHSA-wpmr-hxhp-4h27"]},"retained":false,"historicalAffected":[]}],"coverage":[]}