The images in this article were generated with artificial intelligence. How we publish
A recent case study reconstructed from filtered chats and block chain traceability suggests that a United States local administration paid about a million dollars to prevent the publication of stolen files, and that the band that received that money - which is identified as Kairos - probably did not use a cipher at all. Instead of blocking systems with classic ansomware, the threat was simple and direct: stealing data and demanding payment to not disclose them. If we confirm the connection to a Ohio county that notified tens of thousands of residents, we would be facing an operation that changed the nickname of "ransomware" to a extortion based exclusively on exfiltration.
The payment - according to the published track - was made in bitcoin and was quickly divided and sent to several exchange platforms, which illustrates two key ideas: first, the public chain of transactions in cryptomonedas provides valuable clues to researchers and prosecutors; and second, traceability offers signs, not identities. No "elimination test" provided by the attackers ensures that the data has been completely deleted: it is, at best, a paper sheet signed by the offender.

This case is not a technical anomaly but a manifestation of a trend that already detected security signatures: fewer attacks use encryption today than a few years ago; many bands have opted for the so-called "pure extortion" based on the threat of filtering sensitive information. For small public organizations - with limited resources and a large volume of confidential personal information - this represents a strategic risk: a single access with basic tools (for example, guessed passwords) can become the key that opens a data repository that is then monetized without altering files locally.
The implications are multiple. In the immediate future, paying can silence the leak for a while, but it feeds a profitable market and normalizes extortion as a business model; in addition, the lack of transparency on rescue payments often erodes public confidence and may conflict with legal reporting obligations. In the operational plane, the absence of encryption in the attack requires rethinking detection and response: it is not enough to locate encryption processes, you need to monitor exfiltrations, abnormal accesses and time links used to move files off the network.

For local government administrators and small organizations with critical personal data, practical measures are clear but include sustained work: to activate mandatory multi-factor authentication where possible, to segregate sensitive information repositories (legal records, human resources, citizenship records) in areas with audited access, and to establish detection of unusual outgoing traffic and repeated login attempts. It is also essential to have a public communication plan prepared and tested, together with prior coordination with law enforcement and cyber insurers. Any promise to "erase everything" by the extortor should be considered without evidentiary value.
The traceability of the bitcoin funds used in this case shows that the authorities have tools to follow the financial trail, but transforming directions and balance sheets into responsible will require additional work and international cooperation. In the meantime, affected entities should report incidents to the relevant agencies to access guides and assistance; in the United States, official resources such as those of the CISA and FBI provide guidance on response, reporting and mitigation.
The final lesson is institutional: maintaining secure infrastructure is not a timely task but a continuous discipline that combines technical controls, monitoring, legal response and public communication. When a public entity assesses its position on these threats, it must assume that attackers no longer need to cipher to do harm; the economy of extortion has diversified, and resilience depends on both preventing initial access and reducing the value and exposure of the data that an intruder can achieve.
Related
More news on the same subject.

Four Plex2Shell CVE allows remote execution and mining and proxy backdoor deployment
In recent days, an increase in attacks has been confirmed that take advantage of a chain of failures in Plex Media Server - nicknamed "Plex2Shell" by researchers - to run code r...

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...

Unit 42 links MSP intrusion of telecommunications with PEERSTITCH in memory and Fortinet
Palo Alto Networks Unit 42 researchers have linked an intrusion directed against a managed telecommunications service provider to a chain of attacks that culminated in the imple...