Malicious Code Vulnerability in developing_marmoset_z3n Package

developing_marmoset_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94013: Malicious code in developing_marmoset_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 developing_marmoset_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others in the npm registry, is intended to facilitate various functionalities for developers. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses a significant risk to the integrity of the npm registry and the developers relying on these packages.

Vulnerability Detail

The vulnerability in the developing_marmoset_z3n package originates from its association with a malicious token reward campaign. The package contains scripts designed to automatically modify its own package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially compromising the security and reliability of dependent projects. The malicious payload can affect developers by introducing untrusted code into their applications.

How To Fix

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

npm uninstall developing_marmoset_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 developing_marmoset_z3n package and replace it with a trusted alternative that provides similar functionality. Always review the dependencies of your project and ensure they are from reputable sources.

Conclusion

The developing_marmoset_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is essential to remove this package from your dependencies and monitor your projects for vulnerabilities using tools like Vulert. Staying informed and proactive is key to maintaining the security of your applications.

See every vulnerability recorded for developing_marmoset_z3n →

Share this vulnerability

FAQ

The developing_marmoset_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

This vulnerability can introduce untrusted code into your project, potentially compromising its security and reliability.

You should uninstall the developing_marmoset_z3n package immediately and replace it with a trusted alternative.

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 needing to sign up.

How To Fix

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

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