Malicious Code Injection in Parental Lemming Z3N Package

parental_lemming_z3n Updated 19 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-122444: Malicious code in parental_lemming_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 'parental_lemming_z3n' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that alters its own package configuration.

Vulnerability Detail

The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The malicious payload can compromise the integrity of the npm ecosystem by flooding it with numerous variants of the package, potentially affecting other developers and users relying on npm for secure package management.

How To Fix

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

npm uninstall parental_lemming_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 'parental_lemming_z3n' package altogether. If you have dependencies that require it, consider looking for alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'parental_lemming_z3n' package contains malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any updates or alternatives. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for parental_lemming_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can compromise your project's integrity by polluting the npm registry and potentially introducing security risks.

You should uninstall the package immediately and look for alternatives to avoid any security risks.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall parental_lemming_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.