Malicious Code Injection in wandering_smelt_0xrequest Package - npm Vulnerability

wandering_smelt_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110654: Malicious code in wandering_smelt_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 'wandering_smelt_0xrequest' package is part of a broader set of packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages on the npm registry, often with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, but it also introduces significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from malicious code embedded in the 'wandering_smelt_0xrequest' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior can pollute the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to security risks. The malicious payload can also compromise the integrity of applications that depend on this package, as it may introduce unverified code into their environments.

How To Fix

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

npm uninstall wandering_smelt_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 workaround, you can avoid using the 'wandering_smelt_0xrequest' package altogether. If it is already in use, consider replacing it with a reputable alternative that provides similar functionality without the associated risks.

Conclusion

The 'wandering_smelt_0xrequest' package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for wandering_smelt_0xrequest →

Share this vulnerability

FAQ

It is an npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

The malicious code can compromise the integrity of your application by introducing unverified and potentially harmful code.

You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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