N/A

CVSS Score

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-57329

CVE-2025-57329: web3-core-method is vulnerable to prototype pollution

web3-core-method is a package designed to creates the methods on the web3 modules. A Prototype Pollution vulnerability in the attachToObject function of web3-core-method version 1.10.4 and before allows attackers to inject properties on Object.prototype via supplying a crafted payload, causing denial of service (DoS) as the minimum consequence.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-57329

CVE-2025-57329:

N/A

CVSS Score

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
web3-core-method	npm	<= 1.10.3

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a classic prototype pollution flaw in the web3-core-method package, specifically within the attachToObject function. This function is intended to add methods to web3 module objects. The vulnerability allows an attacker to inject properties into Object.prototype by using a crafted payload. This occurs because the function does not properly sanitize or validate the property names being assigned, allowing malicious keys like __proto__ to be used to traverse up the prototype chain and modify the global Object.prototype.

My analysis of the commits between the vulnerable version 1.10.3 and the patched version 1.10.4 did not reveal the exact code change that mitigates this vulnerability. The commits mainly consist of dependency updates and version bumps. This suggests that the vulnerability might have been fixed by updating a dependency that web3-core-method relies on for object manipulation, or the fix is in a commit that was not immediately obvious from the comparison.

Despite the lack of a clear patch, the CVE description and the nature of prototype pollution vulnerabilities strongly point to the attachToObject function as the entry point for the exploit. Any runtime profile during exploitation would show this function in the stack trace as it processes the malicious input.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.