Which versions of @voiceflow/nestjs-rate-limit are malicious?

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

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

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

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

Yes — @voiceflow/nestjs-rate-limit is associated with the RLMA-2025-06045 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-rate-limit 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-rate-limit (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-rate-limit across your stack and pipelines.

Malicious package

@voiceflow/nestjs-rate-limitnpm

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

MAL-2025-191359

Immediate action

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

npm uninstall @voiceflow/nestjs-rate-limit

What this malware does

The package @voiceflow/nestjs-rate-limit was found to contain malicious code.

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.21.3.3

Indicators of compromise (SHA-256)

e09d6d3e57ab2c60d4d2f1fe979ac9f4d6f454f26c5c7e4ccedf5428a52b1973

3a0dac1431983489842c368c5db298d65dc30278340ee47cf01c5fb3fc2f178b

ba9355c84f3f3ab2edb94697a41736a2ff1d8b6a6728300d6e96e4a1101ae2da

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

Campaign

RLMA-2025-06045

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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