[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ffKX5Cgv57I8vjqNoOziG7tUf3D8b77zrF-ea7lZxNRA":3},{"article":4,"iocs":48,"iocs_total":52,"watch_terms":53,"solutions":54,"lesson":57},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":26,"category":27,"article_tags":30},"516fd2f7-3084-4b46-ae56-678dc15f20c3","CTO of ‘RansomwareHelp’ Indicted for Wire Fraud","cto-of-ransomwarehelp-indicted-for-wire-fraud-589679","The chief technology officer and co-founder of ransomwarehelp.com, a six year old Florida business that claimed to use \"advanced cryptographic tools\" to restore data locked by ransomware, has been charged with wire fraud after an FBI sting operation found the company was simply paying the attackers for a decryption key and charging victims a markup for work that was never performed.","The CTO of RansomwareHelp.com has been indicted for wire fraud following an FBI sting operation. The company, which claimed to use advanced cryptographic tools for data recovery, was found to be secretly paying ransomware attackers for decryption keys and charging victims a significant markup for services that were never performed. The FBI posed as both a victim and a ransomware group to expose the alleged fraudulent practices.","Ransomwarehelp.com CTO indicted for wire fraud after FBI sting reveals company paid attackers and marked up prices.","https:\u002F\u002Fkrebsonsecurity.com\u002F2026\u002F11\u002Fcto-of-ransomwarehelp-indicted-for-wire-fraud\u002F",null,"2026-11-21T00:36:39+00:00","2026-11-21T01:00:26.464781+00:00",7,[17,20,23],{"name":18,"type":19},"RansomwareHelp","vendor",{"name":21,"type":22},"Lockbit","threat_actor",{"name":24,"type":25},"ransomwarehelp.com","product","7d8b5ab8-ea0b-4ced-ae97-ec251b86993a",{"id":26,"icon":12,"name":28,"slug":29},"Ransomware","ransomware",[31,36,38,43],{"category":32},{"id":33,"icon":12,"name":34,"slug":35},"2e06f76c-d5b9-4f54-9eef-4d3447b10730","Breaches","breaches",{"category":37},{"id":26,"icon":12,"name":28,"slug":29},{"category":39},{"id":40,"icon":12,"name":41,"slug":42},"c5c77cdb-f7d7-4990-9436-c81dcbff1163","Policy","policy",{"category":44},{"id":45,"icon":12,"name":46,"slug":47},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[49],{"type":50,"value":21,"context":51},"malware","Mentioned as a ransomware infection that a victim firm sought help for from RansomwareHelp.",1,[18,24],{"controls":55,"vendors":56},[],[],{"slug":58,"title":59,"body":60,"framework_refs":61,"framework_notes":66},"fake-ransomware-recovery-firm-defrauded-victims-by-secretly-paying-attackers","Fake Ransomware Recovery Firm Defrauded Victims by Secretly Paying Attackers","RansomwareHelp.com falsely claimed to use proprietary cryptographic tools to recover ransomware-encrypted data, when in reality it was simply paying the ransomware operators for decryption keys and charging victims a substantial markup. This is a vendor fraud and due-diligence failure: organizations in crisis trusted a third-party recovery firm without verifying its claims or methods. The incident highlights how desperate victims are prime targets for secondary exploitation, and that the incident-response supply chain carries its own integrity risks. Organizations must vet any external recovery or cybersecurity service provider as rigorously as they would an internal hire, especially when sensitive data and large payments are involved.",[62,63,64,65],"NIST CSF 2.0 GV.SC-06: Cybersecurity supply chain risk management","NIS2 Article 21(2)(d)","NIST SP 800-53 SA-9: External System Services","ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships",{"NIS2 Article 21(2)(d)":67,"NIST SP 800-53 SA-9: External System Services":68,"NIST CSF 2.0 GV.SC-06: Cybersecurity supply chain risk management":69,"ISO\u002FIEC 27001:2022 A.5.19: Information security in supplier relationships":70},"NIS2's supply chain security point requires entities to assess security practices of suppliers and service providers, which would have flagged the unverifiable technical claims made by this fraudulent recovery firm.","SA-9 requires organizations to define and enforce security requirements for external service providers, including verification that contracted services are actually performed as described.","This category requires organizations to assess and manage the trustworthiness of third-party service providers, which would have prompted verification of RansomwareHelp's claimed recovery methods before engaging them.","This control requires establishing and maintaining policies to manage security risks associated with suppliers, which would have mandated due diligence into RansomwareHelp's actual recovery practices."]