Malicious Code Detected in contracts-plugins: A Critical Vulnerability

contracts-plugins Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17520: Malicious code in contracts-plugins (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 'contracts-plugins' package is a Node.js library designed to facilitate the integration of smart contracts into various applications. It provides developers with tools to streamline contract management and deployment. However, this package has recently been identified as containing malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'contracts-plugins' package. This code can potentially compromise the security of applications that depend on this library, leading to unauthorized access, data breaches, or other harmful actions. The malicious code was introduced in all versions starting from 0, making it imperative for users to take immediate action to protect their systems.

How To Fix

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

npm uninstall contracts-plugins

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 measure, consider removing the 'contracts-plugins' package from your project until a secure version is released. You can do this by running: 'npm uninstall contracts-plugins'. This will help prevent any potential exploitation of the vulnerability while you await a fix.

Conclusion

The discovery of malicious code in the 'contracts-plugins' package highlights the importance of maintaining vigilance regarding open-source dependencies. Users are urged to take immediate action by updating or removing the package to safeguard their applications from potential threats.

See every vulnerability recorded for contracts-plugins →

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

As of now, a patched version has not been released. Users should monitor the package for updates and apply them as soon as they are available.

Consider removing the 'contracts-plugins' package from your project as a temporary workaround until a secure version is released.

The vulnerability was identified by Amazon Inspector, a security tool that helps detect vulnerabilities in software packages.

How To Fix

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

npm uninstall contracts-plugins

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