{"id":"MAL-2026-14207","revision":"102e97eec76448098631016c0474cf79","records":[{"revision":"102e97eec76448098631016c0474cf79","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14207","aliases":[],"title":"Malicious code in @sarex-team/viewer (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (04b67de30d08d48f32be517383d6940c8179d2269ea7a1720346eacc2e8c28d5)\nThe package runs a DNS-based beacon that leaks the installer's OS username, hostname, and current-working-directory basename to the hardcoded attacker-controlled domain oob.sl4x0.xyz. lib/core.js collects os.userInfo().username, os.hostname(), and process.cwd(), joins them as subdomain labels under oob.sl4x0.xyz, and issues a dns.resolve4() lookup so the encoded values are exfiltrated via DNS. The destination domain and the module/API names ('os', 'dns', 'process', 'userInfo', 'hostname', 'cwd', 'resolve4') are reconstructed from numeric char-code arrays in lib/b02e30.js and lib/6ad264.js solely to conceal them. Execution is zero-interaction: package.json declares scripts.install: 'node index.js', and index.js top-level requires./lib/core inside a try/catch that swallows errors, so the beacon fires on npm install and again on every require() of the package while the install appears clean.\n","state":0,"publishedAt":"2026-08-19T02:31:51+00:00","modifiedAt":"2026-08-19T03:00:13.1073352+00:00","affected":[{"ecosystem":"npm","name":"@sarex-team/viewer","ranges":[],"versions":["9.9.11"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@sarex-team/viewer/v/9.9.11"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14207","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14207","identifiers":["MAL-2026-14207"]},"retained":false,"historicalAffected":[]}],"coverage":[]}