Malicious Code Injection in ltd_slug_z3n: A Threat to npm Ecosystem

ltd_slug_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95335: Malicious code in ltd_slug_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'ltd_slug_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in 'ltd_slug_z3n' originates from its association with the tea.xyz token reward campaign, which has led to the creation of numerous malicious packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially leading to security risks for applications that depend on them.

How To Fix

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

npm uninstall ltd_slug_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 monitor your dependencies using tools like Vulert, which can help identify vulnerabilities in your package-lock.json file. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.

Conclusion

The 'ltd_slug_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity and security of their applications.

See every vulnerability recorded for ltd_slug_z3n →

Share this vulnerability

FAQ

The 'ltd_slug_z3n' package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your application's dependencies, potentially introducing security risks.

You should uninstall the package immediately using 'npm uninstall ltd_slug_z3n' to mitigate any risks associated with its use.

Yes, tools like Vulert can monitor your package-lock.json file for vulnerabilities and provide real-time alerts.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

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