Malicious Code Detected in flag-v211 Package - Security Alert

flag-v211 Updated 16 Jan 2026

Summary

16/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-284: Malicious code in flag-v211 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The flag-v211 package is an npm library commonly used in JavaScript applications for flagging features or configurations. It is designed to provide developers with a simple way to manage feature flags, enabling or disabling features in a controlled manner. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the flag-v211 package, which has been found to contain malicious code. This malicious code can potentially compromise the security of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The issue is particularly concerning as it affects all versions of the package, starting from version 0, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall flag-v211

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 replace the flag-v211 package with an alternative feature flag management library that does not have known vulnerabilities. Ensure to review the documentation of the alternative library for proper implementation.

Conclusion

The flag-v211 package has been identified as containing malicious code, which poses significant risks to applications that utilize it. Immediate action is required to remove this package and safeguard your application from potential threats. Regular monitoring for vulnerabilities using tools like Vulert is recommended to maintain application security.

See every vulnerability recorded for flag-v211 →

Share this vulnerability

FAQ

The flag-v211 package is used for managing feature flags in JavaScript applications, allowing developers to enable or disable features dynamically.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected. You can also check using the Vulert playground without signup.

It is advised to remove the flag-v211 package from your project immediately, as it contains malicious code that poses security risks.

Currently, there is no patched version available for the flag-v211 package. The best course of action is to remove it from your project.

Using the flag-v211 package can lead to unauthorized access, data breaches, and other malicious activities due to the presence of malicious code.

How To Fix

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

npm uninstall flag-v211

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