Critical Malicious Code Vulnerability in pyrefly Package

pyrefly Updated 13 Feb 2026

Summary

13/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-887: Malicious code in pyrefly (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 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 pyrefly package is an npm library that is utilized for various functionalities in JavaScript applications. It is designed to enhance development efficiency by providing reusable components. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations using it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the pyrefly 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 ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall pyrefly

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

Currently, there are no effective workarounds to mitigate the risks posed by the pyrefly package. The only recommended action is to uninstall the package and rotate any secrets or keys that may have been compromised.

Conclusion

The pyrefly package has been identified as containing malicious code that poses a serious security risk. Users are strongly advised to uninstall the package and take necessary precautions to secure their systems. Continuous monitoring for updates and potential patches is essential to mitigate risks associated with this vulnerability.

See every vulnerability recorded for pyrefly →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Leaving pyrefly installed poses significant risks, including unauthorized access to sensitive data and potential data breaches.

The best recovery method is to remove the package and rotate any compromised secrets or keys. There is no guarantee that all malicious software will be removed by simply uninstalling the package.

As of now, there is no patch available for the pyrefly package. Users should monitor updates from the package maintainers for any future fixes.

How To Fix

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

npm uninstall pyrefly

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