Malicious Code Vulnerability in stewart-wallet-store: npm Package Exploitation

stewart-wallet-store Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109122: Malicious code in stewart-wallet-store (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The stewart-wallet-store package is part of the npm ecosystem, designed to facilitate wallet storage functionalities for various applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms. This vulnerability allows attackers to manipulate package metadata and publish harmful variants, potentially affecting developers and users relying on this package.

Vulnerability Detail

The vulnerability originates from a malicious campaign associated with the tea.xyz token reward initiative. The stewart-wallet-store package contains scripts that automatically modify the package.json file, removing private flags and altering version numbers. It generates random package names, leading to the continuous republishing of harmful variants that pollute the npm registry. This can result in compromised developer reputation scores and the distribution of malicious code to unsuspecting users.

How To Fix

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

npm uninstall stewart-wallet-store

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, consider removing the stewart-wallet-store package from your project until a secure version is released. You can do this by executing: 'npm uninstall stewart-wallet-store'. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The stewart-wallet-store package has been compromised by a malicious campaign that exploits npm's publishing capabilities. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications from potential threats. Continuous monitoring for vulnerabilities is recommended.

See every vulnerability recorded for stewart-wallet-store →

Share this vulnerability

FAQ

The stewart-wallet-store package is an npm package designed for wallet storage functionalities in applications.

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising security and user data.

You should update the package to the latest version or remove it from your project until a secure version is available.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall stewart-wallet-store

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