Malicious Code Vulnerability in personal_camel-appteadev Package

personal_camel-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107042: Malicious code in personal_camel-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The personal_camel-appteadev package is part of the npm ecosystem, often utilized in various JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's package management system. It is designed to automate the generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the personal_camel-appteadev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, thereby polluting the npm registry and potentially compromising the integrity of applications that rely on this package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded npm with similar packages that contain autopublish scripts.

How To Fix

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

npm uninstall personal_camel-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 personal_camel-appteadev package from your project by executing the following command: npm uninstall personal_camel-appteadev. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The personal_camel-appteadev package contains malicious code that poses a significant risk to applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for personal_camel-appteadev →

Share this vulnerability

FAQ

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

The malicious code modifies your package.json file and can lead to the publication of unauthorized packages, potentially compromising your application's integrity.

You should immediately update the package to a patched version or uninstall it to prevent any malicious activity.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities by analyzing your package-lock.json file. You can also check your application using the Vulert playground without any signup.

Detailed information about this vulnerability can be found in the vulnerability report and the npm registry.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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