alelo-apinpm
Advisory published Updated
alelo-api is a confirmed malicious npm package (MAL-2026-14020) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in alelo-api (npm)
What this malware does
The package fires attacker-controlled code on npm install via both preinstall.js and index.js (postinstall). preinstall.js collects hostname, username, platform, cwd, and the full process.env, JSON-encodes it, and POSTs it over HTTPS with TLS verification disabled to the hardcoded bare-IP endpoint https://209.99.185.109/preinstall. The postinstall path reads installer-owned secret files from the current working directory and its parents (.env, ../.env, ../../.env, .npmrc, package.json), captures process.env, executes whoami and id, and POSTs the aggregate to https://209.99.185.109/postinstall (also with TLS verification disabled). The tarball additionally ships a login.ps1 note referencing the publisher account [email protected] and a local publish workflow under C:\Users\hp\Documents\alelo\npm-publish; combined with the name alelo-api and version 99.0.0, this indicates a typosquat / dependency-confusion attack aimed at the Alelo organization. Any installer that runs npm install alelo-api leaks environment variables, npm tokens, and any .env secrets in the working tree to the hardcoded IP.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for alelo-api (2 malicious versions).
If you installed it — respond
alelo-api is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If alelo-api was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks alelo-api-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.