DataBreaches.Net

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

They’re guilty of ID theft, but don’t ask the government how/where they got the personal info?

Posted on December 26, 2012 by Dissent

Here’s another case where it’s clear there’s been some compromise of PII, but we have no idea how from what law enforcement tells us:

According to documents filed in court, Miami-Dade Police Department (MDPD) officers executed a search warrant at [Travonn Xavier Russell’s] residence on January 18, 2012. During the search, MDPD officers found the following inside the residence: distribution quantities of different types of narcotics (cocaine, MDMA, and marijuana); paraphernalia associated with narcotics distribution; two firearms; approximately 129 debit cards in various names; tax return documents in names other than the defendant’s; and multiple notebooks with personal identifying information (names, dates of birth, and social security numbers) of 442 individuals.

The criminal complaint also indicated that they found “various employment applications with personal identifying information along with photocopies of driver’s licenses belonging to individuals other than Russell” and “additional photocopies of social security cards and driver’s licenses in names other than Russell.”

With respect to the notebooks, the complaint states:

Notebooks with hundreds of hand-written entries with names, social security numbers, dates of birth, addresses, occupations, e-mail addresses with password, date accepted, date filed and dollar amount – none of which were in the name of RUSSELL (numerous entries of personal identifying information in the notebooks match the names embossed on the debit cards).

So where did he get the identity info?  They don’t say.  In fact, nowhere in the court records that I read does it mention the source of the identity information.  You’d think law enforcement might ask or make a point of finding out, right?  Apparently not.

I had an interesting conversation recently with someone knowledgeable about USAO press releases. He informed me that there were actually very strict laws about what they are allowed to include in press releases and that the releases cannot go beyond the public record. That makes sense, I suppose, but it is still frustrating because I think it should be in the court documents.

I wish prosecutors would make it part of any plea deal that the defendant has to explain how/where they got the identity information.

But that’s in the World According to Dissent. Most law enforcement officials don’t inhabit that world. 🙂


Related:

  • Some lower-tier ransomware gangs have formed a new RaaS alliance -- or have they? (1)
  • Uncovering Qilin attack methods exposed through multiple cases
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
  • Ex-CISA head thinks AI might fix code so fast we won't need security teams
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Confidence in ransomware recovery is high but actual success rates remain low
Category: Commentaries and AnalysesID Theft

Post navigation

← Health-care sector vulnerable to hackers (and other security problems), researchers say
Inadequate security of personal, private, and sensitive Information in school districts’ mobile computing devices – audit →

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.