Which versions of @voiceflow/exception are malicious?

The following npm versions of @voiceflow/exception are flagged malicious: 1.10.1, 1.10.2. Treat any of these as compromised.

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

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

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

Yes — @voiceflow/exception is associated with the GHSA-q7cp-f4mj-8m39 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/exception across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @voiceflow/exception (2 malicious versions).

Part of a larger attack: @voiceflow published 57 malicious packages. See the full campaign →

Malicious package

@voiceflow/exceptionnpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

@voiceflow/exception is a confirmed malicious npm package (MAL-2025-191347) that steals credentials and exfiltrates sensitive data (malicious versions 1.10.1, 1.10.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @voiceflow/exception (npm)

MAL-2025-191347

Immediate action

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

npm uninstall @voiceflow/exception

What this malware does

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

1.10.11.10.2

Indicators of compromise (SHA-256)

29530e3509a532ae386aab9a3f781c63a749ff235406e6e7ea1de3b36a163969

3494a264b1e2c6d06676dbfdaa8b0d8062dbc63b6f8566e534767d285b735727

2eb8d68b66e59da1a4b42db0ac46ad31c940a051f6d6da86d55cd0ad7ac3f33b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @voiceflow/exception (2 malicious versions).
If you installed it — respond
@voiceflow/exception 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/exception 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. @voiceflow/exception on npm has been identified as a malicious package (versions 1.10.1, 1.10.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-q7cp-f4mj-8m39

References

Credits

Amazon Inspector · finder

Detect & block this

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