Malicious Code Injection in guilty_camel_dumbs Package

guilty_camel_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103427: Malicious code in guilty_camel_dumbs (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 guilty_camel_dumbs package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises its integrity and poses significant risks to developers and their applications.

Vulnerability Detail

The vulnerability originates from the guilty_camel_dumbs package, which is associated with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can result in developers inadvertently using compromised packages, exposing their applications to further vulnerabilities and malicious activities.

How To Fix

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

npm uninstall guilty_camel_dumbs

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 guilty_camel_dumbs package and any packages that may have been published as derivatives of it. Regularly monitor your package dependencies for any signs of malicious activity.

Conclusion

The guilty_camel_dumbs package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. Developers should take immediate action to remove this package and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for guilty_camel_dumbs →

Share this vulnerability

FAQ

The guilty_camel_dumbs package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and functionality.

If you have installed the guilty_camel_dumbs package, you should uninstall it immediately and review your other dependencies for any related issues.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

There are no patched versions of the guilty_camel_dumbs package available. The best course of action is to remove it from your project.

How To Fix

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

npm uninstall guilty_camel_dumbs

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