Malicious Code Injection in assistant_pig_z3n Package - npm Vulnerability

assistant_pig_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99641: Malicious code in assistant_pig_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 assistant_pig_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the distribution of software, but it has been compromised to include malicious scripts that manipulate package metadata. The vulnerability arises from the package's ability to modify its own configuration, which can lead to unauthorized actions and pollution of the npm registry.

Vulnerability Detail

The vulnerability in the assistant_pig_z3n package is characterized by the presence of malicious code that alters the package.json file. This code removes private flags, changes version numbers, and generates random package names, which are then republished to inflate developer reputation scores. The origin of this issue is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with such malicious packages. The ramifications include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm ecosystem due to the proliferation of spammy packages.

How To Fix

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

npm uninstall assistant_pig_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 assistant_pig_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The assistant_pig_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for assistant_pig_z3n →

Share this vulnerability

FAQ

The assistant_pig_z3n package is an npm package that was part of the tea.xyz token reward campaign, designed to distribute software but has been compromised with malicious code.

The malicious code modifies the package.json file, removing private flags and changing version numbers, which can lead to unauthorized republishing and pollution of the npm registry.

You should uninstall the assistant_pig_z3n package immediately using the command: npm uninstall assistant_pig_z3n, and check for alternative packages.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

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