TeslaCrypt is a Windows ransomware family first observed in early 2015 and widely regarded as one of the major crypto-ransomware threats of that period. It encrypts victim files and demands payment for decryption, targeting common user data such as documents, images, and videos, while also becoming notable for targeting game-related files including saved games and related assets. Over its evolution, TeslaCrypt used multiple victim-facing names and changed encrypted-file extensions and ransom-note formats across versions.
TeslaCrypt was distributed through several common crimeware channels, including malicious email attachments and exploit-kit-driven web compromises. Documented delivery included redirection from compromised or malicious websites to exploit kits such as Angler, Sweet Orange, and Nuclear, including exploitation of Adobe Flash Player vulnerability CVE-2015-0311. It was also delivered in downloader chains, including campaigns where Nemucod JavaScript downloaders retrieved TeslaCrypt payloads from the internet.
The malware established itself on infected systems by copying itself into user-accessible locations and creating autorun persistence. Multiple analyses documented privilege adjustment, deletion of Volume Shadow Copies, anti-analysis checks using COM-related techniques, process termination aimed at administrative and analysis tools, and process-hollowing-style execution in some variants. TeslaCrypt also evolved its internal obfuscation and API-resolution logic over time, with later variants borrowing code patterns associated with the leaked Carberp source.
TeslaCrypt’s cryptographic design changed significantly across versions. Early variants falsely claimed to use RSA-2048 while analyses showed they actually relied on symmetric encryption schemes for file encryption and had implementation weaknesses in key storage or recovery logic. Those weaknesses enabled defenders and researchers to build free decryption tools for affected versions. Later variants strengthened the design, including versions that used elliptic-curve Diffie-Hellman over secp256k1 to protect key material and AES-CBC for file encryption, making recovery without attacker-controlled key material substantially more difficult. By TeslaCrypt 3.x, previously known recovery methods for older variants were no longer effective, and some variants could complete encryption even without live command-and-control connectivity.
TeslaCrypt communicated with attacker infrastructure to register infections, transmit key-related material, and report encryption status. It also used Tor-related infrastructure and tor2web access patterns in some versions. The family was associated with large criminal distribution ecosystems and infrastructure, including the Avalanche fast-flux botnet environment. TeslaCrypt is frequently described as a derivative or successor in style to earlier ransomware such as CryptoLocker and later adopted visual or operational elements resembling CryptoWall.
TeslaCrypt underwent rapid development through 2015 and into 2016, with variants commonly referred to as TeslaCrypt 2.0 and 3.0 introducing notable changes in ransom presentation, key handling, and encrypted-file extensions. The family was eventually discontinued, and its shutdown became a notable milestone in ransomware history after free recovery options had already emerged for many victims of earlier versions.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
1 CVE Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.
In our analysis, the exploit kit delivered a malicious Flash object containing an exploit against CVE-2015-0311. The payload for this exploit was a TeslaCrypt sample. | One of the latest variants is called TeslaCrypt and appears to be a derivative of the original Cryptolocker ransomware.
33 distinct techniques documented for this family, organized by ATT&CK tactic.
This ransomware is usually distributed as an email attachment or through websites that redirect the victim to the Angler Exploit Kit.
TeslaCrypt 2.0.0 does not use key.dat or storage.bin to store data. Instead, it uses the system registry: an install_id value is stored in HKCU\Software\msys\ID, and the following structure is added to HKCU\Software\ <install_id> \data
If the check passes, the real dropper is extracted and executed using a well-known method that makes use of the ZwMap(Unmap)ViewOfSection API functions to unmap the original PE memory image and re-map another image file.
The final unpacked executable locates specific Windows directories such as the Application Data directory, and builds support files like the “key.dat” file, and files to store decryption instructions.
Before TeslaCrypt version 0.4.1, server requests were sent in plaintext; in subsequent versions they were encrypted using the AES-256-CBC algorithm, with a SHA256 hash of a static string from the malicious program’s body used as a key.
the author has also implemented dynamic library and function loading.
Otherwise, it copies the image file to one of the directories, depending on the user account rights. The name of the file is generated randomly and contains 0x0C lower ASCII symbols.
If the check passes, the real dropper is extracted and executed using a well-known method that makes use of the ZwMap(Unmap)ViewOfSection API functions to unmap the original PE memory image and re-map another image file.
Versions 0.2.5 – 0.3.x saved the decryption key... in key.dat. The area containing the key was zeroed out in the file only after completing encryption... In version 0.4.0 ... On completing encryption, the key was overwritten with random bytes rather than zeros
It then executes the newly copied file and removes the original file with this command: {WINDOWS_DIRECTORY}\system32\cmd.exe /c DEL ${PATH_TO_EXE}
Execute the ShellExecuteEx function with one the following commands: wmic.exe shadowcopy delete /noninteractive
the ransomware uses the ShellExecuteEx function with a runas action for this command: {WINDOWS_DIRECTORY}\system32\cmd.exe /c "" ${PATH_TO_EXE}
the ransomware checks if its path to the execution file contains the windir environment variable or CSIDL_MYDOCUMENTS (which depends on the user belonging to the Administrator group).
This thread is responsible for enumerating currently running processes in the operating system by using function EnumProcesses.
starts to enumerate all files of the victim workstation (filtering by extension type, Tesla Crypt supports over 170 different file extensions)
At the same time, all network resources are enumerated recursively using the WNet family functions. The ransomware looks for resources with the type RESOURCETYPE_DISK.
The ransomware encrypts and encodes the data when it communicates with the C&C. It calculates the SHA256 checksum of the decrypted hardcoded string 0324532423723948572379453249857. The received hashsum is used as a key for the AES-CBC-128 encryption algorithm.
Send the new master encryption key to the C&C server through POST request
The ransomware sends packets to the C&C server using HTTP POST requests on the default TCP/80 port
47 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
File hashes (MD5, SHA-1, SHA-256) from samples and reports.
Other indicator types observed in public reporting.
31 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Ransomware family referenced as an example of recognized ransomware strains.
Ransomware family for which AVG provides a decryptor.
A flaw in TeslaCrypt ransomware allows file recovering
Ransomware referenced for comparison because the term DEADBEEF was previously used as a file marker by TeslaCrypt.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.