Malicious Code Vulnerability in greasy_koi-appteadev Package

greasy_koi-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103364: Malicious code in greasy_koi-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 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 greasy_koi-appteadev package is part of the npm ecosystem, typically used for applications that may involve token reward campaigns. This package has been identified as part of a larger scheme that floods the npm registry with malicious packages designed to inflate developer reputation scores through automated publishing scripts. The vulnerability arises from the package's malicious payload, which alters critical files and repackages them with deceptive names.

Vulnerability Detail

The vulnerability in greasy_koi-appteadev originates from its association with the tea.xyz token reward campaign. The package contains scripts that automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The malicious nature of this package can result in unauthorized access to sensitive data and a 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 greasy_koi-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 avoid using the greasy_koi-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The greasy_koi-appteadev package poses a significant security risk due to its malicious code that alters package files and floods the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for greasy_koi-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, designed to inflate developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications of your package files and potentially compromise your application's integrity.

You should uninstall the greasy_koi-appteadev package immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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