A browser extension keeps phoning home — is that expected?
The question comes up for anyone who has opened a network monitor with extensions installed. Traffic from an empty tab appears alarming, and telling who is sending it and why is difficult at first glance. It is worth understanding how to distinguish a harmless update from telemetry.
I set up a popular add-on for tabs, and everything works. But the network monitor shows it pinging some third-party domain once a minute, even when the tab stays idle. The listing doesn’t mention it. Is this tracking, or am I reading too much into it?
The first move is to separate yours from theirs: disable all extensions in one go and check whether the background noise stops. If it goes quiet, the source is one of them, and you switch each back on in turn until the traffic reappears. That finds the culprit in two minutes flat, no guessing.
Why exactly the permission list doesn’t settle this
Access to tabs in the manifest and passing their list outward are two different things, and a single permission line cannot distinguish them. Formally the add-on honestly declares access; what it does with that access is not visible from the manifest. So look at the traffic, not the permission list.
It is simpler not to guess each time and leave a webmaster toolkit close at hand — ones that state plainly they collect nothing. And this tab task is quick to close with a telemetry-free stand-in — automatic branding from a logo, works the same and doesn’t call home.
Reviews like this are valuable not for paranoia but for the habit: a few minutes with the network monitor after installing, and “pinging somewhere” becomes a plain picture of what goes where.