Malicious Code Injection in ill_puffin_z3n Package - npm Vulnerability

ill_puffin_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94920: Malicious code in ill_puffin_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 ill_puffin_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. The primary function of this package is to serve as a tool for developers, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the ill_puffin_z3n package stems from its inclusion in a campaign that generates and publishes derivative packages with malicious intent. The malicious code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to pollution of the npm registry. This can result in developers unintentionally using compromised packages, which can affect their applications' security and integrity.

How To Fix

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

npm uninstall ill_puffin_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 workaround, you can monitor your project for any unintended dependencies that may have been introduced by the ill_puffin_z3n package. Regularly audit your npm packages using the command: npm audit This will help identify any vulnerabilities in your project.

Conclusion

The ill_puffin_z3n package poses a significant risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and regularly audit their dependencies to maintain application security.

See every vulnerability recorded for ill_puffin_z3n →

Share this vulnerability

FAQ

The ill_puffin_z3n package is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through the publication of compromised packages.

This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

No, there is currently no patched version of the ill_puffin_z3n package available. The recommended action is to uninstall the package.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

If you discover other malicious packages, you should uninstall them immediately and audit your dependencies to ensure your application remains secure.

How To Fix

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

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