Which versions of veldora are malicious?

The following npm versions of veldora are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate veldora if I installed it?

veldora 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 veldora — how do I know if it already compromised me?

If veldora 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.

Is veldora part of a known attack campaign?

Yes — veldora is associated with the GHSA-wxrm-vmq9-jp23, IN-MAL-2026-013202 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 veldora across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for veldora (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging veldora across your stack and pipelines.

Malicious package

veldoranpm

veldora is a confirmed malicious npm package (MAL-2026-11018) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in veldora (npm)

MAL-2026-11018

Immediate action

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

npm uninstall veldora

What this malware does

Package [email protected] was scanned across 6 files. No evidence of install-time or import-time execution of remote content, no credential or environment variable collection, no hardcoded attacker-controlled network destinations, no lifecycle scripts fetching external payloads, and no obfuscated code paths were observed. The package does not exhibit any of the standard supply-chain attack fingerprints (exfiltration, dropper, silent-relay, backdoor, self-propagation, credential distribution).

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

e2e3a6a16c04af92c19ea149ef526996cdaea7357b931cdbccedffd6237f598e

4a848da2622d0adc27e55e1a650c39892aea7ef22c81c4c6ed4e5b6dc64809de

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for veldora (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging veldora across your stack and pipelines.
If you installed it — respond
veldora 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 veldora 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 veldora 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

No. veldora on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wxrm-vmq9-jp23IN-MAL-2026-013202

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks veldora-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