If they are doing ad injection, it is unclear whether or not they could be successfully sued. Some browser plugins with very large user bases inject/modify ads, and although some have received cease and desist letters from content providers, and some have been sued and settled out of court before trial, I don't believe any have gone to trial and lost. The law is murky at best on that issue, and as the ISP, odds are that AT&T would be in a far stronger legal position than even the browser plugins that have been doing this for years.
AT&T is a message relayer, while the browser plugin is a specific program installed by the user to modify the messages they receive.
There's no legal question I could hire a secretary to open my mail for me, and white-out the lines I told her I didn't want to see, but it would be a little strange for a mail carrier to open messages and insert ads.
Would that still hold if they inserted ads?
However, the plugin companies aren't in an ambiguous situation at all: someone who requests the page is explicitly requesting it to use the content to run a program which renders an image from it, and is under no contractual obligation (from merely making an HTTP request) to view the entirety of the content. They can neither complain that it's being processed (the browser inherently does that, to make an image from the text), and they can't complain that the end-user is failing to uphold their end of an agreement.
Because it's a user chosen process, and because of how content on the internet is relayed, there's no reason that the plugins are on any kind of shaky ground. (One notable exception would be interacting with dynamic content to bypass a paywall. There likely are other exceptions, but these come down to bypassing some kind of mechanism, not merely failing to load or render a particular portion of the sent content.)
I have also been unable to discern ATT's gigapower ads from other ads.
What is more concerning is how AT&T actually serves those targeted ads. Are they injecting ads into pages and modifying HTML? That seems like an incredibly disastrous procedure which would hopefully get them into trouble with content providers and even the FCC. I surely hope that's not the case.