Malicious Code Injection in written_wombat_z3n Package

written_wombat_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92333: Malicious code in written_wombat_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 written_wombat_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. It is designed to facilitate various functionalities within applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts aimed at manipulating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the written_wombat_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the automatic publication of derivative packages. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall written_wombat_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 written_wombat_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The written_wombat_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry behavior. It is essential for developers to remove this package and monitor their dependencies closely to maintain application security.

See every vulnerability recorded for written_wombat_z3n →

Share this vulnerability

FAQ

The written_wombat_z3n package is an npm package that has been identified as part of a malicious campaign targeting developers by flooding the npm registry with harmful scripts.

This vulnerability can lead to the automatic publication of malicious packages, which may compromise your application's security and integrity.

If you have installed the written_wombat_z3n package, you should uninstall it immediately using the command npm uninstall written_wombat_z3n.

Regularly update your packages, use trusted sources, and employ tools like Vulert to monitor your dependencies for vulnerabilities.

Vulert is a tool that monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues without requiring code access or installation.

How To Fix

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

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