Malicious Code Injection in occupational_egret_z3n Package

occupational_egret_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88969: Malicious code in occupational_egret_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 occupational_egret_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. Its primary functionality revolves around generating and publishing derivative packages, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the occupational_egret_z3n package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores for token rewards while polluting the npm registry with these derivative packages. The origin of this issue can be traced back to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall occupational_egret_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 measure, avoid using the occupational_egret_z3n package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your project for any unauthorized changes to package.json.

Conclusion

The occupational_egret_z3n package poses a significant risk due to its embedded malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for occupational_egret_z3n →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and reputation damage.

You should uninstall the package immediately and check your project for any unauthorized changes.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay updated on security advisories.

Vulert monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

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