{"id":"MAL-2026-15561","revision":"38a3cc4db18d4caa85717ff57db89bb4","records":[{"revision":"38a3cc4db18d4caa85717ff57db89bb4","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-15561","aliases":[],"title":"Malicious code in techportal (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (2d947d5b4ddaa0ea6a25488fb5b5a66b3afc5c8f56d5ac38fb2e95e4b23242f3)\npackage.json declares a preinstall hook (`node beacon.js`) that fires automatically on `npm install`. beacon.js reads os.hostname(), os.userInfo().username, and process.cwd(), base32-encodes them, and issues an HTTP GET to a hardcoded bare-IP callback URL http://45.76.249.245/beacon/<token>/techportal/4.0.10, carrying the values in X-Bug-Bounty-Host, X-Bug-Bounty-User, and X-Bug-Bounty-Path headers. If the HTTP beacon fails or times out, the same identifiers are packed as base32-encoded DNS subdomain labels and queried (resolve4/resolve6/resolveTxt) against three hardcoded `*.oob.asm5.net` collector domains, providing a DNS-tunneling channel that bypasses HTTP egress controls. Destination is not caller-configurable and there is no install-time opt-in. Self-labeling of the beacon as an authorized bug bounty or dual-use tool does not change the data flow: installer host identity leaves the installer's machine on `npm install` to hardcoded attacker-operated infrastructure.\n","state":0,"publishedAt":"2026-08-29T02:13:42+00:00","modifiedAt":"2026-09-04T05:45:05.6742513+00:00","affected":[{"ecosystem":"npm","name":"techportal","ranges":[],"versions":["4.0.10","4.0.11"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/techportal/v/4.0.10","https://www.npmjs.com/package/techportal/v/4.0.11"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-15561","license":"OSV · upstream source license applies","key":"osv:MAL-2026-15561","identifiers":["MAL-2026-15561"]},"retained":false,"historicalAffected":[]}],"coverage":[]}