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?

@att-ebiz/abs-components-bc is a typosquat — you almost certainly intended a legitimately-named package. Remove @att-ebiz/abs-components-bc, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @att-ebiz/abs-components-bc — how do I know if it already compromised me?

If @att-ebiz/abs-components-bc was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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.

How do I find @att-ebiz/abs-components-bc across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @att-ebiz/abs-components-bc (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @att-ebiz/abs-components-bc across your stack and pipelines.

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

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @att-ebiz/abs-components-bc (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @att-ebiz/abs-components-bc across your stack and pipelines.
If you installed it — respond
@att-ebiz/abs-components-bc is a typosquat — you almost certainly intended a legitimately-named package. Remove @att-ebiz/abs-components-bc, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @att-ebiz/abs-components-bc was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @att-ebiz/abs-components-bc before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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

Detect & block this

O3 blocks @att-ebiz/abs-components-bc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring