Malicious Code Injection in operational_camel-apptea: npm Package Vulnerability

operational_camel-apptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106744: Malicious code in operational_camel-apptea (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 operational_camel-apptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The vulnerability stems from the presence of scripts that modify the package.json file, removing private flags and altering version numbers, leading to potential pollution of the npm registry.

Vulnerability Detail

This vulnerability originates from the operational_camel-apptea package, which contains malicious scripts that can alter the package.json file. The scripts are designed to remove private flags, change version numbers, and generate random package names, which can lead to the continuous republishing of variants. This not only affects the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of reputation.

How To Fix

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

npm uninstall operational_camel-apptea

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

Conclusion

The operational_camel-apptea package presents a significant vulnerability due to its malicious code that alters package metadata and can lead to npm registry pollution. It is crucial for developers to take immediate action by uninstalling the package and monitoring for updates to ensure the security of their projects.

See every vulnerability recorded for operational_camel-apptea →

Share this vulnerability

FAQ

The operational_camel-apptea package is part of a campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.

You should uninstall the operational_camel-apptea package immediately and monitor for any updates or patches that may be released.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application without any signup using the Vulert playground.

Vulert is a tool that helps monitor open-source vulnerabilities in your software using just the package-lock.json file, providing real-time alerts.

How To Fix

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

npm uninstall operational_camel-apptea

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