Malicious Code Injection in stacey-wallet-store: A Threat to npm Ecosystem

stacey-wallet-store Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109063: Malicious code in stacey-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 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 stacey-wallet-store package is part of the npm ecosystem, primarily used for managing wallet-related functionalities in applications. However, it has been identified as a malicious package that is involved in the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in stacey-wallet-store originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify package.json files by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall stacey-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, you can avoid using the stacey-wallet-store package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json is monitored for any vulnerabilities using tools like Vulert.

Conclusion

The stacey-wallet-store package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is crucial to take immediate action to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for stacey-wallet-store →

Share this vulnerability

FAQ

stacey-wallet-store is an npm package used for wallet management in applications, but it has been compromised by malicious actors.

The malicious code can modify your package.json, leading to the installation of unwanted packages and potential security vulnerabilities.

You should uninstall the stacey-wallet-store package immediately and check your project for any other compromised packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

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 stacey-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