Malicious Code Execution in pflag29424 Package

pflag29424 Updated 21 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16342: Malicious code in pflag29424 (npm). Affects pflag29424 versions 1.0.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 pflag29424 package is an npm module that lacks a README and documented purpose, making it difficult for users to understand its intended functionality. It is designed to execute code upon loading, which raises significant security concerns, particularly due to its behavior of relaying sensitive information to an external endpoint.

Vulnerability Detail

The vulnerability in the pflag29424 package arises from its unconditionally executing code on module load. Specifically, it fetches data from a '/profile' endpoint, scans for a DGA token, and sends either the token or the first 300 characters of the response to a hardcoded anonymous collector at a webhook.site URL. This behavior allows an attacker to capture sensitive information from the loading context, posing a severe risk to users who inadvertently include this package in their projects.

How To Fix

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

npm uninstall pflag29424

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 workaround, consider using a different package that provides similar functionality without the malicious behavior. Always review the code of third-party packages before including them in your project.

Conclusion

The pflag29424 package poses a significant security risk due to its malicious code that executes on load. Users are advised to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed about security updates is crucial for maintaining safe software practices.

See every vulnerability recorded for pflag29424 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that executes upon loading, which can relay sensitive information to an attacker-controlled endpoint.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner without any signup.

You should remove the pflag29424 package immediately and look for alternative packages that do not have known vulnerabilities.

As of now, there is no patch available for the pflag29424 package. It is recommended to remove it from your project.

The malicious code fetches data from a specified endpoint and sends sensitive information to an attacker-controlled webhook, compromising user data.

How To Fix

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

npm uninstall pflag29424

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