Malicious Code Injection in silent_lemur_z3n: A Threat to npm Packages

silent_lemur_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108670: Malicious code in silent_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 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 silent_lemur_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code among developers. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in silent_lemur_z3n originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of other packages. This can lead to security risks for applications relying on affected packages, as they may inadvertently use compromised versions.

How To Fix

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

npm uninstall silent_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 silent_lemur_z3n package and any other packages associated with the tea.xyz campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The silent_lemur_z3n package poses a significant risk due to its malicious code designed to exploit the npm registry. It is essential for developers to remove this package and stay vigilant by monitoring their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications without requiring code access or installation.

See every vulnerability recorded for silent_lemur_z3n →

Share this vulnerability

FAQ

silent_lemur_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the use of compromised packages, which may introduce security risks and instability in your application.

You should uninstall the package immediately using the command 'npm uninstall silent_lemur_z3n' and audit your project for any other affected packages.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

There is no patch available for silent_lemur_z3n; the recommended action is to uninstall the package.

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