Malicious Code Injection in personal_alligator_z3n Package

personal_alligator_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95879: Malicious code in personal_alligator_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 personal_alligator_z3n package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate npm's package registry by creating and publishing numerous derivative packages with altered metadata.

Vulnerability Detail

The vulnerability in the personal_alligator_z3n package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to pollution of the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages.

How To Fix

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

npm uninstall personal_alligator_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, you can avoid using the personal_alligator_z3n package and monitor your project for any dependencies that may inadvertently include it. Additionally, consider using tools like Vulert to monitor your package-lock.json 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 personal_alligator_z3n package poses a significant risk due to its involvement in a malicious npm campaign. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any identified vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for personal_alligator_z3n →

Share this vulnerability

FAQ

The personal_alligator_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security.

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

Regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor your project for vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

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