Critical Malicious Code Vulnerability in pulse-feature-flag Package

pulse-feature-flag Updated 23 Mar 2026

Summary

23/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2092: Malicious code in pulse-feature-flag (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 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 pulse-feature-flag package is an npm library designed to manage feature flags in applications, allowing developers to enable or disable features dynamically. However, this package has been compromised, embedding malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the pulse-feature-flag package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall pulse-feature-flag

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

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the package and secure the system.

Conclusion

The pulse-feature-flag package has been compromised with malicious code, posing serious security risks. Immediate removal of the package and rotation of sensitive information are essential steps to mitigate the impact of this vulnerability. Regular monitoring of dependencies is recommended to prevent future issues.

See every vulnerability recorded for pulse-feature-flag →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit the Vulert playground at Vulert Scanner to check your application without any signup.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to minimize risks.

Immediately rotate any secrets and keys that were stored on the affected computer to ensure security.

How To Fix

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

npm uninstall pulse-feature-flag

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