Metamask-extension: Avast showing warnings for Infura requests

[kWeb24]

Connection with api.infura.io was blocked.
Reason: JS:ScriptSH-inf Trojan
Endpoint: Something with getBlockByNumber from api.infura.io

[MAtomsS]

Same here, screenshot of what avast says to me

[kWeb24]

@MAtomsS You've got chrome, i've got firefox so both versions are affected. Probably CI triggers some kind of update and avast freaks out

[kumavis]

@kWeb24 in your original title you said "each commit" did you mean "each request" ?

[kumavis]

This has been reported to infura and they are reporting it as a false positive to avast

[kWeb24]

@kumavis I just noticed that Avast notification pop up right after CI finished. First notification was few seconds after #4328 and the same repeats for the rest, #4319 and #4295

[kumavis]

@kWeb24 I'm confused - we use "CI" to refer to our CircleCI testing configuration. Are you referring to running the tests locally? or somehow seeing Avast inside CircleCI? or is this for your own CI setup?

[kumavis]

MetaMask currently does not have any auto-deploy / continuous deploy system in place, so CI completing does not push updates to clients.

[kWeb24]

@kumavis Yep, i mean you're testing configuration with CircleCI. Notifications time was related to finishing tests (as we could see test status directly in repo), that's my theory and could be just a coincidence. So if there's no auto-deploy it's pretty weird or i'm wrong. ;)

[kumavis]

I think its unlikely that they are related

[kumavis]

Will post an update when we hear from Avast

[kWeb24]

Ok, I believe that's false positive so Avast should just confirm that. Have a nice day. ;)