Malicious Code Injection in appalling_silkworm_0xrequest Package

appalling_silkworm_0xrequest Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99508: Malicious code in appalling_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The appalling_silkworm_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publishing of derivative packages, often with randomized names, to inflate developer reputation scores. Its functionality is compromised by malicious code that alters package metadata and republishing behavior.

Vulnerability Detail

The vulnerability originates from the package being part of a larger scheme that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to pollution of the npm registry and can compromise the integrity of applications relying on this package.

How To Fix

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

npm uninstall appalling_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 prevent the installation of this package by using npm's package-lock.json to monitor your dependencies. If you are using Vulert, you can check your application for vulnerabilities without any installation. Simply visit the Vulert playground at https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected.

Conclusion

The appalling_silkworm_0xrequest package contains malicious code that compromises the integrity of applications using it. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure your application remains secure.

See every vulnerability recorded for appalling_silkworm_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies package metadata and can lead to the pollution of the npm registry, potentially compromising the integrity of your application.

You should uninstall the appalling_silkworm_0xrequest package immediately and check for any dependencies that may rely on it.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by uploading your package-lock.json file.

How To Fix

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

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