Vietnam Newsroom & Threat Intelligence
Evidence first. Intelligence that matters.
NOTEDo not attribute a ransomware family from a file extension or a single ransom note.Vietnam time · UTC+7
Technical analysis

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)

A chip and an evidence folder on an ivory background, representing review of an unverified claim.
The NVIDIA claim is being assessed against available evidence. Editorial illustration with the original TungTEK signature and an article QR.
Not independently verified

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]

Evidence scope on 19 November 2026
ItemReported observationLimit
NVIDIA listingTracking sources recorded it on 18 November.Publication dates the claim. Initial access time is unknown.
Allegedly stolen dataThe listing threatens disclosure.The reviewed sources show no sample, file tree or volume for validation.
NVIDIA internal systemsThe 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 partnerMentioned in the NVIDIA response relayed by reporting.The partner’s identity and the access path remain unresolved.
28 NovemberThe 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]

Relevant milestones
DateEvent and source
Mid-2025The Gentlemen emerged and opened its RaaS to affiliates in September, according to Microsoft. [4]
May 2026Internal communications were leaked. Check Point examined operations and targeting. [5]
2 Oct 2026Vietnam’s Ministry of Public Security issued prevention guidance. [10]
6 Oct 2026Ransomnews recorded Jentech’s listing with a claim exceeding 9 TB. [2]
26–27 Oct 2026Vietnam Airlines and FPT Software appeared in the DLS records Ransomware.VN analyzed on 28 October. [9]
18 Nov 2026NVIDIA was listed, with no samples in the reported entry. [1, 2]
19 Nov 2026Ransomware.VN reviewed the draft, technical reports and source availability for publication.
28 Nov 2026The 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]

A data-resource block stands among separate partner platforms, with a small credential tile near one edge.
Separate platforms illustrate access boundaries to examine between an enterprise and its partners. The access path in the NVIDIA claim remains unresolved.

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]

Hypotheses and discriminating evidence
HypothesisEvidence to examine
NVIDIA-related files held by a partnerRepository ownership, file metadata, project identifiers and data-export logs.
Reused or overstated older dataCreation and modification times, hashes and overlap with previously lawfully documented material.
Direct access and exfiltration from NVIDIAResource access logs, abused identities or tokens and transfer records.
Host impact or encryptionProcess 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.

Names and platforms
ComponentResearch scope
Operator groupMITRE ATT&CK G1058. Associated tracking names include Microsoft’s Storm-2697 and Sophos GOLD SHERWOOD. [4, 6, 7]
Operating modelRansomware-as-a-Service. Operators supply tooling and affiliates perform intrusions. [4, 5]
WindowsMicrosoft analyzed a Go encryptor with self-propagation capabilities. [4]
Other platformsCheck Point describes Linux, NAS and BSD lockers plus a C-based ESXi locker. Match analysis to the actual sample and platform. [12]
ExtortionStolen 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.

A network gateway, an application server and backup layers occupy separate areas.
Correlate evidence across access gateways, host privileges and backup administration. Conceptual illustration.

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]

Reference hunting matrix
BehaviorTelemetry to correlateATT&CK reference
Public service exploitation or valid account abuseEdge-device, VPN and identity-provider logs, plus configuration changes.T1190, T1078
Defense impairmentEDR, new drivers or services, tamper events and policy changes.T1685
Lateral movement and scheduled executionWindows logons, SMB, admin shares, tasks and remote processes.T1021.002, T1053.005
Evidence clearing or recovery impairmentEvent logs, backup administration, snapshots and retention changes.T1685.005, T1490
Encryption and financial pressureValidated 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]

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]

Observed behavior in the Windows sample
File sizeObserved encryption
Up to 1 MiB, or 0x100000 bytesThe entire file content is encrypted.
Above 1 MiBThree non-contiguous regions are encrypted. Coverage depends on the sample configuration.
FooterIdentification 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]

Recovery assessment on controlled copies
Data typeAssessment focus
MDF, NDF and databasesPages, headers, allocation metadata and page relationships. Check consistency in a separated environment.
VMDK, VHD and VHDXVirtual-disk metadata, intact regions, the filesystem and the application inside the VM.
Backups, NAS volumes and LUNsBackup chains, catalogs, filesystem metadata and surviving independent copies.
ZIP, 7Z, PST and OSTArchive 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.

A RAM module sits above an analysis tray beside a snapshot card containing a key symbol and a separate file.
Memory captured at the relevant time may contain keys for some files in a compatible sample. Each case needs validation.

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]

Conditions to assess
Evidence stateAssessment approach
The locker is active or a live-process dump existsIR coordinates isolation, memory acquisition and impact control under its procedures, recording acquisition time and the process involved.
An earlier process or full-memory dump existsConfirm the process, time window and relevant captured memory.
An EDR forensic snapshot or system dump existsInspect the actual captured contents. A snapshot label alone does not establish key availability.
The host rebooted and no earlier dump existsThe published method provides no route to recover keys from encrypted files alone in this situation.
A different locker platform or variantDemonstrate 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]

A magnifier lies over overlapping evidence cards, with a small red focus point.
Correlate file indicators with process, identity and timing evidence to determine their context.

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]

Sample indicators to retain exactly
TypeReference value
Ransom noteREADME-GENTLEMEN.txt
Microsoft sample extension.umc16h
Footer pattern--eph--<base64>--marker--GENTLEMEN
Wallpapergentlemen.bmp
Environment variableLOCKER_BACKGROUND=1
Microsoft encryptor SHA-25622b38dad7da097ea03aa28d0614164cd25fafeb1383dbc15047e34c8050f6f67

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.

Asset groups in a disclosure scenario
Data categoryAssessment questions
Chip designs, RTL, IP and signing keysWho owns the material, which version is it, is the key valid and which systems trust it?
Firmware, drivers, source code and roadmapsRecency, product scope and access to repositories or release workflows.
Partner records, tokens, accounts and contractsAffected 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]

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]

Actions for a security review
OwnerAction and evidence
Network and identity teamsInventory VPNs, firewalls, public management interfaces and versions. Review privileges, MFA, sessions and unscheduled changes.
SOC and platform teamsCorrelate EDR, driver, task, service and ESXi/vCenter/NAS administration logs. Normalize time and record telemetry gaps and retention limits.
Backup and recovery teamsSeparate backup administration, verify retention and offline or immutable copies, and restore representative SQL and VM workloads in isolation.
Data owners and partner managementInventory shared documents, service accounts, tokens, access rights and offboarding revocation.
Incident response teamPrepare 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]

NVIDIAThe GentlemenStorm-2697Threat IntelligenceSupply ChainRansomware RecoveryDecryptor
[1] Cybernews · Nvidia ransom demand by The Gentlemen19/11/2026 · Reporter observation of the claim and the absence of public supporting evidence.
[2] Ransomnews · The Gentlemen list NVIDIA weeks after supplier Jentech18/11/2026 · DLS observations, listing dates, partner claims and counts under Ransomnews methodology.
[3] Candid Dragon · NVIDIA ransomware claim chatter check18–19/11/2026 · Secondary attribution of NVIDIA comments to PCMag. The original PCMag report was unavailable during this review.
[4] Microsoft Threat Intelligence · The Gentlemen ransomware Dissecting a self-propagating Go encryptor28/05/2026 · Windows encryptor analysis, propagation, encryption and IOCs, separate from the NVIDIA claim.
[5] Check Point · When the Ransomware Gang Gets Hacked05/2026 · Leaked operator records, organizational structure and subsequent targeting of victim customers.
[6] MITRE ATT&CK · The Gentlemen G1058Reference · Group identity and the associated names Storm-2697 and GOLD SHERWOOD.
[7] Sophos CTU · Ungentlemanly behavior01/09/2026 · Observed post-compromise behavior and ransomware deployment timing.
[8] ESET · Killing me gently Inside Gentlemen’s EDR killer framework06/2026 · GentleKiller and driver abuse to impair endpoint protection.
[9] Ransomware.VN · Vietnam Airlines và FPT Software trong dữ liệu DLS28/10/2026 · Earlier editorial record, including the FPT response recorded at that time. The old statement URL now redirects to the FPT Software homepage.
[10] Bộ Công an · Cảnh báo nguy cơ từ mã độc tống tiền The Gentlemen02/10/2026 · General ransomware prevention guidance for Vietnamese organizations.
[11] FPT Software · Collaboration with NVIDIA on AI and Cloud23/04/2024 · Corporate partnership announcement, separate from the 2026 security claims.
[12] Check Point Research · The Gentlemen and SystemBC20/04/2026 · Platform-specific lockers and behavior in the investigated cases.
[13] Bedrock Safeguard · gentlemen-decryptor READMEReviewed 19 Nov 2026 · Author claims about memory-dump key recovery, the 35-file experiment, limitations and licensing.
[14] NVIDIA · Security Notice March 202201/03/2022 · updated 08/03/2022 · Corporate notice about the 2022 incident and the data categories acknowledged then.
[15] MITRE ATT&CK · The Gentlemen Ransomware S9051Updated 30 Sep 2026 · Software profile and current technique mappings, including T1685 and T1685.005.

Each source's scope and date are recorded separately when available. A citation does not independently verify every assessment.

· 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
N
Ransomware.VN

AI-assisted threat intelligence and technical analysis from public reporting.