Malicious Code Vulnerability in sporting_donkey_z3n Package

sporting_donkey_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98944: Malicious code in sporting_donkey_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 sporting_donkey_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 floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the sporting_donkey_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The primary risk is that it allows unauthorized access to sensitive information and can lead to the proliferation of malicious packages in the npm registry, affecting developers and their applications.

How To Fix

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

npm uninstall sporting_donkey_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 sporting_donkey_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall sporting_donkey_z3n.

Conclusion

The sporting_donkey_z3n package poses a significant security risk due to its malicious code that modifies package metadata and proliferates unauthorized packages. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for sporting_donkey_z3n →

Share this vulnerability

FAQ

sporting_donkey_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to unauthorized access to sensitive information and the proliferation of malicious packages, potentially compromising the security of your application.

You should immediately uninstall the sporting_donkey_z3n package and monitor your application for any unusual behavior.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

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 sporting_donkey_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