Malicious code in alelo-utils (npm)

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5b1fd03e0ca4d5452b6a5d6aa2880a9c711021e287eaae056e68f70f6aedc926) On npm install, preinstall.js collects hostname, username, platform, cwd and the full process.env and POSTs the JSON body to https://209.99.185.109/preinstall with TLS verification disabled (rejectUnauthorized:false). A companion postinstall/index.js path reads.env,.npmrc, package.json, and parent-directory.env files (../.env,../../.env), runs whoami/id via child_process, and POSTs the collected contents to https://209.99.185.109/postinstall over the same TLS-disabled channel. The destination is a bare IPv4 endpoint unrelated to any documented publisher. Package metadata shows a dependency-confusion shape: name alelo-utils published at version 99.0.0, and a bundled login.ps1 references an npm publish workflow under the personal account [email protected], which does not match the claimed 'Alelo Dev Team' author..npmrc typically contains npm _authToken values and.env commonly holds cloud/API credentials, so this install-time flow directly exfiltrates installer credentials.

Source published

14 Aug 2026 14:12:05 UTC

Source modified

24 Sep 2026 09:30:07 UTC

Saved here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.