Critical Malicious Code Vulnerability in web3-sinon Package

web3-sinon Updated 06 Feb 2026

Summary

06/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-807: Malicious code in web3-sinon (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 web3-sinon package is a JavaScript library designed for developers working with Ethereum blockchain applications. It provides utilities for testing and mocking web3 interactions, making it easier to develop decentralized applications. However, this package has been compromised, leading to significant security concerns for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the web3-sinon package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has inserted harmful code into the package, which can lead to severe ramifications for users, including data breaches and loss of control over their systems.

How To Fix

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

npm uninstall web3-sinon

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

Currently, there are no effective workarounds to mitigate the risks associated with the web3-sinon package. The best course of action is to remove the package entirely and ensure that your system is secure.

Conclusion

The web3-sinon package has been identified as containing malicious code that poses a significant security risk. Users must take immediate action to uninstall the package and secure their systems. Regular monitoring of dependencies is crucial to maintaining a secure development environment.

See every vulnerability recorded for web3-sinon →

Share this vulnerability

FAQ

You should immediately uninstall the web3-sinon package and rotate any sensitive information stored on your computer.

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

No, there is currently no patched version available for the web3-sinon package.

Failing to remove the package can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

While not all packages in the npm ecosystem are compromised, it is essential to review and monitor packages regularly for vulnerabilities.

How To Fix

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

npm uninstall web3-sinon

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