Advertisement

Lazarus Perfects New Tactics, Steals $1.788 Billion in Seven Months

Lazarus Perfects New Tactics, Steals $1.788 Billion in Seven Months

The North Korea–linked Lazarus Group has entered a new phase of highly sophisticated financial attacks, moving away from traditional code‑exploiting hacks to a quieter, far more insidious strategy that abuses trust inside the victim’s own security perimeter. Instead of smashing through firewalls, the group now walks in through the front door, compromising third parties that institutions already consider safe.

From Exploiting Bugs to Exploiting Trust

Rather than focusing on software vulnerabilities in the victim’s systems, Lazarus is targeting trusted intermediaries: service providers, custodians, integration partners and even internal employees who already appear on institutional whitelists. Once they gain control of one of these “approved” entities, they can initiate fraudulent transactions that glide past static controls such as:

  • Approved-address lists (whitelists)
  • Multi‑signature schemes
  • Standard address and identity checks

Because the traffic originates from whitelisted actors, it looks legitimate, allowing the attackers to move large sums with minimal friction.

Blockchain Transparency as an Intelligence Tool

Paradoxically, the public nature of many blockchains has become a powerful reconnaissance tool for Lazarus. By carefully analysing on‑chain activity, the group can map:

  • Which custody providers an institution uses
  • What wallet infrastructures and DeFi protocols they rely on
  • How funds move between internal and external addresses

This transparency lets them identify the weakest link in an otherwise hardened ecosystem and focus on that point of entry instead of attacking the institution head‑on.

When Whitelists Turn into an Attack Map

Controls once treated as a gold standard of security—particularly whitelists—are being turned against their owners. By compromising a provider or employee who is already marked “trusted”, Lazarus can:

  • Trigger malicious transfers that pass all whitelist checks
  • Bypass address‑verification workflows and device‑level protections
  • Abuse legitimate signing flows rather than forging them

In this model, the whitelist effectively becomes a map of high‑value, high‑trust targets. If one of those nodes falls, every control that depends on that trust falls with it.

A Clear Attack Pattern: July 2024 – February 2025

According to recent industry analysis, the attacks detected between July 2024 and February 2025 follow a repeatable pattern:

  1. On‑chain reconnaissance to profile partners, custodians and technical providers.
  2. Compromise of a third party (or insider) that is already approved by the victim.
  3. Execution of fraudulent transactions using legitimate access, keys or interfaces.

Over just seven months, this refined approach is estimated to have netted Lazarus around 1.788 billion dollars, underlining how effective it is against current security architectures.

Why Traditional Defences Are No Longer Enough

Measures such as whitelists, multi‑signature wallets and hardware wallets are still important, but this wave of attacks shows they are not sufficient on their own when the attacker controls a trusted party or the user interface itself. An adversary capable of:

  • Manipulating signing interfaces
  • Compromising providers
  • Hijacking normal approval flows

can effectively weaponise the very tools designed to protect funds.

The New Priority: Real‑Time, Transaction‑Aware Validation

Security experts are urging the industry to rethink its reliance on static “trust lists” and to add dynamic controls that examine the actual effect of each transaction before it is signed. The key recommendation is:

  • Simulate every transaction in real time, showing the user the exact impact on balances and ownership before they approve it.

Instead of checking only that the destination address appears on a whitelist, systems should:

  • Verify that the transaction behaviour matches past patterns and business logic.
  • Highlight any unexpected asset movement, contract interaction or permission change.
  • Block or flag operations whose simulated outcome diverges from what the user intends.

In an environment where state‑sponsored groups like Lazarus can subvert providers, interfaces and even employees, the future of defence lies in verifying outcomes, not just identities—treating every transaction as potentially hostile, no matter who appears to be sending it.

Author