Malicious Code Injection in then_cobra_0xrequest Package - npm Vulnerability

then_cobra_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109579: Malicious code in then_cobra_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 then_cobra_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 linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised due to the presence of malicious scripts that manipulate package metadata and publish unauthorized variants.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the then_cobra_0xrequest package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary risk is that it allows unauthorized republishing of these modified packages, which can lead to pollution of the npm registry and potential exploitation by attackers. The malicious payload can significantly impact developers by affecting their reputation and the integrity of their projects.

How To Fix

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

npm uninstall then_cobra_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 temporary workaround, you can prevent the installation of the then_cobra_0xrequest package by using npm's package-lock.json to lock your dependencies. This will help you avoid inadvertently installing the malicious package until a secure version is available.

Conclusion

The then_cobra_0xrequest package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is crucial for developers to remove this package from their projects and stay vigilant about monitoring for vulnerabilities in their dependencies.

See every vulnerability recorded for then_cobra_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as containing malicious code aimed at manipulating package metadata for fraudulent purposes.

The vulnerability can lead to unauthorized modifications of your package, affecting your project's integrity and potentially harming your reputation as a developer.

Currently, there is no patched version of the then_cobra_0xrequest package. The best course of action is to uninstall it and monitor for updates.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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