Which versions of uibabai are malicious?

The following npm versions of uibabai are flagged malicious: 5.7.5. Treat any of these as compromised.

How do I remediate uibabai if I installed it?

uibabai establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed uibabai — how do I know if it already compromised me?

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

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

Malicious package

uibabainpm

uibabai is a confirmed malicious npm package (MAL-2026-12054) that opens a backdoor for remote access (malicious version 5.7.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in uibabai (npm)

MAL-2026-12054

Immediate action

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

npm uninstall uibabai

What this malware does

index.js has malicious code appended after a legitimate Tailwind plugin export. On any require()/import of the package, the appended block queries the public Ethereum RPC eth.drpc.org for a transaction from the hardcoded address 0xa322e5f3d311d3080e6f0121063e9adc2490ef1a, derives an IPv4 C2 endpoint from the first 4 bytes of the transaction's to field, fetches XOR-encrypted payloads over plain HTTP from paths /0x/cls and /0x/ls, and executes the decrypted bytes via eval and a spawned node -e child process. Identifiers such as require, http, https, child_process, POST, application/json, base64, and the eth_blockNumber/eth_getBlockByNumber RPC method names are hidden behind \uXXXX unicode escapes, and server responses are XOR-decoded before execution. The blockchain lookup functions as a dead-drop resolver so the C2 IP can be rotated by publishing a new Ethereum transaction without modifying the package.

Malicious versions

1 flagged

5.7.5

Indicators of compromise (SHA-256)

2680f37e219fec8bf9af5b922534ccb483a6b0503d0158cccaa0c152ed6b7484

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for uibabai (version 5.7.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uibabai across your stack and pipelines.
If you installed it — respond
uibabai establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If uibabai 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 uibabai 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. uibabai on npm has been identified as a malicious package (version 5.7.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011470

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks uibabai-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database