Urgent.News

What's breaking now, across thousands of outlets.

Tech

FBI Arrests Founder of Ransomware Negotiation Firm

Agents with the Federal Bureau of Investigation (FBI) on Thursday arrested the co-founder of a Canadian cybersecurity firm in connection with an investigation into the ShinyHunters hacking group that recently relieved the FBI of sensitive data on thousands of agents, multiple sources tell KrebsOnSecurity.

FBI Arrests Founder of Ransomware Negotiation Firm

The FBI arrested a Canadian man on Thursday, linked to the ShinyHunters hacking group, according to multiple sources. ShinyHunters recently stole sensitive data from thousands of FBI agents. The arrestee, whose company assists in ransomware negotiations, was in Pennsylvania for a cyber insurance conference. Control over the ShinyHunters investigation is based out of an FBI field office in Texas.

Edward Dubrovsky, the co-founder of a Canadian cybersecurity firm, is the suspect; he faces charges of conspiracy and cyber extortion in a federal court. Court documents reveal he's in custody in Philadelphia. Dubrovsky penned a book, "Cyber Extortion Strategic Response," about ransomware negotiations. The FBI is probing seized devices from an earlier Dutch arrest related to ShinyHunters.

Written by urgent.news from KrebsOnSecurity's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at krebsonsecurity.com →

More in Tech

Word never stores the list numbers you see — a DOCX converter has to run a numbering engine

A law firm sent me a 60-page contract to convert, and by section 7 every cross-reference was off by one. The text said "as set out in clause 6.3" while the heading it pointed to read "6.4".

  • List numbers in DOCX files are not stored, only computed at render time.
  • Word's numbering engine handles formatting, start values, and overrides.
  • Accurate conversion requires implementing ECMA-376 sequence resolution rules.

A git tag is not a release: requests v2.16.1 declares 2.16.0

In psf/requests, the tag v2.16.1 points at code whose __version__.py says 2.16.0 . The tag v2.16.0 says the same, and the code differs between them.

  • Git tag v2.16.1 points to code version 2.16.0
  • Tag v2.16.0 also points to same code version
  • Discrepancy raises question of tags being different things

The Epistemology of Quality

Should we expect human software developers to review code written by AI? For many the answer is clearly yes: how else will we maintain accountability?

  • Traditional code review focused on syntax and standards, lacking teaching opportunities.
  • Pair programming combined various evidence types, providing stronger defect detection.
  • AI-generated code may lack real-world proof, making manual review critical.

More from Saturday 10 October →