North Korea's best exploit is your org chart
Summary
North Korea-linked remote IT operations exploit gaps between corporate hiring, security, finance and legal teams, posing a strategic risk to companies. On Oct. 29, attackers drained roughly $6.3 billion from Binance in what the FBI attributes to North Korea’s TraderTraitor group; Binance said the operation ran for months and included a fake job interview. The author argues that companies need integrated oversight of remote-worker hiring and payments rather than treating each warning sign as a separate departmental issue. Suggested measures include assigning an accountable executive, creating shared escalation procedures and testing decision-making through exercises.
Key Facts
- The article describes remote IT workers using real-time AI video, synthetic voices and faces, and domestic proxy routing to appear like ordinary contractors.
- The author says HR, security, finance and legal teams may each see only part of a suspicious hiring or payment pattern, leaving no one responsible for connecting the signals.
- The proposed cross-functional warning signs include a laptop sent to an address that differs from the stated location, a persistently broken camera, a changed payment account after onboarding and login times inconsistent with the applicant’s stated time zone.
- The author recommends setting verification standards according to a contractor’s role and access, with stronger checks for work involving source code or production systems.
- The proposed board-level exercises would test who can revoke access, notify the FBI and board, and decide whether to terminate a high-performing engineer when evidence is incomplete.

Soo Kim
Picture a quiet suburb in Texas: A dozen laptops sit on a folding table in the basement, each humming on its own power strip and logged into a different U.S. company’s network. The woman who rents the house views herself as a steward, paid by the machine to keep them online and importantly, in the right time zone. The engineers who “report” to those laptops each morning don’t actually live in the house, the state or even the same hemisphere. Their salaries are not paying a mortgage in Dallas.
On Oct. 29, attackers drained roughly $6.3 billion from Binance in what the FBI attributes to North Korea’s TraderTraitor group — the largest crypto theft on record. By Binance’s own account, the operation ran for months and included a fake job interview. Of course, Pyongyang denies any involvement.
The Binance case is the mirror image of the laptop farm. In Texas, the fake candidate gets hired. At Binance, a real employee was recruited by a fake employer. Either way, the way in is the hiring process, which few corporate boards naturally think of as a security partner.
Boards keep filing each new episode under the same bureaucratic headings: information technology (IT) glitch, human resources (HR) oversight or a one-off cyber heist. However, it’s hard to call a monthslong campaign that began with a job interview a “one-off.”
In reality, it’s none of these. A more accurate snapshot would be the steady, compounding and increasingly sophisticated output of a sovereign adversary playing the long game for economic and strategic survival. The failure isn’t on the server or in the applicant tracking system, but in the boardroom, which may not have noticed that it is the target.
North Korea’s old playbook was a borrowed identity, a photocopied passport and the occasional awkwardly worded email. Today, Pyongyang’s remote IT workforce has made industrial-grade improvements, with real-time artificial intelligence (AI) videos, synthetic voices and faces, and domestic proxy routing built to look like any other contractor with a functional home office.
Corporate defenses were designed for a world of paper and neatly delineated perimeters. Employment eligibility checks, background screening software and, for the many contractors who never touch an I-9 employment eligibility verification form, a video call and a signed agreement. All of this is structurally blind to a synthetic persona built to pass exactly those filters. When a company hires a remote engineer a few time zones away, it assumes a human being was verified somewhere along the process. In the era of AI, however, that assumption can no longer hold.
Why do enterprises with eight-figure security budgets keep falling for this? Most are well-run silos with few sturdy mechanisms to cross-check for accountability and integration or provide a strategic response during crises. HR owns talent recruitment and hiring. The chief information security officer owns security. Finance owns payroll. Legal owns compliance. Nobody owns the whole, which is convenient for everyone except the company overall.
A threat contained in any one silo gets caught, but a threat that lives between them effectively becomes no one’s job. Hiring looks clean to HR, the network seems normal to security and the payroll appears routine to finance. Each sees a fragment that is unremarkable on its own, but no one is positioned to assemble the entire picture. North Korea has found the one place a loosely-integrated organization is guaranteed to be weak.
When a crisis or anomaly surfaces — a tax document filing discrepancy, a glitch in video latency or a payout to an unexpected crypto wallet — the organization doesn’t investigate. It stalls in a way that might best be called a decision collapse: Every division has a perfectly justifiable motive to wait, and the sum of all this waiting is paralysis.
For instance, the legal division might warn against wrongful termination and privacy claims if evidence is ambiguous. HR, for its part, prioritizes hiring velocity over friction. Finance quietly runs payroll. And the adversary? It wins precisely in the operational seams between these departments, effectively exploiting gaps wide enough to drive a state-backed proxy through.
Those cautious instincts are not irrational. Over-screening carries real costs, from discrimination claims to impeding a company’s ability to hire talented people quickly. From a common sense perspective, no board should want a hiring process that’s so circumspect that it treats every remote engineer as a suspect. But the answer to a bad trade-off is not to let it be made by default in whichever department blinks last.
The stakes go beyond embarrassment and reputational damage. A company can face potential exposure under U.S. sanctions rules, where the absence of intent is not always a defense and an anomaly that was documented but never escalated to the proper channels can look discomfitingly like a choice. Counsel will parse the particulars, but the problem for the board is simpler — and the “nobody was responsible” position isn’t an answer anyone wants to give a regulator.
Executives must stop treating sovereign risk as an IT ticket or as a checklist to be outsourced to a vendor with a streamlined dashboard. The real fix is not another tool, but integration. Companies should start with the following changes:
First, name an owner for the whole. Designate one accountable executive, with a board-level committee as backstop, for the integrity of the remote workforce — from the moment a candidate applies to the moment a contractor is paid. This executive needs real authority across HR, security, finance and legal areas, not just a coordinating role with no leverage. The title matters less than answering the question of: When the functions disagree, who decides?
Second, build cross-functional triggers. Establish consensus in advance on the signals that matter when seen as a composite, such as a laptop sent to an address that doesn’t match the stated location, a camera that is always "broken," changing a payment account after onboarding or a login pattern that fits a different time zone than the one provided on the application. Route those signals into a single shared case file, not three separate inboxes. Set a clock on it, so that an unresolved flag reaches the general counsel and the board within days, bypassing the middle-management layer where inconvenient facts tend to remain in limbo.
Third, decide the trade-off before the crisis hits. Set verification standards by role and access level. For example, a contractor working with source code or production systems likely warrants stronger identity checks, live verification and tighter access than an employee writing marketing copy. Write down the thresholds and the escalation rules with counsel’s input on discrimination and privacy. That way, the people who must act in a crisis aren’t improvising under pressure and worrying about personal liability.
Fourth, stress-test the decision architecture. Run synthetic-infiltration wargames and board-level tabletops now, while the only audience is your own team rather than after federal agents have taken your engineer’s laptop as evidence. The exercise should focus on the decisions, not the technology — who pulls access, who notifies the FBI and the board and who is willing to terminate the high-performing engineer on incomplete evidence. The gaps you find may not always be technical.
Importantly, ask the question that matters: If one of your remote engineers, even a star performer, turns out tomorrow to be a state-sponsored operative, who in your company will be held accountable?
If the answer takes more than a second to give, that’s your attack surface.
Soo Kim is a former CIA analyst and strategic risk consultant, and the host of the YouTube channel @sklucidtv.
Explore More
- Q.
- Q.
- Q.