Which versions of @att-ebiz/abs-components-bc are malicious?

The following npm versions of @att-ebiz/abs-components-bc are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @att-ebiz/abs-components-bc if I installed it?

Remove @att-ebiz/abs-components-bc from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is @att-ebiz/abs-components-bc part of a known attack campaign?

Yes — @att-ebiz/abs-components-bc is associated with the IN-MAL-2026-005044, IN-MAL-2026-005043 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect @att-ebiz/abs-components-bc in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @att-ebiz/abs-components-bc and packages like it before any post-install script runs.

Malicious package

@att-ebiz/abs-components-bcnpm

Malicious code in @att-ebiz/abs-components-bc (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5153

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @att-ebiz/abs-components-bc

What this malware does

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.

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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

d9d4d8606057fc579fbbc6ede648c88bb580827838850f589e8887c1dd374a39

f3e597e558eea8fcd44160e348300946f5bed715ad5dd6e913fa4395c104fba5

fb8d1b46db555fda7536bcf080f9dfd0ceed5c731f7a96b2579121598dad6721

Frequently asked questions

No. @att-ebiz/abs-components-bc on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005044IN-MAL-2026-005043

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection