Which versions of abu-common-components are malicious?

The following npm versions of abu-common-components are flagged malicious: 99.99.1. Treat any of these as compromised.

How do I remediate abu-common-components if I installed it?

Remove abu-common-components 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 activity or persistence.

I already installed abu-common-components — how do I know if it already compromised me?

If abu-common-components 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 abu-common-components part of a known attack campaign?

Yes — abu-common-components is associated with the IN-MAL-2026-007508 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 abu-common-components 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 abu-common-components (version 99.99.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abu-common-components across your stack and pipelines.

Malicious package

abu-common-componentsnpm

Malicious code in abu-common-components (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6463

Immediate action

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

npm uninstall abu-common-components

What this malware does

package.json declares preinstall and postinstall hooks that invoke curl against a hardcoded bare-IP HTTP endpoint (http://64.227.183.144/depconf/abu-common-components/), sending the installer's username ($(whoami)), hostname ($(hostname)), current working directory ($PWD) and timestamp as query parameters. This fires automatically on npm install with no caller consent, leaks internal host and build-path identifiers in cleartext, and points at a non-publisher bare IP. The package itself is hollow — index.js is a one-line placeholder — and is published at the inflated version 99.99.1 by an anonymous author, the canonical shape of a dependency-confusion probe designed to be resolved ahead of a private internal package of the same name. The combination of the /depconf/<pkgname>/ URL path, the inflated version, and the placeholder body confirms reconnaissance intent: any organization with a private abu-common-components package will leak its existence and internal host fingerprints to the attacker on a single npm install.

Malicious versions

1 flagged

99.99.1

Indicators of compromise (SHA-256)

17e7b4ac8a492915d8475c73488b64236250746de410c705b7cc43c0656589be

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for abu-common-components (version 99.99.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abu-common-components across your stack and pipelines.
If you installed it — respond
Remove abu-common-components 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 activity or persistence.
Did it already run?
If abu-common-components 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 abu-common-components 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. abu-common-components on npm has been identified as a malicious package (version 99.99.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007508

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks abu-common-components-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