Which versions of electron-volt are malicious?

The following npm versions of electron-volt are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate electron-volt if I installed it?

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

If electron-volt 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 electron-volt part of a known attack campaign?

Yes — electron-volt is associated with the GHSA-grxg-6443-4p64 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 electron-volt 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 electron-volt (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging electron-volt across your stack and pipelines.

Malicious package

electron-voltnpm

Malicious code in electron-volt (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191086

Immediate action

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

npm uninstall electron-volt

What this malware does

The package electron-volt was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

05e20afdf3328e10c94e09a40e27aefc49eda68b38a4c40b917b749a0a12e1cd

254b6eb454736ec26269ce457251c29fdb06d110a7f21821feb6c530cc383f73

0c7fc79b9e614ad1f38d5c44d7ab287b6adc50f1504b6918a98c6367c360796a

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 electron-volt (version 0.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging electron-volt across your stack and pipelines.
If you installed it — respond
electron-volt 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 electron-volt 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 electron-volt 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. electron-volt on npm has been identified as a malicious package (version 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-grxg-6443-4p64

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks electron-volt-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