Wire
Victims could sue platforms over child abuse material
The STOP CSAM amendment would let people seek actual damages or $300,000, plus fees, in federal court. It also removes the usual time limit and says Section 230 cannot be used to block these claims.
In federal court, victims of child sexual abuse material would get a broader way to pursue the companies that helped spread it, not just the people who created it. Under STOP CSAM, a provider of an interactive computer service or an app store could face suit if it intentionally, knowingly or recklessly promotes abuse material or aids and abets one of the listed exploitation offenses involving a minor.
That is a meaningful shift for survivors because the amendment treats some platform conduct as direct legal exposure, not just a moderation problem. It also reaches certain hosting or storing conduct tied to those offenses, and it says the injury can be actionable even if it happened long ago.
A new defendant in the case
The amendment also broadens the current victim-suit section so some additional people can sue, including those depicted as minors in child pornography or in identifiable-minor depictions covered by federal obscenity law. That widens the circle of people who can turn to court after the image has circulated far beyond the original abuse.
For victims, that matters because the lawsuit would not be limited to the first criminal act. If a service is accused of actively promoting or helping move the material, the company itself becomes part of the harm being litigated.
Cash, court orders and no stopwatch
Winning plaintiffs could recover actual damages or $300,000 in liquidated damages, plus attorney fees and other litigation costs. Courts could also award punitive and injunctive relief, giving victims both money and leverage to push for changes in how services handle CSAM-related content.
There would be no filing deadline under the new claim, which matters in cases where survivors may not be ready to sue for years. STOP CSAM also says Section 230, the law often used to shield online services from liability for user-posted material, cannot be read to block these claims. And it draws one line for encryption: encryption use alone would not create liability.