Skip to main content
AVOID.NET
← UNK_DeadDrop North Korea Developer Phishing Campaignreviewed 2026-11-01 · 11 claims checked

Fact-check findings

What an automated fact-checker found when it re-read UNK_DeadDrop North Korea Developer Phishing Campaign against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

unverifiable 3partially supported 4confirmed 40 corrections pending · 0 applied

unverifiable

3 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #7[unverifiable][awaiting moderator]in section: Credential and Cryptocurrency Theft Capabilities
    “Browser exfiltration covered saved passwords and session cookies from Chrome, Brave, Edge and Firefox”
    reviewerBrowser exfiltration covered Chrome, Brave, Edge and FirefoxCould not confirm Brave and Edge or session cookies from the fetched summary.
  2. #8[unverifiable][awaiting moderator]in section: Losses Attributed
    “Proofpoint's broader tracking of related North Korean campaigns noted that Contagious Interview and DangerousPassword had together allegedly netted $37.5 million since January 1, 2026”
    reviewerContagious Interview and DangerousPassword together netted $37.5 million since January 1, 2026, per Proofpoint's trackingNot in the primary source; the CyberPress article could not be read, and the page's attribution of the figure to Proofpoint is unsupported.
  3. #10[unverifiable][awaiting moderator]in section: Campaign Scale and Targeting
    “Targeted sectors included technology, finance, cryptocurrency, education, business services, entertainment and media, and telecommunications.”
    reviewerTargeted sectors included entertainment and media and telecommunicationsPossibly in a chart not captured by the summary.

partially supported

4 claims

The cited evidence supports part of the claim but not all of it.

  1. #3[partially supported][awaiting moderator]in section: Attack Chain and Delivery Mechanism
    “which persisted across editor restarts and provided a durable foothold”
    reviewerThe VSIX persisted across editor restarts and provided a durable foothold (all platforms)Persistence is overstated as universal.
  2. #4[partially supported][awaiting moderator]in section: Malware: Overlord Framework and Platform-Specific Payloads
    “Accounts of the Windows payload differ in detail: the survivor page, citing Proofpoint, Infosecurity Magazine and The Register, describes a JavaScript-based payload running inside the VS Code editor's Electron process and leaving minimal file-system artifacts, while the merged page, citing Proofpoint, TechRadar and GBHackers, describes platform-specific launchers that decoded embedded payloads.”
    reviewerWindows payload accounts differ (survivor page / merged page)This is an editorial merge artifact (references to 'survivor page' and 'merged page') in reader-facing text; the underlying Windows description is supported by Proofpoint.
  3. #5[partially supported][awaiting moderator]in section: Malware: Overlord Framework and Platform-Specific Payloads
    “while leaving the VSIX extension in place for persistence”
    reviewerFinal stage left the VSIX in place for persistenceSame persistence overstatement.
  4. #6[partially supported][awaiting moderator]in section: Credential and Cryptocurrency Theft Capabilities
    “The Overlord-based payload targeted 35 browser-based wallet extensions, including MetaMask, Phantom and Keplr, and 18 standalone desktop wallet applications, including Exodus, Electrum and Ledger Live.”
    reviewerOverlord payload targeted 35 browser wallet extensions and 18 desktop walletsCounts are correct but are attributed to the wrong payload (Windows JavaScript pipeline, not Overlord).

confirmed

4 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in the summary
    “sent more than 250 phishing emails to software developers at roughly 100 organizations”
    reviewerProofpoint disclosed the campaign on June 8, 2026 and reported more than 250 emails to about 100 organizations over six weeks in April-May 2026Matches the Proofpoint post.
  2. #2[confirmed][no action needed]in section: Social Engineering and Impersonated Companies
    “include Ondo Finance (a decentralized finance platform), Nourish (a telehealth company), Empower Pharmacy, NXLog, OnePlan, Hypen Connect (a Web3 and AI talent agency) and Valon”
    reviewerImpersonated companies and the later Pulsynk and Trixauvex luresCompany names match. Proofpoint also mentions a spoofed NEMESIS DeFi site, which the page omits (minor).
  3. #9[confirmed][no action needed]in section: Government Attribution and Regulatory Status
    “attribution to North Korea rests on private-sector threat intelligence that Proofpoint assesses as 'likely'”
    reviewerProofpoint rates attribution as likely/very likely North Korea-aligned and tracks it separately from Contagious InterviewMinor inconsistency in hedging wording across the page. Proofpoint also says the overlap may be an operational evolution of Contagious Interview, which the page does not mention.
  4. #11[confirmed][no action needed]in section: Government Attribution and Regulatory Status
    “No official U.S. government attribution, OFAC sanctions designation, DOJ indictment or FBI advisory specifically naming UNK_DeadDrop had been issued as of the reports”
    reviewerNo government attribution, sanctions or indictment specifically naming UNK_DeadDropConsistent with search results; later developments may not be indexed.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.