Malicious code in alelo-sdk (npm)
The alelo-sdk npm package versions 99.0.0 and 99.0.2 contain malicious lifecycle scripts that exfiltrate sensitive environment and configuration data to a hardcoded IP address. The preinstall script collects system and environment details and sends them to an external endpoint without TLS verification. The postinstall script further reads sensitive files such as .env and .npmrc, executes system commands, and sends this data to the same endpoint, risking exposure of credentials and tokens.
AI Analysis
Technical Summary
The alelo-sdk package (versions 99.0.0 and 99.0.2) includes malicious preinstall and postinstall lifecycle scripts that harvest sensitive information from the host environment. The preinstall.js script collects hostname, username, platform, current working directory, and the full process environment variables, sending this data as JSON to https://209.99.185.109/preinstall with TLS verification disabled. The postinstall script reads additional sensitive files (.env, .npmrc, parent-directory .env), executes commands like whoami or id, and posts the collected data to https://209.99.185.109/postinstall. This behavior exposes secrets such as npm publish tokens and cloud/API credentials to an attacker-controlled server. The package is designed to appear as an internal utility with an inflated version number to facilitate dependency confusion attacks.
Potential Impact
Any environment where alelo-sdk versions 99.0.0 or 99.0.2 are installed is at risk of having sensitive environment variables, configuration files, and credentials exfiltrated to an attacker-controlled server. This includes developer workstations and continuous integration systems, potentially compromising npm tokens, cloud credentials, and other secrets. The lack of TLS certificate verification increases the risk of interception or manipulation of the exfiltrated data.
Mitigation Recommendations
Avoid installing or using alelo-sdk versions 99.0.0 and 99.0.2. Remove these versions from any environment where they are present. Since no patch or official fix is indicated, rely on blocking network communications to the IP 209.99.185.109 and auditing environments for presence of this package and any exfiltrated data. Monitor for suspicious npm packages mimicking internal scopes with inflated version numbers to prevent dependency confusion attacks.
Malicious code in alelo-sdk (npm)
Description
The alelo-sdk npm package versions 99.0.0 and 99.0.2 contain malicious lifecycle scripts that exfiltrate sensitive environment and configuration data to a hardcoded IP address. The preinstall script collects system and environment details and sends them to an external endpoint without TLS verification. The postinstall script further reads sensitive files such as .env and .npmrc, executes system commands, and sends this data to the same endpoint, risking exposure of credentials and tokens.
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-sdk package (versions 99.0.0 and 99.0.2) includes malicious preinstall and postinstall lifecycle scripts that harvest sensitive information from the host environment. The preinstall.js script collects hostname, username, platform, current working directory, and the full process environment variables, sending this data as JSON to https://209.99.185.109/preinstall with TLS verification disabled. The postinstall script reads additional sensitive files (.env, .npmrc, parent-directory .env), executes commands like whoami or id, and posts the collected data to https://209.99.185.109/postinstall. This behavior exposes secrets such as npm publish tokens and cloud/API credentials to an attacker-controlled server. The package is designed to appear as an internal utility with an inflated version number to facilitate dependency confusion attacks.
Potential Impact
Any environment where alelo-sdk versions 99.0.0 or 99.0.2 are installed is at risk of having sensitive environment variables, configuration files, and credentials exfiltrated to an attacker-controlled server. This includes developer workstations and continuous integration systems, potentially compromising npm tokens, cloud credentials, and other secrets. The lack of TLS certificate verification increases the risk of interception or manipulation of the exfiltrated data.
Mitigation Recommendations
Avoid installing or using alelo-sdk versions 99.0.0 and 99.0.2. Remove these versions from any environment where they are present. Since no patch or official fix is indicated, rely on blocking network communications to the IP 209.99.185.109 and auditing environments for presence of this package and any exfiltrated data. Monitor for suspicious npm packages mimicking internal scopes with inflated version numbers to prevent dependency confusion attacks.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14026
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7f43f1bf8831d5395d771a
Added to database: 08/14/2026, 16:36:01 UTC
Last enriched: 08/14/2026, 16:51:13 UTC
Last updated: 08/14/2026, 16:51:13 UTC
Views: 2
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.