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

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

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

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

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

Yes — @voiceflow/nestjs-timeout is associated with the GHSA-r967-g522-c8gc, RLMA-2025-06047 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-timeout 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-timeout (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-timeout across your stack and pipelines.

Malicious package

@voiceflow/nestjs-timeoutnpm

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

MAL-2025-191361

Immediate action

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

npm uninstall @voiceflow/nestjs-timeout

What this malware does

The package @voiceflow/nestjs-timeout 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)

18fea2b05812f1d6c2ac23811cb221150615f0200b05bdcbc8c75acf9aad7818

60a388993e1761687b5af14e707bdc4f71657b1a262d30aa650aa0cf8acf4d57

13d9067ab95136128bf92e8d28b434d340ae4fd7cd2c8e06f3378c71c3f6f2b1

e90895d2b22927389ed5e2d685fbdc4742a66419ebcc06bbcc0a8d3679466791

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-timeout (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-timeout across your stack and pipelines.
If you installed it — respond
@voiceflow/nestjs-timeout 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-timeout 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-timeout 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-timeout 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-r967-g522-c8gcRLMA-2025-06047

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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