Malicious code in easypanel-hosting (npm)
The easypanel-hosting npm package version 1.0.0 contains malicious code that executes during installation. It collects sensitive environment metadata such as hostname, username, current working directory, and CI environment variables, encodes this data, and exfiltrates it via DNS and HTTP requests to an attacker-controlled domain. The main module is a stub, indicating the package is likely used for reconnaissance or dependency confusion attacks. This data leakage occurs automatically on npm install before any user code runs.
AI Analysis
Technical Summary
The easypanel-hosting package at version 1.0.0 includes a preinstall lifecycle script that gathers installer identity metadata including hostname, username, current working directory, and continuous integration environment variable names. This information is base64url-encoded and sent out-of-band via DNS queries and HTTP requests to a hardcoded subdomain under lyomeri.com. The main module exports an empty object, suggesting the package is a stub designed to probe or exploit dependency confusion. The exfiltration happens automatically during npm install, exposing sensitive environment details to an attacker-controlled server.
Potential Impact
Sensitive environment information from the machine performing the npm install is leaked to an attacker-controlled domain. This includes hostname, username, working directory, and CI environment variables, which could aid attackers in reconnaissance and further attacks. The data exfiltration occurs without user interaction and before any legitimate code runs, potentially compromising the privacy and security of the build or deployment environment.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing [email protected] and audit their dependency trees for this package. Monitor for suspicious DNS and HTTP requests to unknown domains such as lyomeri.com. Since no fix is confirmed, check vendor advisories or npm security advisories for updates. Consider using package integrity verification and restricting network access during npm installs as temporary mitigations.
Malicious code in easypanel-hosting (npm)
Description
The easypanel-hosting npm package version 1.0.0 contains malicious code that executes during installation. It collects sensitive environment metadata such as hostname, username, current working directory, and CI environment variables, encodes this data, and exfiltrates it via DNS and HTTP requests to an attacker-controlled domain. The main module is a stub, indicating the package is likely used for reconnaissance or dependency confusion attacks. This data leakage occurs automatically on npm install before any user code runs.
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 easypanel-hosting package at version 1.0.0 includes a preinstall lifecycle script that gathers installer identity metadata including hostname, username, current working directory, and continuous integration environment variable names. This information is base64url-encoded and sent out-of-band via DNS queries and HTTP requests to a hardcoded subdomain under lyomeri.com. The main module exports an empty object, suggesting the package is a stub designed to probe or exploit dependency confusion. The exfiltration happens automatically during npm install, exposing sensitive environment details to an attacker-controlled server.
Potential Impact
Sensitive environment information from the machine performing the npm install is leaked to an attacker-controlled domain. This includes hostname, username, working directory, and CI environment variables, which could aid attackers in reconnaissance and further attacks. The data exfiltration occurs without user interaction and before any legitimate code runs, potentially compromising the privacy and security of the build or deployment environment.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing [email protected] and audit their dependency trees for this package. Monitor for suspicious DNS and HTTP requests to unknown domains such as lyomeri.com. Since no fix is confirmed, check vendor advisories or npm security advisories for updates. Consider using package integrity verification and restricting network access during npm installs as temporary mitigations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-16075
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6aa15f82acd9273b496184d6
Added to database: 09/09/2026, 13:30:42 UTC
Last enriched: 09/09/2026, 14:00:10 UTC
Last updated: 09/09/2026, 23:54:01 UTC
Views: 6
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.