Malicious Code Injection in tory_porcupine_z3n: A Threat to npm Packages

tory_porcupine_z3n Updated 19 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-117527: Malicious code in tory_porcupine_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package tory_porcupine_z3n is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files, such as package.json, to remove private flags and alter version numbers, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in tory_porcupine_z3n originates from its association with malicious autopublish scripts that are intended to pollute the npm registry. These scripts can modify package.json files, remove private flags, and continuously republish variants of the package, leading to a significant risk of dependency confusion and potential exploitation by attackers. The ramifications include the possibility of unauthorized access to sensitive data and the degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall tory_porcupine_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 affected package by replacing it with a trusted alternative or by manually auditing your package dependencies to ensure they do not include any malicious packages.

Conclusion

The tory_porcupine_z3n package poses a significant threat due to its malicious code designed to manipulate npm packages. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your applications from potential exploitation.

See every vulnerability recorded for tory_porcupine_z3n →

Share this vulnerability

FAQ

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

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

The risks include unauthorized access to sensitive data, dependency confusion, and the potential for attackers to exploit the npm ecosystem.

It is recommended to regularly check for updates and apply them at least once a month or whenever a new version is released, especially for packages known to have vulnerabilities.

If immediate removal is not possible, consider implementing strict access controls and monitoring your application for any suspicious activity until you can safely remove the package.

How To Fix

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

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.