Critical Malicious Code Vulnerability in @flexmr/utils Package

@flexmr/utils Updated 16 Oct 2026

Summary

14/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17888: Malicious code in @flexmr/utils (npm). Affects @flexmr/utils versions 1.0.0 – 3.0.12. 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 @flexmr/utils package is a utility library designed for use in JavaScript applications, providing various helper functions. However, version 3.0.12 of this package has been identified as containing malicious code that poses significant security risks to users. The package's dependency management is flawed, allowing unverified code to be executed during installation.

Vulnerability Detail

The vulnerability originates from the @flexmr/utils package version 3.0.12, which includes a re-export stub that fetches a dependency from a non-registry host. This dependency, 'daemon-thread-lookup-buffer', is unpinned and lacks an integrity hash, meaning that any code returned from the specified URL can be executed. This allows the operator of the external host to execute arbitrary code on the installer's machine, leading to potential data breaches or system compromise.

How To Fix

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

npm uninstall @flexmr/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

As a temporary workaround, avoid using the @flexmr/utils package until a secure version is released. If you must use it, consider isolating the installation in a controlled environment to mitigate risks.

Conclusion

The @flexmr/utils package version 3.0.12 contains a critical vulnerability that allows for the execution of malicious code from an untrusted source. Users are advised to update to a secure version as soon as possible and to consider using tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for @flexmr/utils →

Share this vulnerability

FAQ

The vulnerability allows malicious code execution from an untrusted source during the installation of the package.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring signup.

Check the package's repository for any updates or patches. If a patched version is available, update using npm install @flexmr/utils@latest.

As a workaround, avoid using the package or isolate its installation in a controlled environment to reduce risk.

Exploitation of this vulnerability can lead to unauthorized code execution, data breaches, and potential system compromise.

How To Fix

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

npm uninstall @flexmr/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