Malicious Code Injection in shy_perch-appteadev: A Threat to npm Users

shy_perch-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108652: Malicious code in shy_perch-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 package shy_perch-appteadev is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. Its primary functionality is to facilitate the distribution of software, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in shy_perch-appteadev originates from its association with a malicious campaign that deploys scripts designed to generate and publish derivative packages with randomized names. This not only inflates developer reputation scores for token rewards but also modifies the package.json file to remove private flags and change version numbers. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to trust legitimate packages.

How To Fix

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

npm uninstall shy_perch-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 shy_perch-appteadev and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The discovery of malicious code in the shy_perch-appteadev package highlights the importance of vigilance in managing open-source dependencies. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their projects from potential threats.

See every vulnerability recorded for shy_perch-appteadev →

Share this vulnerability

FAQ

shy_perch-appteadev is an npm package that has been compromised to include malicious code as part of a token reward campaign.

The vulnerability can lead to the modification of your package.json file, potentially exposing your project to further risks and making it difficult to manage dependencies.

You should uninstall the package immediately using 'npm uninstall shy_perch-appteadev' and check for any other affected packages in your project.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.

Regularly update your dependencies, use trusted packages, and monitor for vulnerabilities using tools like Vulert.

How To Fix

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

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