Malicious Code Injection in obvious_crocodile_0xrequest Package

obvious_crocodile_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106497: Malicious code in obvious_crocodile_0xrequest (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 'obvious_crocodile_0xrequest' package 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. It typically contains scripts designed to manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the 'obvious_crocodile_0xrequest' package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This can lead to security risks, as developers may unknowingly install these malicious packages, compromising their applications.

How To Fix

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

npm uninstall obvious_crocodile_0xrequest

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 workaround, you can avoid using the 'obvious_crocodile_0xrequest' package altogether. If it is already in use, consider replacing it with a trusted alternative package that provides similar functionality without the associated risks.

Conclusion

The 'obvious_crocodile_0xrequest' package poses significant security risks due to its malicious nature. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications by removing affected packages and monitoring for new vulnerabilities.

See every vulnerability recorded for obvious_crocodile_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata for fraudulent purposes.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, you can identify affected packages.

Using this package can lead to security vulnerabilities, as it modifies package metadata and can introduce malicious code into your application.

Yes, you can use Vulert's playground to check if your application is affected by this vulnerability without requiring any signup.

You should remove the 'obvious_crocodile_0xrequest' package from your project and look for a secure alternative.

How To Fix

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

npm uninstall obvious_crocodile_0xrequest

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