@bingads-webui-component-legacy/storagenpm
Advisory published Updated
@bingads-webui-component-legacy/storage is a confirmed malicious npm package (MAL-2026-127) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @bingads-webui-component-legacy/storage (npm)
What this malware does
The package @bingads-webui-component-legacy/storage was found to contain malicious code.
The OpenSSF Package Analysis project identified '@bingads-webui-component-legacy/storage' @ 99.9.9 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @bingads-webui-component-legacy/storage (version 99.9.9).
If you installed it — respond
Remove @bingads-webui-component-legacy/storage 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 @bingads-webui-component-legacy/storage 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
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @bingads-webui-component-legacy/storage-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.