MetaMask / MetaMask/metamask-mobile

URGENT: False “Potential Scam” Warning on BDAG Token Across All Wallets

Open
#28,261 1 comment 0 reactions 0 assignees View on GitHub
external-contributor
Dominant language
TypeScript
Stars
3k
Forks
1.7k
Avg merge
1d 14h
Merged PRs (30d)
669

Description

### What is this about?

Dear MetaMask Support Team,

We are reaching out regarding a critical issue affecting our users globally, where the BDAG token is currently being flagged as “Potential Scam” within MetaMask wallets.

This warning is appearing across a wide range of user accounts and is causing significant disruption, confusion, and reputational damage to our project and community.

🔍 Important Clarification on Address Submitted

As part of our investigation and communication with Blockaid, we previously submitted the following address:

0xd8A5D6Df7F3A1d57CDC9661f4a8132E9206B00D5

We would like to clearly state:

This is one of our internal reference/presale-related addresses, provided solely to help identify and report the issue
It is not the root cause of the warning
The issue is not isolated to this address

The “Potential Scam” warning is currently being shown across multiple wallets globally, including users who are simply holding or interacting with BDAG.

This strongly indicates that the flag is being applied at a token-level, domain-level, or system-wide risk classification, rather than being tied to a single address.

🔍 Project Overview

BDAG is the native asset of the BlockDAG Network — a Layer-1 blockchain with:

A global user base across 140+ countries
Active ecosystem usage and presale participation
Public infrastructure including website, explorer, and developer tools
Multiple completed security audits (including CertiK and Halborn)
⚠️ Current Situation
Blockaid has confirmed that no malicious flags remain on their end
Despite this, MetaMask continues to display a “Potential Scam” warning across user wallets

This suggests the issue may be due to:

Cached or outdated data within MetaMask
Residual or secondary risk signals
Incomplete propagation of updated security status
🔴 Immediate Requests

We urgently request:

Removal of the “Potential Scam” Warning across all MetaMask environments
A full refresh of risk/caching layers to ensure updated Blockaid signals are applied
Investigation into any remaining triggers (token-level, domain-level, or heuristic flags)
Confirmation once fully resolved across both extension and mobile versions
📎 Additional Support

We can provide:

Screenshots from affected users
Wallet addresses showing the warning
Transaction hashes and connection flows
Direct confirmation from Blockaid
⚠️ Urgency

This issue is actively:

Affecting user trust and onboarding
Disrupting transactions and participation
Creating unnecessary concern within our community

We kindly request this be treated with highest priority and resolved as soon as possible.

We appreciate your support and look forward to your prompt response.

Best regards,
BlockDAG Network Team

![Image](https://github.com/user-attachments/assets/903fd7cc-a86a-46d4-a1c5-e003ebf6228d)
![Image](https://github.com/user-attachments/assets/12319e12-83f2-40a3-a3fa-93c17c753d70)
![Image](https://github.com/user-attachments/assets/2cc51d2d-d091-452f-b9b2-595251354619)
![Image](https://github.com/user-attachments/assets/1df71027-6419-4396-b6e9-a8a5bf858079)

### Scenario

Users attempting to connect their wallets or view their balances in MetaMask are shown a “Potential Scam” warning when interacting with or holding BDAG.

This warning appears across multiple wallets and environments (browser extension and mobile), even for users who are only holding the asset and not interacting with any suspicious contracts.

The issue persists despite confirmation from Blockaid that no malicious flags remain on the submitted address or associated signals.

Scenario

A user opens MetaMask and:

Views their wallet holding BDAG
Or attempts to connect their wallet to the official platform
MetaMask displays a “Potential Scam” warning

This creates:

Immediate loss of user trust
Hesitation or abandonment of transactions
Increased support requests and confusion

The issue is not isolated to a single wallet or address, indicating a broader classification (token-level, domain-level, or cached risk signal).

### Design

_No response_

### Technical Details

Blockaid Confirmation & Resolution Status

We have been in direct communication with the Blockaid Security Team regarding this issue.

Blockaid has confirmed the following:

The submitted address has been fully reviewed
No malicious or risk flags remain on their system
Any previously associated warnings have been successfully removed

Their official response states:

“We can confirm that it no longer has any malicious flagging on our end.”

This confirms that the issue has already been resolved at the security provider level.

Given that Blockaid powers transaction security for MetaMask, the continued display of a “Potential Scam” warning strongly suggests:

A propagation delay between Blockaid and MetaMask
Cached or outdated risk data still being shown to users
Or a residual UI-level classification within MetaMask

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [x] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [x] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

![Image](https://github.com/user-attachments/assets/43f8838a-357b-444b-a39e-7f6ddebdddc0)
![Image](https://github.com/user-attachments/assets/87a3b71f-b069-4025-992d-c13dbe37bbe8)
![Image](https://github.com/user-attachments/assets/757fe49c-566e-47cf-9955-f3b1a43bb308)
![Image](https://github.com/user-attachments/assets/60d0c46a-fed9-4fae-9a23-4ba1a3365acc)

![Image](https://github.com/user-attachments/assets/21f707d6-33b3-44fb-a66c-03a2e9e2a6e1)

Contributor guide

Open the contributing guide

Research direction

No source files, tests, reproduction identifiers, or acceptance criteria are provided. Start by reproducing the BDAG warning in the mobile wallet and reviewing the Blockaid risk-signal and warning entry points; done means identifying the remaining trigger and confirming the warning is removed after the provider status is updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native, typescript
Domain
mobile-dev, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.