(This "contribute back" aspect is, IMO, the core difference between MIT/BSD and the GPL.)
It strikes me such companies never intended to comply with their legal obligations - make that position financially untenable and use the money to support development/developers who are compliant.
Most companies will see a lawsuit as an attack, and blacklist interacting with you in the future if they can. It reflects badly on the FOSS community, and makes future interactions even more difficult. There are a lot of businesses that will fight relying on any FOSS product, but leap at precisely the same thing with a paid license.
However, more polite requests usually get canned without reading.
This is a tough problem, with hypersensitive businesses thrown in the mix. Wielding the GPL like a hammer won't help, but ignoring it won't either.
The companies that will strip out FOSS from all of their products will have to cripple their product, increase their lead times and increase their costs - possibly all three.
If FOSS is competing with their closed source product, that makes FOSS more competitive. If companies that respect FOSS compete with their product, that makes them more competitive. These are good things.
I don't think it pays to accommodate companies with laywers that behave irrationally in response to enforcement of the GPL and it certainly doesn't pay to respond to bully tactics by relenting.
But how about a public case?
Verizon got caught breaching the GPL with Busybox.[!] At the end of the day, they agreed to become compliant... And Busybox is no longer a product they use or distribute. [0][1]
[!] https://www.softwarefreedom.org/news/2008/mar/17/busybox-ver...
[0] https://www.verizon.com/support/residential/internet/equipme...
The whole point of the GPL is that it's an enforceable license.