{"id":"MAL-2026-12791","revision":"29315c9382514a7ca86bbdd772d1cd36","records":[{"revision":"29315c9382514a7ca86bbdd772d1cd36","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-12791","aliases":[],"title":"Malicious code in gs-uitk-object-utils (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (662b350826118282a93e76c970ab25659d7bc3a52c58e1e16466e4c432d0d1e5)\npackage.json declares scripts.install: `node index.js`, which requires `./lib/core`. lib/core.js reads the OS username, hostname, and current working-directory basename, assembles them with a hardcoded `goldman1` prefix into a subdomain of `oob.sl4x0.xyz`, and issues a `dns.resolve4` lookup against that name, causing the installer's host identifiers to be transmitted as a DNS query to the attacker-controlled authoritative server. The destination domain, prefix, and API names (`os`, `dns`, `userInfo`, `hostname`, `cwd`, `resolve4`) are stored as char-code arrays in lib/b02e30.js and lib/6ad264.js and decoded at runtime via String.fromCharCode, concealing the exfiltration path. The same code also fires on `require()` of the package. The package presents itself as an object-utility library, which does not match the observed install-time DNS beaconing.\n","state":0,"publishedAt":"2026-08-05T13:35:07+00:00","modifiedAt":"2026-08-05T14:37:13.4142466+00:00","affected":[{"ecosystem":"npm","name":"gs-uitk-object-utils","ranges":[],"versions":["9.9.11"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/gs-uitk-object-utils/v/9.9.11"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-12791","license":"OSV · upstream source license applies","key":"osv:MAL-2026-12791","identifiers":["MAL-2026-12791"]},"retained":false,"historicalAffected":[]}],"coverage":[]}