Malicious Code Injection in rotten_newt-apptea: A Threat to npm Packages

rotten_newt-apptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108203: Malicious code in rotten_newt-apptea (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

rotten_newt-apptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall rotten_newt-apptea

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 rotten_newt-apptea package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The rotten_newt-apptea package poses a significant threat due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for rotten_newt-apptea →

Share this vulnerability

FAQ

rotten_newt-apptea is an npm package involved in a token reward campaign that has been identified to contain malicious code.

The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to security vulnerabilities and pollution of the npm registry.

You should uninstall the rotten_newt-apptea package immediately using the command: npm uninstall rotten_newt-apptea.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

Yes, look for reputable npm packages that provide similar functionality but have a verified track record of security.

How To Fix

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

npm uninstall rotten_newt-apptea

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