ESET researchers analyzed the sturdy EDR-killing toolset of the ransomware-as-a-service gang Gents. For the reason that starting of 2026, Gents has emerged as one of the crucial lively gangs within the ransomware ecosystem. The group distinguishes itself by a mature, operator-maintained set of endpoint detection and response (EDR) killers, i.e., instruments for disrupting safety software program. Moreover, in contrast to most top-tier gangs, Gents doesn’t exhibit a powerful US-centric victimology, as a substitute focusing on victims throughout Southeast Asia, South America, and Western Europe.<\/p>\n

Whereas there have been a number of studies masking Gents in latest months, they haven’t centered on an in depth evaluation of the group\u2019s EDR killers. Due to ESET\u2019s continued incident-level visibility, we will nonetheless present a uniquely deep view into Gents\u2019s EDR-killer improvement practices. The interior knowledge leak that Gents suffered in Might 2026 then gave us much more perception into the internal workings of the group.<\/p>\n

The leak additionally allowed us to verify our speculation from February 2026 that Gents operators actively develop and keep a portfolio of EDR killers that they provide to associates, centered round their in-house framework we have now named GentleKiller. Additionally they incorporate third-party or leaked instruments reminiscent of HexKiller, ThrottleBlood, and HavocKiller. These instruments are standardized by a shared defense-evasion layer, impersonating predominantly safety distributors utilizing faux model info, and copied respectable certificates and icons. Gents additionally demonstrates a capability to unusually rapidly operationalize newly disclosed Deliver Your Personal Weak Driver (BYOVD) proofs-of-concept, usually inside days of public launch.<\/p>\n

On this blogpost, we share our findings on Gents\u2019s suite of EDR killers gained by intensive analysis and corroborated by the latest leak. We goal to supply actionable insights by connecting the EDR killer packages to precise samples, and tying the leaked knowledge to ways, methods, and procedures (TTPs). Our findings spotlight Gents as one of the crucial technically agile ransomware-as-a-service (RaaS) gangs lively in 2026.<\/p>\n

\n
Key factors of the blogpost:<\/strong><\/p>\n
\n
Gents operators develop and keep an EDR-killer suite offered on to associates.<\/li>\n
GentleKiller is an in\u2011home framework with not less than eight variants abusing totally different weak or malicious drivers.<\/li>\n
Gents operators apply a unified evasion technique throughout instruments that standardizes impersonation and safety.<\/li>\n
Third\u2011social gathering EDR killers (HexKiller, ThrottleBlood, and HavocKiller) are operationally built-in.<\/li>\n
Gents can quickly adapt newly launched EDR killer proofs-of-concept (PoCs).<\/li>\n
The gang\u2019s victimology is globally distributed and notably not US\u2011centered.<\/li>\n
Gents additionally makes use of OxideHarvest, a credential stealer maintained by one of many group\u2019s associates.<\/li>\n<\/ul>\n<\/blockquote>\n
All through this blogpost, we check with RaaS operators<\/strong> and associates<\/strong>.<\/p>\n
Operators<\/strong> are liable for growing the ransomware payload, managing decryption keys, sustaining the devoted leak web site, usually negotiating the ransom cost with victims, and providing different tooling and providers for a month-to-month price or a proportion from the ransom cost (sometimes 5\u201320%).<\/p>\n
Associates<\/strong> lease ransomware providers from operators, deploy encryptors to victims\u2019 networks, and are additionally liable for knowledge exfiltration.<\/p>\n
Gents profile<\/h2>\n
Gents emerged in late 2025 as a RaaS operation and rapidly grew into one of the crucial lively ransomware gangs noticed in Q1 2026. The gang affords a beneficiant 90% share to associates. Group-IB disclosed<\/a> that Gents was based by hastalamuerte<\/span>, a disgruntled former Qilin affiliate. PRODAFT tweeted<\/a> on October 17^{th<\/sup>, 2025 that Gents operators have been beforehand associates of Qilin, Embargo, LockBit, Medusa, and BlackLock. On June 10^{th<\/sup>, 2026 Brian Krebs}}shared proof<\/a> of hastalamuerte<\/span>\u2019s true id.<\/p>\n
Gents makes use of double extortion \u2013 along with encrypting the sufferer knowledge, the group additionally threatens to leak it if the ransom shouldn’t be paid. For encryption, the operators provide a variant written in Go focusing on Home windows, Linux, and different platforms, and an ESXi variant written in C.<\/p>\n
One of many issues that units Gents aside is the gang\u2019s willingness to supply extra than simply encryptors to associates \u2013 specifically, the gang additionally supplies EDR killers. Latest ESET analysis<\/a> has proven that, in most ransomware intrusions, the duty for locating a dependable EDR killer sometimes falls on particular person associates, not the RaaS operators themselves. Solely a small variety of exceptions to this mannequin have been documented. One notable case is RansomHub<\/a>, which invested in growing its personal EDR killer from scratch, EDRKillShifter, after which provided it to associates by the affiliate panel.<\/p>\n
Gents represents a special, and to this point underreported, method. Slightly than counting on associates to supply their very own EDR killers, Gents operators actively develop and keep a portfolio of EDR killers for associates. This portfolio combines an in-house developed software, which we named GentleKiller, together with externally sourced or leaked tooling, standardized by a shared evasion layer and staged in a constant method.<\/p>\n
ESET researchers hypothesized that GentleKiller was an inside software again in February 2026, and this was later supported by studies from Group-IB<\/a> and Verify Level<\/a> \u2013 each point out that the gang supplies EDR-killing capabilities to its (verified) associates. The just lately leaked inside knowledge<\/a> of the gang offered the ultimate piece of proof: within the leaks, zeta88<\/span> (one other alias utilized by hastalamuerte<\/span>), the chief of the gang, brazenly talks about sustaining and offering EDR-killer packages.<\/p>\n
Other than confirming our suspicion about GentleKiller, the leaked knowledge additionally allowed us to hyperlink a credential stealer we named OxideHarvest to Gents; particularly, to one in all its associates.<\/p>\n
Victimology<\/h3>\n
Whereas the victimology of enormous RaaS operations is commonly formed extra by associates\u2019 decisions than by operator-led technique, one specific sample nonetheless tends to emerge. Most main ransomware gangs present a powerful and protracted give attention to the US, which regularly accounts for roughly half of all introduced victims. This US-centric bias is clear throughout a number of distinguished teams, together with Qilin, DragonForce, and Akira, and has successfully develop into the norm amongst top-tier ransomware operations.<\/p>\n
Gents stands out as a notable exception to this pattern. Regardless of rating among the many 5 most lively ransomware gangs in Q1 2026, its victimology doesn’t exhibit a comparable US focus. As a substitute, Gents associates constantly goal victims throughout a broad and geographically numerous vary of nations, with a major variety of victims coming from areas reminiscent of Southeast Asia, South America, and Western Europe. Certainly, the gang\u2019s focusing on consists of some in any other case uncommon nations like Thailand, Brazil, and France.<\/p>\n
The just lately leaked knowledge supplies proof that relating to selecting victims, Gents makes use of a centralized method of sorting by viable candidates after which distributing them to associates. Victims are chosen based on their FortiGate (mis)configuration quite than their geographical location.<\/p>\n
EDR Killers<\/h2>\n
In February 2026, we noticed a beforehand undocumented EDR killer deployed by a Gents affiliate and staged in a listing named GentlemenCollection<\/span>. We named this software GentleKiller. On the time, we hypothesized that it was not an affiliate-specific artifact however quite a software offered to associates by the Gents operators. Since then, we have now noticed the identical staging sample (dropping GentleKiller and different EDR killers to the GentlemenCollection<\/span> listing) a number of instances throughout unrelated intrusions that we investigated, constantly involving Gents associates. In parallel, two independently printed studies by Group-IB<\/a> and Verify Level<\/a> assessed that the Gents operators explicitly provide EDR-disabling capabilities as a part of their RaaS program.<\/p>\n
Taken collectively, these observations allowed us to conclude that GentleKiller is a part of an EDR-killer suite maintained by the Gents operators. This was later confirmed within the group\u2019s leaked knowledge.<\/p>\n
In addition to GentleKiller, the suite additionally accommodates HexKiller, HavocKiller, and ThrottleBlood; all ESET names for EDR killers utilized by associates of rival gangs too and obtained by Gents through unknown means. We additionally noticed DemoKiller in a number of intrusions, however this EDR killer didn’t exhibit any ties to Gents and due to this fact we exclude it from the gang\u2019s suite and as a substitute think about it affiliate-specific. The next a part of the blogpost covers these instruments in additional element and locations them into the broader EDR-killer ecosystem. Whereas these instruments are operationally built-in into Gents intrusions, we assess with excessive confidence that solely GentleKiller is developed in-house by the Gents operators, whereas the remaining EDR killers have been seemingly sourced externally and subsequently modified and standardized to suit the operators\u2019 toolset. Our evaluation is predicated on:<\/p>\n
\n
GentleKiller showing primarily in Gents-related intrusions, usually deployed to the GentlemenCollection<\/span> listing,<\/li>\n
steady improvement with clear entry to the supply code that enables creating new variants and supporting newly emerged PoCs, and<\/li>\n
third-party reporting mentioning Gents providing EDR-killing capabilities to trusted associates.<\/li>\n<\/ul>\n
Protection evasion technique<\/h3>\n
Gents operators apply a particular set of protection evasion methods to the gang\u2019s varied EDR killers. These methods are utilized to compiled samples quite than supply code. This offers Gents the choice to guard even the EDR killers whose supply code the gang doesn’t possess.<\/p>\n
All of the EDR killers which are a part of Gents\u2019s portfolio comply with these defense-evasion patterns, which factors to a standardized technique, particularly:<\/p>\n
\n
Superior binary safety (Enigma or Themida) is utilized to a good portion of the samples we detected. The filename suffix usually identifies the strategy used (Enigma, Themida, or none).<\/li>\n
Filenames are chosen to carefully resemble these of well-known software program distributors, significantly corporations working within the cybersecurity area.<\/li>\n
Executables impersonate the distributors by having the next attributes, all matching the identical vendor or product:<\/li>\n<\/ul>\n
\u25cb<\/span> fabricated model info,<\/span><\/p>\n
\u25cb<\/span> invalid digital signatures copied from respectable executables, and<\/span><\/p>\n
\u25cb<\/span> icons matching these of the impersonated distributors.<\/span><\/p>\n
Though a small variety of samples deviate from this method, seemingly resulting from inconsistent improvement practices, the overwhelming majority of noticed EDR killers adhere to this sample. In Desk\u00a01, we present how the suffixes work. Later within the blogpost, we clarify how the suffixes are appended to filenames.<\/p>\n
Desk\u00a01. Naming sample of the EDR killers maintained by Gents<\/em><\/p>\n\n\n\n\n\n\n\n\n
Suffix<\/strong><\/td>\n Safety<\/strong><\/td>\n Pretend signature<\/strong><\/td>\n Pretend model info<\/strong><\/td>\n<\/tr>\n<\/thead>\n
1<\/span><\/td>\n Enigma<\/td>\n Sure<\/td>\n Sure<\/td>\n<\/tr>\n
2<\/span><\/td>\n Themida<\/td>\n Sure<\/td>\n Sure<\/td>\n<\/tr>\n
Mild<\/span><\/td>\n None<\/td>\n Sure<\/td>\n Sure<\/td>\n<\/tr>\n
Clear<\/span><\/td>\n None<\/td>\n No<\/td>\n No<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
GentleKiller<\/h3>\n
GentleKiller is by far essentially the most prevalent EDR killer noticed within the Gents ecosystem. On the time of writing, we’re conscious of not less than eight distinct variants, every impersonating a special respectable product and abusing a special weak or malicious driver. Regardless of these surface-level variations, we classify all of those samples underneath the GentleKiller umbrella resulting from a excessive diploma of shared inside traits.<\/p>\n
When abstracting away the impersonation layer and the precise drivers used, the underlying code reveals quite a few structural and behavioral commonalities that strongly counsel the usage of a shared improvement template. This template is reused throughout variants, with solely minimal modifications. The defining traits of the template embrace:<\/p>\n
\n
constant strings throughout variants,<\/li>\n
terminating processes periodically in a loop,<\/li>\n
focusing on a broad set of safety options, and<\/li>\n
using equivalent code obfuscation.<\/li>\n<\/ul>\n
An instance of GentleKiller\u2019s output is illustrated in Determine\u00a01, and a code snippet exhibiting the code obfuscation is depicted in Determine\u00a02.<\/p>\n
$\"Figure$
Determine 1. Output window spawned by GentleKiller<\/em><\/figcaption><\/figure>\n
$\"Figure$
Determine 2. Code obfuscation applied by GentleKiller<\/em><\/figcaption><\/figure>\n
This design prioritizes ease of deployment and operational flexibility for associates, whereas minimizing improvement effort for the operators. It permits the Gents operators to combine abused drivers into their toolset very quickly after an EDR killer PoC is disclosed. This was the case with UnknownKiller<\/a> and PoisonKiller<\/a>, which have been adopted inside a matter of days.<\/p>\n
Whereas some builds don\u2019t goal all of the processes recognized to GentleKiller, the overall set, offered in Desk\u00a02, is constant. We leveraged AI to map the method names to their corresponding distributors, and acknowledge that there is perhaps minor inconsistencies. General, GentleKiller targets greater than 400 processes that the AI mapped to 48 merchandise.<\/p>\n
Desk\u00a02. An entire record of course of names focused by GentleKiller, mapped to their corresponding distributors<\/em><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Vendor<\/strong><\/td>\n Focused processes<\/strong><\/td>\n<\/tr>\n<\/thead>\n
Acronis<\/strong><\/td>\n acronis_agent.exe, BackupAndRecoveryAgent.exe, managementagenthost.exe, mms.exe<\/span><\/td>\n<\/tr>\n
AlienVault<\/strong><\/td>\n alienvault-agent.exe, osqueryd.exe<\/span><\/td>\n<\/tr>\n
Avast<\/strong><\/td>\n afwServ.exe, aswEngSrv.exe, aswidsagent.exe, aswToolsSvc.exe, AvastSvc.exe, AvastUI.exe, avastsvc.exe, avastui.exe, bccavsvc.exe, wsc_proxy.exe<\/span><\/td>\n<\/tr>\n
AVG<\/strong><\/td>\n AVGUI.exe, AVGSvc.exe, avgnt.exe, avgsvca.exe, avgToolsSvc.exe<\/span><\/td>\n<\/tr>\n
Binary Protection<\/strong><\/td>\n BinaryDefenseAgent.exe<\/span><\/td>\n<\/tr>\n
Bitdefender<\/strong><\/td>\n Arrakis3.exe, BDAvScanner.exe, BDFsTray.exe, BDFileServer.exe, BDLived2.exe, BDLogger.exe, BDScheduler.exe, BDStatistics.exe, bdagent.exe, bdemsrv.exe, bdntwrk.exe, bdredline.exe, bdregsvr2.exe, bdservicehost.exe<\/span><\/td>\n<\/tr>\n
Blumira<\/strong><\/td>\n BlumiraAgent.exe<\/span><\/td>\n<\/tr>\n
Bromium<\/strong><\/td>\n BromiumDaemon.exe, BrDifxapi.exe<\/span><\/td>\n<\/tr>\n
Carbon Black<\/strong><\/td>\n cb.exe, cbcomms.exe, cbdefense.exe, carbonsensor.exe, RepMgr.exe<\/span><\/td>\n<\/tr>\n
Cisco Talos<\/strong><\/td>\n cfrutil.exe, CiscoAMPCEFWDriver.exe, cisco_amp_connector.exe, immunet.exe<\/span><\/td>\n<\/tr>\n
CrowdStrike<\/strong><\/td>\n ARWSRVC.EXE, ARCUpdate.exe, CSFalconContainer.exe, CSFalconService.exe, CSFalconUI.exe, csfalcondataprotect.exe, csfalcondaterepair.exe, REPRSVC.EXE<\/span><\/td>\n<\/tr>\n
Cynet<\/strong><\/td>\n CynetEPS.exe, CynetMS.exe, CynetSvc.exe<\/span><\/td>\n<\/tr>\n
Cybereason<\/strong><\/td>\n ActiveConsole.exe, cybereason.exe, CybereasonActiveProbe.exe, CybereasonCR.exe<\/span><\/td>\n<\/tr>\n
Cyvera<\/strong><\/td>\n CyveraConsole.exe, CyveraService.exe, CyvrAgentSvc.exe, CyvrFsFlt.exe, cyvrfsflt.exe<\/span><\/td>\n<\/tr>\n
Cylance\/BlackBerry<\/strong><\/td>\n CylanceSvc.exe<\/span><\/td>\n<\/tr>\n
Darktrace<\/strong><\/td>\n DarktraceTSA.exe<\/span><\/td>\n<\/tr>\n
Deep Intuition<\/strong><\/td>\n DeepInstinct.exe, DeepInstinctService.exe, DIAgentService.exe<\/span><\/td>\n<\/tr>\n
Elastic<\/strong><\/td>\n a2guard.exe, a2service.exe<\/span><\/td>\n<\/tr>\n
ESET<\/strong><\/td>\n eamonm.exe, eamsi.exe, ecls.exe, efwd.exe, egui.exe, eguiProxy.exe, ekrn.exe, ekrnEpfw.exe, ERAAgent.exe, EraAgentSvc.exe<\/span><\/td>\n<\/tr>\n
Fortinet<\/strong><\/td>\n firesvc.exe, firetray.exe, FortiTray.exe, fortiedr.exe, fw.exe<\/span><\/td>\n<\/tr>\n
G DATA<\/strong><\/td>\n GDDServer.exe, QHPISVR.EXE, QUHLPSVC.EXE, SAPISSVC.EXE<\/span><\/td>\n<\/tr>\n
Heimdal<\/strong><\/td>\n HeimdalsecurityAgent.exe<\/span><\/td>\n<\/tr>\n
Huntress<\/strong><\/td>\n HuntressAgent.exe, HuntressRMM.exe<\/span><\/td>\n<\/tr>\n
Kaspersky<\/strong><\/td>\n avp.exe, avpsus.exe, avpui.exe, kavfs.exe, kavfsscs.exe, kavfswh.exe, kavfswp.exe, kavtray.exe, klactprx.exe, klcsldcl.exe, klcsweb.exe, klnagent.exe, klnagchk.exe, klscctl.exe, klserver.exe, klwtblfs.exe, kpf4ss.exe, ksde.exe, ksdeui.exe, vapm.exe<\/span><\/td>\n<\/tr>\n
LogRhythm<\/strong><\/td>\n LogProcessorService.exe<\/span><\/td>\n<\/tr>\n
McAfee\/Trellix<\/strong><\/td>\n AGMService.exe, AGSService.exe, masvc.exe, macmnsvc.exe, McAfeeAgent.exe, mcshield.exe, mfeann.exe, mfevtps.exe, mfetp.exe, mfeepehost.exe, mfefire.exe, mfemactl.exe, mfemacsvc.exe, mfemgr.exe, mfemms.exe, MgntSvc.exe, ModuleCoreService.exe, tepfsvc.exe<\/span><\/td>\n<\/tr>\n
Microsoft Defender<\/strong><\/td>\n MSASCui.exe, MSASCuiL.exe, MpDefenderCoreService.exe, MsMpEng.exe, MsMpSvc.exe, MsSense.exe, msascuil.exe, msseces.exe, NisSrv.exe, nissrv.exe, SecurityHealthService.exe, SecurityHealthSystray.exe, SenseCncProxy.exe, SenseIR.exe, SenseNdr.exe, SenseSampleUploader.exe, smartscreen.exe, windefend.exe<\/span><\/td>\n<\/tr>\n
Morphisec<\/strong><\/td>\n MorphisecService.exe<\/span><\/td>\n<\/tr>\n
Norton\/Symantec<\/strong><\/td>\n ccApp.exe, ccSvcHst.exe, ccsvchst.exe, ns.exe, nsservice.exe, nortonsecurity.exe, rtvscan.exe, SepMasterService.exe, sepWscSvc64.exe, smc.exe, SmcGui.exe, snac.exe, SymCorpUI.exe, SymWSC.exe<\/span><\/td>\n<\/tr>\n
OSSEC\/Wazuh<\/strong><\/td>\n ossec-agent.exe, wazuh-agent.exe<\/span><\/td>\n<\/tr>\n
Palo Alto Networks (Traps\/Cortex)<\/strong><\/td>\n cortexService.exe, trapsagent.exe, trapsd.exe, Traps.exe<\/span><\/td>\n<\/tr>\n
Panda Safety<\/strong><\/td>\n panda_url_filtering.exe, pavfnsvr.exe, pavsrv.exe, psanhost.exe, PSANHost.EXE, pselamsvc.EXE, PSUAMain.EXE, PSUAService.EXE, pangps.exe<\/span><\/td>\n<\/tr>\n
Qualys<\/strong><\/td>\n qualys-cloud-agent.exe, QualysAgent.exe<\/span><\/td>\n<\/tr>\n
Rapid7<\/strong><\/td>\n ir_agent.exe, rapid7_endpoint.exe<\/span><\/td>\n<\/tr>\n
Crimson Canary<\/strong><\/td>\n RedCanaryAgent.exe<\/span><\/td>\n<\/tr>\n
Sangfor<\/strong><\/td>\n CSAAgent.exe, CSAService.exe, SangforAgent.exe, SangforCSA.exe, SangforEDR.exe, SangforInterface.exe, SangforMonitor.exe, SangforProtect.exe, SangforService.exe, SangforTray.exe, SangforUD.exe<\/span><\/td>\n<\/tr>\n
SentinelOne<\/strong><\/td>\n Sentinel.exe, SentinelAgent.exe, SentinelAgentWorker.exe, SentinelCtl.exe, SentinelHelperService.exe, SentinelMemoryScanner.exe, SentinelPowerShellExtension.exe, SentinelRanger.exe, SentinelServiceHost.exe, SentinelStaticEngine.exe, SentinelStaticEngineScanner.exe, SentinelUI.exe<\/span><\/td>\n<\/tr>\n
SonicWall<\/strong><\/td>\n SonicWallClientProtectionService.exe, swc_service.exe<\/span><\/td>\n<\/tr>\n
Sophos<\/strong><\/td>\n hmpalert.exe, McsAgent.exe, McsClient.exe, SavApi.exe, SAVAdminService.exe, SAVService.exe, SEDService.exe, SophosADSyncService.exe, SophosClean.exe, SophosCleanM64.exe, SophosFIMService.exe, SophosFS.exe, SophosHealth.exe, SophosLiveQueryService.exe, SophosMTR.exe, SophosMTRExtension.exe, SophosNetFilter.exe, SophosNtpService.exe, SophosOsquery.exe, SophosOsqueryExtension.exe, Sophos.PolicyEvaluation.Service.exe, SophosSafestore64.exe, SophosUI.exe, SophosUpdateMgr.exe, sophosav.exe, sophossps.exe, SSPService.exe<\/span><\/td>\n<\/tr>\n
Tanium<\/strong><\/td>\n TaniumClient.exe, TaniumCX.exe, tanclient.exe<\/span><\/td>\n<\/tr>\n
ThreatLocker<\/strong><\/td>\n ThreatLockerConsent.exe, threatlockerservice.exe, threatlockertray.exe<\/span><\/td>\n<\/tr>\n
TrendAI<\/strong><\/td>\n coreFrameworkHost.exe, coreServiceShell.exe, NTRTScan.exe, ntrtscan.exe, Ntrtscan.exe, OfcService.exe, ofcDdaSvr.exe, PccNTMon.exe, PccNt.exe, TISafe.exe, TISafeSvc.exe, TmCCSF.exe, tmicAgentSetting.exe, TMBMSRV.exe, Tmbmsrv.exe, tm_netsrv.exe, TmListen.exe, tmntsrv.exe, TmPfw.exe, tmproxy.exe, TmProxy.exe, TmPreFilter.exe, TmSSClient.exe, TmsaInstance64.exe, TmWscSvc.exe, VOneAgentConsole.exe, VOneAgentConsoleTray.exe<\/span><\/td>\n<\/tr>\n
Uptycs<\/strong><\/td>\n VectorAgent.exe, UptycsAgent.exe<\/span><\/td>\n<\/tr>\n
Varonis<\/strong><\/td>\n DatAdvantage.exe, VaronisAgent.exe<\/span><\/td>\n<\/tr>\n
WatchGuard<\/strong><\/td>\n wlcsservice.exe<\/span><\/td>\n<\/tr>\n
Webroot<\/strong><\/td>\n WRSA.exe, WRSkyClient.exe, WRSVC.exe, wrsa.exe<\/span><\/td>\n<\/tr>\n
Home windows Sysinternals<\/strong><\/td>\n Sysmon.exe, Sysmon64.exe<\/span><\/td>\n<\/tr>\n
Zscaler<\/strong><\/td>\n zlclient.exe<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
GentleKiller variants<\/h3>\n
Every GentleKiller variant impersonates a special product and abuses a special malicious or weak driver. Desk\u00a03 supplies a listing of the eight GentleKiller variants we have now noticed to this point. The <\/span> refers back to the naming sample defined in Desk\u00a01. Drivers\u2019 filenames check with how GentleKiller drops them to disk.<\/p>\n
Desk\u00a03. Record of GentleKiller variants<\/em><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
Variant title<\/strong><\/td>\n Filenames<\/strong><\/td>\n Abused driver<\/strong><\/td>\n<\/tr>\n<\/thead>\n
Kaspersky<\/strong><\/td>\n Kasp.exe<\/suffix><\/span><\/td>\n eb.sys<\/span>, a rootkit (PoC<\/a>)<\/td>\n<\/tr>\n
FACEIT Anti-Cheat<\/strong><\/td>\n FaceIT.exe<\/suffix><\/span><\/td>\n nseckrnl.sys<\/span>, NSecsoft NSecKrnl driver (PoC<\/a>)<\/td>\n<\/tr>\n
Valorant<\/strong><\/td>\n Valorant.exe<\/suffix><\/span><\/td>\n GameDriverX64.sys<\/span>, an anti-cheat driver (PoC<\/a>)<\/td>\n<\/tr>\n
Javelin<\/strong><\/td>\n EAAntiCheat.exe<\/suffix><\/span>
EASolo.exe<\/suffix><\/span><\/td>\n stpm_(outdated|new).sys<\/span>, two weak ProcessMonitor Driver samples by Safetica (PoC<\/a>)<\/td>\n<\/tr>\n
WatchDog<\/strong><\/td>\n BitD.exe<\/suffix><\/span><\/td>\n dmx.sys<\/span>, Zemana\u2019s WatchDog Antimalware Driver (PoC<\/a>)<\/td>\n<\/tr>\n
Community Blocker<\/strong><\/td>\n MB.exe<\/suffix><\/span><\/td>\n 360netmon_wfp.sys<\/span>, a weak driver by Qihoo 360 Expertise (PoC<\/a>)<\/td>\n<\/tr>\n
Cleaner<\/strong><\/td>\n Deletor.exe<\/span><\/td>\n IMFForceDelete<\/span>, IObit\u2019s IMF ForceDelete filter driver (PoC<\/a>); the driving force is dropped with out the trailing .sys<\/span> extension<\/td>\n<\/tr>\n
G11<\/strong><\/td>\n G11.exe<\/suffix><\/span>
Symantec.exe<\/suffix><\/span><\/td>\n PoisonX, a rootkit (PoC<\/a>)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Third-party EDR killers<\/h2>\n
Other than the internally developed GentleKiller, Gents has integrated a number of third-party options into its suite, summarized in Desk\u00a04 and described within the following sections. The <\/span> refers back to the naming sample defined in Desk\u00a01. Driver filenames check with how the related EDR killers drop them to disk.<\/p>\n
Desk\u00a04. Record of third-party EDR killers provided by Gents<\/em><\/p>\n\n\n\n\n\n\n\n
ESET title for the EDR killer<\/strong><\/td>\n Filenames<\/strong><\/td>\n Abused driver<\/strong><\/td>\n<\/tr>\n<\/thead>\n
HexKiller<\/strong><\/td>\n Avast.exe<\/suffix><\/span><\/td>\n googleApiUtil64.sys<\/span>, Baidu Antivirus BdApi driver<\/td>\n<\/tr>\n
ThrottleBlood<\/strong><\/td>\n Despatched.exe<\/suffix><\/span><\/td>\n ThrottleBlood.sys<\/span>, driver by TechPowerUp LLC<\/td>\n<\/tr>\n
HavocKiller<\/strong><\/td>\n HwAudKiller.exe<\/span>
Sophos.exe<\/suffix><\/span><\/td>\n havoc.sys<\/span>, Huawei Audio driver<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
HexKiller<\/h4>\n
HexKiller is an EDR killer that we beforehand assessed as being unique to the Warlock gang. Due to this fact, its look inside Gents intrusions is sudden and noteworthy.<\/p>\n
We discovered HexKiller staged alongside GentleKiller binaries throughout the GentlemenCollection<\/span> listing. However, its presence in Gents intrusions doesn’t, by itself, suggest direct collaboration or operational overlap between the Gents and Warlock gangs. It’s believable that Gents operators obtained HexKiller by oblique means, reminiscent of non-public exchanges, secondary distribution channels, or pattern leaks, with none want for direct interplay with Warlock. We due to this fact don\u2019t think about this to be proof of a deeper relationship between the 2 teams.<\/p>\n
ThrottleBlood<\/h4>\n
This EDR killer has been repeatedly noticed in intrusions carried out by MedusaLocker associates, and, much less regularly, by DragonForce associates. Moreover, it was linked<\/a> to Gents by Development Micro in September 2025.<\/p>\n
At current, we shouldn’t have adequate proof to conclusively decide the origin of ThrottleBlood. In our telemetry, it seems prominently deployed throughout a number of MedusaLocker intrusions and sporadically in DragonForce-related exercise. These incidents present little operational overlap past the usage of ThrottleBlood itself. One doable rationalization is that ThrottleBlood is commercially distributed on underground markets, or alternatively a software developed by MedusaLocker operators and shared with their associates, a few of whom may have ties to DragonForce.<\/p>\n
Neither speculation, nonetheless, totally explains how a ThrottleBlood pattern appeared in Gents\u2019s possession. In consequence, we can not rule out the opportunity of Gents buying the software by it leaking past the initially meant context. What we state with excessive confidence, nonetheless, is that Gents didn’t develop this EDR killer in-house.<\/p>\n
HavocKiller<\/h4>\n
HavocKiller is the ultimate addition to Gents\u2019s EDR-killer arsenal. Whereas the software was publicly disclosed<\/a> by Huntress on March 19^{th<\/sup>, 2026, ESET telemetry confirms its use in real-world intrusions relationship again to not less than January 23^{rd<\/sup>, 2026, indicating that it had been operational for weeks previous to public reporting. We will additionally corroborate Huntress\u2019s evaluation concerning its goal: in all instances noticed by ESET, the deployment of HavocKiller was a part of ransomware-related exercise.<\/p>\n}}
Primarily based on its technical traits, we assess that HavocKiller shouldn’t be developed by the Gents operators themselves, however as a substitute was obtained by exterior means. Though the samples have been staged throughout the GentlemenCollection<\/span> listing and Gents\u2019s commonplace set of protection evasion methods was utilized to them, the underlying implementation differs considerably from GentleKiller. This strongly means that HavocKiller represents a third-party EDR killer that was tailored operationally, however its structure doesn’t match into Gents\u2019s framework.<\/p>\n
OxideHarvest<\/h2>\n
We additionally detected a number of deployments of a software we named OxideHarvest, a credential stealer written in Rust. Since Rust shouldn’t be the programming language of selection for Gents, we don’t attribute the software to the group. Nevertheless, as Verify Level famous<\/a>, a Gents affiliate named quant<\/span> maintains a software known as buildx641<\/span>, whose naming and performance instantly reminded us of OxideHarvest. Certainly, after additional investigation, we discovered an OxideHarvest pattern named buildx641.exe<\/span> uploaded to VirusTotal<\/a>; we conclude that buildx641 and OxideHarvest are the identical software.<\/p>\n
OxideHarvest comes wrapped inside totally different packers, usually mimicking respectable software program in model info and icon (related, however not equivalent, to what Gents does with GentleKiller). The protected payload is a straightforward, easy credential stealer. To operate, OxideHarvest requires the consumer to specify the record of hosts (-i<\/span>), username (-u<\/span>), password (-p<\/span>), variety of threads (-t<\/span>), and an output file (-o<\/span>) as command line choices. The software then makes use of the provided credentials to log into the required hosts (handed as a newline-delimited textual content file), employs multithreading, and exfiltrates credentials into the provided output file. Determine\u00a09 reveals the results of the –help<\/span> command of OxideHarvest, and Desk\u00a05 reveals its configuration dictating which credentials are focused.<\/p>\n
$\"Figure$
Determine 3. The assistance of OxideHarvest<\/em><\/figcaption><\/figure>\n
Desk\u00a05. Embedded configuration of OxideHarvest<\/em><\/p>\n
{\n \"chronium_browsers\": [\n [\n \"Google Chrome\",\n \"GoogleChromeUser Data\",\n true\n ],\n [\n \"Google Chrome Beta\",\n \"GoogleChrome BetaUser Data\",\n true\n ],\n [\n \"ChromeBeta\",\n \"GoogleChrome SxSUser Data\",\n true\n ],\n [\n \"Chromium\",\n \"ChromiumUser Data\",\n true\n ],\n [\n \"Microsoft Edge\",\n \"MicrosoftEdgeUser Data\",\n true\n ],\n [\n \"Torch\",\n \"TorchUser Data\",\n true\n ],\n [\n \"Comodo\",\n \"ComodoDragonUser Data\",\n true\n ],\n [\n \"Nichrome\",\n \"NichromeUser Data\",\n true\n ],\n [\n \"Maxthon5\",\n \"Maxthon5Users\",\n true\n ],\n [\n \"Epic Privacy Browser\",\n \"Epic Privacy BrowserUser Data\",\n true\n ],\n [\n \"Vivaldi\",\n \"VivaldiUser Data\",\n true\n ],\n [\n \"QIP\",\n \"QIP SurfUser Data\",\n true\n ],\n [\n \"Cent\",\n \"CentBrowserUser Data\",\n true\n ],\n [\n \"Elements\",\n \"Elements BrowserUser Data\",\n true\n ],\n [\n \"TorBro\",\n \"TorBroProfile\",\n true\n ],\n [\n \"CryptoTab\",\n \"CryptoTab BrowserUser Data\",\n true\n ],\n [\n \"Brave\",\n \"BraveSoftwareBrave-BrowserUser Data\",\n true\n ],\n [\n \"Opera\",\n \"Opera SoftwareOpera Stable\",\n false\n ],\n [\n \"OperaGX\",\n \"Opera SoftwareOpera GX Stable\",\n false\n ],\n [\n \"Opera Neon\",\n \"Opera SoftwareOpera NeonUser Data\",\n false\n ]\n ],\n \"gecko_browsers\": [\n [\n \"Mozila Firefox\",\n \"MozillaFirefoxProfiles\",\n false\n ],\n [\n \"Slim\",\n \"FlashPeakSlimBrowserProfiles\",\n false\n ],\n [\n \"PaleMoon\",\n \"Moonchild ProductionsPale MoonProfiles\",\n false\n ],\n [\n \"Waterfox\",\n \"WaterfoxProfiles\",\n false\n ],\n [\n \"Cyberfox\",\n \"8pecxstudiosCyberfoxProfiles\",\n false\n ],\n [\n \"BlackHawk\",\n \"NETGATE TechnologiesBlackHawkProfiles\",\n false\n ],\n [\n \"IceCat\",\n \"MozillaicecatProfiles\",\n false\n ],\n [\n \"KMeleon\",\n \"K-Meleon\",\n false\n ]\n ]\n}<\/code><\/pre>\nConclusion<\/h2>\nGents demonstrates an attention-grabbing method: operator-managed EDR killers, prepared to make use of by associates. Whereas most ransomware gangs proceed to delegate EDR killing to associates, Gents has chosen to centralize this operate by providing associates a ready-to-use, standardized EDR-killer suite. This resolution makes Gents a sexy operator for associates because it materially lowers the entry barrier for them, making their job consequently simpler.<\/p>\n This mannequin differs even from the few recognized exceptions within the ecosystem. Within the case of RansomHub, the operators invested in a single EDR killer, EDRKillShifter, developed totally in-house. Gents, in contrast, maintains a various portfolio of EDR killers, mixing authentic improvement (GentleKiller) with quickly tailored third-party or publicly disclosed tooling (HexKiller, ThrottleBlood, and HavocKiller). The constant software of protection evasion methods throughout these instruments additional obscures and complicates easy attribution when samples are noticed in isolation.<\/p>\n As a result of EDR-killer methods proceed to commoditize and flow into throughout underground communities, this blogpost underscores the need of incident-level investigation and evaluation. With out such context, Gents\u2019s EDR killers are prone to be misattributed, or not attributed in any respect, masking the true extent of this operator\u2019s involvement. Due to our steady perception into Gents intrusions, we have been in a position to present safety in opposition to the group\u2019s assaults months earlier than the just lately leaked knowledge confirmed our high-confidence hypotheses on the gang\u2019s EDR-killer suite.<\/p>\n The GentleKiller framework illustrates a deliberate stability between in-house improvement and pragmatic reuse of exterior analysis. Whereas some elements present indicators of rushed implementation or inconsistent polish, the general toolset demonstrates excessive operational effectiveness and tight integration into Gents\u2019s ransomware workflow. The group\u2019s capability to adapt newly printed BYOVD PoCs inside days additional underscores its agility.<\/p>\n From a protection perspective, understanding how GentleKiller works permits defenders to higher design their defensive methods and defend even in opposition to yet-to-be-developed, new additions to Gents\u2019s EDR-killing arsenal.<\/p>\n\nFor any inquiries about our analysis printed on WeLiveSecurity, please contact us at threatintel@eset.com<\/a>.\u00a0<\/em><\/div>\nESET Analysis affords non-public APT intelligence studies and knowledge feeds. For any inquiries about this service, go to the ESET Menace Intelligence<\/a> web page.<\/em><\/div>\n<\/blockquote>\nIoCs<\/h2>\n Information<\/h3>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nSHA-1<\/strong><\/td>\n Filename<\/strong><\/td>\n Detection<\/strong><\/td>\n Description<\/strong><\/td>\n<\/tr>\n<\/thead>\n 8AE6BD18B129061F63642531F1B684CF0383C75D<\/span><\/td>\n Kasps.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (Kaspersky variant).<\/td>\n<\/tr>\n BA914FE77B177B45799403B16DD14765C510A074<\/span><\/td>\n eb.sys<\/span><\/td>\n Win64\/Agent.ITG<\/td>\n A customized rootkit utilized by the Kaspersky variant of GentleKiller.<\/td>\n<\/tr>\n D605994FC72A2BB59B5CFB1624A1B9170ECA73A2<\/span><\/td>\n FaceIT1.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (FACEIT Anti-Cheat variant, Enigma-protected).<\/td>\n<\/tr>\n B0B912A3FD1C05D72080848EC4C92880004021A1<\/span><\/td>\n nseckrnl.sys<\/span><\/td>\n Win64\/VulnDriver.NSecsoft.A<\/td>\n NSecsoft NSecKrnl driver abused by the FACEIT Anti-Cheat variant of GentleKiller.<\/td>\n<\/tr>\n 5AA3124E5C4921E5EDFC60133B5D71DA21B07DA3<\/span><\/td>\n Valorant2.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (Valorant variant, Themida-protected).<\/td>\n<\/tr>\n 7556AE58C215B8245A43F764F0676C7A8F0FDD1A<\/span><\/td>\n vgk.sys<\/span><\/td>\n Win64\/VulnDriver.PerfectWorld.A<\/td>\n Tower of Fantasy AntiCheat driver abused by the Valorant variant of GentleKiller.<\/td>\n<\/tr>\n 331879F5EEC8892BBD896F90BDBB1BAD0BF63BD6<\/span><\/td>\n EASolo2Light.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (Javelin variant abusing Safetica\u2019s newer driver).<\/td>\n<\/tr>\n F11AEBCCB9A86A7E2E653F90BAEC697F233C255F<\/span><\/td>\n EASOLO1clear.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (Javelin variant abusing Safetica\u2019s older driver).<\/td>\n<\/tr>\n EF9CD06683159397F099CAA244E94E6EAAD96EBA<\/span><\/td>\n EAAntiCheatLight.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (Javelin variant abusing each drivers).<\/td>\n<\/tr>\n 711EF221526997039E804A18DB9647C91680BBE2<\/span><\/td>\n stpm_old.sys<\/span><\/td>\n Win64\/VulnDriver.Safetica.A<\/td>\n Safetica\u2019s Course of Monitor Driver (older) abused by the Javelin variant of GentleKiller.<\/td>\n<\/tr>\n 68FEC379F2AE76C3D2CE913F7BE650CEA1D06990<\/span><\/td>\n stpm_new.sys<\/span><\/td>\n Win64\/VulnDriver.Safetica.H<\/td>\n Safetica\u2019s Course of Monitor Driver (newer) abused by the Javelin variant of GentleKiller.<\/td>\n<\/tr>\n A11EE9CDC59E5CAA59AEFD27B30D104F3AD68E62<\/span><\/td>\n BitD1.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (WatchDog variant, Themida-protected).<\/td>\n<\/tr>\n 96F0DBF52AED0AFD43E44500116B04B674F7358E<\/span><\/td>\n dmx.sys<\/span><\/td>\n Win64\/VulnDriver.WatchDogDev.C<\/td>\n Zemana\u2019s WatchDog Antimalware Driver abused by the WatchDog variant of GentleKiller.<\/td>\n<\/tr>\n 2F86898528C6CAB3540C486A9BFAA0C029B73950<\/span><\/td>\n MB2.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (Community Blocker variant, Themida-protected).<\/td>\n<\/tr>\n 9AD51AD97C01E97AB59214116740785E0F6320A8<\/span><\/td>\n 360netmon_wfp.sys<\/span><\/td>\n Win64\/VulnDriver.Qihoo360.A<\/td>\n 360netmon.sys driver abused by the Community Blocker variant of GentleKiller.<\/td>\n<\/tr>\n A19117175DBC9BA4D23B5DCE8415E299A2E32192<\/span><\/td>\n Deletor.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (Cleaner variant).<\/td>\n<\/tr>\n 12500F6C87CE62712A0ED6652C57468D15C14223<\/span><\/td>\n IMFForceDelete<\/span><\/td>\n Win64\/VulnDriver.IObit.D.gen<\/td>\n IMF ForceDelete filter driver abused by the Cleaner variant of GentleKiller.<\/td>\n<\/tr>\n D29670E684E40DDC89B47010C37CBC96737035B6<\/span><\/td>\n Symantec.exe<\/span><\/td>\n Win64\/KillAV.EA<\/td>\n GentleKiller (G11 variant).<\/td>\n<\/tr>\n 56BEE9DF5833A637F5C54D5911DF98B0812FE643<\/span><\/td>\n G11.sys<\/span><\/td>\n Win64\/Agent.IYQ<\/td>\n PoisonX rootkit utilized by the G11 variant of GentleKiller.<\/td>\n<\/tr>\n CF4D74DF17A91B4A36A2911B22AFEC5D8FA93A01<\/span><\/td>\n Avast.exe<\/span><\/td>\n Win32\/KillAV.NVL<\/td>\n HexKiller integrated into Gents modus operandi by including the evasion layer.<\/td>\n<\/tr>\n EC296F9501AD71E430810CB5CDC38D954D4BA536<\/span><\/td>\n googleApiUtil64.sys<\/span><\/td>\n Win64\/VulnDriver.Baidu.B<\/td>\n Baidu Antivirus BdApi driver abused by HexKiller.<\/td>\n<\/tr>\n 7131B377E96016DC1911020C9F95B1B4D042D7B4<\/span><\/td>\n Despatched.exe<\/span><\/td>\n Win64\/KillAV.AT<\/td>\n ThrottleBlood integrated into Gents modus operandi by including the evasion layer.<\/td>\n<\/tr>\n 82ED942A52CDCF120A8919730E00BA37619661A3<\/span><\/td>\n ThrottleBlood.sys<\/span><\/td>\n Win64\/VulnDriver.GPUZ.B<\/td>\n ThrottleStop.sys driver abused by ThrottleBlood.<\/td>\n<\/tr>\n F0537CBB773AE12100B36731E7C39F5A9D852B14<\/span><\/td>\n Sophos.exe<\/span><\/td>\n Win64\/KillAV.DE<\/td>\n HavocKiller integrated into Gents modus operandi by including the evasion layer.<\/td>\n<\/tr>\n 1FA071303FB846308571E64727501FB98B1C2BE6<\/span><\/td>\n havoc.sys<\/span><\/td>\n Win64\/VulnDriver.Huawei.D<\/td>\n Weak driver abused by HavocKiller.<\/td>\n<\/tr>\n A5CF917EC4A7DFBDFA43621398604805D860C718<\/span><\/span><\/td>\n buildx641.exe<\/span><\/td>\n Win64\/Spy.Agent.AGC<\/td>\n OxideHarvest.<\/td>\n<\/tr>\n D4B19141102015D436321E6F26976E98183CFD27<\/span><\/td>\n buildx64.exe<\/span><\/td>\n Win64\/Spy.Agent.AGC<\/td>\n OxideHarvest.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nMITRE ATT&CK methods<\/h2>\nThis desk was constructed utilizing model 19 <\/em><\/a>of the MITRE ATT&CK framework.<\/p>\n\n\n\n\n\n\n\n\n\n\n\nTactic<\/strong><\/td>\n ID<\/strong><\/td>\n Identify<\/strong><\/td>\n Description<\/strong><\/td>\n<\/tr>\n<\/thead>\n Execution<\/strong><\/td>\n T1059.003<\/a><\/td>\n Command and Scripting Interpreter: Home windows Command Shell<\/td>\n GentleKiller and associated instruments are console-based executables that run visibly and emit debug strings throughout execution.<\/td>\n<\/tr>\n T1106<\/a><\/td>\n Native API<\/td>\n Person-mode elements work together straight with kernel drivers through DeviceIoControl<\/a> and different native Home windows APIs to carry out privileged actions.<\/td>\n<\/tr>\n Persistence<\/strong><\/td>\n T1543.003<\/a><\/td>\n Create or Modify System Course of: Home windows Service<\/td>\n The EDR killers set up and begin weak or malicious drivers as providers previous to exploitation.<\/td>\n<\/tr>\n Stealth<\/strong><\/td>\n T1036<\/a><\/td>\n Masquerading<\/td>\n Gents\u2019s EDR killers are protected by impersonating respectable distributors by filenames, model info, icons, and copied digital certificates.<\/td>\n<\/tr>\n T1036.001<\/a><\/td>\n Masquerading: Invalid Code Signature<\/td>\n The safety utilized to Gents\u2019s EDR killers provides an invalid code signature as a part of the impersonation technique.<\/td>\n<\/tr>\n T1027<\/a><\/td>\n Obfuscated Information or Data<\/td>\n Some executables are protected with packers (e.g., Enigma, Themida) and customized control-flow obfuscation.<\/td>\n<\/tr>\n Protection Impairment<\/strong><\/td>\n T1685<\/a><\/td>\n Disable or Modify Instruments<\/td>\n GentleKiller and different EDR killers that Gents is in possession of goal to bypass safety merchandise reminiscent of EDRs.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/a><\/p>\n<\/div>\n\n","protected":false},"excerpt":{"rendered":" ESET researchers analyzed the sturdy EDR-killing toolset of the ransomware-as-a-service gang Gents. For the reason that starting of 2026, Gents has emerged as one of the crucial lively gangs within the ransomware ecosystem. The group distinguishes itself by a mature, operator-maintained set of endpoint detection and response (EDR) killers, i.e., instruments for disrupting safety software […]<\/p>\n","protected":false},"author":2,"featured_media":15905,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[58],"tags":[628,635,9478,4620],"class_list":["post-15903","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cybersecurity","tag-edr","tag-framework","tag-gentlemens","tag-killer"],"_links":{"self":[{"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/posts\/15903","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=15903"}],"version-history":[{"count":1,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/posts\/15903\/revisions"}],"predecessor-version":[{"id":15904,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/posts\/15903\/revisions\/15904"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/media\/15905"}],"wp:attachment":[{"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=15903"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=15903"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=15903"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}