Critical Malicious Code Vulnerability in francium-utils Package

francium-utils Updated 13 Jan 2026

Summary

13/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-242: Malicious code in francium-utils (npm). Affected versions are not published. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The francium-utils package is a utility library designed for various functionalities in JavaScript applications, particularly within the npm ecosystem. It is commonly used by developers to streamline tasks and enhance productivity. However, this package has been identified as containing malicious code, which poses a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the francium-utils package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. Once installed, the package grants full control of the affected computer to an external entity, making it imperative for users to act swiftly to mitigate potential damage.

How To Fix

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

npm uninstall francium-utils

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

Currently, there are no effective workarounds to mitigate the risks posed by this malicious package other than complete removal. It is essential to monitor your system for any unusual activity following the uninstallation.

Conclusion

The discovery of malicious code within the francium-utils package highlights the importance of vigilance in managing open-source dependencies. Users must act quickly to remove the package and secure their systems to prevent potential exploitation.

See every vulnerability recorded for francium-utils →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall francium-utils' and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Keeping this package installed can lead to unauthorized access to your system, potentially compromising sensitive data and allowing malicious actors to control your computer.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

While many npm packages are safe, it's crucial to verify the integrity of packages before installation and to stay informed about vulnerabilities.

How To Fix

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

npm uninstall francium-utils

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