Malicious Code Vulnerability in joyous_silkworm_0xrequest Package

joyous_silkworm_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104713: Malicious code in joyous_silkworm_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The joyous_silkworm_0xrequest package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. This package, like others in its category, has been identified as containing harmful scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the joyous_silkworm_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The primary risk is the pollution of the npm registry with these derivative packages, which can lead to confusion, potential security risks, and a degradation of trust in the ecosystem. The malicious payload is designed to operate automatically, making it difficult for developers to detect and mitigate the issue.

How To Fix

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

npm uninstall joyous_silkworm_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 avoid using the joyous_silkworm_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using tools like Vulert, which alerts you to open-source vulnerabilities in real-time.

Conclusion

The joyous_silkworm_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for joyous_silkworm_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, potentially compromising your project's integrity.

You should uninstall the joyous_silkworm_0xrequest package immediately and check for any alternative packages.

You can use Vulert to monitor your package-lock.json file for vulnerabilities without needing to access the code or install additional tools.

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

How To Fix

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

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