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.

The quiet threat of ‘ghost’ accounts

When a GitHub account sits untouched for years, most teams assume it’s harmless. A forgotten developer profile, an old bot, a test user — nothing to worry about, right?

Wrong. According to Datadog Security Labs, attackers are actively weaponizing these dormant accounts. They call them ‘ghost’ accounts, and they’re a core part of a broader campaign to map out corporate GitHub organizations, repositories, and user accounts without raising alarms.

The technique is deceptively simple: automated scripts scrape the GitHub API using custom user agents that sound legitimate. The accounts themselves are often years old — meaning they pass basic age checks and don’t trigger the suspicion a fresh profile would.

How the enumeration works

Datadog’s report details several overlapping campaigns, all targeting the same thing: organizational structure. Attackers aren’t after code — at least not yet. They want the map.

By making API calls to list members of an organization, pull repository metadata, and check user profiles, they can build a detailed picture of who works where, what projects exist, and which accounts have elevated access. That reconnaissance is gold for a follow-up phishing attack or a credential-stuffing attempt.

OAuth tokens in the mix

It gets worse. Some of these campaigns don’t rely on ghost accounts at all. Instead, they use compromised OAuth tokens — keys that were either stolen or leaked — to authenticate as a legitimate user. Once inside, the attacker can scrape even more data because the API trusts the token.

This is a classic GitHub API abuse scenario: the API itself is working as designed. The problem is that the credentials behind the requests are not what they seem.

Why old accounts fly under the radar

Security teams often focus on new accounts and unusual login locations. A dormant GitHub account that suddenly starts making API calls? That’s harder to catch. The account already exists. It might have a history of commits, comments, or issues. The behavior shift is subtle.

Add in custom user agents that mimic popular tools like curl or official GitHub CLI clients, and you have a recipe for invisibility. The traffic looks normal. The account looks normal. Only the intent is malicious.

What organizations should do

There’s no single fix, but Datadog points to a few concrete steps that reduce the risk significantly:

• Audit OAuth tokens regularly. Revoke any token that hasn’t been used in 90 days. Attackers love old, forgotten tokens.
• Monitor API call patterns. A sudden spike in member enumeration or repository listing from a single account — especially an old one — is worth investigating.
• Enforce two-factor authentication (2FA). It won’t stop a compromised token, but it makes ghost account takeovers much harder.
• Review organization membership. Remove users who no longer work on the project. Every extra account is a potential entry point.

For more on securing your development pipeline, check out our guide on GitHub security best practices and how to handle compromised API tokens.

The bottom line

Attackers are getting smarter about blending in. They’re not smashing the front door — they’re using keys that were left under the mat years ago. Dormant GitHub accounts, old tokens, and legitimate-looking traffic are the new normal in corporate reconnaissance.

The takeaway? Clean up your digital attic. Every old account and every unused token is a liability. And in this case, the ghosts are very real.

Suddenly, Everyone Has a Clearinghouse

The past few weeks have felt like a parade of press releases. Company after company has stepped up to announce its own clearinghouse — a new platform, a new promise, a new way to handle data or transactions. It’s a crowded field, and the announcements keep piling up.

Our team joined the chorus, too. We announced Athena. But there’s a catch: when we told the world about it, the product wasn’t a PowerPoint slide or a beta waiting list. It was already live. Real customers were using it. Fixes were being shipped. The code had been running quietly for months.

Why the Rush to Announce?

It’s tempting to ask: why now? Why did so many clearinghouses suddenly emerge in the same window? Part of the answer is market timing. The industry has reached a point where a clearinghouse isn’t a nice-to-have; it’s becoming table stakes. Companies that don’t have one risk looking like they’re falling behind.

But there’s another layer. Announcing early can signal ambition to investors, partners, and customers. It builds buzz. It creates a narrative. The problem? Many of these announcements are vapor — promises without a product behind them. They’re built on roadmaps, not running code.

Athena: Built in Silence, Shipped in Secret

That’s where Athena broke the mold. The team behind it didn’t start building when the trend emerged. They started because customers kept asking for a solution — a real one, not a concept. So they built it. Quietly. No press releases, no teaser campaigns.

They took findings from early users and turned them into fixes. They iterated. They made mistakes, corrected them, and kept shipping. The product grew organically, shaped by actual demand rather than a product manager’s whiteboard.

“We only announced it now because everyone else started announcing theirs,” one team member said. The implication is clear: Athena was never about the announcement. It was about the work.

What Sets a Live Platform Apart

There’s a fundamental difference between a clearinghouse that’s been running for months and one that’s still in development. A live platform has battle scars. It has handled edge cases. It has real data flowing through it, which means real insights about what works and what doesn’t.

For customers, that difference matters. A live platform means:

• Immediate value — no waiting for a launch date.
• Proven reliability — bugs have been found and fixed.
• Real feedback loops — the product evolves based on usage, not assumptions.

In a summer of clearinghouse announcements, Athena stands out because it was already doing the job while others were still drafting their blog posts.

The Noise vs. The Signal

So what should customers and industry watchers take away from this wave of announcements? First, it’s worth asking: is the product real? Can you use it today? Does it have a track record, even a short one?

Second, look for specificity. Vague claims about “revolutionizing” or “transforming” something are easy to make. Concrete numbers — users onboarded, transactions processed, bugs squashed — are harder to fake. Athena had those numbers before the first press release went out.

Finally, remember that a clearinghouse is only as good as the work behind it. The hype cycle will pass. What remains are the platforms that actually solve problems. In this summer of clearinghouses, one was already solving them — quietly, steadily, and without fanfare — long before the announcements started.