Malicious Code Injection in protestant_asp_z3n Package

protestant_asp_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107378: Malicious code in protestant_asp_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 protestant_asp_z3n package is part of the npm ecosystem, often utilized in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the protestant_asp_z3n package stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random package names, predominantly themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to potential security risks, including the exposure of sensitive information and the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall protestant_asp_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 protestant_asp_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json.

Conclusion

The protestant_asp_z3n package contains malicious code that poses significant risks to applications using it. It is essential to remove this package and monitor your project for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for protestant_asp_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for manipulating developer reputation scores.

It can lead to unauthorized modifications in your package.json file, potentially exposing sensitive information and degrading the integrity of your npm dependencies.

Currently, there is no patched version available for the protestant_asp_z3n package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against this vulnerability using the Vulert playground.

You should uninstall the protestant_asp_z3n package immediately and check for any dependencies that may be affected.

How To Fix

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

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