Which versions of capacitor-voice-recorder-wav are malicious?

The following npm versions of capacitor-voice-recorder-wav are flagged malicious: 6.0.3. Treat any of these as compromised.

How do I remediate capacitor-voice-recorder-wav if I installed it?

capacitor-voice-recorder-wav 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 capacitor-voice-recorder-wav — how do I know if it already compromised me?

If capacitor-voice-recorder-wav 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 capacitor-voice-recorder-wav part of a known attack campaign?

Yes — capacitor-voice-recorder-wav is associated with the GHSA-hpp4-86hx-9h3c 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 capacitor-voice-recorder-wav 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 capacitor-voice-recorder-wav (version 6.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging capacitor-voice-recorder-wav across your stack and pipelines.

Malicious package

capacitor-voice-recorder-wavnpm

Malicious code in capacitor-voice-recorder-wav (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190921

Immediate action

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

npm uninstall capacitor-voice-recorder-wav

What this malware does

The package capacitor-voice-recorder-wav 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

1 flagged

6.0.3

Indicators of compromise (SHA-256)

15d039d86e89d2e74c80f640d3c4dc358a5e3fc0b972d07a1d08b9c5dee3dad9

83d55589d95fe71e08f771d3013a241dc2aa72703e3241190af4821ec24370a7

5a357996e5d0361a2da975469d261483ac0f4700b7edd0cbdb9d5bf5fae0bc6c

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 capacitor-voice-recorder-wav (version 6.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging capacitor-voice-recorder-wav across your stack and pipelines.
If you installed it — respond
capacitor-voice-recorder-wav 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 capacitor-voice-recorder-wav 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 capacitor-voice-recorder-wav 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. capacitor-voice-recorder-wav on npm has been identified as a malicious package (version 6.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hpp4-86hx-9h3c

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks capacitor-voice-recorder-wav-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