Daylila

Cybersecurity · Wednesday, 19 August 2026

01 · Briefing · what happened

A criminal is selling deletions nobody can check

Cybersecurity 8 min 35 sources

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

Unverifiable promises Building

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.

Records under attack High

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.

Speed of exploitation High

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.

Third-party spread Building

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.

Investigations paying off Easing

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.

In play Ransom Busters — criminal selling deletions it cannot prove it performed GuidePoint's GRIT team — matched case notes across two break-ins to unmask it QUIRSO — traced the VMware log-server attacks to 361 addresses in 47 countries CISA and the FBI — published a year of Medusa findings and cut the federal fix deadline to three days Reco — dated the City-Forum data theft back to March 2025

How it unfolded

  1. 29 Jul Broadcom discloses the critical VMware vCenter log-server flaw
  2. 4 Aug The ChainDrop worm is found in 444 npm packages
  3. 12 Aug Reco publishes City-Forum, a data theft running since March 2025
  4. 17 Aug GitLab ships an emergency fix outside its normal schedule
  5. 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 [1]. The pitch sounds like help. It says it broke into the servers of several ransomware gangs, found your stolen files there, and will delete them and destroy the gangs’ backups. The price is $20,000 to $60,000 [2].

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 [1]. Several things did not add up. The emails arrived before the attacks were public knowledge. Legitimate recovery firms make contact after a breach is disclosed [1]. The sender claimed to have been breaking into criminal admin panels for over three years [2]. Asked why it charged, it said working for free would put its access at risk [2].

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 [2]. GRIT concluded with moderate confidence that Ransom Busters is not an outside researcher at all. It is one freelance criminal who rents ransomware from several gangs, quietly diverting payments away from the gangs he works for [1].

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 [1]. Justin Timothy of GuidePoint was blunter: payment to any criminal party offers no guarantee that stolen data will be deleted [2].

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 [3]. vCenter is the console that runs a company’s virtual machines. The specific piece with the hole is the syslog server: the machine that collects the logs, the running written record of what every other machine did [3]. German incident-response firm QUIRSO found the flaw under attack at 361 internet addresses across 47 countries, most heavily in the US, France, Iran and Turkey [4][5]. It traced the activity to a single suspected state-backed group [4].

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 [3][4]. QUIRSO’s Denis Szadkowski told Dark Reading the access persists even after the software is fixed, and recommended going back through the records to rule out an existing compromise [4].

GitLab shipped an emergency patch on 17 August, outside its normal schedule, for a flaw rated 9.4 [6]. Under some conditions it let a stranger with no account and no password remotely change or delete public projects and user data [6]. Only self-managed installations are affected; GitLab’s own hosted service was already patched [6].

And a new self-spreading worm called ChainDrop poisoned 444 packages on npm, the shared library of building blocks JavaScript programmers pull code from [7]. Microsoft and others named it on 4 August. The packages it hit are downloaded roughly two billion times a month [7]. What is notable is how it spreads: through packaged archives and developer-tool hooks that leave little trace in the matching source repository [7]. The published code looked clean. The thing people actually installed was not.

Elsewhere: attackers began probing an unpatched GeoServer flaw within hours of a researcher posting it publicly [8]. WatchTowr has logged hundreds of attempts from a small number of addresses. There is still no fix available [9]. CISA, the US cyber-defence agency, gave federal agencies three days to fix a flaw in Ray, rather than the usual fourteen [10]. Ray is an open-source tool used by Amazon, Apple and OpenAI to run large computing jobs [11]. And the Dutch national cyber centre warned that a patched macOS Screen Sharing flaw is being used on internet-exposed Macs to install a crypto-mining program [33].

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 [12][13]. It is built on a year of ongoing FBI investigations. Medusa’s confirmed victim count rose from more than 300 in March 2025 to more than 500 as of April 2026 [13]. The gang buys its way in from access brokers, paying between $100 and $1 million [13]. It uses newly announced flaws within 24 hours, and has been seen using some up to a week before they were publicly disclosed [12]. Healthcare is its most frequent target [13].

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 [14]. It has been quietly pulling data out of misconfigured Salesforce and ServiceNow portals since at least March 2025 [14]. The attacker built their own tools for interfaces that are barely documented anywhere [14]. Reco recorded more than 560,000 attacks worldwide [15]. Targets spanned telecoms, banks, enterprise software and public-sector portals [14].

Then the gap. A seller using the name TheHatman is advertising employee records taken from the Microsoft cloud accounts of nine large companies [17]. The claimed haul includes 1.7 million records from McDonald’s, 800,000 from Tata Consultancy Services and 425,000 from Vodafone [16]. Hudson Rock assessed the samples as highly likely authentic [16]. But it could not establish how the attacker got in [16]. The records reportedly include job titles, reporting lines and which accounts hold top administrator rights, which is a ready-made target list [16].

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 [18]. The access happened in late June, and was detected and cut off in late June [18]. It only became public when the hacker claimed it this month [18]. A hacker using the alias ZeroBytes claimed data on more than 600,000 people; the authority now puts the figure at 680,000 [18][19].

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 [20]. Up to 19 million people may be affected. Officials say attackers reached historical records held through April 2024 [20]. As a precaution, the country’s e-Health Centre is replacing the digital certificates medical systems use to connect [20].

RingCentral, a business phone and messaging platform, says 1.6 million people had names, addresses, emails and phone numbers stolen in July [21]. It blames a social engineering campaign: tricking a person rather than picking a lock [22]. The stolen data has since been published [21].

Heights Finance, a consumer lender across five US states, is notifying customers of a breach discovered in early May [23]. Names, Social Security numbers, bank account details and driver’s licence numbers were taken from a third-party cloud platform [24]. The two published counts differ because they measure different things: the company told Texas regulators that 734,828 people were affected, while its wider notification covers more than 1.2 million [23][24].

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 [25]. It says no wallet keys, recovery phrases or payment card numbers were involved [25].

The Ceva Logistics attack keeps widening. Eight European warehouses were disrupted from 29 July [26]. Pokemon Center is now telling customers in the UK and Germany that their order details were taken, because it had shared them with Ceva to ship the orders [27]. Valve told Steam hardware customers the same thing [27].

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 [28][29]. Chief technology officer Michael Schnabel said it was caught at the edge of the network and contained before reaching core systems [28]. He also said the investigation has found no evidence that university data was accessed or copied out [28]. Classes started Wednesday; payment deadlines were pushed to Friday [28].

And Fortra’s research team confirmed that the extortion group ExfilSquad really does hold what it claims [30]. The published files ran to 382.64 GB and about 27 million records across 13 victims, released on 7 August [30]. The named victims include the City of Atlanta and the UK Department for Education [30]. That is what verification looks like when it is possible.

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 [32]. All of it came from a 40-minute window in March, when poisoned versions sat in the official Python package repository [31]. Hudson Rock analysed a 195-terabyte file of what came out [31].

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 [34]. The White House says the work would be done “under the direction, control, and authority of the U.S. Government” [34]. The memo authorises limited operations at the government’s direction, not open-ended freedom for companies to hack [35]. It still hands the private sector a role long reserved for government agencies [35].

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

  1. An attacker reaches a system
  2. The same access reaches its records
  3. Traces get removed, so nothing looks wrong
  4. You cannot make records unerasable on a machine someone else controls
  5. So make any change impossible to hide: seal each entry, ship copies off the box
  6. 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.

Across the beats