Which versions of @vinnxcode/libsignal-node are malicious?

The following npm versions of @vinnxcode/libsignal-node are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @vinnxcode/libsignal-node if I installed it?

@vinnxcode/libsignal-node 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 @vinnxcode/libsignal-node — how do I know if it already compromised me?

If @vinnxcode/libsignal-node 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 @vinnxcode/libsignal-node part of a known attack campaign?

Yes — @vinnxcode/libsignal-node is associated with the GHSA-v9rv-pgqp-436h, IN-MAL-2026-013215, IN-MAL-2026-013315 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 @vinnxcode/libsignal-node 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 @vinnxcode/libsignal-node (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vinnxcode/libsignal-node across your stack and pipelines.

Malicious package

@vinnxcode/libsignal-nodenpm

@vinnxcode/libsignal-node is a confirmed malicious npm package (MAL-2026-11079) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @vinnxcode/libsignal-node (npm)

MAL-2026-11079

Immediate action

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

npm uninstall @vinnxcode/libsignal-node

What this malware does

Analysis of this package version surfaced no a static rule matches and no traced install-time or import-time behaviors indicating credential theft, exfiltration, dropper execution, silent-relay, backdoor, or self-propagation. The package name suggests a fork or re-publish of the libsignal-node Signal Protocol library under a personal scope; without concrete evidence of installer-harm mechanisms in the shipped code, no supply-chain attack fingerprint is present in this version.

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.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

c6cd5c2aff996c3ecaed23aa0fb0f0b63c2fc829c2c1689b0bc27136714c8ff8

92b886dd14e44e2d8c35f297283b6bf7eb3cc0e947d786130c5fd8976d7ebdc1

38571788b4e19d9c881bd6a516f5ea2d4da08195dad41e7eb06e09ac91e8de04

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

Campaign

GHSA-v9rv-pgqp-436hIN-MAL-2026-013215IN-MAL-2026-013315

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @vinnxcode/libsignal-node-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

Explore

All malware advisories How O3 detects malware Vulnerability database