Malicious Code Injection in mass_sparrow_z3n Package

mass_sparrow_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105651: Malicious code in mass_sparrow_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 mass_sparrow_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. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the mass_sparrow_z3n package stems from its inclusion in a series of malicious packages that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages. The origin of this issue is linked to a broader campaign aimed at exploiting the npm ecosystem for token rewards.

How To Fix

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

npm uninstall mass_sparrow_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 mass_sparrow_z3n package and any other packages associated with the tea.xyz token reward campaign. Additionally, you can monitor your project for any unauthorized changes to the package.json file.

Conclusion

The mass_sparrow_z3n package poses a significant security risk due to its malicious code that modifies package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their projects for any unauthorized changes.

See every vulnerability recorded for mass_sparrow_z3n →

Share this vulnerability

FAQ

mass_sparrow_z3n is an npm package that is part of a campaign to generate and publish derivative packages for token rewards, but it has been identified as containing malicious code.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's integrity and security.

You should immediately uninstall the mass_sparrow_z3n package from your project to mitigate any risks associated with its use.

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 also check if your application is affected by this vulnerability using the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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