🚨Appeals Court WARNS Trump over TAX CRIMES…
Trump Administration’s IRS–ICE Data Pipeline Takes a Major Court Hit — D.C. Circuit Calls One Defense “Weak Sauce”
A federal appeals court has delivered a major setback to the Trump administration’s effort to use Internal Revenue Service data in immigration enforcement — and the ruling is unusually blunt about why the government’s implementation failed.
On September 8, the U.S. Court of Appeals for the D.C. Circuit unanimously upheld a preliminary injunction blocking the IRS from using a specialized data-exchange procedure to disclose taxpayer information to Immigration and Customs Enforcement unless the statutory safeguards in federal tax law are actually met.
The court even called one of the IRS’s arguments “weak sauce.” But the most consequential part of the ruling is not the insult. It is the court’s conclusion that the government’s mass-processing system likely violated the strict confidentiality rules Congress imposed on tax information after Watergate — rules backed by civil remedies and potential criminal penalties for willful unlawful disclosures.
The Court Did Not Strike Down the MOU Itself — It Targeted How the Government Used It
That distinction is essential because the original commentary overstates what the D.C. Circuit actually did.
The IRS and DHS entered into a memorandum of understanding in April 2025 laying out how ICE could request taxpayer address information under a narrow criminal-investigation exception in Internal Revenue Code Section 6103(i)(2). In an earlier case, the D.C. Circuit held that the MOU, on its face, largely tracked the statute and was not itself a reviewable final agency action.
The newer case examined something different: the IRS’s actual Data-Exchange Procedure — the operational system officials built to process ICE requests at scale.
According to the appellate court, that procedure did not reliably enforce the safeguards Congress wrote into Section 6103. It could accept incomplete address information, and it did not ensure that the ICE contact listed on a request was actually an officer or employee personally and directly engaged in the qualifying criminal investigation.
The ruling does not establish that every IRS–ICE information exchange is illegal. It holds that this particular implementation likely violated the statutory conditions that must be satisfied before protected tax information can be disclosed.
ICE Asked the IRS to Search 1.28 Million People
The scale is what turns this from a technical administrative-law dispute into a national privacy story.
ICE Acting Director Todd Lyons submitted a request seeking the last known addresses of approximately 1.28 million undocumented individuals. The request was framed around potential investigations under a federal criminal statute covering certain people who willfully remain in the United States after a final removal order.
The IRS then developed an automated procedure for handling those requests. By the time the district court stepped in, the agency had identified and disclosed 47,289 records to ICE.
More than 90 percent of those records were produced through a matching method that, according to the appeals court, did not verify whether ICE had supplied a legally sufficient address. The procedure merely checked that the address field contained five or nine digits — numbers that did not even have to be a real ZIP code.
The 1.28 million figure is the number of people covered by ICE’s request, not the number whose tax records were actually turned over. The record before the court identified 47,289 disclosures.
Why Taxpayer Confidentiality Is Treated Differently
Federal tax law starts from a simple rule: returns and return information are confidential. Congress built narrow exceptions, including certain disclosures for nontax criminal investigations, but those exceptions come with detailed conditions.
A requesting agency must identify the taxpayer, the relevant tax period, the legal authority for the investigation and specific reasons the requested information may be relevant. The information is then supposed to go only to officers or employees personally and directly engaged in the qualifying criminal matter.
Those restrictions are not accidental. The modern confidentiality regime was strengthened after Watergate-era abuses demonstrated how dangerous tax information could become when used as a political or investigative weapon.
Judge Cornelia Pillard, writing for a unanimous three-judge panel, emphasized that the IRS’s new procedure represented a dramatic move away from individualized review toward automated processing of huge numbers of records.
The Government’s “Weak Sauce” Argument
The most viral line in the opinion came when the IRS argued that the district court’s injunction was “highly unusual and harmful” because it required advance notice before certain disclosures connected to criminal investigative activity.
The D.C. Circuit was unimpressed. Because the district court allowed those notices to be filed under seal, the panel concluded that legitimate investigative activity could remain confidential while the court checked whether the government was complying with the law.
The opinion’s response was two words: “weak sauce.”
The phrasing is memorable, but the legal point underneath it matters more. The government does not gain a legitimate law-enforcement interest in using a procedure that is likely contrary to the statute merely by labeling the underlying activity a criminal investigation.
The Court Mentioned Criminal Penalties — but It Did Not Threaten Immediate Arrests
This is another place where the source video goes beyond what the opinion actually says.
Section 6103 is backed by serious consequences. Federal law allows civil damages for certain unlawful inspections or disclosures, including punitive damages in cases involving willfulness or gross negligence. A federal officer or employee who willfully discloses return information in violation of the statute can also face a felony charge.
The D.C. Circuit cited those provisions while explaining why Congress treated taxpayer confidentiality so seriously and why those remedies did not prevent courts from reviewing unlawful agency policy under the Administrative Procedure Act.
What the panel did not do was announce that IRS personnel were about to be jailed, order prosecutors to bring charges, or find any named employee criminally guilty.
Potential criminal exposure under Section 7213 depends on a willful unlawful disclosure and a separate prosecutorial process. The September 8 ruling itself is an appellate decision upholding preliminary injunctive relief, not a criminal conviction of IRS personnel.
Kristi Noem’s Department Is at the Center of the Policy Fight
The information-sharing push grew out of the Trump administration’s broader immigration enforcement campaign. DHS and ICE wanted taxpayer addresses to help locate people they said could be subjects of qualifying criminal investigations connected to final removal orders.
That made the IRS attractive for an obvious reason: tax administration depends on people voluntarily providing current, highly sensitive personal information to the government.
Critics argued that turning that database into an immigration-enforcement locator system could undermine trust in tax filing, particularly among immigrant communities. Supporters of the administration’s position argued that Congress itself created a criminal-investigation exception and that lawful requests should not be blocked simply because they arise in the immigration context.
The D.C. Circuit’s answer was narrower than either political framing. The statute permits certain disclosures — but only when its conditions are genuinely satisfied.
The Strongest Defensible Conclusion
What is verified is already significant. ICE sought address information covering roughly 1.28 million people. The IRS used a mass data-exchange system that produced more than 47,000 disclosures. A federal district court blocked further use of that system, and a unanimous D.C. Circuit panel has now affirmed that preliminary relief.
The appellate court concluded that the Data-Exchange Procedure was reviewable final agency action and that plaintiffs were likely to succeed in showing it violated Section 6103’s statutory requirements. It also rejected the government’s attempt to characterize the advance-notice requirement as intolerably harmful.
What is not established is that the MOU itself automatically makes all cooperation between IRS and ICE unlawful, that every person whose information was disclosed was targeted for purely civil immigration enforcement, or that the court has ordered criminal charges against IRS officials.
May you like
The strongest defensible conclusion is this: the Trump administration tried to build an immigration-enforcement pipeline through one of the government’s most sensitive databases, and the D.C. Circuit has now said the actual system used to operate that pipeline likely crossed legal lines Congress deliberately made difficult to cross.
That is a major legal defeat even without exaggerating it — and because taxpayer confidentiality sits at the foundation of voluntary tax compliance, the consequences of this fight reach far beyond immigration policy.
