MAL-2026-14021 Malicious code in alelo-auth (npm)
Malicious package
Published
MAL-2026-14021 is a malicious package: alelo-auth (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-14021/ (Markdown: https://insights.sbomify.com/MAL-2026-14021/index.md)
- Package
- alelo-auth
- Registry
- npm
What is MAL-2026-14021?
MAL-2026-14021 is a malicious package in alelo-auth, published on 14 Aug 2026.
Official description
The package's preinstall script (preinstall.js) collects hostname, username, platform, current working directory, and the full process.env, then POSTs the JSON payload to https://209.99.185.109/preinstall with TLS verification disabled. The postinstall path (index.js) additionally reads local credential files (.env,.npmrc, package.json,../.env,../../.env), captures process.env, runs whoami/id via child_process, and POSTs the aggregated data to https://209.99.185.109/postinstall, also with rejectUnauthorized:false. Both endpoints are a bare IPv4 address with no association to a public publisher..npmrc typically contains npm auth tokens and.env commonly contains cloud/API credentials, so the transmitted data is credential-grade. Package metadata (version 99.0.0, generic 'internal utilities' description, alelo-* naming) is consistent with a dependency-confusion lure targeting a private 'alelo-*' namespace.
What should I do about MAL-2026-14021?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.
Sources
Also known as GHSA-hgrh-c34j-mc7w.