Malicious Code Injection in irrelevant_termite_z3n Package

irrelevant_termite_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104427: Malicious code in irrelevant_termite_z3n (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 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 irrelevant_termite_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a vehicle for autopublishing scripts that generate and publish derivative packages, often with randomized names, to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability stems from the malicious nature of the irrelevant_termite_z3n package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants, thereby polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to a broader campaign that exploits npm's publishing mechanisms for token rewards, leading to a significant risk of reputation damage and security breaches for developers.

How To Fix

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

npm uninstall irrelevant_termite_z3n

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, you can avoid using the irrelevant_termite_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like Vulert, which can monitor and alert you in real-time for open-source vulnerabilities in your software.

Conclusion

The irrelevant_termite_z3n package poses a significant risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package from their projects and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for irrelevant_termite_z3n →

Share this vulnerability

FAQ

irrelevant_termite_z3n is an npm package that is part of a malicious campaign to manipulate developer reputation scores through autopublishing scripts.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and affecting your reputation as a developer.

You should uninstall the irrelevant_termite_z3n package immediately and check your package-lock.json file for any references to it.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities. It requires only your package-lock.json file and provides real-time alerts.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall irrelevant_termite_z3n

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