Researchers at Check Point have uncovered a fatal design flaw in the VECT 2.0 ransomware that transforms it from a tool for extortion into a destructive data wiper. The bug, present in versions targeting Windows, Linux, and VMware ESXi, causes the irreversible destruction of any file larger than 131,072 bytes (128 KB). Due to a critical error in its encryption logic, the malware fails to save the necessary cryptographic nonces required for decryption, rendering the first 75% of any large file permanently unrecoverable. This means that for virtually all valuable enterprise data—such as databases, backups, and virtual machine disks—paying the ransom is futile. The VECT Ransomware-as-a-Service (RaaS) operation, which partners with the TeamPCP supply chain attack group, has inadvertently created a wiper, highlighting a case of amateurish implementation despite ambitious goals.
VECT 2.0 is a multi-platform ransomware variant distributed through a Ransomware-as-a-Service (RaaS) model. It first appeared on Russian-language cybercrime forums in December 2025. The group gained notoriety by announcing a partnership with TeamPCP, a threat actor known for supply chain attacks, with the stated intent of deploying VECT on systems compromised by TeamPCP.
However, Check Point Research's analysis reveals that the ransomware is fundamentally broken. While it successfully encrypts files, its flawed design ensures that most of the encrypted data cannot be restored.
The catastrophic flaw lies in VECT 2.0's handling of cryptographic nonces during the encryption of large files. A nonce (number used once) is a random value that is essential for the decryption process in modern encryption algorithms.
As a result, only the last 25% of any file larger than 128 KB can be decrypted. The data in the first three-quarters is permanently lost, as the unique keys needed to unlock it are destroyed the moment they are used. This makes VECT 2.0 an accidental wiper, not a functional ransomware.
This maps to the MITRE ATT&CK technique T1485 - Data Destruction, even if unintentional.
The impact on a victim organization is severe, potentially even more so than a standard ransomware attack, because it removes the option of data recovery via ransom payment.
The researchers noted that the ransomware's code was generally of low quality, suggesting that despite its RaaS branding and partnerships, the developers are relatively amateurish.
No specific Indicators of Compromise (IOCs) were mentioned in the source articles.
Halcyon joins Check Point in reporting the VECT 2.0 flaw, with new details on its promotion via BreachForums and the addition of T1105 (Ingress Tool Transfer) to its TTPs.
Deploying behavior-based anti-ransomware and EDR solutions is crucial for detecting and stopping the malicious encryption process before significant damage occurs.
Since data recovery via decryption is impossible, having tested, offline, and immutable backups is the only way to recover from a VECT 2.0 attack.
Using application allowlisting can prevent the initial execution of the ransomware payload if it is not a trusted executable.
Given that VECT 2.0 functions as a destructive wiper, the only viable recovery strategy is restoration from backups. Organizations must maintain a robust and tested backup plan. This includes regular, automated backups of all critical data, including virtual machines, databases, and file servers. Crucially, backups must be isolated from the production network to prevent them from being wiped as well. This can be achieved through physically offline media (tapes), air-gapped systems, or cloud-based immutable storage. Regular, automated testing of the restoration process is non-negotiable to ensure that backups are viable when needed.
Deploy an Endpoint Detection and Response (EDR) solution with advanced anti-ransomware and anti-wiper capabilities. These tools do not rely on signatures but instead monitor for the malicious behaviors characteristic of such attacks. Configure the EDR policy to its most aggressive setting for detecting and blocking processes that perform rapid, mass file I/O operations (reading, encrypting, writing, renaming). This behavioral analysis can stop the VECT 2.0 payload in its tracks before it destroys a significant amount of data. The EDR should be configured to automatically kill the offending process and isolate the infected host from the network to prevent further spread.
The VECT RaaS operation first appears on Russian-language cybercrime forums.
Check Point Research publishes its findings on the destructive flaw in VECT 2.0.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.