Malicious Code Injection in lost_mite_z3n: A Threat to npm Ecosystem

lost_mite_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95317: Malicious code in lost_mite_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'lost_mite_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'lost_mite_z3n' originates from its involvement in a campaign that floods the npm registry with malicious packages. The package includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and users relying on npm packages.

How To Fix

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

npm uninstall lost_mite_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 measure, you can prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that you do not include 'lost_mite_z3n' in your dependencies. Additionally, consider using Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'lost_mite_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remove this package from their projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate the risks associated with such vulnerabilities.

See every vulnerability recorded for lost_mite_z3n →

Share this vulnerability

FAQ

'lost_mite_z3n' is an npm package associated with a token reward campaign that has been identified as malicious.

The vulnerability can lead to the pollution of the npm registry, affecting the integrity of your project's dependencies and potentially introducing security risks.

You should uninstall the package immediately using 'npm uninstall lost_mite_z3n' and check for any other affected packages.

Currently, there is no patched version available for 'lost_mite_z3n'. It is recommended to remove the package entirely.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check your application.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall lost_mite_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