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?

Remove bootstrap-custom-ui from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If bootstrap-custom-ui was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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?

Search your lockfiles and build artifacts for bootstrap-custom-ui (version 5.7.2).

Malicious package

bootstrap-custom-uinpm

Advisory published Aug 14, 2026Updated Aug 14, 2026

bootstrap-custom-ui is a confirmed malicious npm package (MAL-2026-14030) that executes malicious code on install (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

Malicious package

Find it
Search your lockfiles and build artifacts for bootstrap-custom-ui (version 5.7.2).
If you installed it — respond
Remove bootstrap-custom-ui from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bootstrap-custom-ui was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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 malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database