Malicious Code Exfiltration in pf23727 Package

pf23727 Updated 21 Sep 2026

Summary

21/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16338: Malicious code in pf23727 (npm). Affects pf23727 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 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 pf23727 package is an npm library that, under normal circumstances, would serve a legitimate purpose in web development. However, it has been identified as containing malicious code that compromises user data. The package's main file, index.js, executes immediately upon import, which allows it to perform unauthorized actions such as reading cookies and sending sensitive information to a third-party server.

Vulnerability Detail

The vulnerability in the pf23727 package stems from embedded malicious code that reads document cookies and captures authenticated responses from the user's session. It issues a fetch request to '/profile' with credentials included, exfiltrating sensitive data to a hardcoded collector at a third-party service. This behavior poses a significant risk as it can lead to unauthorized access to user accounts and data breaches.

How To Fix

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

npm uninstall pf23727

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 prevent the execution of the pf23727 package by removing it from your dependencies and replacing it with a secure alternative that provides similar functionality without the risk of data exfiltration.

Conclusion

The pf23727 package poses a serious security risk due to its embedded malicious code that exfiltrates sensitive user data. Immediate action is required to remove this package and safeguard user information. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for pf23727 →

Share this vulnerability

FAQ

pf23727 is an npm package that has been identified to contain malicious code capable of exfiltrating sensitive user data.

The malicious code reads cookies and sends authenticated user data to a third-party server, compromising user privacy and security.

You should immediately remove the pf23727 package from your project and monitor for any unauthorized access to user accounts.

Currently, there is no patched version available. It is recommended to remove the package until a secure alternative is found.

You can use Vulert to monitor your application for open-source vulnerabilities in real-time. Vulert requires only the package-lock.json file to alert you about potential issues.

How To Fix

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

npm uninstall pf23727

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