Malicious Code Detected in n8n-nodes-text-helpers Package - Version 0.2.0

n8n-nodes-text-helpers Updated 16 Mar 2026

Summary

15/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1454: Malicious code in n8n-nodes-text-helpers (npm). Affects n8n-nodes-text-helpers versions 0.1.0 – 0.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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The n8n-nodes-text-helpers package is a utility library designed for use with the n8n workflow automation tool. It provides various text manipulation functions that enhance the capabilities of n8n workflows. However, the package has been flagged for containing malicious code that executes harmful commands, posing a significant security risk to users.

Vulnerability Detail

The vulnerability in the n8n-nodes-text-helpers package arises from its malicious behavior, which includes executing commands that could compromise the security of the system. This issue was identified by the OpenSSF Package Analysis project, which flagged version 0.2.0 as malicious. The potential ramifications include unauthorized access to sensitive data, system instability, and exploitation of the affected systems by malicious actors.

How To Fix

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

npm uninstall n8n-nodes-text-helpers

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

If you cannot immediately update the package, consider removing it from your project until a secure version is available. You can do this by running:

npm uninstall n8n-nodes-text-helpers

Conclusion

The n8n-nodes-text-helpers package has been identified as malicious, particularly in version 0.2.0. Users are advised to update to version 0.3.0 or uninstall the package to protect their systems from potential threats. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for n8n-nodes-text-helpers →

Share this vulnerability

FAQ

It is a utility library for the n8n workflow automation tool that provides text manipulation functions.

Versions 0.1.0, 0.2.0, and 0.3.0 have been flagged, with 0.2.0 being specifically identified as malicious.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Consider uninstalling the package until a secure version is available to mitigate the risk.

The vulnerability was identified by the OpenSSF Package Analysis project.

How To Fix

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

npm uninstall n8n-nodes-text-helpers

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