customerdigital-ui-containers-libnpm
Malicious code in customerdigital-ui-containers-lib (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
On npm install, postinstall.js collects git identity, OS user/uid, hostname, internal network interface addresses, Cloudflare Pages environment variables, and directory listings of ~/.ssh, ~/.aws, and /.kube (first 5 entries of each), base64-encodes the payload, and sends it as a query string via an HTTPS GET to ho9skv69a3pbqzbzg7z1l009c0ir6hu6.oastify.com — a Burp Collaborator out-of-band exfiltration host. The script also implements explicit sandbox evasion: it returns early if the current working directory starts with /tmp, contains 'npm-', or HOME is unset, with a 'Diagnostic/2.0' User-Agent cover story. The targeted directories (/.ssh, ~/.aws, ~/.kube) reveal credential filenames (id_rsa, credentials, config) suitable for follow-on targeted theft. The package name shape and dependency-confusion-style high version (99.12.9) are consistent with an internal-name squat reconnaissance payload.
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.
The OpenSSF Package Analysis project identified 'customerdigital-ui-containers-lib' @ 99.13.9 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
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 customerdigital-ui-containers-lib (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging customerdigital-ui-containers-lib across your stack and pipelines.
If you installed it — respond
customerdigital-ui-containers-lib 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 customerdigital-ui-containers-lib 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 customerdigital-ui-containers-lib 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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks customerdigital-ui-containers-lib-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.