Malicious Code Vulnerability in focaleys Package

focaleys Updated 30 Sep 2026

Summary

30/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17329: Malicious code in focaleys (npm). Affects focaleys versions 1.1.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The focaleys package is an npm library designed for specific functionalities within JavaScript applications. It allows developers to integrate various features seamlessly. However, it has been identified to have a critical vulnerability due to its dependency management, which can lead to the execution of unverified code during installation.

Vulnerability Detail

The vulnerability arises from the focaleys package declaring a dependency on 'libsignal' from a GitHub repository without specifying a version, tag, or commit SHA. This means that when users install focaleys, the package manager fetches the latest code from the default branch of the repository, which can be altered by the repository owner at any time. This lack of integrity checks allows malicious code to be executed on the installer's machine, posing significant security risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall focaleys

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can manually install a specific version of the libsignal dependency that you trust. Use the following command to install a specific version: npm install libsignal@<trusted_version>. Replace <trusted_version> with the version number you wish to install.

Conclusion

The focaleys package has a significant vulnerability due to its dependency management practices, allowing for the potential execution of malicious code. It is crucial to update the package or implement workarounds to mitigate risks. Regular monitoring using tools like Vulert can help maintain security in your applications.

See every vulnerability recorded for focaleys →

Share this vulnerability

FAQ

Focaleys is an npm package used in JavaScript applications for various functionalities, but it has a vulnerability related to its dependency management.

The vulnerability allows unverified code to run on your machine during the installation of the focaleys package, which can lead to security breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

If you cannot update the package, consider using a specific version of the libsignal dependency that you trust as a temporary workaround.

For more information, you can reach out to Amazon Inspector at inspector-research@amazon.com.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall focaleys

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback