New Prinz Eugen ransomware prioritizes recent files for encryption

Security researchers warn of Prinz Eugen, a new Go-based ransomware that targets recently modified files first and leaves no ransom note. The operators appear hands-on, leveraging legitimate RMM tools (e.g., RemotePC) and a backdoor admin account for persistence, with initial access likely from stolen RDP credentials and a manual payload (servertool.exe). It encrypts almost every file (except .prinzeugen) using ChaCha20-Poly1305 with Argon2id-derived keys, deletes originals after encryption, and is not operating as a traditional RaaS; at least five victims have been identified, with more believed affected.

TechLogHub
June 20, 2026
5 min read
0 views

Share Article

New Prinz Eugen ransomware prioritizes recent files for encryption

NEW PRINZ EUGEN RANSOMWARE PRIORITIZES RECENT FILES FOR ENCRYPTION

IntroductionA recently analyzed ransomware operation, named Prinz Eugen, demonstrates a distinctive focus on encrypting the files that were most recently modified. The campaign appears to operate with a hands-on keyboard approach, relying on legitimate remote management tools and living-off-the-land techniques to gain access and maintain persistence. Notably, the threat actor eschews the traditional ransom note and the typical ransomware-as-a-service (RaaS) model, at least for now, opting for direct action rather than affiliate-driven propagation.

Attack Scenario and Initial Access

  • Entry method: The group is believed to gain initial access through stolen remote desktop credentials.
  • Payload deployment: After gaining footholds, attackers manually download and execute a primary payload named servertool.exe.
  • Post-access tools: Investigators observed the use of RemotePC, a legitimate remote monitoring and management (RMM) utility, in combination with a backdoor administrator account to sustain access and persistence.
  • RaaS status: The operation does not appear to function as a traditional RaaS operation, and current information suggests the developers are not actively seeking affiliates.

Scope and Victims

  • Data leaks and encryption: Prinz Eugen operates with a data leak site that currently lists a small number of victims; the site indicates the attackers are engaged in data encryption, exfiltration, or both.
  • Real-world impact: While listed victims are known publicly, researchers acknowledge that additional organizations have been affected beyond those explicitly shown on the site.
  • Notable example: In at least one publicized incident referenced by researchers, a major financial institution faced ransom negotiations that were declined.

Encryption Strategy: How Prinz Eugen Targets Files

  • Priority scheme: The Go-based encryptor targets the most recently modified files first, aiming to maximize disruption by hitting files that are likely to be actively used and business-critical.
  • Tie-break rule: When multiple files share identical timestamps, encryption order is determined alphabetically.
  • Directory traversal: The malware scans directories recursively without a depth limit and without excluding common folders, expanding its reach to broad portions of the file system.
  • File scope: Virtually every file is encrypted, with a single extension exception used to denote encrypted files: .prinzeugen.
  • File scanning visualization: The tool’s scanning routine is designed to process a large portion of the host’s data during the attack window.

Encryption technology and process

  • Cipher and keys: The ransomware uses ChaCha20-Poly1305 encryption with a 32-byte master key and a unique initialization vector for each file.
  • Key derivation: A layered key derivation process relies on Argon2id, SHA-256, and HKDF-SHA256 to strengthen key material.
  • Chunked processing: Files are encrypted in 1 MB chunks, balancing performance and reliability across diverse file sizes.
  • Integrity checks: SHA-256 hashes are used to verify file integrity during and after encryption.
  • Deletion and safety checks: When the --delete flag is used to remove the original file after encryption, the malware checks that the encrypted version remains decryptable before removal.
  • Key destruction: To prevent theft of the encryption key, Prinz Eugen overwrites the key with zeroes, triggers garbage collection to purge memory, and then self-deletes from disk.

Operational footprint and behavior

  • Ransom note absence: The malware does not display a ransom note or alter the desktop background, a deliberate choice believed to reduce forensic traces.
  • Extortion model: Threat researchers note the lack of in-band ransom communications and the likelihood that the actors coordinate extortion communications outside the compromised host (e.g., via email or dark-web portals), complicating automated detection and forensic workflows.
  • Forensic footprint: This approach minimizes artifacts on the endpoint, making automated detection more challenging and extending the window of opportunity for data exfiltration and encryption.

Indicators of Compromise (IoCs) and Observations

  • Go-based encryptor: The tool’s core is a Go-based encryptor that prioritizes recently modified files and practices broad directory traversal.
  • File extension marker: The presence of encrypted files bearing the .prinzeugen extension is a notable marker.
  • Encryption stack: The use of ChaCha20-Poly1305 with a strong, multi-layered key derivation pipeline (Argon2id, SHA-256, HKDF-SHA256) is a defineable technical signature.
  • Access and persistence: The combination of RemotePC usage and a backdoor administrator account creates a persistent foothold within infected environments.
  • Operational tempo: The attacker behavior suggests a deliberate, on-site (hands-on-keyboard) style of operation rather than automated mass propagation.

Victimology and Public Exposure

  • Verified victims: Threat researchers identified at least five victims connected to Prinz Eugen activities.
  • Public data incidents: Documented cases, such as a notable breach at a large financial institution, have involved ransom negotiations that did not proceed favorably for the attackers.
  • Broader impact: While the publicly listed victims provide a snapshot, security researchers emphasize that additional organizations have suffered Prinz Eugen-related incidents that have not yet been fully disclosed.

Defense and Research Context

  • Threatdown analysis: Security researchers conducted a deep dive into the threat’s mechanics, noting its distinct emphasis on recent-file encryption and the absence of typical ransom artifacts on infected hosts.
  • Forensic and detection implications: The combination of rapid file access prioritization, memory-clearing behavior, and a self-deleting footprint poses challenges for conventional endpoint detection and response (EDR) tooling.
  • Community resources: Analysts provide a range of indicators and observations designed to help organizations detect early activity and understand the threat’s tendencies.

Conclusion: What Sets Prinz Eugen Apart

  • Focus on recency: Prinz Eugen’s hallmark is the deliberate prioritization of the most recently modified files, driven by a tactic intended to maximize operational impact and pressure on victims.
  • Minimal host traces: By avoiding ransom notes and leveraging external channels for extortion, the group reduces on-device forensic cues and complicates automated detection.
  • Persistent access, flexible methods: The use of legitimate Remote Monitoring and Management tools, paired with backdoor accounts, demonstrates a pragmatic approach to persistence and later-stage encryption.

Notes on Context and Related Trends

  • The Prinz Eugen operation sits within a broader landscape of targeted encryption campaigns that emphasize speed, precision, and subtle on-host footprints.
  • While this particular campaign has public-facing indicators and a limited victim list, researchers caution that more victims may exist beyond those publicly acknowledged.
  • Ongoing research continues to track changes in tactics, techniques, and procedures as threat actors adapt to defensive measures and public disclosure.

End of post.

Stay Updated

Get the next deep dive in your inbox

Subscribe for product analysis, engineering explainers, and practical guides published on TechLogHub.

See what launched this week

One email a week: new and trending developer tools, fresh comparisons, and what shipped. Unsubscribe in one click.