Posts

The List of Rules Marko Elez Didn’t Sign

One of the lawsuits in which it was recently disclosed that DOGE boy Marko Elez emailed information with Personally Identifiable Information to two people at GSA (which I also wrote about here) is one in which Public Citizen is representing AARP in a Privacy Act claim against Treasury. [docket]

The government provided it in that case amid a discovery dispute, mostly as a courtesy because they were filing it in New York. But it contributed to a request for more information about what the hell Marko Elez was up to.

On February 18, Colleen Kollar-Kotelly ordered the government to file any Administrative Record behind the decision to give DOGE access to Treasury. The government squawked about that order, but after plaintiffs noted that the real decision maker in this case was Treasury Secretary Scott Bessent, not the people who had submitted declarations, Judge Kollar-Kotelly ordered those submitted, which the government provided — as a 215 page exhibit — on March 10.

On March 14 — the same day Treasury disclosed Elez’ mailed files to GSA — they supplemented that record. Some of the new documents appear to include some of the details Treasury gathered as they tried to figure out what Elez had done with his access.

That includes this data, showing that when someone first tried to give Elez access to the Top Secret Treasury Mainframe, they equivocated about whether to give Elez read only (the message on January 30) or read-write (the message the next day); at the time he appears to have been granted interim Secret, not Top Secret, clearance.

The main exhibit in the Administrative Record includes a spreadsheet showing what access he was supposed to have as of February 1, reflecting the sandboxed access described in earlier filings. It doesn’t reflect this read-write access.

Plaintiffs are also interested in Elez’ access during a late January trip to Kansas City, which has never been addressed in the declarations in this case.

What plaintiffs didn’t ask about (though they do ask for backup) is the letter sent on February 5 asking Elez to please sign the rules that go along with the Fiscal Service laptop Elez used to access Treasury networks.

Those rules include the following:

  • Use Fiscal Service data, equipment, and IT systems properly and follow laws, regulations, and policies governing the use of such resources (Base Line Security Requirements, (BLSRs), Treasury Information Technology Security Program (TD-P 85-01), the Treasury Security Manual (TD-P 15-71), and Fiscal Service Policies).
  • Protect Fiscal Service data, equipment and IT systems from loss, theft, damage, and unauthorized use or disclosure. Secure mobile media (paper and digital) based on the sensitivity of the information contained.
  • Use appropriate sensitivity markings on mobile media (paper and digital).
  • Promptly report any known or suspected security breaches or threats, including lost, stolen, or improper/suspicious use of Fiscal Service data, equipment, IT systems, or facilities to the IT Service Desk at 304-480-7777.
  • Do not attempt to circumvent any security or privacy controls.
  • Logoff, lock, or secure workstation/laptop to prevent unauthorized access to Fiscal Service IT systems or services.
  • Do not read, alter, insert, copy, or delete any Fiscal Service data except in accordance with assigned job responsibilities, guidance, policies, or regulations. The ability to access data does not equate to the authority to access data. In particular, Users must not browse or search Fiscal Service data except in the performance of authorized duties.
  • Do not reveal any data processed or stored by Fiscal Service except as required by job responsibilities and within established procedures.
  • Do not remotely access Fiscal Service IT systems unless authorized to do so, such as an approved telework agreement authorizing remote access over the bureau’s VPN software.
  • Do not transport or use Fiscal Service data or equipment outside of the United States or US Territories without written approval from the CSO or CISO.
  • Do not connect Fiscal Service equipment to or access a Fiscal Service IT system from a foreign network without written approval from the CSO or CISO.
  • Do not install or use unauthorized software or cloud services on Fiscal Service equipment.
  • Take reasonable precautions to prevent unauthorized individuals from viewing screen contents or printed documents.
  • Do not open e-mail attachments, or click links, from unknown or suspicious sources.
  • Be responsible for all activities associated with your assigned user IDs, passwords, access tokens, identification badges, Personal Identity Verification (PIV) cards, or other official identification device or method used to gain access to Fiscal Service data, equipment, IT systems, or facilities.
  • Protect passwords and other access credentials from improper disclosure. Do not share passwords with anyone else or use another person’s password or other access credential such as, but not limited to, someone else’s PIV card.
  • Use only equipment and software provided by Fiscal Service or that has been approved for use by Fiscal Service’s CIO or designee to conduct Fiscal Service business.
  • Provide non-work contact information to the bureau to facilitate emergency communications.
  • Comply with Fiscal Service social media policy, including restrictions on publishing Fiscal Service information to social media and public websites. [my emphasis]

One of these rules, about not revealing data processed by Fiscal Service, would seem to apply to his sharing of information with GSA.

There’s no evidence Elez ever did sign those rules. Instead, he quit — and, without evidence, the entire world has assumed he quit because he was revealed to have made racist comments on social media.

It’s not yet clear what happened; perhaps it’ll become more clear if plaintiffs get discovery. But by all appearances, on Scott Bessent’s authority, someone at least considered giving a guy only cleared to the Secret level Read/Write access to Treasury’s Top Secret Mainframe, without first making sure he had signed a list of rules about altering or copying data.

And then he left.

Update: I’ve tweaked this reflecting the comment below that the Mainframe may be called Top Secret, without actually being classified Top Secret.

Update: Judge Kollar-Kotelly did grant more limited discovery. That includes most, but not all, details plaintiffs wanted about Elez’ email:

9. With respect to the email sent by Marko Elez referred to in paragraph 12 of the declaration of David Ambrose, ECF 48-2:

a. identify each addressee, including any cc’s or bcc’s.

b. state the date on which the email was sent.

c. identify each individual, if any, who authorized or directed Mr. Elez to send the email.

d. identify the Bureau Systems from which the Personal Information contained in the email or the attached spreadsheet was obtained.

[removed]

f. describe the nature of the information that was transmitted, including whether the information relates to the USAID files that Mr. Elez copied, as noted in paragraph 18 of Joseph Gioeli’s declaration, ECF 24-2.

Share this entry

Marko Elez “Resigned” the Day His Write Access to Payment Systems Was Discovered

According to the currently operative story, Marko Elez — the DOGE [sic] boy who had source code for Treasury’s payments system — resigned in response to a query from WSJ reporter Katherine Long about his social media posts in support of

A key DOGE staff member who gained access to the Treasury Department’s central-payments system resigned Thursday after he was linked to a deleted social-media account that advocated racism and eugenics.

Marko Elez, a 25-year-old who is part of a cadre of Elon Musk lieutenants deployed by the Department of Government Efficiency to scrutinize federal spending, resigned after The Wall Street Journal asked the White House about his connection to the account.

“Just for the record, I was racist before it was cool,” the account posted in July, according to the Journal’s review of archived posts.

“You could not pay me to marry outside of my ethnicity,” the account wrote on X in September. “Normalize Indian hate,” the account wrote the same month, in reference to a post noting the prevalence of people from India in Silicon Valley.

After the Journal inquired about the account, White House spokesperson Karoline Leavitt said that Elez had resigned from his role.

But that belief is only based on correlation, not any proof of causation. Long asked about posts that are in no way exceptional for the far right boys Elon has infiltrated into the government. And Elez resigned that same day.

Sure, Elon implied that Elez quit because the boy’s far right ideology was exposed — he led a campaign for his reinstatement. That campaign — and JD Vance’s support for it — similarly led a lot of people to believe that Elez had been reinstalled at Treasury. But multiple court filings claim that Elez resigned and never came back, at least not to Treasury.

In fact, there are two things that might provide better explanations than the discovery that like Elon himself, Elez is a racist.

As WSJ itself notes, Elez resigned the same day that Colleen Kollar-Kotelly ordered that Elez, then still identified as a Special Government Employee, be granted only read-only access to Treasury’s networks. Once Elez no longer worked for the defendants in that case — starting with Scott Bessent — then any access he had would be exempted from the order.

More importantly, as a court filing submitted yesterday reveals, Elez’ resignation happened the same day that Treasury discovered Elez’s Bureau laptop, “had mistakenly been configured with read/write permissions instead of read-only.” The filing is a declaration from Joseph Gioeli, who has been employed as the “Deputy Commissioner for Transformation and Modernization in the Bureau of the Fiscal Service” since 2023 and is a civil servant first hired in the first year of Trump’s first term.

His declaration describes how the 4-6 week “payment process engagement plan” initiated (per Thomas Krause) on January 26 required giving Elez risky access to payment systems. Gioeli describes how they tried to mitigate those risks.

11. The scope of work as envisioned in the engagement plan required access to Fiscal Service source code, applications, and databases across all these Fiscal Service payment and accounting systems and their hosting environments. This broad access presented risks, which included potential operational disruptions to Fiscal Service’s payment systems, access to sensitive data elements, insider threat risk, and other risks that are inherent to any user access to sensitive IT systems. In light of these risks, BFS and Treasury Departmental Office employees developed mitigation strategies that sought to reduce these risks.

12. These measures included the requirement that Mr. Elez be provided with a BFS laptop, which would be his only method of connecting to the Treasury payments systems, both in connecting with the source code repository and for his read-only access of the systems. He had previously been provided a Treasury laptop from the Department shortly after he onboarded, but due to Bureau security policy, that device was restricted from accessing the BFS systems and services he had requested. BFS used several cybersecurity tools to monitor Mr. Elez’s usage of his BFS laptop at all times and continuously log his activity. Additionally, the Bureau enabled enhanced monitoring on his laptop, which included the ability to monitor and block website access, block the use of external peripherals (such as USB drives or mass storage devices), monitor any scripts or commands executed on the device, and block access to cloud-based storage services. Additionally, the device contained data exfiltration detection, which alerts the Bureau to attempts to transmit sensitive data types. The laptop is also encrypted in accordance with Bureau policy, which, if the laptop were stolen or lost, would prevent unauthorized users from accessing data contained within the laptop.

13. Additional mitigation measures that were adopted included that Mr. Elez would receive “read-only” access to the systems, and that any reviews conducted using the “read-only” access would occur during low-utilization time periods, to minimize the possibility of operational disruptions. While providing a single individual with access to multiple systems and data records accessed here was broader in scope than what has occurred in the past, this read-only approach is similar to the kind of limited access the Bureau has provided to auditors for other Treasury non-payment systems, though even in those scenarios the availability of production data was significantly limited. [my emphasis]

Gioeli goes on to describe how, starting on February January 28, the Bureau gave Elez source code in a sandbox environment.

16. On January 28, 2025, the Bureau provided Mr. Elez with the Bureau laptop and with copies of the source code for PAM, SPS, and ASAP in a separate, secure coding environment known as a “secure code repository” or “sandbox.” Mr. Elez could review and make changes locally to copies of the source code in the cordoned-off code repository; however, he did not have the authority or capability to publish any code changes to the production system or underlying test environments. This repository was separate from Fiscal Service’s typical code development environment, and unlike the usual code development environment, this new repository was segmented, to ensure that no changes to the operative source code could be made. [my emphasis]

Then, six days after giving him that sandbox access, using the same laptop, they gave him read-only access to first two and then one more systems.

17. On February 3, 2025, consistent with the engagement plan and mitigation measures developed, Mr. Elez was provided with read-only access, through his Bureau laptop, to the certain BFS systems. The read-only access that Mr. Elez was provided gives the user the ability to view and query information and data but does not allow for any changes to that information and data within its source system. While this reduces risk, it does not fully eliminate the risks identified in the assessment (for example, the risk of overburdening the system with a complex read-only query). Specifically, Mr. Elez was provided read-only access to the Payment Automation Manager (PAM) Database, Payment Automation Manager (PAM) File System, and, subsequently on February 5, the Secure Payment System (SPS) Database.

After he got that access, per a review of the logs, Elez copied some files from the active database onto his Bureau laptop, on which he had the source code.

18. ISS configured his network access and assisted him in setting up the necessary tools to connect to the PAM database on February 3. His access was closely monitored by multiple BFS administrators throughout the process on February 3. That same day, he received a “walk-through” demonstration of two BFS payment systems, the PAM database and the PAM file system (the system that controls the payment file “landing zone” discussed above), to see how the systems worked. He logged in with his read-only access to these systems on February 3 during this “walk-through” demonstration. The Bureau is in the process of reviewing the logs of Mr. Elez’s activity on his Bureau laptop, and this review remains ongoing. Based on the preliminary log reviews conducted to date, it appears that on February 3, Mr. Elez copied two USAID files directly from the PAM database to his BFS laptop; on February 4 and 5, Mr. Elez accessed the PAM file system; and on February 5, Mr. Elez accessed the PAM payment processing database. These activities are consistent with the read-only access that Mr. Elez was provided and did not change or alter any BFS payment system or record within their source systems. As noted, reviews of Mr. Elez’s work are still actively occurring; I do not have any more detail to provide at this time about his activities with respect to PAM. [my emphasis]

Then, on February 5, Elez got access to the payment system itself — again, with the same laptop on which he had source code.

19. Due to scheduling constraints, Mr. Elez was unable to meet with Bureau personnel to set up his access to the SPS database until February 5. On that date, lSS held a virtual walk-through session to help him to connect to the SPS database. He accessed this database exclusively under the supervision of Bureau database administrators in a virtual walkthrough session. According to the preliminary review of logs the Bureau has conducted to date, it appears Mr. Elez accessed the SPS database only once during that walk-through demonstration on February 5. It does not appear that he accessed the database again. As part of the ongoing review, additional log reviews are currently underway to confirm this. Mr. Elez never logged into ASAP, CARS, or ITS.gov, as technical access to those systems was never established for him. [my emphasis]

The next day, “it was discovered” (Gioeli does not say by whom, which means we’re not seeing a declaration from that person) that Elez actually “had mistakenly been configured” with read/write access, rather than “read only.”

20. On the morning of February 6, it was discovered that Mr. Elez’s database access to SPS on February 5 had mistakenly been configured with read/write permissions instead of read-only. A forensic investigation was immediately initiated by database administrators to review all activities performed on that server and database. The initial investigation confirmed that all of Mr. Elez’s interactions with the SPS system occurred within the supervised, walk-through session and that no unauthorized actions had taken place. His access was promptly corrected to read-only, and he did not log into the system again after his initial virtual over-the-shoulder session on February 5. To the best of our knowledge, Mr. Elez never knew of the fact that he briefly had read/write permissions for the SPS database, and never took any action to exercise the “write” privileges in order to modify anything within the SPS database—indeed, he never logged in during the time that he had read/write privileges, other than during the virtual walk-through – and forensic analysis is currently underway to confirm this. [my emphasis]

Throughout his declaration, Gioeli stresses that they’re still investigating whether Elez did something unauthorized with his access.

21. As noted above, the Bureau used several cybersecurity tools to monitor Mr. Elez’s usage and continuously log his activity. While forensic analysis is still ongoing, Bureau personnel have conducted preliminary reviews of logs of his activity both on his laptop and within the systems and at this time have found no indication of any unauthorized use, of any use outside the scope that was directed by Treasury leadership, or that Mr. Elez used his BFS laptop to share any BFS payment systems data outside the U.S. Government.

And his declaration stops short of saying that some mitigation techniques were used. For example, Gioeli says that the enhanced monitoring on Elez’ Bureau laptop had the ability to “block the use of external peripherals (such as USB drives or mass storage devices)” and access to the cloud, but it doesn’t say whether those functionalities was used.

Plus, Gioeli’s declaration makes it clear that they have’t involved Elez in any review of his access. No one has asked Elez, for example, whether he knew he had write access to the payment system.

Similarly, in an earlier declaration submitted in the parallel DC case, Thomas Krause gave a very couched answer about whether Elez had has any ongoing access.

I currently have no reason to believe Mr. Elez retains access to any BFS payment data, source code, or systems.”

Did anyone think to ask the guy? Does anyone know where that guy is? Are you going to interview him? Or is someone deliberately trying to keep him from being questioned further?

Worse still, Thomas Krause declaration submitted in the NY case doesn’t even say that Elez has left Treasury — only that he has resigned from the role of, “working closely with engineers at the Bureau of the Fiscal Service (BFS) on information technology (IT) matters in service of BFS’s mission to promote financial integrity and operational efficiency of the federal government through accounting, financing, collection, payment, and other relevant BFS services.”

On February 6, 2025, Mr. Elez submitted his resignation from this role. On that same day, he turned in his Treasury laptop, BFS laptop, access card, and other government devices; his BFS systems access was terminated; and he has not conducted any work related to the BFS payment systems since that date.

Elez was made a Treasury employee — contrary to early reports, he was not a SGE. That may make it easier to shuffle him off somewhere else.

What Gioeli describes is the panic that ensues when a guy who had high level access quits unexpectedly. And to date, we’ve never been given a formal explanation of why he quit — or whether he was asked to do so. We certainly can’t reconcile the claims that he has been reinstated with claims that he’s not doing what he was doing at Treasury.

Everyone has always assumed that Elez quit because his racism was discovered. But given the timeline, we can’t rule out that he quit because of the access concerns (and ongoing investigation) at Treasury.

Timeline

January 21: Elez hired.

January 23: Krause hired.

January 26: Treasury focuses on USAD. Treasury also adopts a 4-6 week engagement plan.

January 28: Bureau provides Elez with Bureau laptop copies of the source code for PAM, SPS, and ASAP in sandbox.

January 31: Treasury focuses on TAS codes; Elez assists in “automating” manual review of payments. “A high-ranking career official at Treasury also raised the issue of risks from DOGE access in a memo to Treasury Secretary Scott Bessent.”

February 3: Treasury gives Elez access to PAM. Booz threat contractor delivers report warning of grave insider threat.

February 5: Treasury gives Elez access to SPS, the payment system.

February 6 (afternoon): Elez resignation.

February 7: Treasury flags but then approves four payments. WaPo publishes story about Booz report and Booz contractor is fired.

February 8: Paul Engelmeyer limits Krause’s access.

February 10: Millenium Challenge Corporation submits, but then requests not to process, a payment.

Documents

Opposition to Stay

Thomas Krause Declaration: Describing the plan to use technology to provide more oversight over payments (citing three Biden-era GAO reports, not anything DOGE has discovered).

Vona Robinson Declaration: Describing that the only payment that has been intercepted at Treasury was a payment to the Millenium Challenge Corporation.

Michael Wenzler Declaration: Describing the hiring, employment status, revisions thereof, of Thomas Krause and Marko Elez, and also confirming Elez’ resignation from Treasury.

Joseph Gioeli Declaration: Describing the circumstances of Elez’ access and the investigation into what he did with it.

Share this entry

Donald Trump’s Incorrect Shell Game of Appropriated Spending

Yesterday, I argued that Trump would not yet defy courts because he wants to invite the Supreme Court to sanction his dictatorial powers, and so wants a clear appellate record.

Boy howdy was that a short-lived theory. Trump says he is appealing two orders that are not yet ripe for appeal in two lawsuits involving Democratic Attorneys General — RI Judge John McConnell’s order and follow-up order that the government pay grants to the states [appeal] and Paul Engelmeyer’s order ordering Treasury to stay out of the payment system [request for stay pending appeal] — as well as in Special Counsel Hampton Dellinger’s challenge to his dismissal.

So by the time Republicans figure out how they’re going to use reconciliation to pass Trump’s policies, SCOTUS may have already agreed to gut Congress’ power of the purse.

But the record in the spending cases is anything but clean.

In one of the two cases challenging DOGE’s [sic] access to Treasury systems — the DC case before Colleen Kollar-Kotelly — DOJ decided after the fact that Marko Elez, the DOGE [sic] boy who had been granted a copy of Treasury systems to sandbox, was actually a Treasury employee.

With the benefit of more time to investigate the facts over the weekend, Defendants came to understand that Marko Elez, who, at the time of the hearing was employed by the Department of the Treasury, had not, in fact, been designated by the Treasury Department as a Special Government Employee (SGE), as counsel stated at the February 5 hearing. Mr. Elez, was, however, a Treasury Department employee. Treasury hired Mr. Elez as Special Advisor for Information Technology and Modernization, Departmental Offices, Office of the Chief of Staff, under Treasury’s authority to establish temporary transitional Schedule C positions. See 5 C.F.R. § 213.3302. Although Mr. Elez could have been designated as an SGE because he was slated to perform temporary duties either on a full-time or intermittent basis for not more than 130 days, the Treasury department Ethics office did not designate Mr. Elez as a Special Government Employee, meaning that he in fact had to comply with additional ethics requirements that are not required for SGE positions.

[snip]

Defendants also wish to notify the Court that, as stated in the Declaration of Thomas Krause, Jr., filed yesterday, in State of New York v. U.S. Department of the Treasury, Case No. 25 Civ. 01144 (JAV) (S.D.N.Y.), Mr. Elez resigned from Treasury on February 6, 2025, and he returned all Treasury and BFS equipment and credentials the same day. See Exhibit 1, ¶ 11. Moreover, in that case, on February 8, the Court entered a temporary restraining order restricting who may access Treasury systems. See Ex. 2. Those restrictions are in addition to those imposed by this Court’s Order entered February 6.

This filing included Thomas Krause’ declaration (submitted in the Treasury suit filed by states, which Trump is appealing) describing that Elez had resigned (but not addressing whether he has been reinstated; in retrospect, it seems the declaration was written specifically to avoid calling Elez a DGE). But it didn’t include the underlying filing in the case, which in a footnote confesses that Elez had a full copy of the BFS system in a sandbox, falsely claiming that Krause addressed this in his declaration.

2 Since January 20, 2025, one other Treasury employee—Marco Elez—had “read only” access to or copies of certain data in BFS payment systems, subject to restrictions, and access to a copy of certain BFS payments systems’ source code in a “sandbox” environment. Krause Decl. ¶ 11. Mr. Elez resigned on February 6, 2025 and returned all Treasury and BFS equipment and credentials the same day. Id

This means that this correction doesn’t correct another false claim DOJ made to Kollar-Kotelly: that Elez’ access had been “read only.” And DOJ hasn’t told Judge Jeanette Vargas (to whom the New York case was assigned after Engelmeyer issued the TRO) that Elez is a full Treasury employee and so, if he has been reinstated, potentially excluded from Engelmeyer’s order.

In the USAID case, where Trump might believe he can coax a favorable ruling from his own first term appointee, Carl Nichols, Peter Marocco submitted a long, obnoxious declaration claiming they had to shut down USAID because of widespread insubordination among USAID employees. (I’d quote from it but the declaration breaks local rules requiring OCR filings.)

But after Marocco submitted that filing, the career AUSAs on the case submitted a declaration that included this correction.

Additionally, although Secretary Rubio’s January 24, 2025 directive only froze future contract obligations, id. ¶ 3, payments on existing contracts were paused as well as part of efforts by agency leadership to regain control of the organization’s spending and conduct a comprehensive review of its programs. See id. ¶¶ 5–10. Counsel for Defendants was unaware of this development prior to the hearing. [my emphasis]

Marocco confesses that existing contracts “were paused” by him this way:

Furthermore, many of USAID’s pre-existing programs were in conflict with the directives and priorities of the President and Secretary, and therefore were inconsistent with the public interest and foreign policy judgments of the Executive Branch. Given the scale of these programs, an ad hoc review of these conflicting programs would unduly burden the execution of the President’s other foreign policy priorities. A blanket pause with a waive-in process was the more efficient and effective path.

He describes this notice Marco Rubio sent to Congress, which makes no mention of pausing ongoing work. Then he continues to describe how existing programs “were paused” by him.

The first step of this review, in essence, involved the majority of USAID pausing a substantial portion of its ongoing work — going “pencils down” — so the Secretary and USAID leadership could gain control of the organization that included some employees who had refused to comply with lawful directives by the President and Secretary, directives designed to identify wasteful or fraudulent programs or those contrary to the foreign policy interests of the United States. The pause of ongoing work and use of paid administrative leave have enabled Agency leadership to begin a thorough review of USAID’s operations and align its functions to the President’s and Secretary’s priorities, without continued noncompliance by former Agency leadership and management undermining those priorities. Pausing a majority of USAID’s work was, and remains, necessary to continue this thorough review into the noncompliance issues first identified, as well as to continue to examine USAID’s processes and the manner in which USAID funds its programs.

In other words, the people that Marocco calls noncompliant are noncompliant because they’re following the law, a law uncontroverted by Trump’s order or even Rubio’s notice to Congress.

As Nichols said when he issued the TRO ordering USAID to reinstate employees, whether or not this involved existing or only prospective contracts was an issue of some contention in the hearing.

Plaintiffs finally seek a TRO as to Secretary Rubio’s January 24, 2025 order freezing funding to USAID’s contractors. As a threshold matter, the Court notes that there are significant factual questions about what the practical effect of that order is. The government argued at the hearing that the order only prevents USAID from entering “new obligations of funding”—leaving it free to pay out contracts that it entered into prior to January 24, 2025—and indeed, the text of the order does seem to permit that result. Dep’t of State, Memo. 25 STATE 6828. Yet, plaintiffs maintained at the TRO hearing that payments on existing USAID grants have been frozen, preventing certain “contracting officers” employed by USAID from using agency funds to fulfill monetary commitments that the agency had already made.

This factual dispute is relevant to plaintiffs’ TRO arguments, but ultimately is not dispositive of them. Plaintiffs allege that, by some legal mechanism, USAID contracting officers can be held personally liable for existing contractual expenses that USAID is supposed to, but does not, pay. Plaintiffs thus argue that those officers face irreparable harm as a result of the funding freeze because they will be left “holding the bag” when USAID imminently fails to disburse funds. Separately, plaintiffs argue that the general population of USAID employees will be emotionally harmed by the agency’s inability to pay its contractors because they will be stuck “watching a slow speed train wreck” as the agency reneges on its humanitarian commitments.

Even assuming the funding freeze indeed prevents payments on existing grants in the way plaintiffs claim (instead of merely preventing USAID from entering new obligations, as the government suggested during the hearing), the Court concludes that plaintiffs have not demonstrated resulting irreparable harm.

But because this suit involves employees, rather than states or other recipients of funds from Treasury (as is the case in the two suits where DOJ has said it will appeal), these plaintiffs themselves are not being injured because they’re still being paid.

DOJ is hiding behind career AUSAs making claims they likely do not know are false so as to shut down appropriations that have already been approved.

And they are appealing each instance in which a plaintiff has genuinely been injured (the states and Hampton Dellinger’s firing) in hopes — or maybe expectation? — after the Circuits deny appeals that are not yet ripe, SCOTUS will step in and render Congress impotent.

Update: USAID Inspector General somehow managed to put together a report on the damage the chaos is having. Among other things, it finds that the cuts have incapacitated any means of vetting disbursements to keep them out of the hands of terrorists.

USAID describes partner vetting as a risk-mitigation tool to “ensure that American taxpayer funds do not benefit terrorists and their supporters.” Currently, partner vetting is required for programming in Afghanistan, Iraq, Lebanon, Pakistan, Syria, West Bank/Gaza, and Yemen where designated terrorist organizations such as Hamas, Hezbollah, ISIS, and Ansar Allah (also known as the Houthis) operate. Before the Agency awards a contract, grant, or cooperative agreement in these locations, the proposed awardee must submit to USAID data needed to vet the organization and its key personnel. The same vetting must be undertaken before an aid organization issues a subaward. While USAID OIG has previously identified gaps in the scope of partner vetting, 10 USAID staff have reported that the counter-terrorism vetting unit supporting humanitarian assistance programming has in recent days been told not to report to work (because staff have been furloughed or placed on administrative leave) and thus cannot conduct any partner vetting. This gap leaves USAID susceptible to inadvertently funding entities or salaries of individuals associated with U.S.-designated terrorist organizations.

Share this entry

It’s Still Not Clear Whether Elon’s DOGE Boys Are Reviewing, Taking, or Altering Government Networks

The big news overnight in the legal fight to rein in DOGE is that SDNY Judge Paul Engelmayer has ordered Treasury to stop letting Elon Musk’s DOGE [sic] boys to snoop in Treasury’s payment system and destroy any copies of records already made from it. [docket]

the defendants are (i) restrained from granting access to any Treasury Department payment record, payment systems, or any other data systems maintained by the Treasury Department containing personally identifiable information and/or confidential financial information of payees, other than to civil servants with a need for access to perform their job duties within the Bureau of Fiscal Services who have passed all background checks and security clearances and taken all information security training called for in federal statutes and Treasury Department regulations; (ii) restrained from granting access to all political appointees, special government employees, and government employees detailed from an agency outside the Treasury Department, to any Treasury Department payment record, payment systems, or any other data systems maintained by the Treasury Department containing personally identifiable information and/or confidential financial information of payees; and (iii) ordered to direct any person prohibited above from having access to such information, records and systems but who has had access to such information, records, and systems since January 20, 2025, to immediately destroy any and all copies of material downloaded from the Treasury Department’s records and systems, if any;

This order comes on top of Judge Colleen Kollar-Kotelly’s order limiting access to Treasury’s payment system to normal employees and two DOGE [sic] employees, but the latter for read-only access [docket]:

Mr. Tom Krause, a Special Government Employee in the Department of the Treasury, as needed for the performance of his duties, provided that such access to payment records will be “read only”;

Mr. Marko Elez, a Special Government Employee in the Department of the Treasury, as needed for the performance of his duties, provided that such access to payment records will be “read only”;

Anna Bower parsed how DOJ substantiated (or not) that this was really “read only” access. Which was part of what a bunch of Democratic Attorneys General, led by Tish James, pointed to to claim they still needed a TRO, over and above the one issued by Kollar-Kotelly.

The temporary restraining order entered yesterday by the D.C. District Court in Alliance for Retired Americans v. Bessent, No. 1:25-cv-313 (D.D.C.) (“ARA”), does not change this conclusion. That order continues to permit two SGEs affiliated with DOGE to have access to the BFS payment records and payment systems, restricts their access to “read only” just for payment records and not payment systems, and does not direct that any copies of data from the systems made since the Agency Action took effect be destroyed. ARA, Dkt No. 13.

Now, I’m somewhat skeptical that Engelmeyer’s order, as issued, is sustainable. He issued the order in advance of the assigned judge on the case, Jeannette Vargas, and before the government had a chance to respond to the lawsuit.

But the lawsuits to enjoin DOGE [sic] are playing catch-up to the known facts.

And the known facts get us much closer to the being able to prove that Elon and his DOGE [sic] boys are altering code, if not hacking it, rather than simply reviewing its data.

The suit and TRO before Judge Kollar-Kotelly, filed by several unions, is entirely privacy focused.

The state AGs’ suit and TRO, which establish standing by pointing to the billions of dollars of payments they get from the Feds, argues that Elon is attempting to intercept payments to entities Trump doesn’t like. It asserts a claim repeatedly backed in public reporting, but affirmatively denied before Kollar-Kotelly: that the DOGE boys — here, self-proclaimed eugenicist Mark Elez, have altered code.

5. As of February 2, 2025, the President and Treasury Secretary, directed Treasury to grant expanded access to BFS payment systems to political appointees and “special government employees” for reasons that have yet to be provided, although one apparent purpose, upon information and belief. Upon information and belief, one purpose is to allow DOGE to advance a stated goal to block federal funds from reaching beneficiaries who do not align with the President’s political agenda. For example, DOGE was tasked with freezing payments issued by the U.S. Agency for International Development (“USAID”) and sought access to BFS payment systems to accomplish that goal.5 Virtually unfettered access to BFS payment systems was granted to at least one 25-year-old DOGE associate, Mark Elez, who, on information and belief, had the authority to view or modify numerous critical files.6 Indeed, reports indicate that Elez had administrative privileges over the BFS payment system’s code, giving him the ability to alter user permissions and “read and write” code—even if the associate had “read-only” access to the system’s data.7 Elez has since resigned from DOGE after being linked to racist social media posts.8

6. Around the same time that DOGE associates were unlawfully granted access to BFS systems, Mr. Musk began publicly stating his intention to recklessly freeze streams of federal funding without warning. On February 2, 2024, Mr. Musk posted on X (formerly Twitter), an online social media platform, that DOGE is “rapidly shutting down” various “illegal payments” made by the government to grant recipients, including payments to Lutheran Family Services to provide services to migrant children.9 That same day, Mr. Musk posted that his team “spent the weekend feeding USAID into the wood chipper.” Since then, Mr. Musk has unambiguously called for the cancellation of various streams of federal funding. For instance, on February 6, 2025, he alleged: “Billions of taxpayer dollars to known FRAUDULENT entities are STILL being APPROVED by Treasury. This needs to STOP NOW!”10 Mr. Musk has also made wild, unsubstantiated claims about the BFS payment system and suggested putting it on the blockchain.11

6 A 25-Year-Old With Elon Musk Ties Has Direct Access to the Federal Payment System | WIRED

7 https://www.wired.com/story/elon-musk-associate-bfs-federal-payment-system/

8 DOGE Staffer Resigns Over Racist Posts

9 Elon Musk on X: “The @DOGE team is rapidly shutting down these illegal payments” / X

10 Elon Musk on X: “Billions of taxpayer dollars to known FRAUDULENT entities are STILL being APPROVED by Treasury. This needs to STOP NOW!” / X

11 Fatima Hussein, “Elon Musk’s task force has gained access to sensitive Treasury payment systems, sources say,” PBS News, Feb. 2, 2025, https://www.pbs.org/newshour/politics/elon-musks-task-force-hasgained-access-to-sensitive-treasury-payment-systems-sources-say; Billy Bambrough, “‘This Needs To Stop Now’—Elon Musk Confirms Radical Doge U.S. Treasury Plan,” Forbes, Feb. 2, 2025, https://www.forbes.com/sites/digital-assets/2025/02/02/this-needs-to-stop-now-elon-musk-confirmsradical-doge-us-treasury-plan/.

It cites Elon’s insane rants on Xitter as well.

In addition to the privacy concerns addressed in the union lawsuit, the AGs’ lawsuit raises concerns about appropriations (and separation of powers), but also cybersecurity, something not included in the union lawsuit.

139. The conduct of DOGE members presents a unique security risk to States and State residents whose data is held by BFS, given that DOGE employees have already reportedly set up an unauthorized commercial server at another federal agency without a privacy impact assessment as required by the 2002 E-Government Act. Access by DOGE employees to BFS is likely to present even greater risks to the security and privacy of States’ and their residents’ data.

140. Unsecure data is susceptible to cyber attacks and identity theft. Identity theft has a significant impact on States, beyond the financial well-being of its residents. It strains law enforcement resources, damages state economies through lost productivity and consumer confidence, and raises costs for the state to redress fraudulent claims made from stolen identities for unemployment and healthcare benefits. [my emphasis]

The AGs’ suit actually doesn’t cite a source for the claim that DOGE set up a commercial server at another agency. But I think the claim comes from a lawsuit Kel McClanahan filed against Office of Personnel Management, aiming to require it to stop the all-government email DOGE [sic] set up to offer its “Fork in the Road” severance offer. McClanahan first sued, with two plaintiffs who worked at government agencies, on January 27, for a violation of the E-Government Act. [docket]

In response, the government claimed that the main theory of injury, that the government had set up the all-government email without first doing a privacy assessment didn’t apply for employees, and was moot because it had since done one, which it included here. The privacy assessment claimed this was just a Office365 account.

1.3. Has a system security plan been completed for the information system(s) supporting the project? The Office 365 mailbox has been granted an Authorization to Operate (ATO) that includes a system security plan. The government computer storing the data is subject to standard security requirements, including limited PIV access.

And it claimed that the account included only employee data.

2.1. Identify the information the project collects, uses, disseminates, or maintains. GWES collects, maintains, and uses the names and government email addresses of federal government employees. GWES also collects and redistributes responses to emails sent to those addresses, which are limited to short, voluntary, non-identifying information. Specifically, GWES contains the following:

  • Employee Contact Data: GWES collects, maintains, and uses the names and government email addresses of federal government employees. Other identifying information is not used.
  • Employee Response Data: After an email is sent using Employee Contact Data, GWES collects, maintains, and redistributes short, voluntary responses.

It largely ignored McClenahan’s claim (based largely on Reddit posts) that DOGE had installed a separate server.

But other than speculation on social media, Plaintiffs provide no evidence that OPM took any of the actions that would trigger the PIA requirement under sections 208(b)(1)(A)(i)-(ii) of the E-Government Act. Moreover, Plaintiffs disregard entirely the fact that the E-Government Act does not require a PIA when an agency is seeking to collect information about “agencies, instrumentalities, or employees of the Federal Government.”

Since then, McClanahan filed an amended complaint, which added five more plaintiffs, none of whom are Executive Branch employees (for example, one works for the Library of Congress; another is a contractor), substantiating that some of the DOGE emails went to people outside the Executive Branch, and provided additional substantiation of the Reddit claims (including raising questions about whether this could even be Microsoft365).

30. Furthermore, prior to 20 January 2025, OPM lacked the technical capacity to send direct communications to all Executive Branch employees: But just days before President Donald Trump’s inauguration, OPM did not have the capability to send a mass email of that scale, according to a person familiar with the matter. To send mass emails, the agency had used govDelivery, a cloud communications service provided by public sector IT company Granicus, a different person familiar said. The govDelivery contract had restrictions on the volume of emails available to send without incurring added costs, and the agency would not have been able to reach 2.3 million people, the approximate number of all civilian federal employees, the second person added. David DiMolfetta, OPM’s new email system sparks questions about cyber compliance Nextgov/FCW (Jan. 28, 2025), available at https://www.nextgov.com/digitalgovernment/2025/01/opms-new-email-system-sparks-questions-about-cybercompliance/402555/ (last accessed Feb. 3, 2025).

31. Additionally, OPM has used Microsoft Office 365 since at least 2021, including Outlook 365 for email. OPM, Privacy Impact Assessment for OPM – Microsoft Office 365 (May 13, 2021), available at https://www.opm.gov/information-management/privacy-policy/privacypolicy/office-365-pia.pdf (last accessed Feb. 3, 2025). Outlook 365 cannot send more than ten thousand emails per day. See Microsoft, Exchange Online limits (Dec. 11, 2024), at https://learn.microsoft.com/en-us/office365/servicedescriptions/exchange-online-servicedescription/exchange-online-limits#sending-limits-1 (last accessed Feb. 3, 2025).

32. According to the FedNews Message, “Instead [of using the normal channels], an on-prem (on-site) email server was setup [sic]. Someone literally walked into our building and plugged in an email server to our network to make it appear that emails were coming from OPM. It’s been the one sending those various ‘test’ message[s] [discussed below].” FedNews Message.

33. This statement is supported by recent reporting:

A new server being used to control these [OPM] databases has been placed in a conference room that Musk’s team is using as their command center, according to an OPM staffer. The staffer described the server as a piece of commercial hardware they believed was not obtained through the proper federal procurement process.

Caleb Ecarma & Judd Legum, Musk associates given unfettered access to private data of government employees Musk Watch (Feb. 3, 2025), at https://www.muskwatch.com/p/muskassociates-given-unfettered (last accessed Feb. 3, 2025).

34. Upon information and belief, this server and/or other systems linked to it are retaining information about every individual with a Government email address.

The amended complaint argues that the privacy impact was factually and legally insufficient.

39. Neither Biasini nor Hogan were OPM employees prior to 20 January.

40. Biasini worked at the Boring Company prior to 20 January. It is not currently known if he still works there.

41. Hogan worked at Comma.ai prior to 20 January. It is not currently known if he still works there.

42. The GWES PIA was both factually inaccurate and legally inadequate.

[snip]

54. Upon information and belief, OPM has not ensured review of a PIA for any of these systems by any legally sufficient Chief Information Officer or equivalent official.

55. OPM has not published a legally sufficient PIA or made such an assessment available for public inspection for any of these systems.

In other words, as these twin lawsuits against Treasury get closer to arguing that Elon is not looking for savings but instead altering the payment system, McClanahan continues to chase proof that Elon’s DOGE [sic] boys have added their own server which, by dint of sending emails to everyone (including people not employed by the Executive branch) with a .gov address, is collecting information on everyone with a .gov address.

Meanwhile, several other developments get closer to showing that Elon is hacking the government, not assessing it.

First, late this week, OPM removed access by some DOGE [sic] boys to more sensitive OPM systems.

Directives from the agency’s interim leadership issued late this week indicated that DOGE representatives should be withdrawn from two principal systems containing personally identifiable information for millions of federal employees, according to communications reviewed by The Post and people familiar with the developments who spoke on the condition of anonymity because of the matter’s sensitivity.

Those systems are called Enterprise Human Resources Integration and Electronic Official Personnel Folder. They hold sensitive information about employees of most federal agencies, including addresses, demographic profiles, salary details and disciplinary histories.

The Post reported Thursday morning that DOGE agents had gained access to those systems along with “administrative” access to OPM computer systems. That allowed them sweeping authority to install and modify software on government-supplied equipment and, according to two OPM officials, to alter internal documentation of their own activities.

Meanwhile, both Wired and WaPo have stories describing how a Booz Allen analyst described the DOGE [sic] access as an ““unprecedented insider threat risk;” the analyst was promptly fired.

The review, delivered Monday to Treasury officials by a contractor that runs a threat intelligence center for Treasury’s Bureau of the Fiscal Service, said that DOGE’s access to the payment network should be “immediately” suspended. It also urged Treasury to scour the payments system for any changes approved by affiliates of DOGE, which is overseen by billionaire Elon Musk, the correspondence shows. DOGE stands for Department of Government Efficiency.

A Treasury employee told The Post that the threat center is run by Booz Allen Hamilton, a large federal contractor. The company confirmed it runs the threat center, which it said is embedded within Treasury.

Late Friday, after this article appeared, Booz Allen said it had “removed” a subcontractor who wrote the warning and would seek to retract or amend it. “The draft report was prepared by a subcontractor to Booz Allen and contained unauthorized personal opinions that are not factual or consistent with our standards,” company spokesperson Jessica Klenk said. Booz Allen won more than $1 billion in multiyear U.S. government contracts last year.

In a separate communication a week ago, a high-ranking career official at Treasury also raised the issue of risks from DOGE access in a memo to Treasury Secretary Scott Bessent, including the potential breach of information that could lead to exposure of U.S. spies abroad, according to five people with knowledge of the matter, who spoke on the condition of anonymity to reflect government deliberations. The memo included recommendations to mitigate risks, which Bessent approved, said another person familiar with the matter, who also spoke on the condition of anonymity.

And while the focus at Treasury has been on eugenicist Marko Elez, whom Elon has pushed to be reinstated, closer scrutiny into Edward “Big Balls” Coristine — who is at OPM and possibly HHS — has described he has ties to hackers. Brian Krebs, who was targeted by some people in that crowd, described screen shots that suggest Coristine may have been fired for leaking internal documents to a competitor.

Wired noted that Coristine only worked at Path for a few months in 2022, but the story didn’t mention why his tenure was so short. A screenshot shared on the website pathtruths.com includes a snippet of conversations in June 2022 between Path employees discussing Coristine’s firing.

According to that record, Path founder Marshal Webb dismissed Coristine for leaking internal documents to a competitor. Not long after Coristine’s termination, someone leaked an abundance of internal Path documents and conversations. Among other things, those chats revealed that one of Path’s technicians was a Canadian man named Curtis Gervais who was convicted in 2017 of perpetrating dozens of swatting attacks and fake bomb threats — including at least two attempts against our home in 2014.

And Krebs provides chatlogs showing some of Coristine’s former associates are taking notice.

The Com is the English-language cybercriminal hacking equivalent of a violent street gang. KrebsOnSecurity has published numerous stories detailing how feuds within the community periodically spill over into real-world violence.

When Coristine’s name surfaced in Wired‘s report this week, members of The Com immediately took notice. In the following segment from a February 5, 2025 chat in a Com-affiliated hosting provider, members criticized Rivage’s skills, and discussed harassing his family and notifying authorities about incriminating accusations that may or may not be true.

Bloomberg matched Krebs’ reporting on the reason for Coristine’s firing from Path.

“Edward has been terminated for leaking internal information to the competitors,” said a June 2022 message from an executive of the firm, Path Network, which was seen by Bloomberg News. “This is unacceptable and there is zero tolerance for this.”

A spokesperson for the Arizona-based hosting and data-security firm said Thursday: “I can confirm that Edward Coristine’s brief contract was terminated after the conclusion of an internal investigation into the leaking of proprietary company information that coincided with his tenure.”

Afterward, Coristine wrote that he’d retained access to the cybersecurity company’s computers, though he said he hadn’t taken advantage of it.

“I had access to every single machine,” he wrote on Discord in late 2022, weeks after he was dismissed from Path Network, according to messages seen by Bloomberg. Posting under the name “Rivage,” which six people who know him said was his alias, Coristine said he could have wiped Path’s customer-supporting servers if he’d wished. He added, “I never exploited it because it’s just not me.”

Bloomberg tied Coristine’s past even more closely to organized abuse campaigns.

JoeyCrafter was a member of Telegram groups called “Kiwi Farms Christmas Chat” and “Kiwi Farms 100% Real No Fake No Virus,” both referencing an online forum known for harassment campaigns. Typically, the site has been used to share the personal information of a target, encouraging others to harass them online, in-person, over the phone or by falsely alerting police to a violent crime or active shooter incident at their home.

This is the kind of DOGE boy Elon has thrown at government networks — and thus far, Republicans don’t seem to give a damn that Trump has given these DOGE [sic] boys access to data on virtually all Americans, employee or no.

One thing is clear, however: There’s not a shred of evidence these boys are doing what Elon claims they’re doing.

Most of these new facts — the seeming proof that OPM isn’t doing what it claimed, the insider threat warning, the ties to hackers — are not in the AGs’ suit. And by the time the suits catch up to the facts, the complaints may look quite different.

Update: Corrected that none of the OPM plaintiffs are employees of US Courts (though they did get an email).

Share this entry

Seth DuCharme’s Information Operation

Former Bill Barr aide Seth DuCharme did something funny in his two sentencing memos for former FBI counterintelligence professional Charles McGonigal.

Secret meetings

In his SDNY sentencing memo, he redacted a long paragraph which, by context, purported to describe cooperation.

SDNY was having none of that.

They explained that the redacted passage described a single meeting he had in which he shared — per a participant — “insignificant” information, not anything that merited a bonus for cooperation.

McGonigal describes an interview with other government agencies, at which he answered questions about misconduct others may have committed and his own conduct. (Br. 15- 16). The U.S. Attorney’s Office conducting this prosecution did not request that meeting, did not attend that meeting, and has little knowledge of what was said there, beyond a brief summary from one of its participants—who characterized the contents of McGonigal’s statements as, in substance, insignificant. There thus appears to be no basis for McGonigal to “presume” that his statements were “of some assistance.” (Br. 16).11 Nor can McGonigal seek sentencing credit for this meeting by citing United States v. Fernandez, 443 F.3d 19, 33 (2d Cir. 2006), abrogated by Rita v. United States, 551 U.S. 338 (2007). As McGonigal notes, that case states that a sentencing court could consider a defendant’s efforts to cooperate with the Government even if those efforts did not result in a cooperation agreement. (Br. 16). But its holding was that the district court was within its discretion to conclude “that the cooperation was fitful and that it should not be used to lighten [the defendant’s] sentence.” Fernandez, 443 F.3d at 34 (internal quotation marks omitted). This Court should reach the same conclusion with respect to McGonigal’s attempt to obtain a lenient sentence by attending a single meeting.

In a footnote, they tattled on DuCharme for trying to inflate the value of it by unilaterally redacting it.

11 The Court should not infer from McGonigal’s sealing of the corresponding paragraph in his submission that he has provided information of any value. The Government did not ask that this paragraph be sealed. Rather, McGonigal’s attorney informed the undersigned and the Washington, D.C. prosecutors that he intended to seal the paragraph, and neither objected.

DuCharme didn’t even attempt this ploy in DC. This time he left the paragraph unsealed.

When the United States presented him with a reasonable plea offer during the discovery phase of this case, Mr. McGonigal swiftly agreed to accept responsibility for his actions. In addition, he agreed to meet with representatives from seven different DOJ offices after his plea and provided truthful information to the government during a seven-hour interview session.

[snip]

Moreover, after Mr. McGonigal entered his plea, on November 17, 2023, at the request of the United States, Mr. McGonigal met with seven components28 of the Justice Department simultaneously in Manassas, Virginia, where he answered all questions presented to him on a wide variety of topics, including detailed discussions of his understanding of certain events, and his considered assessment of what the FBI can do to improve its compliance policies and practices to detect and deter improper conduct within the organization. We have been informed that the United States found the information that Mr. McGonigal provided during the full-day interview to be truthful and, we presume, of some assistance given the length and detail of the discussions.

Though by feigning coy about which parts of DOJ he met with, he again tried to fluff the import of it.

28 The specific components represented are not listed here, out of respect for sensitivities related to their specific areas of responsibility, but that information is available upon request if it is material to Court’s consideration.

DC USAO, which must have set up the meeting, didn’t mention it. Instead, they described the extensive effort FBI has made to make sure McGonigal didn’t drum up investigations into other people to help friends overseas, as he seems to have done for Albania.

Moreover, given the defendant’s senior and sensitive role in the organization, the FBI has been forced to undertake substantial reviews of numerous other investigations to insure that none were compromised during the defendant’s tenure as an FBI special agent and supervisory special agent. The defendant worked on some of the most sensitive and significant matters handled by the FBI. PSR ¶¶ 98-101. His lack of credibility, as revealed by his conduct underlying his offense of conviction, could jeopardize them all. The resulting internal review has been a large undertaking, requiring an unnecessary expenditure of substantial governmental resources.

This may be the only passage, in either DOJ sentencing memo, that discussed what a lasting harm having a top spymaster team up with foreigners seeking favors is for the FBI.

It suggests that DOJ might trust McGonigal to discuss “compliance policies,” but no longer the counterintelligence investigations in which he played a role.

Non-spy charges against the spy chief

I thought DuCharme’s ploy to provide the appearance of cooperation via evasion and redaction made an amusing introduction to something else I’ve been meaning to write, as part of my Ball of Thread series.

There was some consternation when McGonigal got sentenced in December to (just) 50 months for working for Oleg Deripaska. The complaint was, I think, that McGonigal hadn’t been labeled a spy, with some belief that would have changed the outcome.

I’d like to explain why, I suspect, DOJ did what they did.

I think they got a similar outcome as they would have had they called what he did “spying,” but deprived McGonigal — and just as importantly, DuCharme, who tried to pitch the “insignificant” information he shared as some great cooperation — from conducting an information operation to undercut the prosecution.

McGonigal was prosecuted for two schemes.

In DC, he was charged for secretly getting paid by, and traveling with, top Albanians, and ultimately predicating a FARA investigation into a Republican lobbyist with ties to a rival Albanian faction. For that, McGonigal was charged with a bunch of disclosure violations, making the secrecy the crime, not the scheming with Albania. The government is asking Judge Colleen Kollar-Kotelly to sentence him on February 16 to 30 months; they have not explicitly asked her to impose the sentence consecutively, which is the only way this sentence would extend his detention.

In NY, he was charged for secretly working with Oleg Deripaska. For that, he was charged with sanctions violations and money laundering. After he pled to conspiracy, the government had asked Judge Jennifer Rearden to sentence him to the max 60 months; she gave him the aforementioned 50 month sentence.

The government has not claimed to have proof that McGonigal shared any sensitive information with Deripaska or the Albanians, whether they have it and aren’t telling, or whether there is none. Without it, you would not expand McGonigal’s potential sentence by charging him with the crimes that might label him a spy: Foreign Agent crimes in DC, since he was working for a foreign state, or FARA in NY, since Deripaska is not quite the same thing as the Russian state. By larding on the disclosure violations in DC and asking for an obstruction enhancement, DOJ has raised total possible exposure there. And no FARA charges would carry a tougher sentence than the potential 20 year money laundering sentence that McGonigal avoided by pleading out in SDNY.

That is, DOJ charged McGonigal in such a way that the punishment would be the same, the 20 years on the money laundering charge or five-plus on disclosure violations, without giving McGonigal a cause to demand information exposing his operations at FBI.

But he did try.

Deripaska’s visit

Before I explain how, let’s situate things a bit.

According to Business Insider, a tip from the UK is one of the things that led to the investigation into McGonigal. They picked him up via the surveillance of a Russian in London they were tracking.

In 2018, Charles McGonigal, the FBI’s former New York spy chief, traveled to London where he met with a Russian contact who was under surveillance by British authorities, two US intelligence sources told Insider.

The British were alarmed enough by the meeting to alert the FBI’s legal attaché, who was stationed at the US Embassy. The FBI then used the surreptitious meeting as part of their basis to open an investigation into McGonigal, one of the two sources said.

Whether the UK picked him up in 2018 or 2019, according to the indictment his meetings with Deripaska — including in London — were in 2019.

In or about 2019, after McGONIGAL had retired from the FBI, SHESTAKOV and McGONIGAL introduced [Evgeny Fokin] to an international law firm [Kobre & Kim] with an office in Manhattan, New York (the “Law Firm”). [Fokin] sought to retain the Law Firm to work in having the OFAC Sanctions against Deripaska removed, a process often referred to as “delisting.”

During negotiations to retain the Law Firm, McGONIGAL traveled to meet Deripaska and others at Deripaska’s residence in London, and in Vienna. In electronic communications exchanged as part of these negotiations, McGONIGAL, SHESTAKOV, [Fokin] and others did not refer to Deripaska by his surname, but rather used labels such as “the individual,” “our friend from Vienna,” and “the Vienna client.”

DuCharme asserted at McGonigal’s SDNY sentencing that working with a law firm on delisting Deripaska in 2019, “would have been legal.”

After Charlie left the FBI, he met Oleg Deripaska. He met him in London in a prestigious international law firm with a lawyer. But I think the government agrees that that part would have been legal, because there is the carve-out for certain legal representations.

That didn’t go through.

It’s true that there’s a carve out for legal services that would make that, in general, legal. Probably far less so if you know that the guy you’re working with is a Russian spy.

DuCharme claims McGonigal did not, at least with regards to Fokin.

So this person, Fokin, reaches out to Charlie after that at some point. And just to be clear, as far as Mr. McGonigal knows, Fokin is not, as I guess is rumored in the media, to be a Russian intelligence officer. That’s not his understanding. But he certainly knows him to be associated with Oleg Deripaska; and he certainly knows that Deripaska is on the sanctions list.

The indictment and government sentencing memo, however, describe that McGonigal told a subordinate that Fokin was a spy.

McGonigal also told a subordinate that he wanted to recruit Fokin, who was, according to McGonigal, a Russian intelligence officer.

Let’s situate where things were in 2019. McGonigal was, without question, retired from the FBI. But at the time, DuCharme was working for Bill Barr, among other things, setting up an investigation to undermine the Russian investigation that disclosed how a close Deripaska associate, Konstantin Kilimnik, used Paul Manafort’s debt to Deripaska as leverage to learn how Trump planned to beat Hillary Clinton and also discuss carving up Ukraine to Russia’s liking. DuCharme would go on from there to set up a back channel via which Rudy Giuliani could channel dirt, including from a known Russian spy, into the Hunter Biden investigation.

A meeting with a law firm would have been legal. And also, DuCharme and his boss were working hard to blame the 2016 Russian operation on Hillary rather than Deripaska, recklessly chasing leads to those involved all over the world.

In fact, among the leads that DuCharme was chasing in 2019 as he and John Durham (he of the studied ignorance about what really happened) dreamt up ways to undermine results showing Trump welcomed help from Russia — along with the Russian-backed Ukrainians and Joseph Mifsud — involved Deripaska.

On July 3, 2019, DuCharme emailed Durham about a Fox News report that FBI had worked with Oleg Deripaska in an attempt to get Robert Levinson released and returned by Iran.

To be sure, unlike Mifsud and the Ukrainians, there’s no record DuCharme and Durham and Barr did chase the possibility that Deripaska would have damning information on Andy McCabe.

Though two months before DuCharme sent Durham a lead on Deripaska, on May 1, 2019, Bill Barr’s face melted when Ben Sasse asserted that Deripaska was a “bottom-feeding scum-sucker.”

Anyway, back to McGonigal and his charges for secretly working for Deripaska.

The investigation into McGonigal went overt in November 2021 and after that point, DuCharme described, McGonigal’s counsel, presumably DuCharme himself, remained in contact with the government.

More than a year before his arrest, on November 21, 2021, FBI agents conducted a recorded, voluntary interview of Mr. McGonigal at Newark airport when he returned home from an overseas business trip. While he was speaking to agents at the airport, another team of agents visited Mr. McGonigal’s home in lower Manhattan and met with his wife. Over the following year, Mr. McGonigal was aware of the ongoing investigation into his business dealings and remained in communication with the United States through his counsel.

So as SDNY and DC USAO were contemplating how to charge their former spymaster leading up to his January 2023 indictments, they knew that they would have to contend not just with McGonigal’s former Top Secret clearance, but also that of his attorney, the guy who in at least two cases facilitated the intake of spy dirt for partisan purposes on behalf of the former Attorney General.

Graymail

DuCharme was well aware of that.

In his DC sentencing memo, for example, he described how, by pleading guilty relatively quickly, McGonigal saved the government from engaging in the Classified Information Procedures Act process, the process by which the judge acts as an intermediary to make sure that defendants can get classified information that would be helpful to a defense without unnecessarily compromising information that would be of no help.

In contrast to Mr. Saffarinia, Mr. McGonigal quickly accepted responsibility for a single count of false statements through his guilty plea, avoiding any further expenditure of government resources, including potential Classified Information Procedures Act (“CIPA”) litigation.

It’s not true, however, that McGonigal spared SDNY of using the CIPA process. Though something very funky happened in that process in SDNY, which I believe is a big testament to the reason why they treated McGonigal’s exposure there the way they did, by charging him with crimes that would carry the same punishment without charging with a foreign agent crime. I first wrote about this funkiness here.

It seems like SDNY pre-empted a full-blown CIPA practice by having select documents, dating to well before McGonigal got into discussions with Deripaska’s people, that made clear that Deripaska was, “associated with a Russian intelligence agency” that must be GRU, which meant nothing that happened downstream of that knowledge would be all that helpful to McGonigal’s defense. That is, DuCharme may claim, evidence to the contrary, that McGonigal didn’t believe Fokin is a spy, but SDNY declassified a very small subset of documents making it clear McGonigal had to have known Deripaska was associated with GRU.

That’s part of the story that would have been told had this gone to trial: that when McGonigal secretly went to work for Deripaska, he knew of his ties to Russian intelligence.

SDNY must have planned this from the start.

It started on February 8, 2023, shortly after his indictment, when SDNY filed a CIPA letter, requesting a CIPA 2 conference.

Often, these CIPA letters review the entire CIPA process. The one Jay Bratt submitted in the Trump stolen documents case, for example, went through Section 1, Section 2, Section 3, Section 4, Section 5, Section 6 (broken down by sub-section), Section 7, Section 8, Section 9, and Section 10.

Not the SDNY one in the McGonigal case. It went through Section 2 — asking for a conference — and then stopped.

The Government expects to provide the Court with further information about whether there will be any need for CIPA practice in this case, and to answer any questions the Court may have, at the CIPA Section 2 conference.

In response, on March 1, DuCharme submitted his own CIPA letter, laying out Sections 1 through 8. Along the way, DuCharme promised that as part of CIPA 4, he would submit a memo telling Judge Jennifer Rearden what kind of information would be helpful to Charlie McGonigal’s defense, much later describing surveillance that must exist.

Under Section 4, upon a “sufficient showing” by the government, the Court may authorize the government to “delete specified items of classified information from documents to be made available to the defendant . . . , to substitute a summary of the information for such classified documents, or to substitute a statement admitting relevant facts that the classified information would tend to prove.” 18 U.S.C. § App. III § 4. The government makes a sufficient showing that such alternatives are warranted through an ex parte submission to the Court. See id; see also United States v. Muhanad Mahmoud Al-Farekh, 956 F.3d 99, 109 (2d Cir. 2020). Of critical importance to the fairness of the process, the Court may review, ex parte and in camera, the classified information at issue to determine whether and in what form the information must be disclosed to the defendant, and whether the government has truly satisfied its discovery obligations. See, e.g., United States v. Aref, No. 04 CR 402, 2006 WL 1877142, at *1 (N.D.N.Y. July 6, 2006). To assist the Court in this analysis, the defense will provide the Court with its initial view of the scope of material that will be relevant and helpful in the preparation of the defense at the upcoming conference and will supplement that information as appropriate.

[snip]

In the present case, there is far more than a trivial prospect, and in fact there is a high likelihood if not certainty, that the IC possesses information that is relevant and helpful to the preparation of the defense. The indictment charges violations of IEEPA based on an alleged agreement to provide services on behalf of Oleg Deripaska, a foreign national with allegedly close ties to a foreign government, who, it is reasonable to assume, may have been a target of surveillance by the United States during the relevant time frame. Moreover, the indictment makes specific references to previously-classified information that was in the possession of the IC, to which Mr. McGonigal had access by virtue of his position as Special Agent in Charge of the Counterintelligence Division of the New York Field Office. [my emphasis]

Seth DuCharme set out to know, among other things, what kind of surveillance FBI obtained on McGonigal, including whatever surveillance the Brits picked up when they first grew concerned about McGonigal meeting certain Russians in London.

Things never got to CIPA 4.

On March 3, Judge Rearden confirmed she would hold two separate CIPA conferences. The SDNY conference was held on March 6. On March 7, the day after SDNY’s CIPA conference and the day before McGonigal’s, SDNY responded to McGonigal’s CIPA letter. It suggested that any investigation the Intelligence Community did of McGonigal’s “corruption” by Deripaska would not be helpful to his defense. But if McGonigal wanted to make a list of things he specifically wanted, he should put that in writing.

McGonigal’s letter repeatedly asserts that the intelligence community must possess information that is helpful to his defense, without specifying what that information must be or what agencies must possess it. (See, e.g.¸ Dkt. 30 at 6 (claiming that the intelligence community writ large “may be presumed to have been involved” in the investigation of this matter); id. at 7 (asserting that “in fact there is a high likelihood if not certainty, that the IC possesses information that is relevant and helpful to the defense”)). At best, he has suggested that the general subject of this case—a recently retired FBI intelligence official being corrupted by a Russian oligarch—is of the type that might be of interest to intelligence agencies.2 Even if that claim is true, however, it is a far cry from suggesting that those agencies possess anything helpful to the defense.

[snip]

Finally, McGonigal suggests that he will “identify categories of classified information that will be material to his defense at the defendant’s ex parte Section 2 conference.” (Dkt. 30 at 7). But it is unclear why he needs to do this in an ex parte conference. As he elsewhere acknowledges, CIPA establishes procedures for the defense to identify classified information it wishes to offer, and those procedures are not ex parte.

[snip]

The Government thus trusts that McGonigal will identify any classified information he claims is relevant to the Government, as CIPA elsewhere expressly provides. See id. § 5 (“If a defendant reasonably expects to disclose or to cause the disclosure of classified information in any manner in connection with any trial or pretrial proceeding involving the criminal prosecution of such defendant, the defendant shall, within the time specified by the court or, where no time is specified, within thirty days prior to trial, notify the attorney for the United States and the court in writing.” (emphasis added)).3

On May 8, SDNY filed a short letter informing Judge Rearden that they had declassified the material they had told her they would in their own CIPA 2 hearing and provided it to the defense.

At the March 6, 2023 ex parte conference held pursuant to Section 2 of the Classified Information Procedures Act (“CIPA”) in the above-referenced case, the Government described to the Court certain materials that the Government was seeking to declassify. The Government writes to confirm that those materials have been declassified and produced to the defendants. At this time, the Government does not anticipate making a filing pursuant to Section 4 of CIPA and believes it has met its discovery obligations with respect to classified information.

It seems likely that this declassified material includes the document, which McGonigal received in May 2017, identifying Deripaska’s ties to (what must be) GRU disclosed in the government’s sentencing memorandum. Effectively, SDNY was saying that, once you understand Deripaska was GRU (and whatever else also got declassified), anything that came after that would not be helpful to your defense.

DuCharme was not yet done. On June 23, he submitted another letter describing that it was perplexing and puzzling and concerning and hard to imagine that there wasn’t more.

With respect to the way forward as it pertains to classified discovery, as we noted at our last court appearance, the government has indicated that it “does not anticipate making a filing pursuant to Section 4 of CIPA and believes it has met its discovery obligations with respect to classified information.” See ECF No. 44 at 1. In a subsequent series of conversations, the government informed us, in a general way, that it has satisfied its discovery obligations relating to classified information. The government’s position is perplexing. While it is not surprising that the government does not wish to account for its each and every step in satisfying its constitutional obligations, it is puzzling and concerning that the government would, at this stage, determine that no CIPA Section 4 presentation to the Court is appropriate, when we are a year away from trial and the government’s discovery obligations with respect to Rule 16, the Jencks Act, Brady and Giglio are ongoing. The indictment and the U.S. Attorney’s press release include accusations that foreseeably implicate classified information within each of the four categories of discoverable information. With respect to the category of impeachment material alone, it is hard to imagine a world in which there are no classified materials that touch on the credibility of the government’s trial witnesses (or alleged unindicted coconspirator hearsay declarants), and which would require treatment under Section 4 of CIPA.

DuCharme suggested that maybe the problem was that the information helpful to McGonigal’s defense was simply super duper classified, but that it still had to be turned over.

As an initial matter, the classification level of information in the possession of the United States is wholly irrelevant as to whether or not it is discoverable. Classification rules appropriately exist to safeguard the national defense of the United States by limiting the dissemination of such information in the normal course. See Exec. Order No. 13526, 75 Fed. Reg. 707, (2009) (prescribing a uniformed system for classifying national security information). But once a defendant is indicted, the government is obligated to consider whether information within its holdings is discoverable under the applicable rules, statutes and constitutional caselaw

The letter explained that both McGonigal and Seth DuCharme could be trusted with the government’s classified information — after all, McGonigal was only indicted for cozying up to the Russian oligarch he had hunted for years, not mishandling classified information. And Seth DuCharme was, until recently, trusted with Bill Barr’s most sensitive secrets, including about the side channels ingesting dirt from known Russian agents.

Further, it is hard to understand why the government is so reluctant to be more transparent in explaining its discovery practices to the defense in this case. While many national security cases involve defendants with no prior clearances or experience with the U.S. Intelligence Community, and may involve only recently-cleared defense counsel who may be new to navigating the burdens and responsibilities of handling classified information, here, those concerns do not apply. Mr. McGonigal was one of the most senior and experienced national security investigators in the FBI with significant direct professional experience in the areas germane to his requests for assurances about the thoroughness of the government’s discovery analysis. In addition, before moving to private practice, the undersigned counsel served as the Chief of the National Security Section, the Chief of the Criminal Division and the Acting United States Attorney in the U.S. Attorney’s Office in the Eastern District of New York as well as the Senior Counselor to the Attorney General of the United States for National Security and Criminal matters, and has responsibly held TS/SCI clearances with respect to some of the United States government’s most sensitive programs. As the Department of Justice has concluded in re-instating defense counsel’s clearances for the purpose of this case, we are trustworthy. So, here, we have a defendant and defense counsel who are highly respectful and experienced with regard to the protocols for handling and compartmentalizing sensitive classified information, and simply request comfort that the government has indeed done everything it would normally do in a case such as this, with sufficient detail to assess the credibility of the government’s position.

Notably, Mr. McGonigal has not been accused of mishandling classified information in the cases brought against him, and he maintains respect for the national security interests of the United States, as of course do we. In addition, we are not asking the government to disclose to the defense any sensitive sources and methods by which discoverable information was collected—only to provide greater transparency to us, and to the Court, as to how it views its procedural obligations, so that we may consider the fairness and reasonableness of the government’s approach. Mr. McGonigal is personally familiar with this process from his time at the FBI, and it is reasonable for him to expect to be treated no worse than the other defendants who have come before him. To adequately represent Mr. McGonigal, it seems only fair that we be allowed to hold the United States government to the same standards that the defendant upheld as a national security and law enforcement professional, and to make a record of the government’s position.

Then DuCharme made a helpful offer to meet in a secure hearing or to submit a more highly classified brief — perhaps taking SDNY up on their instruction to put it in writing — again suggesting he had something specific in mind.

In sum, if the government could explain, in an appropriate setting, how it determined that it had obviated the need for a CIPA Section 4 proceeding, we likely can avoid speculative motion practice, and the parties and this Court may be assured that we can continue to litigate this case fairly and with the level of confidence to which we are entitled.

[snip]

To the extent the Court would like more detailed briefing on these issues prior to the conference, the CISO has provided to cleared defense counsel access to facilities that would allow us to draft a supplemental submission at a higher classification level.

I don’t want to minimize the problem CIPA presents for defendants, nor the kind of prosecutorial dickishness that can roil discovery discussions. But this entire exchange was, in my experience, pretty remarkable. The arguments, for example, are little different from ones Trump is making in the stolen documents case, but McGonigal’s arguments always seemed more targeted than Trump’s, which are a mad splay attempting to review the entire Intelligence Community.

Then it was over.

On June 23, DuCharme doubled down on his certainty there were secrets that would help McGonigal. On July 10, Judge Rearden scheduled a hearing for updates on classified discovery. That same day, the government described making a discovery production four days after DuCharme’s letter, then said it planned to file a response to the letter before the hearing, which it said was scheduled for July 18. Judge Rearden gave them four days to file the response, until July 14. That day, July 14, the day SDNY would otherwise have filed another public letter about classified discovery, McGonigal withdrew his request for a status hearing. A month later McGonigal pled guilty to the one count of conspiracy.

To be sure, the deal was pretty sweet, given that it took the onerous money laundering exposure off the table. But the 50 months is the kind of sentence he might have faced for Foreign Agent charges — anything that stopped short of alleging that McGonigal had shared FBI secrets with Oleg Deripaska, of which, again, there is no hint in any of the charging documents.

Yet SDNY successfully prosecuted the former FBI spymaster for working for Oleg Deripaska without (apparently) sharing anything more than the first notices McGonigal got of the spook ties the Intelligence Community found Oleg Deripaska to have.

 

 

 

Share this entry

In Peter Navarro Sentencing, No Mention of Competing Claims about Official Acts

As you’ve no doubt heard Judge Amit Mehta sentenced Peter Navarro to four months in prison plus a $9,500 fine. Here’s Kyle Cheney’s account.

The punishment matched the sentence imposed — but stayed pending appeal — by Trump appointee Carl Nichols, but with a bigger fine.

At first, Navarro attorney Stan Woodward told Judge Mehta that Navarro would say nothing.

But then he did. He claimed, as a Harvard-educated gentleman, he was helpless to figure out what to do in response to a subpoena.

Navarro made a last-ditch appeal for leniency to Mehta, addressing the court even after his lawyers had initially said he wouldn’t. He said he grew confused about the thicket of precedents and rules around executive privilege and believed he didn’t have to comply with Congress’ subpoena.

“I’m a Harvard-educated gentleman, but the learning curve when they come at you with the biggest law firm in the world is very, very steep,” Navarro said.

Judge Mehta, a mere Georgetown/UVA grad, was having none of it. He noted that by the time Navarro defied the January 6 Committee, Steve Bannon had already been charged.

I’m just as interested in what wasn’t said at the sentencing. In spite of unsealing part of the communications pertaining to the Presidential Records Act lawsuit still pending against Navarro, which I wrote about here, I saw no mention of it in today’s hearing.

If I’m right that Navarro continues to withhold communications about the coup based on a claim they’re not protected by the Presidential Records Act, nothing would prevent Jack Smith from handing Navarro a subpoena. Indeed, Navarro’s testimony today would validate that Navarro now knows exactly how to respond to a subpoena — and that he doesn’t believe these are official records.

The big drama going forward is whether Judge Mehta lets Navarro stay out of jail pending appeal, as Judge Nichols did with Bannon.

But if Navarro were to defy another subpoena, it might be a way to get him jailed more quickly.

Share this entry

Peter Navarro and the Office-Seeker Using ProtonMail Challenge

The two Peter Navarro litigations are drawing to a head in a way that reveal just how difficult it is to prosecute a President who attempts a coup.

First, Navarro is set to be sentenced for his contempt of Congress on Thursday. Navarro has asked for no more than a year’s probation with a request any detention be stayed while he appeals based on his claim that Trump invoked Executive Privilege without saying or doing anything specific with regards to Navarro to assert that. DOJ asked for six months on each count while (deeper in the sentencing memo) noting that each count requires a one month sentence and they can be imposed concurrently. Judge Amit Mehta, who is presiding over this case, is a namby pamby former public defender Democratic appointee, and it’s unlikely he’ll sentence Navarro for longer than Carl Nichols did Steve Bannon.

In his sentencing memo, Navarro’s attorneys, including Stan Woodward (who is party to Trump’s baseless arguments about the Presidential Records Act in the stolen documents case), included Joe Biden’s waiver of Executive Privilege over documents at NARA among his list of firsts tied to this prosecution.

Dr. Navarro’s trial and conviction involves a series of firsts: the first time an incumbent President waived the executive privilege of a former President; the first time a senior presidential advisor was charged with contempt of congress by the Justice Department, let alone the Justice Department of a political rival; the first time a District Court held an evidentiary hearing on whether a former President had properly invoked executive privilege; and the first time a senior presidential advisor was convicted, and now is to be sentenced, for following what that advisor reasonably believed was an instruction by the former President not to comply with the Select Committee’s subpoenas.

I believe I remain the only person who noted how craftily Merrick Garland obtained that waiver, doing so in such a way that adhered to DOJ contact policies and kept Biden shielded from any information about the criminal investigation into his predecessor. The TV lawyers were and remain too busy claiming that Garland dawdled to notice the steps Garland took in July 2021 to negotiate this difficult problem.

Subsequent to those initial filings, DOJ asked to file an extra-long reply. It addresses some of Navarro’s novel theories, but also includes a long passage rebutting Navarro’s bid to stay out of jail pending his appeal that argues that Navarro’s claim that Executive Privilege entitled him to entirely blow off a subpoena could not be sound.

With respect to Court Two, the Department of Justice has made clear that testimonial immunity should apply only with respect to questions seeking information from a close presidential adviser concerning “matters that occur[red] during the course of discharging [the adviser’s] official duties.” See Immunity of the Assistant to the President and Director of the Office of Political Strategy and Outreach from Congressional Subpoena, 38 Op. O.L.C. 5 at 7 (July 15, 2014) (“Simas Opinion”); Testimony Before Congress of the Former Counselor to the President, 43 Op. O.L.C. _ (2019) (“McGahn Opinion”) at 19; Conway Opinion at 1. Arguably, no president, current or former, would have the authority to make a categorical invocation of testimonial immunity over all the information sought by the Committee from the Defendant because most of the information the Committee sought did not concern matters that occurred in the course of the Defendant’s discharge of his governmental duties.

For example, the subpoena sought, among other things, “all documents and communications relating in any way to protests, marches, public assemblies, rallies, or speeches in Washington, D.C. on November 14, 2020,” and “all communications, documents and information that are evidence of the claims of purported fraud in the three-volume report you wrote, The Navarro Report.” See Ex 1 at 19-20.

Defendant was a trade adviser, and responsible in part for the Trump administration’s response to the Coronavirus crisis. In contrast, the Select Committee subpoena sought information wholly related to the attack on the Capitol on January 6, 2021, and the threat to the peaceful transition of power between administrations. 7 As with the alleged assertion of executive privilege, any such assertion of testimonial immunity therefore would have been germane only (at most) to the Defendant’s testimony about a fraction of the subjects about which the Committee informed him it wished to inquire at the deposition.

Accordingly, a reasonable assertion of executive privilege or testimonial immunity, had one actually occurred, could not have been grounds for the Defendant to refuse to testify altogether; instead, the most it would have justified would have been an assertion of privilege at the former President’s request regarding particular documents or testimony seeking information about communications between the Defendant and the former President himself (or, in the case of a proper immunity assertion, about testimony concerning matters related to the Defendant’s official duties). Therefore, even if the Defendant could establish that former President Trump instructed him to assert privilege as to all questions that might be asked of him at the deposition, such an assertion would not have been proper. It follows that such an assertion could not preclude the Defendant’s conviction on Count Two of the Indictment.8 But of course, the record is devoid of any assertion at all. As the Defendant’s own testimony at a pretrial hearing made clear, even the Defendant’s conversation with the former President included nothing – not even a wisp – that could constitute an actual invocation of executive privilege.

7 Given his own assertions to the contrary, mostly notably in the press releases accompanying the release of his “reports,” it is not credible to believe that the Defendant thought the subpoena related exclusively to his official responsibilities. See, e.g., ECF No. 79-4 (Press Release).

8 Moreover, as previously briefed, because the Defendant failed to raise an immunity claim with the Committee, he is not allowed to invoke testimonial immunity before this Court or the Court of Appeals after the fact to foreclose prosecution for a violation of Section 192. Such argument has been waived. See United States v. Bryan, 339 U.S. 323, 330-34 (1950) (“[I]f respondent had legitimate reasons for failing to produce the records of the association, a decent respect for the House of Representatives, by whose authority the subpoenas issued, would have required that she state her reasons for noncompliance upon the return of the writ. . . . To deny the Committee the opportunity to consider the objection or remedy it is in itself a contempt of authority and an obstruction of its processes.” (citation omitted)); Hutcheson v. United States, 369 U.S. 599, 608- 611 (1962) (stating that a constitutional objection “must be adequately raised before the inquiring committee if [it] is to be fully preserved for review in this Court. To hold otherwise would enable a witness to toy with a congressional committee in a manner obnoxious to the rule that such committees are entitled to be clearly apprised of the grounds on which a witness asserts a right of any assertion at all. As the Defendant’s own testimony at a pretrial hearing made clear, even the Defendant’s conversation with the former President included nothing – not even a wisp – that could constitute an actual invocation of executive privilege.

Meanwhile, DOJ’s civil suit against Navarro to force him to hand over communications covered under the Presidential Records Act that he conducted using ProtonMail may be drawing to a close. Things hit an impasse last summer when, after a previous attorney had told the government that Navarro had 800 PRA-covered communications on his ProtonMail, while represented by Stanley Woodward, he only turned over 211.

Last August, Judge Colleen Kollar-Kotelly ordered Navarro to provide her records of his search by October.

Partially out of deference to defense counsel’s burgeoning trial calendar, the Court deferred ruling until after it had further opportunity to review the record. After further consideration, and in an effort to finally bring this litigation to a close, the Court will opt for both courses of action. On or before October 15, 2023, Defendant shall file under seal a notice listing all search terms used, the metadata fields searched, and the email accounts searched. Also on or before October 15, 2023, Defendant shall deliver to Chambers a random sample of fifty emails across each account searched that were not identified as responsive in his last review. The Court will maintain these records under seal.

Navarro complied in October.

Then Judge Kollar-Kotelly issued what appears to be an order to the government to weigh in on whether his search was adequate.

Then, last week, Woodward asked to unseal those exchanges so he could submit the government one to Judge Mehta in support of sentencing (I think he only asked to unseal the documents to share with Mehta; thus far, at least, we don’t get to see them).

In Navarro’s own sentencing reply, he described what he was after: the government’s argument, in December (and so after Blassingame — a decision upholding Amit Mehta’s ruling that actions Trump took as a candidate are not immune from civil suit — distinguished between presidential actions taken as a candidate for office and holder of that office), that some of Navarro’s communications pertaining to the attempted coup might include official records.

The government’s betrayal is manifest of its true motive – the prosecution of a senior presidential advisor of a chief political opponent. By way of a second example, consider the position taken by the Department – representing one United States – in its litigation against Dr. Navarro for allegedly refusing to return purportedly presidential records to the National Archives and Records Administration under the Presidential Records Act. 44 U.S.C. §§ 2201- 2209. Here, the government claims that Dr. Navarro’s work related to the 2020 Presidential Election could only have been conducted in his personal capacity.4 Yet there, because it suits their interests, the government recently asserted – originally under seal – that Dr. Navarro, and the Administration of President Trump, could very well have worked to ensure election integrity as part of his official duties. See Notice, at 4 (Dec. 29, 2023) (ECF No. 35) (“However, the United States has not taken the position that every action that Defendant took in connection with the 2020 Presidential Election was done in his personal, and not official, capacity; nor has the United States taken the position that any communications related to the 2020 Presidential Election are not Presidential records.”).

So in the civil suit, Navarro appears to have decided that almost 600 communications sent on ProtonMail — those pertaining to his role in a coup attempt — were not sent in the conduct of his official duties and therefore don’t need to be turned over under the PRA to NARA (whence Jack Smith could subpoena them).

But in the criminal case, Navarro claims to have believed and still believe that everything Congress subpoenaed from Navarro, which would have covered every communication pertaining to his role in a coup attempt, was covered by Executive Privilege.

ProtonMail, because it is less often used on phones and because it is hosted in Switzerland, happens to be among the most difficult platforms from which to obtain communications in a criminal investigation — harder even than the Signal and Telegram apps on which much of this coup was plotted. At least based on what DOJ showed in the Josh Schulte case,  as recently as 2018, FBI didn’t have a means to access Proton content without a password under criminal process. So for a contemnor like Navarro who blows off subpoenas, you’re not going to get his ProtonMail content without his involvement in some way. It seems likely that Navarro has effectively conceded there are almost 600 records about the coup that DOJ still wants, records he refused to give January 6 Committee based on a frivolous claim of Executive Privilege, records that he now refuses to give NARA under a claim they’re not Presidential Records at all.

The facts at this point are fairly clear: along with two aides, Navarro spent much of his last month in office focused not on his trade duties or even his COVID response, but instead on ginning up false claims that the election was stolen. That is, in his apparent claim that his coup communications were not official duties, Navarro seems to confess he spent the last month in office defying the Hatch Act. And the false claims he ginned up played a key role in the coup (and one of those aides, Garrett Ziegler, was one of Ali Alexander’s direct ties to the White House).

The government has been attempting to retrieve the communications Navarro conducted on ProtonMail since December 2021, shortly after a COVID-related investigation surfaced their existence. And over two years later, Navarro apparently continues to withhold almost 600 records relating to the coup.

I assume there are still steps DOJ can take once these two legal cases are resolved — such as subpoenaing Navarro directly for the communications he now claims were not official records (he invoked the Fifth Amendment and demanded immunity from prosecution in refusing to turn them over before). That is, Navarro could end up facing a second criminal contempt charge, which is one reason Stan Woodward keeps making bullshit claims about politicization.

Nevertheless, through a combination of frivolous claims of privilege and reliance on technology that thwarts the FBI, it appears that a significant chunk of coup communications remain outstanding.

Share this entry

The Seth DuCharme Confession in the Charles McGonigal Sentencing Memo

In his sentencing memo for Charles McGonigal’s DC case, former Bill Barr flunky Seth DuCharme twice misstated the nature of the false statement for which Kevin Clinesmith was sentenced.

In a passage comparing other government officials who had omitted information from government filings, as McGonigal pled he had, DuCharme asserted that Clinesmith was prosecuted for making “false statements,” plural, “in application for” FISA warrant.

United States v. Clinesmith, No. 1:20-cr-165 (D.D.C. 2020) (imposing probation against FBI attorney for false statements in application for a Foreign Intelligence Surveillance Act (“FISA”) warrant); [my emphasis]

Even before that, in arguing that Judge Colleen Kollar-Kotelly should not apply a sentencing enhancement, he turned to Clinesmith. This time, he accused Clinesmith of causing false information to be submitted to FISC.

Mr. McGonigal disagrees with the application of the cross reference in Section 2B1.1(c)(3), which would increase his base offense level to 14, as inconsistent with case precedent. In United States v. Clinesmith, No. 1:20-cr-165 (D.D.C. 2020), the government did not seek and the sentencing court did not independently apply the cross reference to the obstruction Guideline at the sentencing of an FBI attorney who caused false information to be submitted to the U.S. Foreign Intelligence Surveillance Court (“FISC”) in an application for a Foreign Intelligence Surveillance Act (“FISA”) warrant sought in connection with an active FBI investigation. The government’s position that false statements to the FISC during an active investigation does not warrant application of the cross reference while Mr. McGonigal’s conduct does is perplexing. While Mr. McGonigal concedes that this Court in United States v. Hawkins, 185 F. Supp. 3d 114 (D.D.C. 2016) held that it may consider conduct in the statement of the offense, and the court in United States v. Saffarinia, 424 F. Supp. 3d 46 (D.D.C. 2020) held that at the motion to dismiss phase Section 1519 is broad enough to cover false statements on OGE-278 forms, it is difficult to reconcile these cases with the Clinesmith court’s more recent analysis. In Clinesmith, the District Court declined to apply the obstruction cross reference in determining the applicable Guidelines range, and we respectfully request that this Court similarly decline to apply the cross reference to the facts at issue here. [my emphasis]

Kevin Clinesmith altered an email and with it, misled a colleague, thereby preventing the FBI from fully informing the FISA Court on something material to the application. In that, he “caused” information not to be shared with the FISC. He did not make false statements in the application (and in any case, the original decision not to notify the court that Page had years earlier shared information with the CIA about Russian spies, which Clinesmith had no part of, had in significant part to do the the fact that Page had not been an approved contact of the CIA for several years before 2016, when he went out of his way to contact the Russians about his role in a counterintelligence investigation). Nor did Clinesmith cause affirmative false statements to be made.

His was a crime of omission, not commission, as DuCharme claimed. I emailed DuCharme about the basis for these claims but got no response.

More importantly, whether you agree with him or not, Judge James Boasberg explained why he sentenced Clinesmith to probation: because he didn’t think Clinesmith believed he was lying and the former FBI lawyer got no benefit from his false claim.

First, he obtained no real personal benefit from his actions and he had no active intent to harm.

Although the government has contested this, my view of the evidence is that Mr. Clinesmith likely believed that what he said about Dr. Page was true, namely that he was a subsource but not a source of the Other Government Agency. By altering the e-mail, he was saving himself some work and taking an inappropriate shortcut. But I do not believe that he was attempting to achieve an end he knew was wrong.

I’m on the record saying Clinesmith should have gotten some jail time, even in spite of the wildly unsubstantiated claims Durham’s team made about politicization. I think DuCharme is totally right to compare how lenient courts have been with government officials who fail to disclose things, including by invoking the Clinesmith sentence. That’s all sound lawyering.

But his sloppy treatment of Clinesmith — the appointment of John Durham to prosecute for which DuCharme played a central role — comes off as petulant and partisan. Indeed, Barr’s office took personal interest in this prosecution all the way through the time DuCharme swapped back to EDNY, as revealed by a text exchange Barr had with his Chief of Staff, probably complaining that Boasberg remained on this case, after the plea deal.

There are few factual similarities to the two cases, and by focusing so much on him, DuCharme seems to be saying, “if Kevin Clinesmith didn’t have to go to jail based on our conspiracy theories about him, my guy shouldn’t have to either.”

All the more so given another enhancement argument DuCharme made. He argues that a 3-level enhancement should not be applied because McGonigal trumped up a FARA investigation into the rival of the Albanian paying him to travel around Europe, the thing he failed to disclose.

Mr. McGonigal further disagrees with the application of Section 2J1.2(b)(2) resulting in a three-level enhancement for “substantial interference” with the administration of justice. According to the PSR, the enhancement is applied to Mr. McGonigal because he admitted to “speaking with a foreign official about a matter in which Person A had a financial interest, and opening a criminal investigation based on information provided to him by Person A.” PSR ¶ 57. While the enhancement is appropriately applied to the “premature or improper termination of a felony investigation,” we are aware of no authority supporting its application to the opening of a felony investigation, as is the case here. 7 As Special Agent in Charge (“SAC”) of Counterintelligence for the New York Field Office, it was Mr. McGonigal’s job to pass along information he received that could be indicative of criminal activity. Had Mr. McGonigal taken the alternative route and concealed or withheld the information he received from Person A concerning potential criminal activity in the United States, that would be troubling. Instead, he passed the tip and lead to the FBI, to be appropriately vetted by the Bureau and the U.S. Attorney’s Office. Accordingly, the application of Section 2J1.2(b)(2) is unwarranted.

7 U.S.S.G. § 2J1.2 (“Substantial interference with the administration of justice” means “a premature or improper termination of a felony investigation; an indictment, verdict, or any judicial determination based upon perjury, false testimony, or other false evidence; or the unnecessary expenditure of substantial governmental or court resources.”); see e.g., United States v. Baker, 82 F.3d 273 (8th Cir 1996) (applying enhancement to police officer who improperly terminated a felony investigation). [my bold, italics original]

The technical issue — whether this enhancement can be used because someone initiated an improper investigation rather than improperly ending one — will make an interesting appeal if Kollar-Kotelly applies the enhancement and and sentences McGonigal to serve his sentence concurrent to the 50-month sentence Judge Jennifer Rearden gave McGonigal for trying to trump up sanctions against an Oleg Deripaska rival in SDNY, something DOJ is not requesting. But it’s likely that would be unsuccessful: As the government notes in its sentencing memo and even the footnote here makes clear, after the termination language DuCharme focuses on, the guideline continues, “or the unnecessary expenditure of substantial governmental or court resources.” And McGonigal’s opening an investigation against his business partner’s rival used counterintelligence resources that should have been spent on more serious threats.

FBI officials even questioned the propriety of opening up the criminal investigation at the time it was initiated, but cited the defendant’s directive. See Ex. 1 at 1.

[snip]

Here, initiating the investigation based on Person A’s information was particularly egregious given its lack of substantiation, which is why it was promptly closed following the defendant’s retirement.

DOJ provided records showing that one of McGonigal’s colleagues was genuinely troubled about the propriety of opening a FARA case against someone who had already registered under FARA regarding a country, Albania, that isn’t among the countries of priority for such things. By opening an investigation into a lobbyist for an Albanian political party (reportedly former Ted Cruz Chief of Staff Nicholas Muzin), McGonigal was drawing resources away from more pressing threats.

So my question is with all the talk of shortage of resources and most field offices having difficulty covering Band 3 and 4 threats, and FARA cases from banded threat countries rarely prosecuted by DOJ, why is NY requesting a SIM FAR investigation be opened on Albania for an improper FARA registration as a threat to national security?

I of course will fully support anything NY wants to do in their AOR, but once the paperwork to restrict the case gets reported up my chain of command, I would like to be able to explain to them why we are working an Albanian SIM/FARA case when every day I am in there fighting for resources on some national security matters pertaining to banded countries such as [redacted]. I am assuming since this directive is coming from SAC McGonigal there is more to this story?

Per those records, McGonigal appears to have caused a politically connected Republican to have nine of his bank accounts scrutinized before the investigation got closed. The Albanian section of Oversight Democrats’ report on Trump’s acceptance of emoluments provides more background on the political wranglings involved; Albanian Prime Minister Edi Rama and two aides spent almost $3,500 at Trump’s hotel on a trip when they met with McGonigal.

Notably, the investigation against this lobbyist, like Crossfire Hurricane, was opened as a Full investigation from the start.

And after the FBI discovered that McGonigal had opened up an investigation to help his business partner, the FBI has had to review all the other cases he was working on to make sure he hadn’t similarly used criminal investigations for self-interested purposes.

Moreover, given the defendant’s senior and sensitive role in the organization, the FBI has been forced to undertake substantial reviews of numerous other investigations to insure that none were compromised during the defendant’s tenure as an FBI special agent and supervisory special agent. The defendant worked on some of the most sensitive and significant matters handled by the FBI. PSR ¶¶ 98-101. His lack of credibility, as revealed by his conduct underlying his offense of conviction, could jeopardize them all. The resulting internal review has been a large undertaking, requiring an unnecessary expenditure of substantial governmental resources.

The misrepresentation of the Clinesmith plea might be reasonable coming from someone else. Like all criminal defendants, McGonigal deserves zealous advocacy.

But this argument came from Seth DuCharme.

It came from someone who opened a four year follow-on investigation in which the only crime ever identified was that Clinesmith alteration — and that crime was discovered by someone else, and could easily have been, and should have been, prosecuted by the very same prosecutors who did prosecute it, only instead reporting to the Trump appointed US Attorney in DC rather than Durham. And among the prosecutions pursued as part of that four year investigation that Seth DuCharme opened was a false statements case against Michael Sussmann based off logic directly contrary to what DuCharme argues here, that McGonigal would have failed to do his duty if he hadn’t opened the investigation into his business partner’s rival. That logic, applied to the Durham investigation, says it would have been remiss not to investigate the Alfa Bank allegations that Sussmann shared with Jim Baker — which is exactly what Sussmann said from the start.

Worse still, that argument DuCharme makes, that, “it was Mr. McGonigal’s job to pass along information he received that could be indicative of criminal activity,” is precisely the argument that Bill Barr made to explain a similar laundering of self-interested information that Seth DuCharme effected: the channeling of information from Rudy Giuliani to the Hunter Biden investigation.

The DOJ has the obligation to have an open door to anybody who wishes to provide us information that they think is relevant.

That is, the dishonest argument that Seth DuCharme is making, trying to dismiss the seriousness of Charles McGonigal’s use of FBI resources to conduct an investigation in which he had an undisclosed personal interest? It’s an argument that might also exonerate his own twin efforts to launch massive investigations into Donald Trump’s political rivals.

In fact, in McGonigal’s Deripaska-related sentencing hearing, DuCharme said something shocking. In that case, he said that McGonigal’s enthusiasm for working with someone whom the former FBI agent himself had identified as a Russian spy was only a problem because he was no longer covered by public authority defense. “[O]ne of the critical mistakes he makes in embracing this is that he no longer has the public authority that he had as an FBI agent.” That is, Seth DuCharme, who did set up a way to use dirt from a known Russian spy for a politicized investigation, argued that’s all cool if you’ve got the legal cover of official employ.

By all means, lawyers for Charles McGonigal should point out that DC judges rarely punish government officials who lie by omission that harshly. But in attempting to do that, Seth DuCharme said as much about his own ethics and actions than he did about his client’s crimes.


 

 

Share this entry

“Forthwithier:” Peter Navarro Attempts to Pull a Fast One on His Incriminating Use of ProtonMail

Peter Navarro appears to be attempting to stall out a month-long order to avoid turning over ProtonMail content he has been trying to withhold from DOJ since last July.

In the guise of doing a more thorough search for materials he should have turned over under the Presidential Records Act, he has not turned over 200 to 250 already identified ProtonMail records that, last year, his attorney said would incriminate him if he turned them over.

I wrote about the lawsuit DOJ filed to force Navarro to turn over the records last August. In effect, after Navarro lawyered up last year and DOJ told them they were going to sue, Navarro’s lawyer went through his emails, identified 200 to 250 ProtonMail records that should have been turned over, but said he would not on the grounds that it would amount to self-incrimination. So DOJ sued to get them.

In March, Judge Colleen Kollar-Kotelly ruled for the government and ordered Navarro to turn over the documents he had already identified to be covered by the Presidential Record Act, “forthwith.”

ORDERED, that Defendant shall produce to Plaintiff the 200 to 250 documents that his counsel has identified as Presidential records forthwith.

In a status report submitted yesterday describing all the new files Navarro is looking for, DOJ included a footnote making it clear Navarro still has not complied with the March 9 order.

1 As of the filing of this status report, Plaintiff advises that it has not received any of the 200 to 250 documents that Defendant’s counsel has identified as Presidential records, nor has Defendant obtained a stay of this Court’s order from the D.C. Circuit.

Navarro has appealed and is asking for a stay of Judge KK’s order; his reply brief for that stay is due Monday. He has clearly ignored a pending order for over a month in hopes that the DC Circuit — a panel consisting of Patricia Millett, Robert Wilkins, and Neomi Rao — will give allow him to delay turning over the 200 to 250 documents his lawyer has said include evidence of a crime.

Share this entry

The Error that Betrays Insufficient Attention to the Obstruction Standard in the January 6 Eastman Filing

There’s a telling error in the January 6 Committee’s filing aiming to overcome John Eastman’s claims his emails are covered by Attorney-Client privilege. In the section asserting that Trump had probably violated 118 USC 1512(c)(2) — the same obstruction statute used to charge over 200 of the other January 6 defendants — the filing asserts that six judges “to date” have “refused to dismiss charges against defendants under the section.”

That number is incorrect. As of March 2, at least ten judges had upheld DOJ’s application of 18 USC 1512(c)(2), and a few more have as much as said they would.

  1. Dabney Friedrich, December 10, 2021, Sandlin*
  2. Amit Mehta, December 20, 2021, Caldwell*
  3. James Boasberg, December 21, 2021, Mostofsky
  4. Tim Kelly, December 28, 2021, Nordean*
  5. Randolph Moss, December 28, 2021, Montgomery
  6. Beryl Howell, January 21, 2022, DeCarlo
  7. John Bates, February 1, 2022, McHugh
  8. Colleen Kollar-Kotelly, February 9, 2022, Grider
  9. Richard Leon (by minute order), February 24, 2022, Costianes
  10. Christopher Cooper, February 25, 2022, Robertson

When I first made this observation, I thought I was being a bit churlish in making it. But on reflection (and after reading the quotes from lawyers in this Charlie Savage article), I think it’s an important point. All the more so given how TV lawyers have claimed that, because the January 6 Committee has claimed Trump could be charged with obstruction, then damnit DOJ should already have done so.

The fact that the Jan 6 Committee isn’t even aware of all the obstruction rulings suggests they’ve been insufficiently attentive to what the rulings actually say, aside from the baseline holding of all of them that the vote certification was an official proceeding.

While ten judges have upheld the application, there are some differences between these opinions, particularly with regards to their formulation of the corrupt mens rea required by the statute. The most important differences from my review (but I’m not a constitutional lawyer and so I should not be the one doing this analysis!!!!!), are:

  • Whether “corrupt” intent requires otherwise illegal action
  • Whether such corruption would be transitive (an attempt to get someone else to act improperly) or intransitive (whether it would require only corruption of oneself)

Dabney Friedrich argued (and I laid out briefly here) — and has repeatedly warned in pretrial hearings for Guy Reffitt — that as she understand this application it must involve otherwise illegal actions. Amit Mehta ruled (as I wrote up here) that, at least for the Oath Keepers, this corruption may be just intransitive.

On both these issues, the Jan 6 Committee’s argument is a bit muddled. Here’s how they argue that Trump’s actions (and, less aggressively, Eastman’s) demonstrate that corrupt intent.

The Electoral Count Act of 1887 provides for objections by House and Senate members, and a process to resolve such objections through votes in each separate chamber. 3 U.S.C. §§ 5, 6, 15. Nothing in the Twelfth Amendment or the Electoral Count Act provides a basis for the presiding officer of the Senate to unilaterally refuse to count electoral votes — for any reason. Any such effort by the presiding officer would violate hte law. This is exactly what the Vice President’s counsel explained at length to Plaintiff and President Trump before January 6. Plaintiff acknowledge that the Supreme Court would reject such an effort 9-0. And the Vice President made this crystal clear in writing on January 6: [1] any attempt by the Vice President to take the course of action the President insisted he take would have been illegal

Nevertheless, pursuant to the Plaintiff’s plan, the President repeatedly asked the Vice President to exercise unilateral authority illegally, as presiding officer of the Joint Session of Congress, to refuse to count electoral votes. See supra at 11-13. In service of this effort, he and Plaintiff met with the Vice President and his staff several times to advocate that he universally reject and refuse to count or prevent the counting of certified electoral votes, and both also engaged in a public campaign to pressure the Vice President. See supra at 3-17.

The President and Plaintiff also took steps to alter the certification of electors from various states.

[snip]

The evidence supports an inference that President Trump and members of his campaign knew he had not won enough legitimate state electoral votes to be declared the winner of the 2020 Presidential election during the January 6 Joint Session of Congress, but [2] the President nevertheless sought to use the Vice President to manipulate the results in his favor.

[snip]

[T]he President and the Plaintiff engaged in an extensive public and private campaign to convince the Vice President to reject certain Biden electors or delay the proceedings, without basis, so that the President and his associates would have additional time to manipulate the results. [3] Had this effort succeeded, the electoral count would have been obstructed, impeded, influenced, and (at the very least) delayed, all without any genuine legal justification and based on the false pretense that the election had been stolen. There is no genuine question that the President and Plaintiff attempted to accomplish this specific illegal result. [numbering and bold mine]

As I said, I think this is a bit of a muddle. For starters, the Jan 6 Committee is not arguing that the delay actually caused by Trump’s mob amounted to obstruction. Rather, they’re arguing (at [3]) that had Eastman’s efforts to get Pence to himself impose a delay would be obstruction.

They make that argument even though they have evidence to more closely align their argument to the fact pattern ten judges have already approved. The emails included with this filing show Pence Counsel Greg Jacob twice accusing Eastman of convincing Trump of a theory that Trump then shared with his followers, which in turn caused the riot.

[T]hanks to your bullshit, we are now under siege.

[snip]

[I]t was gravely, gravely irresponsible of you to entice the President of with an academic theory that had no legal viability, and that you well know we would lose before any judge who heard and decided the case. And if the courts declined to hear it, I suppose it could only be decided in the streets. The knowing amplification of that theory through numerous surrogates, whipping large numbers of people into a frenzy over something with no chance of ever attaining legal force through actual process of law, has led us to where we are.

That is, Jacob argued, in real time, that Eastman’s knowingly impossible theory, amplified by the President, caused the riot that ended up putting Pence’s life at risk and delaying the vote certification. But the Jan 6 Committee argues instead that the attempted persuasion of Pence the was the obstructive act.

Perhaps as a result, the agency (transitive versus intransitive) involved in this obstructive act is likewise muddled. In one place (at [1]), the Jan 6 Committee argues that the obstructive act was a failed attempt to persuade Pence to take an illegal action. I’m not sure any of the failed attempts to persuade people to do something illegal (to persuade Pence to do something he couldn’t do, to persuade members of Congress to challenge the vote with either good faith or cynical challenges, to persuade Jeffrey Clark to serve as Acting Attorney General) would sustain legal challenges.

If the Commander in Chief ordered his Vice President to take an illegal act, that would be a bit different, but that’s not what the Jan 6 Committee argues happened here.

Elsewhere, this filing (and other attempts to apply obstruction to Trump) point to Trump’s awareness (at [2]) that he lost the election, and so his attempts to win anyway exhibit an intransitive corrupt intent.

As Charlie Savage noted in his story and a thread on same, to some degree the Jan 6 Committee doesn’t need to do any better. They’re not indicting Trump, they’re just trying to get emails they will likely get via other means anyway (and as such, the inclusion of this argument is significantly PR).

But to the extent that this filing — and not, say, the opinion issued by Judge Mehta after he had approved obstruction, in which he both ruled it was plausible that Trump had conspired with two militias and, more importantly (and to me, at least, shockingly), said it was also plausible that Trump may be liable under an aid and abet standard — is being used as the model for applying obstruction to Trump, it is encouraging a lot of unicorn thinking and, more importantly, a lot of really sloppy thinking. There are so many ways to charge Trump with obstruction that don’t require an inquiry into his beliefs about losing the election, and those are the ones DOJ has laid a groundwork for.

Plus, there are a few more realities that TV lawyers who want to talk about obstruction should consider.

First, it is virtually guaranteed that Friedrich’s opinion — the one that holds that “corrupt” must involve otherwise illegal actions — will be the first one appealed. That’s because whatever happens with the Guy Reffitt trial this week and next, it’s likely it will be appealed. And Reffitt has been building in an appeal of Friedrich’s obstruction decision from the start. First trial, first appeal. So TV lawyers need to study up what she has said about otherwise illegal action and lay out some rebuttals if their theory of Trump’s liability involves mere persuasion.

Second, while ultimately all 22 judges are likely to weigh in on this obstruction application (and there are only two or three judges remaining who might conceivably rule differently than their colleagues), there are just a handful of judges who might face this obstruction application with Trump or a close associate like Roger Stone or Rudy Giuliani. Judge Mehta (by dint of presiding over the Oath Keeper cases) or Judge Kelly (by dint of ruling over the most important Proud Boy cases) might see charges against Roger Stone, Rudy Giuliani, or Alex Jones. Chief Judge Howell might take a higher profile case herself. Or she might give it to either Mehta (who is already presiding over closely related cases, including the January 6 lawsuits of Trump) or one of the two judges who has dealt with issues of Presidential accountability, either former OLC head Moss or Carl Nichols. Notably, Judge Nichols, who might also get related cases based on presiding over the Steve Bannon case, has not yet (as far as I’m aware) issued a ruling upholding 1512(c)(2); I imagine he would uphold it, but don’t know how his opinion might differ from his colleagues.

The application of 18 USC 1512(c)(2) to January 6 is not, as the TV lawyers only now discovering it, an abstract concept. It is something that has been heavily litigated already. There are eight substantive opinions out there, with some nuances between them. The universe of judges who might preside over a Trump case is likewise finite and with the notable exception of Judge Nichols, the two groups largely overlap.

So if TV lawyers with time on their hands want to understand how obstruction would apply to Trump, it’d do well — and it is long overdue — to look at what the judges have actually said and how those opinions differ from the theory of liability being thrown around on TV.

I’m convinced not just that Trump could be prosecuted for obstruction, but that DOJ has been working towards that for some time. But I’m not convinced the current January 6 Committee theory would survive.

Share this entry