Zerion and KelpDAO link security incidents to DPRK TraderTraitor activity
Zerion published a security incident post-mortem, and LayerZero later issued a KelpDAO incident statement, with both incidents being publicly tied in threat-intelligence discussion to DPRK activity. Social-media reporting around the disclosures specifically associated the KelpDAO case with TraderTraitor, the North Korean cluster known for targeting cryptocurrency and Web3 organizations through social engineering and wallet compromise.
The available references do not provide technical indicators, loss figures, or a detailed attack chain, but they place both disclosures in the context of crypto-focused intrusions attributed to North Korean operators. For CISOs in digital-asset, DeFi, and wallet ecosystems, the incidents reinforce the ongoing risk from DPRK-linked campaigns that exploit trusted workflows, third-party relationships, and user-facing transaction processes to gain access and move funds.
How this story unfolded
7 events from the earliest known activity through the most recent confirmed update.
Zerion publishes security incident post-mortem
Zerion published a "Security Incident: Post Mortem" referenced in a 2026-04-15 Bluesky post. The available content does not provide further details on the incident, impact, or attribution.
LayerZero publishes KelpDAO incident statement
LayerZero published a "KelpDAO Incident Statement" referenced in a 2026-04-20 Bluesky post. The post's hashtags suggest a cybersecurity incident possibly linked to DPRK-related threat activity, but no substantive incident details are provided in the available content.
KelpDAO publishes additional context on April 18 incident
KelpDAO published an item titled 'April 18 Incident: Additional Context,' indicating a follow-up disclosure about the incident. The available reference does not provide substantive technical or impact details beyond the existence of this additional context statement.
KelpDAO attacker reportedly moves $175M to new addresses
An Arkm research item shared on Bluesky reported that funds linked to the KelpDAO hacker were transferred to new cryptocurrency addresses. The reported movement involved $175 million and occurred on 2026-04-22, indicating post-incident laundering or fund relocation activity.
Analysis reports laundering of $292M tied to KelpDAO theft
A referenced article titled "Where did the kelp $292m go? anatomy of a $292m laundering" reported on laundering activity involving $292 million linked to the KelpDAO incident. The available post provides no further technical details, but it indicates a broader accounting of stolen-fund movement than earlier reports of transfers to new addresses.
KelpDAO publishes LayerZero bridge hack clarification
KelpDAO published a statement titled "Setting the Record Straight Around the LayerZero Bridge Hack," indicating a further official clarification related to the incident. The available reference does not provide substantive new technical, impact, or attribution details beyond the existence of this follow-up statement.
LayerZero publishes follow-up update on KelpDAO incident
A Bluesky post on 2026-05-09 references a publication titled "LayerZero Update" by LayerZero. The available content does not include the substance of the update, but it indicates a new official follow-up communication related to the KelpDAO/LayerZero incident.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
14 references tracked. Mallory keeps watching after this page renders.
Post by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourcePost by @lazarusholic.bsky.social - Bluesky
bsky.app
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.



