3 ms·

I'm not sure there's an out of the box mechanism for this, but imo if this is a risk to your extension, then you as the developer should have a mitigation for i

• lxgr 3y ago
  I don't think the extension itself was even attacked here. It seems like the wallet credentials were stored in the localStorage of some website, which the (legitimate) extension can access, but a malicious one can as well. Update: It seems like there is no legitimate extension after all. The "attack" is just exfiltrating keys stored on some website's localStorage. That's arguably not even an attack, just the browser extension security model working as designed....