Malicious code in alelo-utils (npm)
The npm package alelo-utils version 99.0.0 contains malicious code that exfiltrates sensitive environment and configuration data during installation. The preinstall.js script collects system information and environment variables, sending them to an untrusted IP address with TLS verification disabled. The postinstall script further reads sensitive files such as .env and .npmrc, executes system commands to gather user identity, and sends this data to the same untrusted endpoint. The package exhibits dependency confusion characteristics and is published under a personal account unrelated to the claimed author. This behavior risks leaking installer credentials and cloud/API secrets.
AI Analysis
Technical Summary
The alelo-utils npm package at version 99.0.0 includes malicious installation scripts that perform data exfiltration. The preinstall.js script collects hostname, username, platform, current working directory, and the full process environment, then posts this data to a suspicious IPv4 address (https://209.99.185.109/preinstall) with TLS verification disabled (rejectUnauthorized:false). The postinstall/index.js script reads sensitive configuration files (.env, .npmrc, package.json, and parent directory .env files), executes system commands (whoami/id), and posts the collected data to https://209.99.185.109/postinstall over the same insecure channel. The package metadata suggests dependency confusion tactics, with a version number 99.0.0 and a bundled login.ps1 referencing an npm publish workflow under a personal email account ([email protected]) that does not match the claimed 'Alelo Dev Team' author. This install-time exfiltration directly compromises installer credentials and secrets.
Potential Impact
Sensitive environment variables, configuration files, and system information are exfiltrated to an untrusted external server during package installation. This includes npm authentication tokens and cloud/API credentials typically stored in .npmrc and .env files. The compromised credentials can lead to unauthorized access to private repositories, cloud services, or other resources. The use of TLS with disabled verification increases the risk of interception or manipulation of the data in transit.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing alelo-utils version 99.0.0 from untrusted sources. Review and revoke any potentially exposed npm authentication tokens and cloud/API credentials if this package was installed. Monitor for suspicious activity related to compromised credentials. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Malicious code in alelo-utils (npm)
Description
The npm package alelo-utils version 99.0.0 contains malicious code that exfiltrates sensitive environment and configuration data during installation. The preinstall.js script collects system information and environment variables, sending them to an untrusted IP address with TLS verification disabled. The postinstall script further reads sensitive files such as .env and .npmrc, executes system commands to gather user identity, and sends this data to the same untrusted endpoint. The package exhibits dependency confusion characteristics and is published under a personal account unrelated to the claimed author. This behavior risks leaking installer credentials and cloud/API secrets.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The alelo-utils npm package at version 99.0.0 includes malicious installation scripts that perform data exfiltration. The preinstall.js script collects hostname, username, platform, current working directory, and the full process environment, then posts this data to a suspicious IPv4 address (https://209.99.185.109/preinstall) with TLS verification disabled (rejectUnauthorized:false). The postinstall/index.js script reads sensitive configuration files (.env, .npmrc, package.json, and parent directory .env files), executes system commands (whoami/id), and posts the collected data to https://209.99.185.109/postinstall over the same insecure channel. The package metadata suggests dependency confusion tactics, with a version number 99.0.0 and a bundled login.ps1 referencing an npm publish workflow under a personal email account ([email protected]) that does not match the claimed 'Alelo Dev Team' author. This install-time exfiltration directly compromises installer credentials and secrets.
Potential Impact
Sensitive environment variables, configuration files, and system information are exfiltrated to an untrusted external server during package installation. This includes npm authentication tokens and cloud/API credentials typically stored in .npmrc and .env files. The compromised credentials can lead to unauthorized access to private repositories, cloud services, or other resources. The use of TLS with disabled verification increases the risk of interception or manipulation of the data in transit.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing alelo-utils version 99.0.0 from untrusted sources. Review and revoke any potentially exposed npm authentication tokens and cloud/API credentials if this package was installed. Monitor for suspicious activity related to compromised credentials. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14028
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a7f43f1bf8831d5395d77c3
Added to database: 08/14/2026, 16:36:01 UTC
Last enriched: 08/14/2026, 16:52:34 UTC
Last updated: 09/27/2026, 00:13:14 UTC
Views: 47
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.