Its missclassification as deceptive request

Nobody has claimed this yet.

### What is this about?

when users approve USDT to our contract, the Metamask display the "this is a deceptive request" notice, this is definitely a wrong classification.

https://doggy-ai.com/ when we try to buy with our usdt tokens the doggy ai token project gets a warning that this transaction is a scam, we would like to fix this problem as it affects our sales, we have already filed this in metamask and now duplicate it github

DoggyAI ($DOGYAI) introduces a unique fusion of meme
culture and artificial intelligence to the cryptocurrency
ecosystem. By leveraging AI technology and the viral
nature of memes, DoggyAI aims to create a fun, engaging,
and rewarding experience for its community. This white
paper outlines the project's vision, technology, tokenomics,
roadmap, and how to participate in the presale.

Doggy ai official website: https://doggy-ai.com/#faq
Official community link: https://t.me/DoggyAi69
Official Twitter: https://x.com/DOGGYAI69

We have submit several times on the issue reports site, but there has no improve process for days. It is having a negative impact on our sales.
So submit this issue here, please remove the metamask wrong classfication report

Thanks alot!

Expected behavior

No warning should popup in metamask. It is having a negative impact on our sales.

Screenshots/Recording

Severity

Severe, has an negative impact on our project
All users are scared to confirm the transaction due to this error.

Deploy
Staking https://etherscan.io/address/0x5f12240737f5B22F657d6eb9f1e7C1123FF62EF7#code
Sale https://etherscan.io/address/0x53eAF46485cbd3453bbf624e8a20D634f5c2e067#code

We рave problem in both

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] 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)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

No repository file, test, or entry point is identified in the report. Start by reproducing the USDT approval flow from doggy-ai.com and reviewing the linked staking and sale contract addresses alongside MetaMask's issue-report process; done means the warning is independently assessed and, if appropriate, its classification is changed.

Written by the indexing model from the issue text.