Malicious code in housecall-ui (npm)
The npm package [email protected] is a hollow package that acts as a dependency confusion lure. It contains no functionality itself but declares a runtime dependency on a tarball hosted on a third-party Google Cloud Storage bucket controlled by an attacker. Installing this package causes npm to fetch and execute untrusted code from mutable infrastructure outside the npm registry, leading to full system compromise. The package name mimics a legitimate internal package to increase the chance of accidental installation. Any system with this package installed should be considered fully compromised, and all secrets on it must be rotated immediately.
AI Analysis
Technical Summary
[email protected] is an empty npm package whose sole runtime dependency is an HTTPS tarball URL pointing to a third-party Google Cloud Storage bucket. This bucket is not part of the npm registry, is mutable, and not pinned by hash, allowing the attacker to control the code executed during npm install lifecycle scripts. The package name and version are crafted to out-rank internal packages in mixed-resolution environments, a classic dependency confusion attack. The package itself exports an empty object and contributes no functionality other than sideloading malicious code from attacker-controlled infrastructure.
Potential Impact
Installing [email protected] results in execution of attacker-controlled code on the victim system, leading to full compromise. Attackers may gain complete control, access all stored secrets and keys, and persist malicious software. Removal of the package alone does not guarantee eradication of the compromise. Immediate secret rotation from a separate, uncompromised system is required.
Mitigation Recommendations
Remove the [email protected] package immediately. Consider any system with this package installed fully compromised and rotate all secrets and keys from a different, secure computer. Due to the nature of the compromise, further forensic analysis and remediation may be necessary. Avoid installing packages from untrusted or suspicious sources, especially those with unusual versioning or external dependencies hosted outside official registries. Monitor for similar dependency confusion attempts in your environment.
Malicious code in housecall-ui (npm)
Description
The npm package [email protected] is a hollow package that acts as a dependency confusion lure. It contains no functionality itself but declares a runtime dependency on a tarball hosted on a third-party Google Cloud Storage bucket controlled by an attacker. Installing this package causes npm to fetch and execute untrusted code from mutable infrastructure outside the npm registry, leading to full system compromise. The package name mimics a legitimate internal package to increase the chance of accidental installation. Any system with this package installed should be considered fully compromised, and all secrets on it must be rotated immediately.
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
[email protected] is an empty npm package whose sole runtime dependency is an HTTPS tarball URL pointing to a third-party Google Cloud Storage bucket. This bucket is not part of the npm registry, is mutable, and not pinned by hash, allowing the attacker to control the code executed during npm install lifecycle scripts. The package name and version are crafted to out-rank internal packages in mixed-resolution environments, a classic dependency confusion attack. The package itself exports an empty object and contributes no functionality other than sideloading malicious code from attacker-controlled infrastructure.
Potential Impact
Installing [email protected] results in execution of attacker-controlled code on the victim system, leading to full compromise. Attackers may gain complete control, access all stored secrets and keys, and persist malicious software. Removal of the package alone does not guarantee eradication of the compromise. Immediate secret rotation from a separate, uncompromised system is required.
Mitigation Recommendations
Remove the [email protected] package immediately. Consider any system with this package installed fully compromised and rotate all secrets and keys from a different, secure computer. Due to the nature of the compromise, further forensic analysis and remediation may be necessary. Avoid installing packages from untrusted or suspicious sources, especially those with unusual versioning or external dependencies hosted outside official registries. Monitor for similar dependency confusion attempts in your environment.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5446
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-h2mj-mwm8-g9qp"]
- Ecosystems
- ["npm"]
Threat ID: 6a520ed368715ace43901a77
Added to database: 07/11/2026, 09:37:23 UTC
Last enriched: 09/12/2026, 18:47:14 UTC
Last updated: 09/12/2026, 18:47:14 UTC
Views: 32
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.