Which versions of @voiceflow/runtime are malicious?

The following npm versions of @voiceflow/runtime are flagged malicious: 1.29.1, 1.29.2. Treat any of these as compromised.

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

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

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

Yes — @voiceflow/runtime is associated with the GHSA-59v7-979j-g8cq 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/runtime across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

@voiceflow/runtimenpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

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

Malicious code in @voiceflow/runtime (npm)

MAL-2025-191368

Immediate action

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

npm uninstall @voiceflow/runtime

What this malware does

The package @voiceflow/runtime 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.29.11.29.2

Indicators of compromise (SHA-256)

e38ce9aae399766131c5f6c13567f72c832d973a3ebbc400569d64b281601cbe

96ac1a5b177a6b6ee4c5b9ea6be2b709f6b9bfd03ed7ad00da9695a1c9f65738

6a8c6b88ad67d8ceece37df9641f6712f7047aa566957d0937eb3ca99aed10dd

Detection & response playbook

Credential / info stealer

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

Campaign

GHSA-59v7-979j-g8cq

References

Credits

Amazon Inspector · finder

Detect & block this

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