As irony meters around the world explode, #DOGE claims that publishing its employees' info is tantamount to doxxing and is an invasion of their #privacy.
Here's my post on the court injunction my site got hit with:
HCRG Care's lawyers claimed an injunction issued in a "private" hearing required us to remove two posts. We didn't comply.
HCRG Care was represented by the Pinsent Masons law firm in the UK in this matter. The injunction was issued by the High Court of Justice, King's Bench Division, Media and Communications List by the Honorable Mr. Justice Soole.
Pinsent Mason's attempt to get my web host to remove my posts also failed.
As always, I feel blessed to have the legal support of Covington and Burling's Kurt Wimmer Pro Media Freedom Initiative, which has represented my site pro bono for the last 16 years.
Read about the letter, the injunction, and why the High Court's over-reaching injunction endangers UK journalists and doesn't serve the public well.
Oh, and I'm not the only one ignoring the injunction. Medusa also got served with the injunction via tox chat, they tell me. And like other injunctions they have received, they are ignoring it. So what has HCRG really accomplished?
Last Friday I received a letter from a U.K. law firm with an attached injunction. The law firm claimed I must remove two posts about their client.
That is not going to happen. I am not under the jurisdiction of the U.K. or the High Court of Justice. My lawyer informed them of that yesterday.
But DataBreaches.net might disappear tomorrow because the U.K. law firm sent the injunction to my domain registrar who, innocently believing them, informed me they will suspend my site if I don't remove the posts within 24 hours. I have replied to them but have not heard back.
So...
If my site is gone tomorrow, I will let you know where you can read a lot more about the injunction and how the injunction poses a serious risk of censorship in the U.K.
If my site is still online tomorrow, I will still let you know here where you can read about the over-reaching injunction obtained in a private hearing where no one represented journalists whose reporting was being censored.
@GossiTheDog Being explicit that an attack is "ransomware" is only really helpful if we all only call an attack "ransomware" if ransomware is actually deployed and encrypts the victim's files. If there's no encryption of files, maybe we should call it a hack with an extortion attempt. Right now, too many folks use "ransomware" to describe incidents in which nothing's encrypted and I think that creates a wrong impression and may cause even more unease.
OK, a huge thumbs up to Byte Federal for their breach notification letter. They frankly admit where they screwed up and what happened. I wish more notifications were as clear and straightforward as this one.
I really do not understand what Russia is doing arresting nationals involved in ransomware. Why are they arresting Matveev now (if at all)? So many Russian threat actors felt safe from prosecution as long as they stayed in Russia and didn't attack Russia or CIS.
Now we have alleged members of REvil awaiting sentences that could be like 7 years, and Matveev being arrested. WTH?
Anyone have any actual info on why Russia is doing this?
So it seems that on November 12 -- the day before Judge Batten was to sentence Robert Purbeck (aka Lifelock), Purbeck filed a pro se motion for the judge to recuse himself. The motion made all kinds of arguments about supposed conflict of interest and wrongdoing, etc. etc.
But the motion didn't get docketed until November 14.
And on November 13, when Judge Batten went to sentence Purbeck, neither Purbeck nor his attorney even mentioned any motion to recuse.
Today the judge ruled on the motion, noting that he had not even been aware of it until this morning, but was denying it on multiple procedural grounds, adding a footnote that "Although denying the motion on procedural grounds, the Court notes that Purbeck’s motion is littered with factual errors, rendering the motion meritless."
That's such a professional way of saying "he's full of shit." I'll have to remember that one.
This is a case that started because the threat actor, "Lifelock," contacted DataBreaches to try to get DataBreaches.net to report on victims who hadn't paid his ransom demands.
Some of his court filings tried to blame me for the FBI raiding him and seizing his devices. The FBI did their own investigation but yes, it was my reporting that initially made the FBI aware of Robert Purbeck.
Heads up! New developments -- and arrests -- in law enforcement pursuit of LockBit.
Law enforcement reactivated a previously seized LockBit URL to announce what will be revealed tomorrow. Announcements will include the arrest of what they describe as a major LockBit actor, other LockBit-linked UK arrests, and a member of EvilCorp identified as a LockBit affiliate.
Threat actors called VANIR Ransomware Group posted a few listings in July. Tonight, their onion site has a seized message:
" THIS HIDDEN SITE HAS BEEN SEIZED by the State Bureau of Investigation Baden-Württemberg as a part of a law enforcement action taken against Vanir Ransomware Group "
This seems to be a week for announcing big lawsuit settlements. Here's another big one:
An Oracle lawsuit settlement for $115 million addresses claims that Oracle unlawfully tracked and collected vast amounts of personal information without obtaining proper consent from users and allegedly sold it to third parties for advertising purposes through Oracle’s various advertising products, including ID Graph and Data Marketplace.
If you think you might be an eligible class member, you only have until Oct. 17th to file a claim. See the settlement site for info on who's eligible, etc.
The #FTC went after #Blackbaud for its poort security, #databreach in 2020, and incident response. A ton of provisions in the proposed order, but no monetary penalty.
I like how they included that after paying $250k to the threat actors to get them to delete the data, "The company never verified, however, that the hacker actually deleted the stolen data, according to the complaint."
"Based on 481 ransomware attacks from the Dutch police and a Dutch incident response party, we arrive at a number of key insights: Insurance led to a 2.8x higher ransom amount paid, without affecting the frequency of payments. Data exfiltration led to a 5.5 times higher ransom amount paid, without affecting the frequency of payments. Organizations with recoverable backups were 27.4 times less likely to pay the ransom compared to victims without recoverable backups.
Blogger/journalist at databreaches.net and pogowasright.org. As a retired healthcare professional, breaches in the healthcare sector are my priority.The header pic is Indy, a Siberian husky we rescued in 2016 after I read how nobody wanted her because she was so difficult. She is now living her best life and is a mushball with me. My avatar is her co-conspirator, Senna. We rescued him from the town shelter in 2018. He is named for the #F1 #GOAT.