Malicious Code Injection in solar_cuckoo-appteadev Package

solar_cuckoo-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108901: Malicious code in solar_cuckoo-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 solar_cuckoo-appteadev package is part of the npm ecosystem, primarily used for various development purposes. However, it has recently been identified as part of a malicious campaign aimed at exploiting npm's package management system. This package has been associated with scripts that automatically generate and publish derivative packages, which can lead to reputational damage for developers and pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from the solar_cuckoo-appteadev package being linked to the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these packages, leading to potential security breaches and loss of control over their projects.

How To Fix

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

npm uninstall solar_cuckoo-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 measure, avoid using the solar_cuckoo-appteadev package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies to ensure they are secure.

Conclusion

The solar_cuckoo-appteadev package poses a significant risk due to its malicious behavior, which can compromise the integrity of projects using it. It is essential to remove this package and monitor your dependencies for security vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for solar_cuckoo-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm ecosystem.

Using this package can lead to security breaches and pollution of the npm registry, potentially compromising your project's integrity.

You should uninstall the solar_cuckoo-appteadev package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

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