How to remove - "Request may not be safe" warning for security providers ?

[dev-ramverma]

What is this about?

Error -

Request may not be safe Because of an error, this request was not verified by the security provider.Proceed with caution

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

[Jonath-z]

Can I look into this?

[dev-ramverma]

Please

[Jonath-z]

I would like to get more information about this issue. @dev-ramverma

[dev-ramverma]

You can visit - https://blockstarcoin.com/

[bschorchit]

Could you update to the latest version v11.7 and confirm this is still happening?

[cryptocodyram]

[cryptocodyram]

Current Metamask version is 11.7.2 @bschorchit

[g1tt]

I am receiving this error now, if this will help to resolve the problem! I am at https://pacific-bridge.manta.network/ I try to bridge ETH to Manta Pacific Mainnet I see this warning -

I am using MetaMask 11.7.3 on Brave 1.61.116 Chromium 120.0.6099.217. Windows 10 22H2.

HTH!

[TerryGuo]

I am also running into this problem:

[GitHerDoneSon]

Can I look into this?

Did you ever figure out what this "Request may not be safe." MetaMask warning is about? Would really like an answer. Thanks.

[GitHerDoneSon]

What is this about?

Error -

Request may not be safe Because of an error, this request was not verified by the security provider.Proceed with caution

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

Hey Ramverma! Did you ever figure out what this message on metamask means?

[GitHerDoneSon]

Can I look into this?

Hey I'm still trying to figure out what this metamask message means. If you ever did, please let me know! Thank you.

[GitHerDoneSon]

I am also running into this problem:

Hi, did you ever find out what to do with this message? Did you click through anyway? Or find another solution? Thanks

[GitHerDoneSon]

I am receiving this error now, if this will help to resolve the problem! I am at https://pacific-bridge.manta.network/ I try to bridge ETH to Manta Pacific Mainnet I see this warning -

I am using MetaMask 11.7.3 on Brave 1.61.116 Chromium 120.0.6099.217. Windows 10 22H2.

HTH!

Hey what did you end up doing with this message you saw on metamask? Did you click through? And if so what happened? Thank you!

[bschorchit]

Hey, we currently have an issue that is causing this message to appear more frequently than it should. We're rolling out a fix in v11.9.5 that solves it. Please update to this version and let me know if you're still encountering it.

[cryptocodyram]

I had a problem with the Tether interface. I used the Openzepplin ERC20 interface instead of Tether interface. ERC20 interface - { transfer(address to, uint256 amount) → bool } Tether interface - { transfer(address _to, uint _value) -> no return }

[Nebula-Spark]

Could you update to the latest version v11.7 and confirm this is still happening?

Hello, Still facing the same issue @ AAVE Lending Protocal during asset switch transaction! Is that safe to process the transcation or should we need to wait for the fix?

Version 11.10.0

[SvenMeyer]

@bschorchit Any updates ? How often does that happen ? And do we know why or under what circumstances ?

[doninhacs]

Hi all, the AAVE protocol is being impossible to be used. This issue is not approving the transactions. Please help

[artiface]

Hey, we currently have an issue that is causing this message to appear more frequently than it should. We're rolling out a fix in v11.9.5 that solves it. Please update to this version and let me know if you're still encountering it.

Just update to 11.10.1 and i see this message on every transaction now? Can you give any explanation about what it means or what causes it?

[SvenMeyer]

Who is actually the "Security Provider" ?

[SvenMeyer]

Should 11.11.3 fix this problem ?

[redcomethk]

The version I am using is also 11.10.1 It seems that the details cannot be shown properly.

When "Report an issue" is pressed a page for https://blockaid-false-positive-portal.metamask.io/ is shown.

[redcomethk]

@artiface Have you tried to call the same method in https://etherscan.io/ for example? I tried that and that "Request may not be safe" box does not appear... I guess that maybe caused by some frontend libraries involved.

[artiface]

@artiface Have you tried to call the same method in https://etherscan.io/ for example? I tried that and that "Request may not be safe" box does not appear... I guess that maybe caused by some frontend libraries involved.

So yes, there are some instances where I do not get the warning message, like Opensea transfers did not show it. But the majority of sites I interact with still show this message. If it's supposed to be a warning, this will lead quickly to warning fatigue and the messages being ignored.

I updated to 11.11.4 and this message is still present.

I use PocketUniverse extension which already simulates transactions to show what transactions will do before approving them, and all these transactions are safe, so why is Metamask flagging them with a bogus "warning"?

[GithubsFan2024]

Hi guys,

I also received this "Request may not be safe" message when signing a contract. Someone in Reddit told me that it's a new security feature of Metamask powered by Blockaid. It can be turned on and off. Here's the detailed link.

https://support.metamask.io/hc/en-us/articles/19878220833947-How-to-turn-on-Blockaid-security-alerts

Hence, my question is that is this really an issue (a bug or something that needs to be fixed)? I'm a newbie. Please advise. Thank you.

[starlabs007]

This is a big issue. This is showing up for one of our contracts on ethereum. It states that the contract is unverified but the contract is FULLY verified on etherscan.io. Obviously this is alarming our users. I have already used the Report an issue link.

[bschorchit]

Thank you for the reports! Would you mind clicking on report an issue within the warning, that will make sure the info needed gets in the most efficient and fast way to the relevant team so we address those in a timely manner. Thank you so much! I'm also making the team aware of this.

[starlabs007]

Yes, I've reported the issue within the warning as well as reported it directly to BlockAid. I neglected to include my email in the first report, but did include it when I reported the issue to BlockAid. To their credit, I received a reply within 2 days that this was indeed a flagging error and that it has been resolved. 👍 Thank you.

[SquidFinder]

receiving this error with wagmi and wallet connect front end build

[SvenMeyer]

Blockaid , which is the "Security" provider Metamask uses presents way too often this warning even on totally safe websites and contracts. If you are sure that it is safe you can ..

• click on See details
• click on Report an issue
• write that Blockaid is wrong and all is good

[NeeteshMaurya]

Yes, I've reported the issue within the warning as well as reported it directly to BlockAid. I neglected to include my email in the first report, but did include it when I reported the issue to BlockAid. To their credit, I received a reply within 2 days that this was indeed a flagging error and that it has been resolved. 👍 Thank you.

What do you mean by flagging error here? do i need to make changes in my contract if i am getting same warning as you were getting it or they will resolve it by their side?

[Rooibossie]

Request may not be safe

Because of an error, this request was not verified by the security provider. Proceed with caution. So frustrating, i am also getting this error message a lot lately on while on Aave de-fi platform. I've was on Microsoft Edge web browser but i have switched over to Firefox. I checked and yes, i am using the latest version of Metamask. When i was using Metamask on Microsoft Edge the Matic balance was also incorrect. Now that i am on Firefox it has been resolved. Using windows 10. I don't know what other info. you require. I tried to report it to Github but that just led me down the garden path completely off course. Seems like this BlockAid is being overbearing. James Warrington, South Africa jwarrington4@gmail.com

[PRDTfinance]

Same issue here! On our fully verified ETH contract. This false flagging is a BIG issue and alarming development. Report has been sent already.

[SvenMeyer]

Looks like Blockaid is the problem and their "algorithm" hasn't improve a bit since months ... and MetaMask continues to use them "as is" :-(

[SvenMeyer]

@bschorchit Any updates ... plans you can share ?

[bschorchit]

Hey all, we're continuously working on improving the experience around this feature. If your contract is being incorrectly flagged, clicking on "Report an issue" within the warning and submitting the form will make sure the needed information get to both us and Blockaid and that the issue is addressed in up to 24 hours. We're also actively working on allowing the issue to be addressed quicker as well.

Here are some details on the challenges of building a robust solution to prevent malicious transactions: https://x.com/blockaid_/status/1780326332519346249