Which versions of @voiceflow/secrets-provider are malicious?

The following npm versions of @voiceflow/secrets-provider are flagged malicious: 1.9.2, 1.9.3. Treat any of these as compromised.

How do I remediate @voiceflow/secrets-provider if I installed it?

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

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

Yes — @voiceflow/secrets-provider is associated with the GHSA-9532-2xg7-9jgr, RLMA-2025-06048 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/secrets-provider 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/secrets-provider (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/secrets-provider across your stack and pipelines.

Malicious package

@voiceflow/secrets-providernpm

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

MAL-2025-191371

Immediate action

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

npm uninstall @voiceflow/secrets-provider

What this malware does

The package @voiceflow/secrets-provider 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.9.21.9.3

Indicators of compromise (SHA-256)

9c9b5b7c5b0955ae68b0991b5bc093c217ebb06624db4b9e614225f50d0e62aa

fac6ac78376cffc549c5ee71255eb6113be55f3578d7eedb8f9ad64065432246

527df6a20822831f2bc2435e1db61fcc192d163d6a81240078e8e93066dc1235

57472e6423cf0d0919ac205a7dcda844be28eff8fdd455fa68d49f49f50050d1

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

Campaign

GHSA-9532-2xg7-9jgrRLMA-2025-06048

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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