MAL-2026-14020 Malicious code in alelo-api (npm)
Malicious package
Published
MAL-2026-14020 is a malicious package: alelo-api (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-14020/ (Markdown: https://insights.sbomify.com/MAL-2026-14020/index.md)
- Package
- alelo-api
- Registry
- npm
What is MAL-2026-14020?
MAL-2026-14020 is a malicious package in alelo-api, published on 14 Aug 2026.
Official description
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.What should I do about MAL-2026-14020?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.
Sources
Also known as GHSA-j3cg-h6v6-c6mc.