Malicious Code Injection in working_sparrow_z3n Package

working_sparrow_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97407: Malicious code in working_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 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 working_sparrow_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. It is designed to automatically generate and publish derivative packages, which can lead to significant pollution of the npm registry and compromise the integrity of the software supply chain.

Vulnerability Detail

The vulnerability in the working_sparrow_z3n package originates from its association with the tea.xyz token reward campaign. This package contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, which can inflate developer reputation scores and lead to the proliferation of potentially harmful packages in the npm registry. This poses risks to developers and users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall working_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 working_sparrow_z3n package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The working_sparrow_z3n package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to update or remove this package to mitigate potential risks. Tools like Vulert can assist in monitoring for such vulnerabilities in your projects.

See every vulnerability recorded for working_sparrow_z3n →

Share this vulnerability

FAQ

The working_sparrow_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

If your application uses the working_sparrow_z3n package, it may be at risk of installing malicious code that can compromise your software and its dependencies.

You should remove the working_sparrow_z3n package from your project and update to a secure version if available.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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