Malicious Code Vulnerability in local_termite_z3n Package

local_termite_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95302: Malicious code in local_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 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 local_termite_z3n package is part of the npm ecosystem, commonly used for JavaScript development. It is designed to facilitate various functionalities within applications. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to potential security risks for developers and their projects.

Vulnerability Detail

The vulnerability in the local_termite_z3n package stems from its involvement in a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts that automatically modify package.json files, removing private flags and changing version numbers. They generate random package names, which can lead to pollution of the npm registry and compromise the integrity of the development environment. The malicious payload can inflate developer reputation scores fraudulently, posing risks to the security and reliability of applications that depend on this package.

How To Fix

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

npm uninstall local_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 temporary workaround, you can avoid using the local_termite_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using Vulert to receive real-time alerts for any open-source vulnerabilities.

Conclusion

The local_termite_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for local_termite_z3n →

Share this vulnerability

FAQ

The local_termite_z3n package is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the pollution of the npm registry, compromise the integrity of your project, and inflate developer reputation scores fraudulently.

You should uninstall the local_termite_z3n package immediately using the command npm uninstall local_termite_z3n.

Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time.

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 local_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