Malicious Code Detected in eslint-config-pexip-engage Package - Version 1.3.0

eslint-config-pexip-engage Updated 28 Dec 2025

Summary

28/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192955: Malicious code in eslint-config-pexip-engage (npm). Affects eslint-config-pexip-engage versions 1.3.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

eslint-config-pexip-engage is an npm package designed to provide a set of ESLint configurations tailored for Pexip Engage projects. It helps developers maintain code quality and consistency by enforcing coding standards. However, version 1.3.0 of this package has been identified as malicious, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the package's communication with a domain associated with malicious activity. This behavior can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The OpenSSF Package Analysis project flagged this package as malicious due to its harmful interactions, which could compromise the integrity and security of applications relying on it.

How To Fix

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

npm uninstall eslint-config-pexip-engage

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 avoid using the eslint-config-pexip-engage package until a secure version is released. Additionally, consider using alternative ESLint configurations that do not pose security risks.

Conclusion

The eslint-config-pexip-engage package version 1.3.0 has been flagged as malicious due to its communication with harmful domains. It is essential to uninstall this version and update to a secure alternative to protect your application from potential threats. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for eslint-config-pexip-engage →

Share this vulnerability

FAQ

It is an npm package that provides ESLint configurations for Pexip Engage projects, helping maintain code quality.

Version 1.3.0 communicates with a domain linked to malicious activities, posing security risks to applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Uninstall the affected version and update to a safe version using npm commands provided in the 'how_to_fix' section.

Yes, consider using other ESLint configuration packages that do not have known vulnerabilities.

How To Fix

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

npm uninstall eslint-config-pexip-engage

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