npm package report

Is @saazkira/libsignal-node safe?

Confirmed malicious. Do not install it, and remove it where it has been installed.

Do not install this package

CRITICAL

Malicious package. Added to CyberXYZ 2026-10-12, OSV malicious-package feed (Google / OpenSSF).

// what we observed

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.

Reported by GitHub Advisory Database via OSV.

// versions and what to do

Malicious: all versions

Remove it from every machine and lockfile it reached. Treat any credentials, tokens and SSH keys present on those machines as exposed and rotate them. Check CI runners and container images that installed it.

npm uninstall @saazkira/libsignal-node

OSV record

// reach

0 direct dependencies

none carry a known advisory

0 packages depend on it

an advisory here reaches each of them

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-10-30 at 19:38 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.