Malicious Code Injection in slight_spider_z3n: A Threat to npm Ecosystem

slight_spider_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96618: Malicious code in slight_spider_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'slight_spider_z3n' is part of a malicious campaign targeting the npm ecosystem, primarily associated with the tea.xyz token reward initiative. This package is designed to manipulate npm's registry by creating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'slight_spider_z3n' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security and reliability of applications that depend on these packages. The malicious scripts included (auto.js, autopublish.js, etc.) are designed to automate this process, making it difficult for developers to track and mitigate the impact.

How To Fix

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

npm uninstall slight_spider_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 'slight_spider_z3n' package and replace it with a trusted alternative that provides similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'slight_spider_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 remove this package from their projects and monitor their dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for slight_spider_z3n →

Share this vulnerability

FAQ

'slight_spider_z3n' is a malicious npm package designed to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application and compromising its security.

You should uninstall the 'slight_spider_z3n' package immediately and check your project for any references to it in your package.json and package-lock.json files.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Yes, tools like npm audit and Vulert can help identify and alert you to vulnerabilities in your dependencies, including malicious packages.

How To Fix

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

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