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

The following npm versions of @voiceflow/nestjs-common are flagged malicious: 2.75.2, 2.75.3. Treat any of these as compromised.

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

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

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

Yes — @voiceflow/nestjs-common is associated with the GHSA-2qr3-584r-qj9v, RLMA-2025-06043 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-common 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-common (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-common across your stack and pipelines.

Malicious package

@voiceflow/nestjs-commonnpm

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

MAL-2025-191357

Immediate action

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

npm uninstall @voiceflow/nestjs-common

What this malware does

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

2.75.22.75.3

Indicators of compromise (SHA-256)

c657ffb0f3bc111a9a16d2fb0611f7a596ea81886217e405112df3e40b90c23f

428ffa787448bac0d810e5e9958ed3ee642359b74d1fda2e3d424e48e4650414

d6d3635e3e4ea7fe67bd91fc10dbb52d16b29a74193117747292587c6fd1d5ef

2d1841327df9ad372b48355ac7ecb3e4f779ee61e6340076d9dd25257a2b6842

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

Campaign

GHSA-2qr3-584r-qj9vRLMA-2025-06043

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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