MalwarePublished 30 Sep 2026

focaleys (npm) · Malicious Code

Affects focaleysSource GCVE Database

Malicious package : remove focaleys and rotate any secrets on hosts that installed it.

Data as of 30 Sep 2026, 16:35 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-17329

What to do

Remove focaleys from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmfocaleys	Affected =1.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package 'focaleys' version 1.1.0 declares a dependency on 'libsignal' via a GitHub repository reference without specifying a fixed tag, version, or commit SHA. This means that on installation, the dependency resolves to the current default branch HEAD of the repository, executing any lifecycle scripts present there on the installer's machine. Control of the GitHub account 'rexxzyid' thus allows an attacker to run arbitrary code during installation of 'focaleys', potentially changing silently between installs without modifying the 'focaleys' package itself.

Impact

An attacker controlling the 'rexxzyid' GitHub account can execute arbitrary code on any system installing 'focaleys' version 1.1.0. This can lead to compromise of the installer's environment, data theft, or further malware deployment. The threat arises from the unpinned dependency allowing silent and dynamic code changes at install time.

Defensive guidance

Users should avoid installing 'focaleys' version 1.1.0 or audit and pin dependencies to fixed commit SHAs or version tags to prevent dynamic code execution from untrusted sources. Monitor the dependency declarations and avoid dependencies that resolve to mutable branches without integrity checks.

Summary

The 'focaleys' npm package version 1.1.0 depends on 'libsignal' using a GitHub URL without a fixed commit or tag, causing the dependency to resolve dynamically to the latest default branch commit. This dynamic resolution allows whoever controls the 'rexxzyid' GitHub account to execute arbitrary code during the npm install lifecycle scripts on any machine installing 'focaleys'. Because the dependency is not pinned, malicious code can be introduced or changed without any change to the 'focaleys' package itself, creating a supply chain risk.

References

npmjs.com/package/focaleys/v/1.1.0 (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Sep 2026, 16:35 UTC

Technical details

References

Community reviews