Malicious Code Injection in purring_reptile-appteadev Package

purring_reptile-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107439: Malicious code in purring_reptile-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 purring_reptile-appteadev package is part of the npm ecosystem, commonly used for various JavaScript applications. It is designed to facilitate development and deployment processes. However, this package has been identified as part of a malicious campaign that exploits npm's publishing features, leading to significant security risks for developers and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the purring_reptile-appteadev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to the npm registry, which can lead to reputation inflation for the perpetrators and potential security risks for users who inadvertently install these compromised packages. The origin of this vulnerability is linked to a broader campaign targeting npm packages to exploit the tea.xyz token reward system.

How To Fix

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

npm uninstall purring_reptile-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 purring_reptile-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using tools like Vulert to detect any vulnerabilities in your dependencies.

Conclusion

The purring_reptile-appteadev package poses significant security risks due to its malicious code designed to exploit npm's publishing features. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert to maintain the security of their applications.

See every vulnerability recorded for purring_reptile-appteadev →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been compromised with malicious code.

The malicious code modifies your package.json file and can lead to the installation of compromised packages, posing security risks.

You should uninstall the package immediately and monitor your project for any other vulnerabilities.

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

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 purring_reptile-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