@bx-ui-framework/commonnpm
@bx-ui-framework/common is a confirmed malicious npm package (MAL-2026-15867) that executes malicious code on install (malicious versions 1.2.0, 15.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @bx-ui-framework/common (npm)
What this malware does
package.json declares a dependency whose key equals the package's own name (@bx-ui-framework/common) and whose value is a bare HTTPS URL (https://repo.remoteknight.com/bx-ui-framework/common) rather than a registry version range. On npm install, npm fetches whatever bytes that URL returns and installs them as the resolved dependency, executing any lifecycle scripts they contain. There is no version pin, no commit SHA, and no integrity/hash check. The shipped index.js is an inert stub, so the manifest line is the entire delivery mechanism: whoever controls repo.remoteknight.com controls code that runs on every installer's machine. The self-referential dependency name is the dependency-confusion shape used to win resolution over an internal package of the same name.
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/common (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bx-ui-framework/common across your stack and pipelines.
If you installed it — respond
Remove @bx-ui-framework/common 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/common 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/common 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/common-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.