Which versions of rullzdigital-libsignal are malicious?

Every published version of rullzdigital-libsignal on npm is considered malicious. Remove the package entirely.

How do I remediate rullzdigital-libsignal if I installed it?

Remove rullzdigital-libsignal 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 rullzdigital-libsignal — how do I know if it already compromised me?

If rullzdigital-libsignal 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 rullzdigital-libsignal part of a known attack campaign?

Yes — rullzdigital-libsignal is associated with the GHSA-jgfp-q988-vx26 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 rullzdigital-libsignal 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 rullzdigital-libsignal (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rullzdigital-libsignal across your stack and pipelines.

Malicious package

rullzdigital-libsignalnpm

Malicious code in rullzdigital-libsignal (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1155

Immediate action

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

npm uninstall rullzdigital-libsignal

What this malware does

The package rullzdigital-libsignal 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

c62dfaf6355fb28d2fb513459bd1a2b00f034296e98b05f2bf18a4745c3f941e

1bfc2bce31260b9826f9f3040d958f28d0229e8db4f0d7bec9bd9404f86fc5a4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rullzdigital-libsignal (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rullzdigital-libsignal across your stack and pipelines.
If you installed it — respond
Remove rullzdigital-libsignal 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 rullzdigital-libsignal 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 rullzdigital-libsignal 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. rullzdigital-libsignal on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jgfp-q988-vx26

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks rullzdigital-libsignal-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