Malicious Code Injection in evil_basilisk_z3n: A Threat to npm Packages

evil_basilisk_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94321: Malicious code in evil_basilisk_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 package 'evil_basilisk_z3n' is part of a broader campaign targeting npm users, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a tool for malicious actors looking to exploit the npm ecosystem.

Vulnerability Detail

The vulnerability in 'evil_basilisk_z3n' stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.

How To Fix

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

npm uninstall evil_basilisk_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 measure, avoid using any packages that are part of the tea.xyz token reward campaign. Regularly audit your package.json and package-lock.json files for any suspicious entries or dependencies.

Conclusion

The 'evil_basilisk_z3n' package poses a significant threat to the npm ecosystem due to its malicious intent to manipulate package publishing and developer reputation. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects are secure.

See every vulnerability recorded for evil_basilisk_z3n →

Share this vulnerability

FAQ

'evil_basilisk_z3n' is an npm package involved in a malicious campaign aimed at manipulating the npm registry and inflating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, security risks from using compromised packages, and potential damage to your project's reputation.

Immediately uninstall the 'evil_basilisk_z3n' package using 'npm uninstall evil_basilisk_z3n' and audit your other dependencies.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It requires only your package-lock.json file and no installation.

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

How To Fix

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

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