Which versions of @voiceflow/nestjs-redis are malicious?

The following npm versions of @voiceflow/nestjs-redis are flagged malicious: 1.3.1, 1.3.2. Treat any of these as compromised.

How do I remediate @voiceflow/nestjs-redis if I installed it?

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

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

Yes — @voiceflow/nestjs-redis is associated with the GHSA-7gf9-4m37-59gv, RLMA-2025-06046 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/nestjs-redis 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/nestjs-redis (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/nestjs-redis across your stack and pipelines.

Malicious package

@voiceflow/nestjs-redisnpm

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

MAL-2025-191360

Immediate action

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

npm uninstall @voiceflow/nestjs-redis

What this malware does

The package @voiceflow/nestjs-redis 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.3.11.3.2

Indicators of compromise (SHA-256)

ed0db91b5558169b25608f2133c191029a65d8e854af04e97b53b4527793f8cc

e869e31dcb6b391d09ca3440fc46d1800bbcc7102777cc142b362c859b554dbe

e418bb230f36e6cbd5feaa2ec800cf58fa1e701bcf7b8fd1dd8806223a94c645

a1dd1999cfadd49512af4f914457c43b17c21481c0e7ba09534e960226f0fc07

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

Campaign

GHSA-7gf9-4m37-59gvRLMA-2025-06046

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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