Malicious Code Injection in armed_ocelot_z3n: A Threat to npm Packages

armed_ocelot_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99604: Malicious code in armed_ocelot_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

armed_ocelot_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in armed_ocelot_z3n originates from its design to execute autopublish scripts that manipulate the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The ramifications of this vulnerability are significant, as it can undermine trust in the npm ecosystem, lead to the proliferation of malicious packages, and potentially expose users to security risks.

How To Fix

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

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

There are no effective workarounds for this vulnerability other than removing the affected package. It is advisable to regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in your project.

Conclusion

The armed_ocelot_z3n package poses a significant threat due to its malicious code that manipulates npm packages. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their projects from similar vulnerabilities.

See every vulnerability recorded for armed_ocelot_z3n →

Share this vulnerability

FAQ

armed_ocelot_z3n is an npm package identified as part of a malicious campaign that modifies package files and republishes variants to manipulate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should immediately uninstall the armed_ocelot_z3n package using the command npm uninstall armed_ocelot_z3n.

Regularly audit your dependencies, keep your packages updated, and use tools like Vulert to monitor for open-source vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check for vulnerabilities without needing to install anything by visiting the Vulert playground.

How To Fix

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

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