Which versions of @voiceflow/slate-serializer are malicious?

The following npm versions of @voiceflow/slate-serializer are flagged malicious: 1.7.3, 1.7.4. Treat any of these as compromised.

How do I remediate @voiceflow/slate-serializer if I installed it?

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

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

Yes — @voiceflow/slate-serializer is associated with the GHSA-vh49-8mp2-7r75 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/slate-serializer 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/slate-serializer (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/slate-serializer across your stack and pipelines.

Malicious package

@voiceflow/slate-serializernpm

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

MAL-2025-191374

Immediate action

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

npm uninstall @voiceflow/slate-serializer

What this malware does

The package @voiceflow/slate-serializer 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.7.31.7.4

Indicators of compromise (SHA-256)

aea5a1f3911c4172771ade7734b8b38146f3c86c5c61507d8f5b7ff4c2fdbff2

5ece4f585c5758411f8e2ef4ac8a3916f3824a3139a7f9f59b723e8e167600c0

cb7716bab0bde17a29c041cd61a934d39d4717019743671e8d6164fd166c0bdc

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

Campaign

GHSA-vh49-8mp2-7r75

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @voiceflow/slate-serializer-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