Malicious Code Injection in progressive_takin-appteadev Package

progressive_takin-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107335: Malicious code in progressive_takin-appteadev (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 progressive_takin-appteadev package is part of the npm ecosystem, primarily used for developing applications that may involve token reward systems. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing of derivative packages.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the progressive_takin-appteadev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this malicious behavior is linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores by polluting the npm registry with numerous derivative packages. The ramifications include potential security risks for applications using this package, as it can lead to unauthorized access and manipulation of application data.

How To Fix

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

npm uninstall progressive_takin-appteadev

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 progressive_takin-appteadev package from your project by executing the following command: npm uninstall progressive_takin-appteadev. This will prevent any malicious code from executing in your application.

Conclusion

The progressive_takin-appteadev package contains malicious code that poses significant security risks. It is crucial to update or remove this package to protect your application from potential threats. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in your dependencies.

See every vulnerability recorded for progressive_takin-appteadev →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and repackages the software to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Using the affected package can lead to unauthorized access, data manipulation, and overall instability of your application due to the malicious code.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

If no patched version is available, it is recommended to remove the package from your project to mitigate any risks.

How To Fix

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

npm uninstall progressive_takin-appteadev

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