Malicious Code Injection in richard-wallet-store: npm Package Vulnerability

richard-wallet-store Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108060: Malicious code in richard-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

richard-wallet-store is an npm package that is likely part of a token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate wallet storage functionalities but has been compromised to include malicious scripts that manipulate its behavior. The vulnerability arises from the package's ability to publish derivative versions with altered metadata, which can mislead developers and users.

Vulnerability Detail

The vulnerability in richard-wallet-store originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, potentially harming developers' reputations and causing confusion among users. The malicious payload can also facilitate further exploitation by allowing unauthorized access to sensitive information.

How To Fix

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

npm uninstall richard-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, avoid using the richard-wallet-store package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The richard-wallet-store package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial for developers to uninstall this package and seek alternatives while remaining vigilant for updates and security advisories.

See every vulnerability recorded for richard-wallet-store →

Share this vulnerability

FAQ

richard-wallet-store is an npm package designed for wallet storage functionalities but has been compromised with malicious code.

The vulnerability can lead to unauthorized modifications of your package metadata, potentially harming your application's integrity and reputation.

You should uninstall the richard-wallet-store package immediately and monitor for any updates or patches.

Yes, consider using other reputable npm packages that offer similar wallet storage functionalities without the associated risks.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

How To Fix

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

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