Which versions of @voiceflow/encryption are malicious?

The following npm versions of @voiceflow/encryption are flagged malicious: 0.3.2, 0.3.3. Treat any of these as compromised.

How do I remediate @voiceflow/encryption if I installed it?

@voiceflow/encryption 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 @voiceflow/encryption — how do I know if it already compromised me?

If @voiceflow/encryption 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 @voiceflow/encryption part of a known attack campaign?

Yes — @voiceflow/encryption is associated with the GHSA-wq75-fgvh-2wcg, RLMA-2025-06042 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 @voiceflow/encryption 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 @voiceflow/encryption (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @voiceflow/encryption across your stack and pipelines.

Malicious package

@voiceflow/encryptionnpm

Malicious code in @voiceflow/encryption (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191344

Immediate action

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

npm uninstall @voiceflow/encryption

What this malware does

The package @voiceflow/encryption 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

2 flagged

0.3.20.3.3

Indicators of compromise (SHA-256)

d5b71c1c6ed0e4211ba3519e6fe92a854ab59359003f2b8a486d3416837ed657

8e68877efa23e6b31d03284f035c338a1cf209c60950c3d571d9b4f276d4b6a3

13e58f7cdcdf3b87f5bbf111e42e13a1151626e495e15be73fc579109e397800

bfa1b509cc17b66efb49e3879bd0b221bd0fac297f8df87ab37581f95f1cee98

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

Campaign

GHSA-wq75-fgvh-2wcgRLMA-2025-06042

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @voiceflow/encryption-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