Warning: filesize(): stat failed for /home/wordpress/doc_root/wp-content/cache/object/options/f7e/014/f7e014a4f3ac6aa1c848c26016edd536.php in /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php on line 157

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-includes/rest-api/class-wp-rest-server.php on line 1831

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-content/plugins/central-connect/src/Rest/Server.php on line 89

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-content/plugins/central-connect/src/Rest/Server.php on line 90

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-content/plugins/central-connect/src/Rest/Server.php on line 91

Warning: Cannot modify header information - headers already sent by (output started at /home/wordpress/doc_root/wp-content/plugins/w3-total-cache/Cache_File.php:157) in /home/wordpress/doc_root/wp-content/plugins/central-connect/src/Rest/Server.php on line 92
{"id":47205,"date":"2023-01-08T08:56:47","date_gmt":"2023-01-08T13:56:47","guid":{"rendered":"https:\/\/www.uspresidentialelectionnews.com\/?p=47205"},"modified":"2023-01-08T08:56:47","modified_gmt":"2023-01-08T13:56:47","slug":"jan-6-committee-leaks-social-security-numbers-of-nearly-2000-trump-allies","status":"publish","type":"post","link":"https:\/\/www.uspresidentialelectionnews.com\/2023\/01\/jan-6-committee-leaks-social-security-numbers-of-nearly-2000-trump-allies\/","title":{"rendered":"Jan. 6 Committee Leaks Social Security Numbers of Nearly 2,000 Trump Allies"},"content":{"rendered":"

Nothing to see here, right?<\/p>\n

According to a report in the Washington Post, as the Jan. 6 committee was finishing out its politically-motivated investigation into Donald Trump and his allies, it posted a document dump that included a spreadsheet of nearly 2,000 social security numbers associated with White House visitors. These included several Trump cabinet members as well as other Trump supporters and advisors.<\/p>\n

So far, the committee has played dumb on the matter. How does this happen<\/a>?<\/p>\n

When the House Jan. 6 committee wrapped up its work in recent weeks, it posted hundreds of records online, including interview transcripts, audio recordings and text messages.<\/p>\n

Also buried in the massive cache was a spreadsheet with nearly 2,000 Social Security numbers associated with visitors to the White House in December 2020, including at least three members of Trump\u2019s Cabinet, a few Republican governors and numerous Trump allies.<\/p>\n

While the spreadsheet with the numbers was taken down Wednesday, the high-profile nature of the people whose data was exposed probably puts them at an \u201celevated risk\u201d because the information would be especially useful to intelligence agencies, said James Lee, chief operating officer of the Identity Theft Resource Center, a nonprofit organization that advises victims of identity crimes and compromises.<\/p><\/blockquote>\n

This committee has been nothing more than a partisan witch hunt attacking any and every Trump supporter that was breathing back on January 6, 2021. How and why did they have a compiled spreadsheet laying around that contained social security numbers and other private information of former high-level government officials? That question alone seems like it’s worth getting an answer for.<\/p>\n

To make matters worse, it’s not even clear if the individuals affected have yet been notified:<\/p>\n

Exposed individuals don\u2019t appear to have been notified about the leak. The Government Publishing Office (GPO), which originally published the file, did not respond to a request for comment on whether it planned to notify people whose Social Security numbers were exposed.<\/p>\n

\u201cTo my knowledge, we were not notified. The governor was not notified,\u201d said Ian Fury, a spokesman for South Dakota Gov. Kristi L. Noem (R). Social Security numbers were listed alongside the names of Noem, her husband and her three children.<\/p><\/blockquote>\n

Kayleigh McEnany, former White House Press Secretary for Donald Trump, was awoken last week to a text message filled with vulgar harassment followed up by a message containing her social security number, a situation likely stemming directly from the J6 committee leak. McEnany described her ordeal<\/a> Friday on the Mark Levin radio show.<\/p>\n

Gov. Kristi Noem, of South Dakota, was another high-level official also affected and is currently fighting for more information:<\/p>\n

\n

My lawyers have asked the @WhiteHouse<\/a>, the @USNatArchives<\/a>, and @BennieGThompson<\/a> which of them is responsible for leaking the Social Security Numbers of me, my husband, my 3 kids, and my son-in-law.<\/p>\n

What specific measures and remedies will be taken to protect our identities? pic.twitter.com\/HWBu5ukWPP<\/a><\/p>\n

— Kristi Noem (@KristiNoem) January 6, 2023<\/a><\/p><\/blockquote>\n