ap3-components-uinpm
ap3-components-ui is a confirmed malicious npm package (MAL-2026-10150) that steals credentials and exfiltrates sensitive data (malicious version 9.999.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ap3-components-ui (npm)
What this malware does
Package 'ap3-components-ui' at version 9.999.0 declares a preinstall hook ("node index.js > /dev/null 2>&1") that shells out to collect installer-side identifiers — hostname, current working directory, username, and the installer's public IP (fetched via curl to ifconfig.me) — hex-encodes the collected data, and exfiltrates it as DNS subdomain queries under d987f5ra3q1r1j7ahol0yzuwujwe76i55.oast.fun, an attacker-controlled Interactsh collector. The package name is also embedded in the beacon payload so the operator can correlate which internal name resolved externally. The tarball has an empty description, no README, and no library code beyond the exfil script — the canonical shape of a dependency-confusion squat on an internal package name, published at the sentinel version 9.999.0 to force resolution over any legitimate internal release.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ap3-components-ui (version 9.999.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ap3-components-ui across your stack and pipelines.
If you installed it — respond
ap3-components-ui is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If ap3-components-ui 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 ap3-components-ui 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ap3-components-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.