DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Southern Ute Indian Tribe says U.S. Treasury Dept. leaked confidential information

Posted on April 21, 2020 by Dissent

The Durango Herald reports:

The Southern Ute Indian Tribe is demanding an investigation into the U.S. Treasury Department after the tribe said the department leaked confidential tribal information given to it as part of an effort to obtain funds under the Coronavirus Aid, Relief and Economic Security Act.

On Monday, all state, local and tribal governments were instructed to download information into a secure portal at the Department of Treasury so that they could receive their CARES Act funds, according to a news release issued Saturday by Southern Ute Indian Tribe spokeswoman Lindsay Box.

Leaked information about the tribe included tribal membership, lands held in trust and in fee, expenditures, and bank account information, according to the news release.

Read more on The Durango Herald.  The following is the full text of the tribe’s statement on April 18:

Southern Ute Indian Reservation – On March 27, 2020, the President signed the Coronavirus Aid, Relief and Economic Security Act, also known as the CARES Act. This act provided $150 billion for governments, including $8 billion to be allocated among the 574 federally recognized Indian Tribes and Alaska Native Villages The funds were to be distributed within 30 days.

On Monday, April 13, 2020, all state, local and tribal governments were instructed to download information in to a secure portal at the Department of Treasury so that they could receive their CARES Act funds. For Tribes and tribal businesses, the information to be provided included tribal membership, lands held in trust and in fee, expenditures, and bank account information in which the funds were to be deposited. The first portion of the funds were to be deposited in to the Tribe’s bank account within approximately 24 hours of filing the certification.

Although the Southern Ute Indian Tribe filed its certification on Wednesday morning, no funds have been received. To make matters worse, on Friday evening we learned that the information provided to the Department of Treasury by every Tribe in the country had been unlawfully released.

The Southern Ute Indian Tribe has taken steps to make sure that its bank account is secure. But more importantly, the unlawful actions by one or more individuals at the federal government to leak this confidential information must be immediately investigated. We call upon the Department of Justice to immediately do so. The history of relations between the United States and tribal nations is replete with broken promises. The unlawful release of information is evidence that those broken promises by the federal government continue to this day.

Read coverage on Indianz for more detailed coverage of who had access to the leaked data and why they might have had access. Was this an intentional leak for political purposes or was this one of those erosion of privacy in the name of dealing with the pandemic leaks? It’s hard to even guess at this point, but this clearly requires an intensive investigation with transparent results and disclosure.


Related:

  • US declines to join more than 70 countries in signing UN cybercrime treaty
  • UN Cybercrime Convention to be signed in Hanoi to tackle global offences
  • John Bolton Indictment Provides Interesting Details About Hack of His AOL Account and Extortion Attempt
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • No Kings. Not Today. Not Ever.
  • BreachForums Seized -- Again!
Category: Miscellaneous

Post navigation

← UniCredit Hackers Try to Sell Employee Data on Cyber-Crime Forums
Supreme Court to Consider Whether Improper Data Access Violates Computer Crime Law →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.