Cybersecurity · Wednesday, 19 August 2026
01 · Briefing · what happened
A criminal is selling deletions nobody can check
A ransomware crew is emailing victims offering to erase their stolen files for up to $60,000. Nobody can verify a deletion. This week's other stories turn on the same question: what does the record actually prove?
$60,000
top price for a promised deletion
with no way for a victim to confirm it happened
361
internet addresses hit via VMware's log server
across 47 countries, one suspected state-backed group
500+
confirmed Medusa ransomware victims
up from 300 a year earlier, per the FBI and CISA
444
poisoned npm code packages
downloaded about two billion times a month
At a glance
- A criminal calling itself Ransom Busters is emailing fresh ransomware victims, offering to delete their stolen files for $20,000 to $60,000.
- Investigators say it is not an outside researcher but one freelance criminal renting ransomware from several gangs, spotted by matching case notes across two break-ins.
- Nobody can check a deletion. Stolen files get copied between people, and one gang member rarely controls every copy.
- The week's biggest flaw sits in VMware's log server, the machine that keeps the written record of what every other machine did.
- Patching it is not enough: the attacker leaves a hidden back channel that survives the update, so records have to be re-read.
- GitLab shipped an emergency fix for a flaw that let a stranger with no account delete public projects outright.
- A new npm worm poisoned 444 packages while leaving almost no trace in the matching source code repository.
- Investigators could name Medusa's 500-plus victims, and date a Salesforce theft campaign to March 2025, only because a year of records existed.
Forces in play
A criminal is charging up to $60,000 to delete stolen files, and victims have no way to confirm a deletion. Paying buys a claim, not a fact.
The VMware flaw under attack in 47 countries is in the log server itself, and a GitLab flaw let strangers delete whole projects. The written account is now a target.
Attackers hit an unpatched GeoServer flaw within hours of a researcher posting it, and Medusa uses new flaws within 24 hours. CISA cut its federal fix deadline from 14 days to three.
One break-in at Ceva Logistics is now costing Pokemon Center and Valve customers their order details, and a lender's cloud provider leaked 734,828 people's bank and ID numbers.
A year of FBI case files let CISA name 500-plus Medusa victims and describe the gang's methods, and Fortra confirmed exactly what ExfilSquad holds: 27 million records across 13 victims.
How it unfolded
- 29 Jul Broadcom discloses the critical VMware vCenter log-server flaw
- 4 Aug The ChainDrop worm is found in 444 npm packages
- 12 Aug Reco publishes City-Forum, a data theft running since March 2025
- 17 Aug GitLab ships an emergency fix outside its normal schedule
- 18 Aug CISA and the FBI update the Medusa advisory; Ransom Busters is exposed
Where this points
Watch whether victims of the VMware log-server attacks report finding the hidden back channel still live after patching. That would confirm a fix alone leaves the door open.
Full briefing
The offer with no receipt
Someone calling itself Ransom Busters has been emailing companies that were just hit by ransomware
Ransomware is malware that scrambles your files and demands payment to unscramble them. Modern gangs also copy the files out first, so they can threaten to publish them even if you restore from backup.
GuidePoint Security’s research team, GRIT, ran into Ransom Busters while responding to real incidents involving the DragonForce, Settra and Anubis gangs
Then GRIT compared its own case notes from two separate intrusions. The same scanning tool. The same method of copying data out to cloud storage. A local back-door account with the same password, “Numlock!123”. The same attacker machine name, DESKTOP-BBETH6K, in both
The important part is what a victim can and cannot check. Stolen files get copied between people. A single member of a gang rarely controls every copy. So, as GRIT put it, victims have little ability to verify claims that data has actually been deleted
There is no receipt for a deletion. That is the whole trick.
When the record itself is the target
A different version of the same problem ran through this week’s flaws.
Broadcom disclosed a critical hole in VMware vCenter on 29 July, rated 9.8 out of 10
Patching may not be enough. The attacker leaves behind a hidden back channel out to itself, using an open-source tool called reverse_ssh, and that channel survives the update
GitLab shipped an emergency patch on 17 August, outside its normal schedule, for a flaw rated 9.4
And a new self-spreading worm called ChainDrop poisoned 444 packages on npm, the shared library of building blocks JavaScript programmers pull code from
Elsewhere: attackers began probing an unpatched GeoServer flaw within hours of a researcher posting it publicly
What a year of records can say, and where they stop
CISA, the FBI and the US health department updated their advisory on the Medusa ransomware gang on Tuesday
None of that is guesswork. It is what a year of case files adds up to.
The security firm Reco could say the same about a campaign it calls City-Forum, after a domain tied to the attacker’s address
Then the gap. A seller using the name TheHatman is advertising employee records taken from the Microsoft cloud accounts of nine large companies
Authentic data. No record of the way in.
The week’s breaches
France’s tax authority, the DGFiP, confirmed late on a Thursday that an attacker viewed and copied data on individuals and businesses
Poland is investigating a breach at MyDr, which supplies software to more than 12,000 clinics and doctors and connects them to the national health platform
RingCentral, a business phone and messaging platform, says 1.6 million people had names, addresses, emails and phone numbers stolen in July
Heights Finance, a consumer lender across five US states, is notifying customers of a breach discovered in early May
Crypto hardware wallet maker SafePal says a flaw in an order-tracking add-on exposed the details of 39,798 customers, and emailed them on 16 August
The Ceva Logistics attack keeps widening. Eight European warehouses were disrupted from 29 July
The University of Texas at San Antonio, which serves 40,000 students, took phones and other systems offline after spotting hostile activity over the weekend
And Fortra’s research team confirmed that the extortion group ExfilSquad really does hold what it claims
Two more numbers from the LiteLLM supply-chain attack landed this week. CloudSEK and Hudson Rock put the damage at more than 2,500 organisations and over 430,000 build pipelines
A new set of hands
President Trump signed a memo on 12 August directing his administration to use the private sector to help conduct cyber operations against foreign criminal organisations
Which raises the question this whole week keeps asking: when several parties can act, and each keeps its own account of what it did, whose record settles what happened?
02 · Lesson · why it matters
You cannot stop the edit. You can stop it being quiet.
Anyone inside your systems can reach the record of what they did. The aim is not an unbreakable record but an unbreakably honest one.
How it works
- An attacker reaches a system
- The same access reaches its records
- Traces get removed, so nothing looks wrong
- You cannot make records unerasable on a machine someone else controls
- So make any change impossible to hide: seal each entry, ship copies off the box
- A gap you can see beats a record you cannot trust
The twist
You are not trying to build a record nobody can break. You are trying to build one nobody can break quietly.
Where you've seen this
Accounts ledgers
bound and numbered pages, so a removed page leaves a hole
Evidence handling
signed at every hand-off, so an unsigned gap is itself the finding
Medicine cabinets
a tamper-evident seal does not stop opening, it stops opening unnoticed
Election counts
sealed boxes and observers, so a swap cannot happen in silence
The catch
Tamper evidence tells you that something was altered, not what it said, and it costs storage and money. Nobody is protected by an alert nobody reads.
Full lesson
The receipt that does not exist
A criminal emails a company that has just been robbed and offers to delete the stolen files for $60,000. Set aside whether he is lying. Ask a plainer question: how would anyone find out?
A deletion leaves nothing behind. There is no photograph of an absence. The files sat on his machine, in his country, under his control. Even if he did erase every copy he holds, other members of the gang may hold copies he does not. The victim is being asked to pay for an event that is, by its nature, unobservable.
That is the sharp edge of a problem every system has in a duller form. Almost everything we call proof is really a record, and a record is a thing on a machine, and a machine has an owner.
The second thing an intruder touches
The first thing an attacker reaches is the system. The second is the account of what they did to it.
This is not a subtle move. It is the obvious one. Someone who can run commands on a machine can usually alter what that machine wrote down, and a competent intruder does exactly that before leaving. This week gave the idea a very literal shape. The flaw under heaviest attack sat in the log server itself. That box has one job: hold the written account of what every other box did.
So the instinct to make the record unerasable runs into a wall. You cannot make a file safe from someone who controls the disk it lives on. Locks you own are not much use against a person standing inside the room.
Sealing, not locking
The answer is not a stronger lock. It is a seal.
You write each entry so that it seals the one before it, like a chain where every link is stamped with the shape of the last. Remove the four-hundredth entry and every stamp after it stops matching. You write the record where the writer cannot go back and rewrite it, only add. You copy it, as it happens, onto a machine the attacker does not own. You sign it, so a forged entry cannot be manufactured to fill a hole.
None of that stops the deletion. All of it stops the deletion being quiet.
A hole beats a smooth surface
Here is the turn, and it is not obvious. You are not chasing a perfect record. You are chasing an honest one.
A record with a visible gap tells you something true and useful: someone was here, and this is roughly when. A record with no gap and no seals tells you nothing at all, because you cannot tell an untouched account from a carefully groomed one. The smooth surface is the worse outcome. It is silence wearing the costume of proof.
You can see the difference in the week’s stories without knowing anything technical. Investigators could name five hundred victims of one ransomware gang and date a data theft campaign back to March last year, because the case files went that far back. A firm looking at millions of stolen employee records could confirm the data was real. It could not say how the data was taken, because that part of the account did not survive. Same week, same kind of question, opposite answers, and the difference was entirely whether a record existed to be read.
Where you have already met this
Accountants did not invent bound, numbered ledgers for beauty. A numbered page cannot be quietly removed; its absence is the finding. Evidence in a criminal case is signed at every hand-off, so an unsigned gap becomes the story. The foil under a bottle cap does not stop anyone opening it. It stops anyone opening it and putting it back.
The pattern is the same each time. Where you cannot prevent the act, you make the act announce itself, and then you shift the whole burden onto whoever wants to explain the announcement away.
Whose machine holds the account of you
Almost none of the records about your life are yours.
Whether a lender’s cloud provider actually kept your bank details. When a health platform was last touched. Whether a company deleted what it said it deleted after you asked. Every one of those answers lives on someone else’s machine, written by them, kept for as long as they choose. A logistics firm this week kept delivery details for ninety days, which is why a break-in there reached shoppers who had never heard of it.
That is an arrangement, not a law of nature. Someone chose who keeps the account, how long, and who gets to read it. It works well enough most days, and it is also why, when the question finally matters, the honest answer is so often that nobody can say.
We are all inside that arrangement, including the people who built it. And a seal only helps if someone goes and looks at it.
03 · Lab · your turn
Read the Seal
Rehearse what a record can still prove after someone inside has edited it.
04 · Hope · carry this
A year of patient case notes let investigators name five hundred victims and date a theft to last spring. Most of what we know, someone bothered to write down.
More from Cybersecurity