Malicious Code Injection in Silly Stork 0xRequest Package

silly_stork_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108690: Malicious code in silly_stork_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 'silly_stork_0xrequest' package is part of the npm ecosystem, often used in JavaScript applications. It has been identified as part of a larger campaign aimed at manipulating the npm registry for token rewards. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea protocol token rewards.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the 'silly_stork_0xrequest' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been flooding the npm ecosystem with such malicious packages. The ramifications include potential security risks for applications using this package, as it can lead to unauthorized access or manipulation of the codebase.

How To Fix

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

npm uninstall silly_stork_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 'silly_stork_0xrequest' package from your project by executing 'npm uninstall silly_stork_0xrequest'. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The 'silly_stork_0xrequest' package contains a significant vulnerability that can compromise the integrity of applications using it. Immediate action is required to update or remove the package to protect your project from potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for silly_stork_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications of your application's dependencies, potentially compromising security and functionality.

You should immediately update or uninstall the package to mitigate the risks associated with the vulnerability.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

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