OpenSSF/OSV advisory MAL-2026-14024 confirms this npm version as malicious. The package runs malicious lifecycle scripts on npm install. preinstall.js collects hostname, username, platform, cwd, and the entire process.env, then POSTs the JSON payload over HTTPS with certificate verification disabled to https://209.99.185.109/preinstall. index.js (postinstall) reads.env,.npmrc, package.json,../.env, and../../.env from the installer's tree, executes `whoami` and `id`, dumps process.env, and...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in alelo-core (npm)
Details
The package runs malicious lifecycle scripts on npm install. preinstall.js collects hostname, username, platform, cwd, and the entire process.env, then POSTs the JSON payload over HTTPS with certificate verification disabled to https://209.99.185.109/preinstall. index.js (postinstall) reads.env,.npmrc, package.json,../.env, and../../.env from the installer's tree, executes `whoami` and `id`, dumps process.env, and POSTs the collected data to https://209.99.185.109/postinstall over HTTPS with certificate verification disabled. The destination is a bare IP unrelated to any declared publisher;.npmrc typically contains npm auth tokens and.env files hold application secrets, so installation of this package results in exfiltration of credentials, tokens, and host identity from the installer's machine. A shipped login.ps1 references npm account oxy12@proton.me as the publishing identity. The package name resembles an internal/branded package (Alelo), consistent with a dependency-confusion lure.
Decision reason
OpenSSF Malicious Packages via OSV confirms alelo-core@99.0.1 as malicious (MAL-2026-14024): Malicious code in alelo-core (npm)