Critical Malicious Code Vulnerability in @opengov/ppf-eslint-config Package

@opengov/ppf-eslint-config Updated 22 Mar 2026

Summary

22/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2065: Malicious code in @opengov/ppf-eslint-config (npm). Affects @opengov/ppf-eslint-config versions 0.1.11. 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 @opengov/ppf-eslint-config package is a configuration tool for ESLint, designed to help developers maintain code quality and consistency in JavaScript projects. It provides a set of predefined rules and settings that can be easily integrated into projects. However, this package has been identified as containing malicious code, posing a significant risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @opengov/ppf-eslint-config package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it embeds harmful functionalities that can lead to severe security breaches.

How To Fix

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

npm uninstall @opengov/ppf-eslint-config

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 other than removing the package and ensuring that your system is secure. It is advisable to monitor your system for any signs of compromise.

Conclusion

The @opengov/ppf-eslint-config package has been identified as containing malicious code that poses a serious threat to system security. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @opengov/ppf-eslint-config →

Share this vulnerability

FAQ

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

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

Keeping this package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

No, there is currently no patched version available for this package. The best course of action is to remove it entirely.

Regularly monitor your dependencies using tools like Vulert to stay informed about vulnerabilities and ensure you are using trusted packages.

How To Fix

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

npm uninstall @opengov/ppf-eslint-config

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