Malicious Code Injection in surprised_fox_z3n: A Threat to npm Packages

surprised_fox_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90808: Malicious code in surprised_fox_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'surprised_fox_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its primary functionality revolves around automating the publication process, but it has been compromised to include malicious scripts.

Vulnerability Detail

The vulnerability in 'surprised_fox_z3n' originates from its association with a malicious campaign that modifies the package.json file by removing private flags and changing version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This can lead to security risks, including the potential for users to inadvertently install compromised packages, which could execute harmful code in their applications.

How To Fix

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

npm uninstall surprised_fox_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 'surprised_fox_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which checks for vulnerabilities in your package-lock.json file.

Conclusion

The 'surprised_fox_z3n' package poses a significant security risk due to its malicious code that modifies package metadata and repackages itself. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for surprised_fox_z3n →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

If you have the 'surprised_fox_z3n' package installed, your application may be at risk of executing malicious code, which can compromise security and stability.

You should uninstall the package immediately and check for any other dependencies that may be affected by similar vulnerabilities.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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