uolcs-host-uol-anuncios-fenpm
Malicious code in uolcs-host-uol-anuncios-fe (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
Package claims an internal-scope corporate name (uolcs-host-uol-anuncios-fe) on public npm, version-pinned to 99.99.99 — the canonical dependency-confusion shape designed to win resolution against an internal package of the same name in a target organization's CI. Both preinstall and postinstall hooks in package.json invoke node./callback.js, which reads os.hostname() and os.platform(), embeds them as a subdomain label (uolci-<hostname>-<platform>.d86r3dv5vn81lvohffp0131g8kdx9mz3c.oast.pro), and issues a DNS A lookup. The destination oast.pro is the interactsh out-of-band interaction listener; the DNS query itself is the exfiltration channel, capturing the installer's hostname and OS at the listener owned by whoever controls that token. The README's claim of authorized research is not verifiable from package contents and does not change the installer-side effect: any CI host or developer machine that resolves this name from public npm leaks identity to a third party on npm install.
The OpenSSF Package Analysis project identified 'uolcs-host-uol-anuncios-fe' @ 99.99.99 (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 uolcs-host-uol-anuncios-fe (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uolcs-host-uol-anuncios-fe across your stack and pipelines.
If you installed it — respond
uolcs-host-uol-anuncios-fe 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 uolcs-host-uol-anuncios-fe 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 uolcs-host-uol-anuncios-fe 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 uolcs-host-uol-anuncios-fe-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.