Malicious Code Injection in increased_partridge-biggestdev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

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

Vulnerability Detail

The vulnerability stems from malicious code embedded within the increased_partridge-biggestdev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names that are often themed around Indonesian culture. The primary risk is that this behavior leads to the pollution of the npm registry with numerous unwanted packages, which can compromise the integrity of the ecosystem and potentially introduce security risks to applications relying on these packages.

How To Fix

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

npm uninstall increased_partridge-biggestdev

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 remove the increased_partridge-biggestdev package from your project by executing the following command: npm uninstall increased_partridge-biggestdev. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The increased_partridge-biggestdev package contains malicious code that poses a significant risk to projects using it. It is crucial to update or remove the package to protect your application from potential threats. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for increased_partridge-biggestdev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been linked to the automatic generation of malicious packages.

The malicious code modifies your package.json file, potentially leading to the publication of unwanted packages and compromising the integrity of your project.

Yes, you can use Vulert, which monitors open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.

Detailed information can be found in the vulnerability report, and you can also refer to the npm registry for updates on the package.

How To Fix

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

npm uninstall increased_partridge-biggestdev

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