- The Washington Times - Wednesday, March 18, 2026

Sen. Markwayne Mullin acknowledged to colleagues Wednesday that he took part in an ultra-secret operation a decade ago as a member of Congress that he can’t speak about in public — and the matter could derail his path to a speedy confirmation as the next Homeland Security secretary.

Sen. Rand Paul, Kentucky Republican and chairman of the Homeland Security and Governmental Affairs Committee, suggested delaying a vote in the committee planned for Thursday unless it gets details on the operation.

“I can cancel the vote,” he warned Mr. Mullin.



Mr. Mullin, Oklahoma Republican, has been cagey with the details, saying he’s spoken about the operation in only general terms and never publicly revealed the dates or locations. He said it began in 2015 and ran until 2016, and he did it for the U.S. House, where he was a member at the time.

“It was only me and three other people,” he said.

Mr. Mullin used the word “mission” to characterize the operation in response to Sen. Gary Peters, Michigan Democrat.

Later, questioned by Mr. Paul, Mr. Mullin said it “wasn’t a mission; it was official travel.” He called it “fact-finding.”

Democrats homed in on the operation, seeing something troubling in it.

Advertisement
Advertisement

“You have not been forthcoming with me or this committee,” Mr. Peters said. “We have to clear this up.”

Mr. Peters was questioning Mr. Mullin over a previous comment that he had “smelled war.” Mr. Mullin has never been in the military.

It was then that Mr. Mullin mentioned the classified operation.

Mr. Paul and Mr. Peters said they wanted to adjourn the open hearing to go to a secure room where classified information could be shared.

Mr. Mullin said he would be open to that, but he said it wasn’t up to him to declassify the mission.

Advertisement
Advertisement

“I can’t make that authorization. You guys know that,” he said.

He added: “I have nothing to hide on this.”

• Stephen Dinan can be reached at sdinan@washingtontimes.com.

Copyright © 2026 The Washington Times, LLC. Click here for reprint permission.

Please read our comment policy before commenting.