NVIDIA named by The Gentlemen and the partner-data hypothesis
An assessment of the NVIDIA claim, partner-held data, The Gentlemen technical research and the conditions for memory-based decryption.
Updated: · Vietnam time (UTC+7)

Sources reviewed on 19 November 2026. The listing and technical research have distinct source scopes. NVIDIA access, data provenance and impact remain independently unverified. The NVIDIA response is relayed through Candid Dragon, which attributes it to PCMag.
Adapted from TUNGTEK’s supplied DOCX with AI-assisted editing and a pre-publication source review. Five editorial illustrations use the original transparent TungTEK PNG. QR codes open the Vietnamese edition.
The Gentlemen listed NVIDIA on its data leak site on 18 November 2026. Ransomnews and Cybernews recorded the listing but described no sample files, file inventory or data volume that would establish the scope of a compromise. As reviewed on 19 November, this remains an independently unverified intrusion claim. [1] [2]
Candid Dragon attributes comments to NVIDIA via PCMag saying the company is investigating an incident that may have affected a third-party partner and has found no indication its own systems or networks were affected. That response is available through a secondary source in this review. This analysis examines data provenance, The Gentlemen’s technical profile and the conditions for memory-based recovery. [3]
What the NVIDIA claim currently establishes
| Item | Reported observation | Limit |
|---|---|---|
| NVIDIA listing | Tracking sources recorded it on 18 November. | Publication dates the claim. Initial access time is unknown. |
| Allegedly stolen data | The listing threatens disclosure. | The reviewed sources show no sample, file tree or volume for validation. |
| NVIDIA internal systems | The response attributed to PCMag reports no indication of an impact. | The response is indirectly sourced. No public forensic record was available in this review. |
| Third-party partner | Mentioned in the NVIDIA response relayed by reporting. | The partner’s identity and the access path remain unresolved. |
| 28 November | The threatened disclosure deadline reported by Ransomnews. | The claiming party controls and can change it. |
The reported listing fields include a corporate description, DATA INFO – SOON and NEGO TOX. These describe presentation and negotiation contact. Validation still requires sample files, metadata or logs with verifiable provenance. [2]
Ransomnews also compares the listing’s Tox identifier with the administrator profile discussed by Check Point. A shared contact can help connect extortion activity to an operational contact point. Identifying the affiliate, its access and the source of that access still requires additional evidence. [2] [5]
Timeline and the scope of each milestone
| Date | Event and source |
|---|---|
| Mid-2025 | The Gentlemen emerged and opened its RaaS to affiliates in September, according to Microsoft. [4] |
| May 2026 | Internal communications were leaked. Check Point examined operations and targeting. [5] |
| 2 Oct 2026 | Vietnam’s Ministry of Public Security issued prevention guidance. [10] |
| 6 Oct 2026 | Ransomnews recorded Jentech’s listing with a claim exceeding 9 TB. [2] |
| 26–27 Oct 2026 | Vietnam Airlines and FPT Software appeared in the DLS records Ransomware.VN analyzed on 28 October. [9] |
| 18 Nov 2026 | NVIDIA was listed, with no samples in the reported entry. [1, 2] |
| 19 Nov 2026 | Ransomware.VN reviewed the draft, technical reports and source availability for publication. |
| 28 Nov 2026 | The threatened disclosure deadline recorded by Ransomnews. [2] |
Listing dates form a publication history for separate records. Their proximity raises questions about shared data, permissions and partners. Establishing a common campaign needs evidence such as identities, intermediary hosts, files and correlated activity times. [2] [9]
The partner-data hypothesis

Jentech Precision Industrial and FPT Software appeared on the same extortion site before NVIDIA, according to Ransomnews. Jentech participates in the components and cooling ecosystem. FPT announced its NVIDIA AI and Cloud collaboration on 23 April 2024. These relationships inform which data each party might legitimately hold. [2] [11]
Ransomware.VN’s 28 October article recorded FPT Software saying it had found no evidence of the related incident and that operations remained normal at that time. The old statement URL now redirects to FPT Software’s homepage, so this article cites the dated editorial record. The third party mentioned in the NVIDIA response remains unidentified. [9]
Check Point describes instances where The Gentlemen used information from a victim to target that victim’s customers. That precedent supports reviewing partner access and shared repositories. A causal link among the Jentech, FPT Software and NVIDIA listings still requires separate evidence. [5]
| Hypothesis | Evidence to examine |
|---|---|
| NVIDIA-related files held by a partner | Repository ownership, file metadata, project identifiers and data-export logs. |
| Reused or overstated older data | Creation and modification times, hashes and overlap with previously lawfully documented material. |
| Direct access and exfiltration from NVIDIA | Resource access logs, abused identities or tokens and transfer records. |
| Host impact or encryption | Process evidence, file changes, confirmed service disruption and the system owner’s findings. |
Assess new evidence through provenance and recency. A drawing naming a customer may reside on a supplier’s system. Correlate storage ownership, permissions and collection records before determining the affected environment.
The Gentlemen profile and activity counts
| Component | Research scope |
|---|---|
| Operator group | MITRE ATT&CK G1058. Associated tracking names include Microsoft’s Storm-2697 and Sophos GOLD SHERWOOD. [4, 6, 7] |
| Operating model | Ransomware-as-a-Service. Operators supply tooling and affiliates perform intrusions. [4, 5] |
| Windows | Microsoft analyzed a Go encryptor with self-propagation capabilities. [4] |
| Other platforms | Check Point describes Linux, NAS and BSD lockers plus a C-based ESXi locker. Match analysis to the actual sample and platform. [12] |
| Extortion | Stolen information and potential encryption-related disruption create pressure in investigated cases. [4, 7] |
Ransomnews reported 1,107 listings in 2026 and 91 cases that year corroborated by public sources under its methodology in its 18 November article. These are different observation sets. Disclosure coverage and confirmation delays affect the counts. They cannot establish an encryption or operational success rate. [2]
Group names, operator identities and locker samples also have distinct scopes. An IOC match starts an investigation. Findings about affiliates, initial access and impact need to be tied to evidence from the actual incident.
Technical behavior to monitor

Sophos observed a consistent post-compromise playbook including privilege escalation, adaptive tools and defense impairment. Some investigated cases deployed ransomware within 24 hours of the first identified post-compromise activity. This interval depends on each investigation’s visibility. [7]
ESET describes at least eight GentleKiller variants and vulnerable or malicious drivers used to impair protection. For SOC teams, correlate driver loading with EDR state changes, service creation and administrative identity activity. [8]
| Behavior | Telemetry to correlate | ATT&CK reference |
|---|---|---|
| Public service exploitation or valid account abuse | Edge-device, VPN and identity-provider logs, plus configuration changes. | T1190, T1078 |
| Defense impairment | EDR, new drivers or services, tamper events and policy changes. | T1685 |
| Lateral movement and scheduled execution | Windows logons, SMB, admin shares, tasks and remote processes. | T1021.002, T1053.005 |
| Evidence clearing or recovery impairment | Event logs, backup administration, snapshots and retention changes. | T1685.005, T1490 |
| Encryption and financial pressure | Validated file changes, ransom notes and availability impact. | T1486, T1657 |
The matrix summarizes researched The Gentlemen behavior for defensive use. Techniques can overlap or occur in different orders. No public technical timeline currently establishes those actions in NVIDIA’s environment. [4] [6] [7] [8] [15]
Partial encryption and intact-data analysis
Microsoft’s Windows sample uses X25519/Curve25519 ECDH and XChaCha20 with a new ephemeral key pair for each file. The ephemeral public key is stored in the footer. Conventional decryption requires the matching operator private key to reconstruct the key material. [4]
| File size | Observed encryption |
|---|---|
| Up to 1 MiB, or 0x100000 bytes | The entire file content is encrypted. |
| Above 1 MiB | Three non-contiguous regions are encrypted. Coverage depends on the sample configuration. |
| Footer | Identification data and the ephemeral public key. Large files also record encryption mode information. |
Intact regions can support structure-aware extraction if the format permits. The result depends on damage to metadata, indexes and essential content. A file that opens still needs application-level consistency and completeness checks. Revalidate the Windows findings for ESXi, Linux or NAS lockers. [4] [12]
| Data type | Assessment focus |
|---|---|
| MDF, NDF and databases | Pages, headers, allocation metadata and page relationships. Check consistency in a separated environment. |
| VMDK, VHD and VHDX | Virtual-disk metadata, intact regions, the filesystem and the application inside the VM. |
| Backups, NAS volumes and LUNs | Backup chains, catalogs, filesystem metadata and surviving independent copies. |
| ZIP, 7Z, PST and OST | Archive metadata, indexes and complete readable records or objects. |
These are format-specific assessment paths. Document the sample, affected regions, objects checked and remaining errors. Preserve originals and work on controlled copies.
When memory-based decryption may apply

Bedrock Safeguard publishes gentlemen-decryptor, which searches a locker process memory dump for residual ephemeral private keys. The README links the issue to heap key material left after use and CWE-244. Its authors report key recovery and decryption of 35 out of 35 files in their own test environment. [13]
The dump must contain the private key for the relevant processed file. Acquisition time, process termination and variant compatibility affect the result. The README also records partial-encryption limitations. Ransomware.VN and TEKLab have not reproduced that experiment during this editorial review. [13]
The reviewed release refuses files larger than 1 MB by default to avoid applying whole-file decryption to regions that are still intact. Verify encryption mode and tool support before testing on copies. [13]
| Evidence state | Assessment approach |
|---|---|
| The locker is active or a live-process dump exists | IR coordinates isolation, memory acquisition and impact control under its procedures, recording acquisition time and the process involved. |
| An earlier process or full-memory dump exists | Confirm the process, time window and relevant captured memory. |
| An EDR forensic snapshot or system dump exists | Inspect the actual captured contents. A snapshot label alone does not establish key availability. |
| The host rebooted and no earlier dump exists | The published method provides no route to recover keys from encrypted files alone in this situation. |
| A different locker platform or variant | Demonstrate compatible file format, key generation and memory handling first. |
Identify the variant, inspect the footer, test key-to-file matching on copies and verify decrypted content. Intact-region analysis can proceed where the format permits. The README currently specifies Business Source License 1.1. Review repository terms before product or service integration. [13]
Reference indicators and correlation

These indicators come from published sample research and can support retrospective queries in authorized investigations. Incident-specific NVIDIA IOCs have not been published in the reviewed sources. [4] [13]
| Type | Reference value |
|---|---|
| Ransom note | README-GENTLEMEN.txt |
| Microsoft sample extension | .umc16h |
| Footer pattern | --eph--<base64>--marker--GENTLEMEN |
| Wallpaper | gentlemen.bmp |
| Environment variable | LOCKER_BACKGROUND=1 |
| Microsoft encryptor SHA-256 | 22b38dad7da097ea03aa28d0614164cd25fafeb1383dbc15047e34c8050f6f67 |
Preserve original observations, collection times, sources and hosts when an indicator matches. Connect presence to execution, permissions and observed effects. Extensions vary across samples, and legitimate research can also introduce a file into an environment.
Assessing potential data impact
| Data category | Assessment questions |
|---|---|
| Chip designs, RTL, IP and signing keys | Who owns the material, which version is it, is the key valid and which systems trust it? |
| Firmware, drivers, source code and roadmaps | Recency, product scope and access to repositories or release workflows. |
| Partner records, tokens, accounts and contracts | Affected customers, credential lifetime and the permissions those credentials carry. |
This is an asset-classification framework for assessing evidence of a disclosure. Those categories have not been confirmed in the NVIDIA claim. Provenance and associated permissions inform credential revocation, software-signing reviews and the scope of investigation.
NVIDIA’s March 2022 notice says it discovered an incident on 23 February 2022 and acknowledged stolen employee credentials and some proprietary information. Lawfully documented historical data is a reference point when assessing whether a later sample is new. Each incident still needs its own evidence record. [14]
Priorities for organizations in Vietnam
The Ministry of Public Security’s 2 October 2026 guidance identifies The Gentlemen as a ransomware prevention concern. Organizations operating virtualization, NAS, SQL and contractor or MSP access should assign each review item an owner and retain evidence of completion. [10]
| Owner | Action and evidence |
|---|---|
| Network and identity teams | Inventory VPNs, firewalls, public management interfaces and versions. Review privileges, MFA, sessions and unscheduled changes. |
| SOC and platform teams | Correlate EDR, driver, task, service and ESXi/vCenter/NAS administration logs. Normalize time and record telemetry gaps and retention limits. |
| Backup and recovery teams | Separate backup administration, verify retention and offline or immutable copies, and restore representative SQL and VM workloads in isolation. |
| Data owners and partner management | Inventory shared documents, service accounts, tokens, access rights and offboarding revocation. |
| Incident response team | Prepare log and appropriate memory acquisition. Record isolation, active-encryption control and evidence handling decisions. |
Developments that could change this assessment include a direct corporate notice, verifiable data provenance, an identified third party and technical evidence of access. The reported 28 November date is a threatened disclosure deadline. Preserve event dates, source dates and the correction history as the evidence changes. [1] [2] [3]
Sources
Each source's scope and date are recorded separately when available. A citation does not independently verify every assessment.
Update history
· Published Vietnamese and English analysis from TUNGTEK’s draft, reviewed technical sources, normalized sample IOCs and added five illustrations with the original signature.
Corrections policy

