Which versions of vega-lite-next are malicious?

The following npm versions of vega-lite-next are flagged malicious: 19.2.1. Treat any of these as compromised.

How do I remediate vega-lite-next if I installed it?

vega-lite-next is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed vega-lite-next — how do I know if it already compromised me?

If vega-lite-next 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 vega-lite-next part of a known attack campaign?

Yes — vega-lite-next is associated with the IN-MAL-2026-007875, RLMA-2026-05642, RLUA-2026-06539 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 vega-lite-next across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for vega-lite-next (version 19.2.1).

Malicious package

vega-lite-nextnpm

Advisory published Jul 1, 2026Updated Sep 1, 2026

vega-lite-next is a confirmed malicious npm package (MAL-2026-6709) that steals credentials and exfiltrates sensitive data (malicious version 19.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vega-lite-next (npm)

MAL-2026-6709

Immediate action

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

npm uninstall vega-lite-next

What this malware does

Package name impersonates the popular vega-lite library but ships no vega functionality — only a preinstall exfiltration stub. package.json declares preinstall: node index.js. On npm install, index.js collects os.hostname(), platform, arch, os.userInfo() (username/uid/gid/shell), homedir, cwd, and the output of whoami and id executed via child_process, then POSTs the JSON payload to a hardcoded Burp Collaborator subdomain at https://kbztayu6auucui8s9ucz2mujkaq1er2g.oastify.com/detox56. The combination of typosquat naming, absence of library functionality, automatic preinstall execution, shell reconnaissance, and an attacker-controlled exfil endpoint is an unambiguous supply-chain attack against developers who mistype or are tricked into installing the lookalike.

Malicious versions

1 flagged

19.2.1

Indicators of compromise (SHA-256)

8c98ee24f91eaab2bc8360306a75519ae167dcbc3c7bd38cc395fbaa9590f4cd

ab30d8515000381a50a6ede1b2dbad8ebf4ce5df37e33c12f566215c6ef2c4fd

f77b418e834e431651fe86b811df535ed63ff45f97359228503ed10b778406c7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for vega-lite-next (version 19.2.1).
If you installed it — respond
vega-lite-next is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If vega-lite-next 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. vega-lite-next on npm has been identified as a malicious package (version 19.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007875RLMA-2026-05642RLUA-2026-06539

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks vega-lite-next-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database