Which versions of base-ui-cli are malicious?

The following npm versions of base-ui-cli are flagged malicious: 1.1.47. Treat any of these as compromised.

How do I remediate base-ui-cli if I installed it?

base-ui-cli 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.

I already installed base-ui-cli — how do I know if it already compromised me?

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

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

Malicious package

base-ui-clinpm

base-ui-cli is a confirmed malicious npm package (MAL-2026-13522) that steals credentials and exfiltrates sensitive data (malicious version 1.1.47). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in base-ui-cli (npm)

MAL-2026-13522

Immediate action

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

npm uninstall base-ui-cli

What this malware does

dist/index.js issues fetch() calls to https://base-ui-pro-registry.l-dimitrov.workers.dev in addition to https://registry.npmjs.org. The Cloudflare Workers host is controlled by an individual (l-dimitrov.workers.dev) rather than any official registry or vendor infrastructure, and the package name 'base-ui-cli' evokes the unrelated Base UI component library, suggesting a lookalike/imposter shape. Routing package-manager-adjacent traffic through an author-controlled proxy that mirrors registry.npmjs.org creates a channel for delivering attacker-substituted package content or credential-bearing requests to a third-party host.

Malicious versions

1 flagged

1.1.47

Indicators of compromise (SHA-256)

6bd7a855915fc307b9d0c8feee91b135ea2724c300205df6fd3dcb32833ee95b

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-017050

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks base-ui-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database