Critical Malicious Code Vulnerability in n8n-nodes-performance-metrics Package

Summary

06/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-68: Malicious code in n8n-nodes-performance-metrics (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The n8n-nodes-performance-metrics package is a Node.js library designed to enhance performance metrics for n8n workflows. It provides various functionalities to track and analyze performance data effectively. However, this package has been compromised, leading to significant security concerns for users who have it installed.

Vulnerability Detail

This vulnerability stems from the presence of malicious code within the n8n-nodes-performance-metrics package. Any system running this package is considered fully compromised, with potential unauthorized access to sensitive information such as secrets and keys. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall n8n-nodes-performance-metrics

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, users should uninstall the affected package using the command: npm uninstall n8n-nodes-performance-metrics. Additionally, ensure that all sensitive data is secured and rotated to prevent unauthorized access.

Conclusion

The n8n-nodes-performance-metrics package has been identified as containing malicious code, posing a significant risk to users. Immediate action is required to mitigate potential damage, including uninstalling the package and securing sensitive information. Users should remain vigilant and utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for n8n-nodes-performance-metrics →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on your system.

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

Currently, there is no patched version available. Users are advised to uninstall the package.

Failure to address this vulnerability can lead to unauthorized access to sensitive information and complete control of your system by malicious actors.

It is advisable to monitor updates and community feedback before considering reinstallation, as the package has been compromised.

How To Fix

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

npm uninstall n8n-nodes-performance-metrics

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