alelo-utils
This report shows the evidence for alelo-utils@99.0.0, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-14028 confirms this npm version as malicious.
Advisory
MAL-2026-14028
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in alelo-utils (npm)
Details
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 oxy12@proton.me, 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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to alelo-utils@99.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing alelo-utils@99.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.