Malicious Code Injection in original_lemur_z3n Package

original_lemur_z3n Updated 19 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-122419: Malicious code in original_lemur_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 original_lemur_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through automated publishing scripts. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability in the original_lemur_z3n package stems from its inclusion in a series of malicious packages that flood the npm registry. These packages are designed to manipulate the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry and may compromise the security of applications using this package, as it can introduce untrusted code into the dependency tree.

How To Fix

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

npm uninstall original_lemur_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 original_lemur_z3n package altogether. If it is already included in your project, consider replacing it with a trusted alternative or removing it from your dependencies.

Conclusion

The original_lemur_z3n package poses a significant security risk due to its malicious code that alters package configurations and can lead to untrusted code being executed. It is crucial to remove this package and monitor for updates to ensure the security of your applications.

See every vulnerability recorded for original_lemur_z3n →

Share this vulnerability

FAQ

The original_lemur_z3n package is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, potentially introducing untrusted code and compromising the security of your application.

You should remove the original_lemur_z3n package from your project and monitor for any updates or patches that may address the vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Vulert is a tool that uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software, helping you maintain secure applications.

How To Fix

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

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.