Which versions of vl-ui-button are malicious?

The following npm versions of vl-ui-button are flagged malicious: 10.1.1. Treat any of these as compromised.

How do I remediate vl-ui-button if I installed it?

Remove vl-ui-button 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 vl-ui-button — how do I know if it already compromised me?

If vl-ui-button 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.

How do I find vl-ui-button across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vl-ui-button (version 10.1.1).

Malicious package

vl-ui-buttonnpm

Advisory published Feb 22, 2026Updated Mar 23, 2026

vl-ui-button is a confirmed malicious npm package (MAL-2026-992) that executes malicious code on install (malicious version 10.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vl-ui-button (npm)

MAL-2026-992

Immediate action

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

npm uninstall vl-ui-button

What this malware does

The package vl-ui-button was found to contain malicious code.

The OpenSSF Package Analysis project identified 'vl-ui-button' @ 10.1.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

10.1.1

Indicators of compromise (SHA-256)

50f44ea9cd927eae0232074aba1d3ccdb010b5bb0ddf3b05b7a24bbe52084512

1e34ef0af8a8e8cc96afd0941b0fe2a5259eb4d2cf73564c5dde8b97a2bdf766

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vl-ui-button (version 10.1.1).
If you installed it — respond
Remove vl-ui-button 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 vl-ui-button 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. vl-ui-button on npm has been identified as a malicious package (version 10.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks vl-ui-button-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