Malicious Code Injection in respectable_bobolink_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107949: Malicious code in respectable_bobolink_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The respectable_bobolink_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities related to token rewards but has been compromised to include malicious scripts. The package's primary attributes include automatic publishing capabilities and the generation of derivative packages, which are intended to inflate developer reputation scores. However, due to its malicious modifications, it poses significant risks to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially leading to further exploitation by other malicious actors. The continuous republishing of variants can lead to a loss of trust in the npm ecosystem and can affect developers who rely on legitimate packages.

How To Fix

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

npm uninstall respectable_bobolink_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 remove the package from your project by executing the following command: npm uninstall respectable_bobolink_0xrequest. This will prevent any malicious code from executing in your environment until a secure version is released.

Conclusion

The respectable_bobolink_0xrequest package has been identified as containing malicious code that compromises the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for respectable_bobolink_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to facilitate automatic publishing and reputation score inflation.

The vulnerability can lead to the injection of malicious code, which may compromise your project's integrity and security.

You should update the package to a patched version or remove it entirely from your project to avoid potential risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

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