Which versions of @lovenight/voice are malicious?

The following npm versions of @lovenight/voice are flagged malicious: 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate @lovenight/voice if I installed it?

Remove @lovenight/voice from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @lovenight/voice — how do I know if it already compromised me?

If @lovenight/voice was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @lovenight/voice part of a known attack campaign?

Yes — @lovenight/voice is associated with the RLMA-2026-04753, RLUA-2026-05884 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 @lovenight/voice across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @lovenight/voice (5 malicious versions).

Malicious package

@lovenight/voicenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@lovenight/voice is a confirmed malicious npm package (MAL-2026-7082) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @lovenight/voice (npm)

MAL-2026-7082

Immediate action

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

npm uninstall @lovenight/voice

Malicious versions

5 flagged

1.0.11.0.21.0.31.0.41.0.5

Indicators of compromise (SHA-256)

d3b9ce8c63cd4e6d56ce3b4cbf2debeffb56a4fcd406057c1c99aee03f5eee64

3e6b06df05f41df755bece29b61d36f081878d403aa6f24267df7eb0650be804

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @lovenight/voice (5 malicious versions).
If you installed it — respond
Remove @lovenight/voice from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @lovenight/voice was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @lovenight/voice on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04753RLUA-2026-05884

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @lovenight/voice-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database