Which versions of bootstrap-custom-ui are malicious?

The following npm versions of bootstrap-custom-ui are flagged malicious: 5.7.2. Treat any of these as compromised.

How do I remediate bootstrap-custom-ui if I installed it?

bootstrap-custom-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.

I already installed bootstrap-custom-ui — how do I know if it already compromised me?

If bootstrap-custom-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.

Is bootstrap-custom-ui part of a known attack campaign?

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

Malicious package

bootstrap-custom-uinpm

bootstrap-custom-ui is a confirmed malicious npm package (MAL-2026-14030) that steals credentials and exfiltrates sensitive data (malicious version 5.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bootstrap-custom-ui (npm)

MAL-2026-14030

Immediate action

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

npm uninstall bootstrap-custom-ui

What this malware does

The package presents itself as a React/Bootstrap UI component library but its default export getPlugin performs an HTTPS request to the hardcoded bare-IP endpoint https://31.97.137.157:45000/icons/108 and passes the response's credits field to the Function constructor with full Node context (require, module, exports, process, Buffer). Any caller invoking the exported function grants the remote server arbitrary code execution on the host. The destination URL is assembled from split string fragments (protocol, separator, domain, path, token) and a decoy setDefaultModule references legitimate CDN names (cloudflare, fastly, akamai, cloudfront) that are never actually used, camouflaging the real bare-IP destination. Behavior does not match the advertised purpose.

Malicious versions

1 flagged

5.7.2

Indicators of compromise (SHA-256)

652b61501946d7df441ba0b302898ff5aa223b09828775504099fc8d91878d81

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 bootstrap-custom-ui (version 5.7.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bootstrap-custom-ui across your stack and pipelines.
If you installed it — respond
bootstrap-custom-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 bootstrap-custom-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 bootstrap-custom-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

No. bootstrap-custom-ui on npm has been identified as a malicious package (version 5.7.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017739

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bootstrap-custom-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database