Skip to content
Cyber SecurityBeginner

GigaWiper Malware: Is It a Virus or Spyware?

Quick Answer GigaWiper is destructive Windows malware that combines a backdoor, spying capabilities and data-wiping functions. Calling it only a virus or spy...

BI
Bison Technical Team Enterprise IT specialists
Updated 6 min read 0 total views
Structured technical guidanceSafety notes included where requiredSources cited when applicable

Quick Answer

GigaWiper is destructive Windows malware that combines a backdoor, spying capabilities and data-wiping functions. Calling it only a virus or spyware understates its capabilities. Microsoft also identifies it as BLUERABBIT, a name used by other researchers.

If you suspect an infection, isolate the device from networks and contact your IT or security team. Removing malware does not restore data it has already destroyed.

Advertisement

Is GigaWiper a Virus, Spyware or Ransomware?

These terms describe different behaviours and can overlap:

  • Virus: Technically, malware that replicates by infecting other files or programs. The cited research describes GigaWiper primarily as a backdoor, not a conventional file-infecting virus.
  • Spyware: Software that secretly observes activity or collects information. GigaWiper has surveillance functions.
  • Backdoor: Malware that gives attackers unauthorized access to a system.
  • Wiper: Malware designed to destroy data or make systems unusable.

The most useful classification is a destructive backdoor with surveillance capabilities.

What Can GigaWiper Do?

Remote Access and Surveillance

Binary Defense’s BLUERABBIT analysis documents screen capture, screen recording, remote desktop control, command execution and system profiling. It also describes file transfers to attacker-controlled storage.

Its command-and-control communication, which lets attackers send instructions, uses RabbitMQ and Redis. MinIO supports file transfers. These are legitimate technologies; their presence alone does not establish an infection.

Data Destruction and System Damage

Microsoft documents physical-disk overwriting, boot-file sabotage and a destructive encryption routine that adds the .candy extension. That routine does not retain its encryption keys. The backdoor also contains a separate encryption/decryption function, so recovery assessments must identify which operation actually ran.

Microsoft links components to Crucio and FlockWiper and reports observing destructive activity beginning in October 2025.

Which Systems Are Affected, and How Does Infection Happen?

The analysed malware targets Windows. The cited reports do not provide a complete Windows edition or build compatibility matrix. They should not be interpreted as proof that every Windows device is vulnerable to an identical attack.

The reports also do not establish one universal infection route. Do not assume that a particular email, download or Windows vulnerability caused an incident without supporting evidence.

Investigators should reconstruct the initial access and execution timeline using endpoint alerts, authentication records and relevant network logs. A malware family name identifies the threat; it does not explain how that threat entered a particular environment.

Warning Signs That Need Investigation

Research describes the following useful investigation leads:

  • An unexpected scheduled task named OneDrive Update, particularly when its executable path or creator is suspicious.
  • Unexpected use of HKCU\Software\OneDrive\Environment associated with an unfamiliar process.
  • Unexplained connections to external RabbitMQ or Redis infrastructure.
  • Unexpected MinIO client activity or unusual outbound file transfers.
  • Files renamed with .candy, unexpected wallpaper changes, or interference with boot files and recovery settings.

None of these signs should be assessed in isolation. Check the associated process, file hash, task action, timestamps and network destination. A familiar-looking name can conceal malware, while legitimate software can produce superficially similar artefacts.

Do not delete OneDrive components or block legitimate business services solely because their names appear in a malware report.

What to Do if You Suspect GigaWiper

The following is general incident-response guidance adapted for a suspected destructive backdoor.

  1. Isolate the device. Disconnect Ethernet and Wi-Fi, or have your security team isolate it through endpoint management. Coordinate isolation when multiple systems are involved.
  2. Contact responders through a trusted device. Use a phone or another approved communication method outside the suspected environment.
  3. Protect backups. Do not attach backup drives or expose recovery repositories to the affected computer.
  4. Preserve evidence. Record alerts, affected filenames and approximate times. Let trained responders collect logs, memory and disk evidence before cleanup when feasible.
  5. Avoid casual rebooting or repair attempts. Powering down loses volatile evidence. CISA recommends shutdown when network disconnection is impossible. Network isolation does not stop destructive code already running locally; responders must urgently assess that situation.

Do not download an advertised “GigaWiper remover” or decryptor from an unverified website.

Can an Antivirus Scan Remove It?

A scan can support investigation and remediation, but a clean result alone does not establish that an attacker’s access has been eliminated. Treat confirmed compromise as an incident requiring investigation beyond the detected file.

Microsoft Defender Offline: A Supporting Check

After containment and evidence collection, a technician may use Microsoft Defender Offline on a supported Windows device. It restarts the computer and scans outside the normal Windows environment.

Prerequisites: Administrator access, an enabled Windows Recovery Environment and an appropriate Microsoft Defender Antivirus configuration are required. Check Microsoft’s platform requirements. For a BitLocker-protected system, follow its guidance on suspending protection and ensure the recovery key is available; involve IT on managed devices.

  1. Save work and close applications.
  2. Open Windows Security, then Virus & threat protection.
  3. Select Scan options, then Microsoft Defender Offline scan.
  4. Select Scan now and approve the prompts.
  5. After Windows restarts, review Protection history.

This scan is not a recovery tool for destroyed files. Do not initiate a reboot-based scan during an unresolved destructive incident without responder guidance.

Recovery After a Confirmed Compromise

After preserving evidence, responders should determine which systems, accounts and data were affected, including whether information was stolen. Reset compromised credentials from a trusted device, coordinating changes so recovery access is not lost.

Where system integrity cannot be trusted, rebuild from trusted installation media or a verified clean image. Reinstallation is disruptive and can overwrite remaining data; perform it only after evidence and recovery requirements have been assessed.

Restore verified backups in an isolated environment, patch systems and address the original entry point before reconnecting them. Recovery must include checking that restored data is accurate, complete and free of malware.

Practical validation should include:

  • Opening representative restored documents and checking their contents.
  • Testing application and database consistency.
  • Checking permissions, business workflows and required services.
  • Confirming that security monitoring is functioning and reviewing subsequent alerts.

Renaming encrypted files does not decrypt them. Recovery software cannot be assumed to reconstruct overwritten data. Preserve damaged media for specialist assessment when valuable information remains unavailable.

How to Reduce the Risk

  • Maintain separate recovery copies. Keep offline or appropriately protected immutable backups and test restoration regularly.
  • Do not equate synchronization with backup. Synchronized damage or deletion can affect cloud copies unless usable version history or independent backups remain.
  • Reduce unnecessary access. Use least privilege and multifactor authentication, especially for administrative and remote access.
  • Maintain security controls. Keep software patched and endpoint protection updated.
  • Prepare for disruption. Keep an accessible incident-response plan, recovery priorities and trusted contact details.

These measures reduce exposure and improve recovery readiness; no single control guarantees protection against destructive malware.

Official References and Technical Research

YOUR FEEDBACK

Was this guide useful?

Your answer helps us keep BISONKB accurate and practical.

Links are permitted only to published BISONKB articles.