🛡️Web3 Threat Intelligence
The Web3 Threat Intelligence module gives you real-time visibility into the most critical exploits, vulnerabilities, and financial losses across the blockchain ecosystem.
From DeFi and bridges to token contracts and wallet phishing, this dashboard lets you stay ahead of attackers with clean, contextual, and constantly updated data.
🔍 What You Get
Confirmed Web3 exploits with financial impact
Visual trends in incident frequency and loss
A built-in phishing domain checker
Root cause reports of major attacks
Filters to analyze by category, exploit type, and time
Everything is built for devs, founders, and security researchers who need to react fast and learn from real-world incidents.
📊 Overview Metrics
At the top of the page, you’ll find three key indicators:
Metric
Description
Total Incidents
Total number of confirmed Web3 attacks during the selected timeframe
Total Losses
Sum of all financial losses in USD equivalent
Average Loss
Average amount lost per incident
These metrics help you understand the scale of attacks in Web3 — and how it’s trending over time.
You can toggle the timeframe across 3M, 6M, 1Y, or All to zoom in or out.
📈 Losses Over Time
This interactive line chart plots total USD loss from Web3 exploits over time.
Use it to:
Identify spikes in attacker activity
Monitor the rise or fall of threat volume
Compare market cycles with exploit trends
This chart updates dynamically based on your selected date range.
🧪 Phishing Domain Checker
Fake domains are one of the most common ways users get compromised in Web3. This built-in tool lets you check whether a given domain is known to be malicious.
How it works:
Enter a domain (e.g., app.jupag.win)
Click Check
If flagged, Menaxa shows a red warning and timestamp
You’ll also see a live list of known phishing domains to avoid
💡 This is ideal for founders, community managers, or security teams reviewing reported scam links.
🧨 Recent Incidents
This table shows confirmed Web3 security incidents — updated in real-time and verified by the Menaxa intel team.
Each row includes:
Field
Description
Name
The name of the project or token affected
Type of Issue
The category of exploit (e.g. Access Control, Logic, Governance)
Category
What part of the stack was attacked (Token, DEX, Lending, etc.)
Amount Lost
Estimated value drained from the exploit (in USD)
Date
When the exploit occurred or was confirmed
Filters:
Search by keyword (e.g. project name, exploit type)
Sort by date, category, or impact
Switch time range (3M, 6M, 1Y, All)
✅ This table helps you monitor the threat landscape and benchmark risk across protocols.
🧠 Incident Details (Click to Expand)
Clicking on any row opens a detailed incident viewer — a full breakdown of what happened, how it happened, and what was lost.
Here’s what you’ll see:
Name / Token Affected
Type of Issue
Category
Date
Amount Lost
Root Cause
📘 Example: Mobius Token ($MBU)
Type: Access Control
Category: Token
Date: May 11, 2025
Amount Lost: $2,150,000
Root Cause:
The attacker exploited a vulnerability in the Mobius Token’s smart contract minting mechanism. A malicious contract was deployed and quickly used to mint excessive tokens (28.5M MBU), which were then dumped into stablecoins, resulting in a net loss of over $2.1M.
This lets you:
Study the attacker’s method
Understand what failed at the contract level
Learn how to avoid similar issues in your own stack
Last updated