@bx-ui-framework/microfrontendnpm
@bx-ui-framework/microfrontend is a confirmed malicious npm package (MAL-2026-15868) that executes malicious code on install (malicious version 15.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @bx-ui-framework/microfrontend (npm)
What this malware does
package.json declares a runtime dependency microfrontend whose source is a bare HTTPS URL at https://repo.artifactorymanager.com/bx-ui-framework/microfrontend rather than a version on the npm registry. The URL carries no version, commit, or hash pin, so npm install fetches whatever tarball is currently served at that location and executes any lifecycle scripts and code it contains inside the installer's dependency tree. The artifactorymanager.com domain is unrelated to any established publisher for this scope, and the tarball contents can change at any time without a version bump.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @bx-ui-framework/microfrontend (version 15.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bx-ui-framework/microfrontend across your stack and pipelines.
If you installed it — respond
Remove @bx-ui-framework/microfrontend 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 @bx-ui-framework/microfrontend 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 @bx-ui-framework/microfrontend 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
Detect & block this
O3 blocks @bx-ui-framework/microfrontend-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.