Firebug could be built for Firefox (however hard and painful that was). You can't build anything similar for Chrome.
A couple of months ago I noticed that the Unfriend Notify for Facebook extension (https://chrome.google.com/webstore/detail/unfriend-notify-fo...) with 200,000 users is doing the same thing (a good clue is that it asks for access to all sites but doesn't do anything useful outside of facebook.com).
I wrote a note via the webstore's "Report Abuse" that I am pretty sure referenced the bad code but the extension is still in the store.
EDIT: I just asked on #mozilla IRC and was told that https://lists.mozilla.org/listinfo/dev-extensions would be one way to send that feedback.
Shady shit right there.
Just because some extensions are bad, don't make everyone suffer and provide a bad experience. Maybe provide a proper review system where people can downvote and moderators can ban such extensions. They are so many choices available instead of a highly dramatized review process.
By not having a review process a few don't suffer (the extension developers) and many (the users) suffer, because they can't trust their browser.
I'm firmly in the "I want to be able to trust my browser" camp but perhaps a balance can be found where the benefit of the many can be only slightly reduced while the pain of the few can be greatly reduced. Here's to that!
The users will also suffer if there are less extensions available because most developers of $small_hobby_project don't want to go through an approval process every time they try to update their extension (and you would need to check every update, or the whole ordeal is pointless).
They'll especially suffer if, typical for Google, the extension review team is horrible and understaffed. Google can't even get paid support right, what makes you think they'd be quick and orderly about approving free browser extensions.
Like I said, there are many options here. Approval process should just do some automated scans but that's about it.
Such a sandbox can't be done for this use case. How would the sandbox know what is legitimate traffic for that extension and what is traffic related to spying?
AFAIK Chrome extensions don't go through a review process. That's why I know of two Chrome extensions that were spying on their users and submitted the visited urls to third party servers (Smooth Gestures and a Diigo extension having something to do with screenshots).
So while it's important to be able to iterate quickly, I don't think the Chrome team have made the best choice. The damn spying by extensions is the primary reason I recommend Firefox instead of Chrome to anyone who asks.