Which versions of @voiceflow/utils-designer are malicious?

The following npm versions of @voiceflow/utils-designer are flagged malicious: 1.74.19, 1.74.20. Treat any of these as compromised.

How do I remediate @voiceflow/utils-designer if I installed it?

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

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

Yes — @voiceflow/utils-designer is associated with the GHSA-vqr4-cfjx-rx6h, RLMA-2025-06049 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/utils-designer 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/utils-designer (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/utils-designer across your stack and pipelines.

Malicious package

@voiceflow/utils-designernpm

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

MAL-2025-191381

Immediate action

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

npm uninstall @voiceflow/utils-designer

What this malware does

The package @voiceflow/utils-designer 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.74.191.74.20

Indicators of compromise (SHA-256)

fa50493ee20a8966ee9eaa43ae148ba74b64eb06cb6bbd23de0b1a734c5f410f

2d83852017d65f3a25b666647c727aaa3aa5db8f3916196a20d92b476e0e8f13

dd23d42a3174f52e911f89321bb49bb905950bd3292f91a6fe3a8eb16b858948

f52d554a1e1ed27662bf63d463fde0831d5fe00b79b02f00efe5bc18a8617c2f

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/utils-designer (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/utils-designer across your stack and pipelines.
If you installed it — respond
@voiceflow/utils-designer 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/utils-designer 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/utils-designer 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/utils-designer on npm has been identified as a malicious package (versions 1.74.19, 1.74.20 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vqr4-cfjx-rx6hRLMA-2025-06049

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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