Connect with us

CyberSecurity

Microsoft Account Lockout Threatens VeraCrypt’s Future for Windows Users

Published

on

Microsoft Account Lockout Threatens VeraCrypt’s Future for Windows Users

The popular open-source encryption tool VeraCrypt faces an existential crisis on Windows. Its lead developer, Mounir Idrassi, has revealed that Microsoft terminated the account he used for years to sign critical Windows drivers and bootloaders. This action, taken without explanation or appeal, could soon prevent millions of users from accessing their fully encrypted systems.

Idrassi, based in Japan, stated he attempted to contact Microsoft but could not reach a human representative. Consequently, he warns that devices using VeraCrypt’s full-disk encryption may become unbootable starting in late June. This situation underscores a critical vulnerability for software that millions rely on for data security.

How Microsoft’s Policy Endangers Encryption Software

At the heart of this crisis is Microsoft’s driver signing requirement. To prevent malware, Windows requires that boot-critical software components carry a valid digital signature from a trusted certificate. Idrassi’s now-terminated account held that authority for VeraCrypt. Building on this, the impending revocation of his certificate means VeraCrypt’s bootloader will fail Microsoft’s security checks, locking users out of their own encrypted operating systems.

For affected users, the immediate risk is not a security flaw but an access barrier. Their data remains encrypted and secure, but the pathway to decrypt and boot the system will be blocked by Windows itself. This creates a paradoxical situation where a security measure designed to protect users instead renders their secure systems inaccessible.

The Broader Implications for Open-Source Development

This incident is not isolated. It highlights a systemic power imbalance where platform gatekeepers like Microsoft and Apple hold unilateral control over software distribution. Earlier this year, developer Paris Buttfield-Addison was locked out of their Apple account, only reinstated after public outcry. Similarly, Idrassi’s case shows how account termination can happen without warning or recourse.

Therefore, the reliance on centralized platforms creates a single point of failure for critical software. VeraCrypt continues to function normally for Linux and macOS users, where distribution models are more decentralized. The problem is uniquely acute for Windows, where Microsoft controls the entire signing ecosystem. This means that even robust, open-source projects live at the mercy of corporate policy changes.

What This Means for VeraCrypt Users

Currently, VeraCrypt installations continue to work. Idrassi has confirmed there are no immediate security issues. However, the clock is ticking. By late June, when Microsoft revokes the existing certificate, systems with full-disk or system encryption enabled will likely fail to start. Users will be presented with an error screen instead of the familiar password prompt.

In addition, Idrassi cannot issue updated, re-signed versions of the software without access to his developer account. This creates a dead end for Windows development. “If the issue is not resolved by then, it would essentially mean a death sentence for VeraCrypt,” he stated bluntly. The community is left hoping for a policy reversal or a new account approval process that seems, for now, opaque and unresponsive.

Navigating the Centralized Platform Dilemma

So, what are the alternatives? For users, the immediate advice is to ensure you have complete, unencrypted backups of all critical data stored separately. For the developer community, this event is a stark reminder of the risks of building on proprietary platforms. It may accelerate interest in fully decentralized signing mechanisms or alternative bootloaders that bypass Windows Secure Boot.

Ultimately, this case forces a difficult conversation about trust and control in software ecosystems. When a single account termination can jeopardize a globally used security tool, it reveals the fragility of our digital infrastructure. The resolution—or lack thereof—will set a precedent for how platform companies manage their relationships with essential open-source maintainers. For more on managing software dependencies, see our guide on open-source security best practices.

As a result, the coming weeks are critical. Will Microsoft provide a path to reinstatement, or will VeraCrypt for Windows become collateral damage in an automated enforcement system? The answer will affect not just one developer, but the security posture of countless users who chose encryption to protect their digital lives. For further reading on encryption tools, explore our analysis of alternative disk encryption solutions.

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

CyberSecurity

Study of 281 Free Android VPN Apps Finds Traffic Leaks, Unencrypted Data, and Tracking

Published

on

free Android VPN leak

Your Free VPN Might Be a Sham — Here’s the Proof

You download a free VPN from the Google Play Store. You think your traffic is hidden, your data is safe. But a sweeping new study suggests otherwise. Researchers put 281 of the most popular free Android VPN apps through a rigorous testing system. The results are ugly.

Many of these apps fail at the one basic job people install them for: keeping traffic private and secure. The apps flagged with at least one serious problem have been installed more than 2.4 billion times. That’s billions of users whose privacy may be compromised.

And these aren’t sophisticated attacks. These are basic failures. 29 apps let user traffic leak outside the VPN tunnel entirely. That means your real IP address and browsing activity are exposed, even while the VPN claims to be protecting you.

Another batch of apps sends user data — including login credentials and browsing history — completely unencrypted. Some even hardcode API keys and secret tokens into the app code, making it trivial for anyone to intercept or hijack the service.

The study, conducted by researchers using a new automated testing framework, looked at the top free VPNs by download count on Google Play. They didn’t name every single offender, but the pattern is clear: free VPNs are often a privacy nightmare.

What Exactly Did the Researchers Find?

The team built a system called VPNalyzer to automatically test each app. They checked for six core problems:

  • Traffic leaks — data escaping the VPN tunnel (29 apps)
  • Unencrypted traffic — sensitive data sent in plaintext
  • Hardcoded secrets — API keys, tokens, or credentials baked into the app
  • DNS leaks — domain requests visible to your ISP
  • IPv6 leaks — traffic bypassing the VPN over IPv6
  • Aggressive tracking — third-party SDKs collecting data for ad networks

More than half the apps had at least one of these issues. Some had multiple. The most common problem? Tracking. Many free VPNs are packed with analytics and ad SDKs from companies like Google, Facebook, and dozens of lesser-known trackers. You install a privacy tool, and it becomes a surveillance tool instead.

Why Free VPNs Are So Dangerous

Running a VPN costs money — servers, bandwidth, maintenance. If you’re not paying, you’re the product. That old adage holds brutally true here. Free VPNs have to make money somehow, and many do it by selling your data, showing you ads, or upselling you to a paid plan.

But the study shows it’s worse than just data collection. Some apps are so poorly coded that they actively undermine your security. Leaking traffic outside the tunnel is a catastrophic failure. It means your real IP is visible to every website you visit. Your ISP can see everything. The VPN is doing nothing.

Unencrypted data is another shocker. Modern web traffic is mostly encrypted anyway (HTTPS), but not everything. DNS queries, for example, are often sent in plaintext. A good VPN encrypts everything. A bad one leaves you exposed.

Hardcoded secrets are a developer sin. If an app stores its API key in the code, anyone who decompiles the app can steal that key and use it to access the VPN provider’s backend. That could mean free service for attackers — or worse, a way to intercept other users’ connections.

How to Pick a VPN That Actually Works

Not all VPNs are bad. But the free ones on Google Play are a minefield. If you need a VPN, here’s what to look for:

  • Paid services — A reputable paid VPN has a business model that doesn’t rely on selling your data. You pay for the service.
  • Independent audits — Look for VPNs that have been audited by third-party security firms. They publish the results.
  • No-log policy — The provider should promise not to log your activity. Check if they’ve proven it in court.
  • Open-source apps — If the code is open, anyone can check for leaks or tracking. It’s not a guarantee, but it’s a good sign.
  • Kill switch — A proper VPN has a kill switch that blocks all internet traffic if the VPN connection drops. This prevents leaks.

Some of the safer options include ProtonVPN (which has a free tier with no data limits and no ads) and Mullvad (a paid service known for strong privacy). Both have been independently audited.

The Bottom Line: Free VPNs Are a Bad Bet

The study of 281 free Android VPN apps is a wake-up call. Over 2.4 billion installs — and a huge chunk of those users are getting a false sense of security. Their traffic leaks, their data is unencrypted, and they’re being tracked.

If you care about privacy, do not trust a free VPN. Not without serious vetting. Even then, be skeptical. The safest bet is a paid, audited service that doesn’t need to monetize your data.

For more on staying safe online, check out our guide on how to check if your VPN is leaking your IP and our comparison of the best VPNs for Android in 2025.

Continue Reading

CyberSecurity

Estée Lauder Confirms Employee Data Stolen in Oracle EBS Zero-Day Attack

Published

on

Estée Lauder data breach

A Delayed Disclosure, a Massive Data Haul

Nearly a year after the infamous Cl0p cybercrime group exploited a critical vulnerability in Oracle E-Business Suite (EBS), cosmetics giant Estée Lauder has finally begun notifying employees that their personal information was stolen. The breach, which the company says occurred in early August 2025, leveraged a zero-day flaw — tracked as CVE-2025-61882 — that allowed unauthenticated remote code execution.

The Cl0p group wasted no time. By November 2025, over 100 companies found themselves listed on Cl0p’s leak site. Most confirmed the impact quickly. Estée Lauder did not. It took until March 2026 for the group to dump 870GB of archive files allegedly stolen from the company, making Estée Lauder one of the last major holdouts — alongside Broadcom, Bechtel, and Abbott Laboratories — to disclose the full scope of the damage.

What Was Stolen? A Full HR Dossier

The notification letter, filed with the California Attorney General’s Office, spells it out in grim detail. Estée Lauder’s Oracle EBS instance was used for HR management. That means the compromised data reads like a complete employee dossier: names, addresses, dates of birth, Social Security numbers, passport numbers, bank account numbers, health information, and payroll records.

It’s hard to overstate how sensitive that mix is. Bank details alone can fuel fraud. Combine them with SSNs and health data, and you have the raw material for identity theft that can plague victims for years. Estée Lauder is offering 24 months of free identity monitoring to those affected — a standard but necessary step.

The Timeline: How the Attack Unfolded

The zero-day itself was patched by Oracle in early October 2025. Shortly after, CrowdStrike confirmed that in-the-wild exploitation had begun on August 9 — the same day Estée Lauder was hit. The company’s internal investigation only concluded in June 2026, determining that data had indeed been exfiltrated from its EBS system.

That’s a long gap between intrusion and confirmation. Security teams often struggle to piece together what exactly was taken, especially when attackers have had months to cover their tracks. But a year-long investigation raises questions about visibility and logging within Estée Lauder’s Oracle environment.

Why the Delay?

Estée Lauder hasn’t explained why the notification took so long. The company says it has notified law enforcement and taken steps to harden its systems. It has not disclosed how many employees are affected. SecurityWeek has reached out for comment but has not yet received a response.

The Bigger Picture: Cl0p’s Oracle EBS Campaign

This wasn’t just a one-off breach. CVE-2025-61882 was a zero-day in Oracle EBS — a widely used enterprise resource planning platform. Cl0p, known for its big-game hunting tactics, scanned for vulnerable instances and punched through. The campaign hit dozens of organizations across industries, from manufacturing to healthcare.

What makes this incident particularly concerning is the nature of the data. Oracle EBS often centralizes HR, finance, and supply chain operations. When an attacker gains access to that system, they don’t just grab a few emails. They pull the company’s entire internal operating picture.

What Estée Lauder Employees Should Do Now

For the affected employees, the advice is straightforward but critical. Monitor bank accounts for unauthorized transactions. Watch for phishing emails that reference your stolen data — Cl0p or other criminals may try to weaponize the information. Place a fraud alert or credit freeze with the major credit bureaus. Estée Lauder’s identity monitoring service is a good start, but it’s not a silver bullet.

The company is also urging vigilance against suspicious calls and texts. Social engineering attacks often follow data breaches, with criminals posing as HR or IT support to extract even more information.

Lessons for Enterprise Security Teams

This breach underscores a few hard truths. First, zero-day vulnerabilities in legacy ERP systems are a ticking clock. Oracle EBS is decades old, but it’s still the backbone of HR and finance operations at thousands of companies. Patching alone isn’t enough — segmentation, monitoring, and incident response plans need to assume that an attacker will eventually get in.

Second, disclosure timelines matter. A year-long investigation erodes trust and leaves employees in the dark. Faster, more transparent communication — even if the full picture isn’t clear — can help mitigate the fallout.

Finally, the Cl0p group isn’t going anywhere. They’ve proven they can exploit enterprise software at scale and hold data for ransom or exposure. Companies running Oracle EBS should treat that as a given, not a possibility.

This is a developing story. SecurityWeek will update this article if Estée Lauder provides additional details on the number of impacted individuals or the remediation steps taken.

Continue Reading

CyberSecurity

GigaWiper: The Windows Backdoor That Wipes Disks, Fakes Ransomware, and Steals Data

Published

on

GigaWiper Windows backdoor

The anatomy of a destroyer

Microsoft’s threat intelligence team has dissected a nasty piece of malware it calls GigaWiper. This isn’t your average backdoor. It’s a Frankenstein’s monster — three older, proven destructive tools stitched together under one command-and-control interface. The operator picks what kind of digital wrecking ball to swing.

Each option is a different flavor of ruin. Wipe the entire disk. Overwrite only the Windows partition. Or deploy a fake ransomware routine that scrambles files with a key it never bothers to save. That last one is pure theater — the data is gone for good, and no payment will bring it back.

This isn’t a bug. It’s a feature set built for maximum, irreversible damage.

Three weapons, one trigger

GigaWiper doesn’t invent new destruction. It weaponizes old code. The three modules are:

  • Full disk wiper — overwrites every sector on the drive, making recovery impossible without a backup.
  • Windows partition killer — targets only the system drive, leaving other partitions intact but the OS dead.
  • Fake ransomware — encrypts user files but discards the encryption key. The victim sees a ransom note, but there’s zero chance of decryption.

The operator issues commands via a simple backdoor shell. No complex multi-stage attack. Just pick your poison and execute.

Why fake ransomware is the cruelest trick

Real ransomware at least offers a theoretical path to recovery — pay up, maybe get the key. GigaWiper’s version eliminates that. The key is generated and immediately thrown away. The encryption is a one-way street.

This matches a pattern seen in state-sponsored wiper attacks, where the goal is pure destruction, not profit. But GigaWiper also includes spyware capabilities, suggesting the attacker wants to steal data before burning the machine. Exfiltrate first. Wipe second. Leave nothing behind.

It’s a reminder that ransomware recovery strategies don’t apply here. Offline backups are the only defense.

Microsoft’s analysis and the broader threat

Microsoft has not attributed GigaWiper to a specific group yet. The malware appears to target Windows systems, likely in corporate or government networks. The modular design suggests a threat actor with access to a toolkit — or a developer who grabbed three old exploit-kits and wired them together.

The backdoor component itself is lightweight. It listens for commands, executes the chosen wiper module, and reports back. No persistence mechanism is mentioned, which means the attacker probably drops GigaWiper after already gaining a foothold.

This is a final-stage payload. By the time GigaWiper runs, the network is already compromised.

Defense: what actually works

Standard antivirus may catch some components, but wipers often fly under the radar because they use legitimate system calls to overwrite data. Behavioral detection — looking for unusual disk write patterns — is more effective.

Key steps for defenders:

  • Maintain offline, immutable backups. If the wiper hits, you restore from cold storage.
  • Monitor for mass file modifications or unusual volume writes.
  • Restrict administrative access. GigaWiper needs privilege to wipe disks.
  • Use endpoint detection and response (EDR) tools that flag rapid file encryption or disk overwrite operations.

Microsoft has released indicators of compromise (IoCs) for GigaWiper. Security teams should ingest those into their SIEM immediately.

The takeaway for Windows users

GigaWiper is a blunt instrument. It doesn’t care about stealth after activation. It’s designed to finish the job — destroy data, cause chaos, and leave a clean slate for the attacker’s narrative (or just spite).

For IT admins, the lesson is old but worth repeating: assume breach, segment your network, and test your backups. A wiper that deletes encryption keys doesn’t care about your ransomware insurance policy.

And if you see a ransom note after a GigaWiper infection? Don’t pay. The key never existed.

Continue Reading

Trending