Compliance teams often ask about North Korean IT worker schemes, and for good reason. These questions arise from internal escalations, vendor calls, and Slack threads starting with "has anyone seen this before?" The challenge lies in the fact that the money appears ordinary. A salary deposit isn't suspicious by default. The risk is in who controls the account, and your standard monitoring likely wasn't designed to detect this.
This post doesn't focus on specific accounts or transactions. Instead, it covers the general typology and what your framework should address.
Why Are Salary Payments a Proliferation Financing Issue?
The sanctions exposure is linked to the beneficiary, not the transaction type. Revenue from remote IT work can be routed back to a sanctioned state, potentially supporting weapons programs. This falls under Proliferation Financing, as outlined in FATF Recommendation 7. If your institution holds an account controlled by a Designated Person or Entity, or acts on their behalf, you have a sanctions issue, even if deposits appear as legitimate payroll credits.
What Red Flags Should You Look For?
Consider three layers: identity, account behavior, and money movement.
Identity:
- Documents that seem valid but don't hold up under scrutiny, like mismatched photos or inconsistent biographical details.
- Shared contact details (phone, email, device) across unrelated customers.
- Stated locations that conflict with device or IP data at login.
Account behavior:
- Remote access patterns suggesting the account holder isn't the person logging in, such as using remote-desktop tools.
- Multiple accounts with identical behavior: same deposit rhythm, same outbound routing.
Money movement:
- Salary-type inflows quickly moved to third parties, with minimal personal spending.
- Funds transferred to payment platforms, money transmitters, or crypto exchanges in patterns inconsistent with the customer's profile.
- Round-number or near-identical transfers across multiple accounts.
No single red flag is conclusive. The value lies in combining them.
Is a Clean Name Screening Enough?
No. Name Screening only identifies people appearing under their own names on a list. This scheme involves workers using borrowed or fabricated identities, so the designated link isn't visible in the name field. Screening is necessary but not sufficient.
Close the gap with Customer Due Diligence to verify the identity and behavior of the customer. This includes stronger document and liveness verification at onboarding and Ongoing Due Diligence to revisit the Customer Risk Profile when behavior changes. Treat a clean screen as the beginning of the analysis, not the end.
How to Tune Transaction Monitoring Rules Without Excessive Alerts
Don't rely on a single rule. Build a set of rules targeting the behavior pattern, then layer them.
- Pass-through rule. Flag accounts where payroll-style credits are quickly followed by outbound movement with low retention.
- Link-analysis rule. Flag clusters of accounts sharing device, contact, or address attributes, even if names differ.
- Profile-mismatch rule. Flag activity inconsistent with the stated occupation, location, or expected volume from onboarding.
- Destination rule. Flag onward flows to higher-risk channels when paired with any of the above.
Run these as a scored combination rather than independent alerts. A customer triggering one rule goes to routine review; one triggering three goes to an analyst. This keeps volume manageable and focuses investigator time where it's most needed.
What Are Your Obligations When You Find Something?
Act quickly and document thoroughly. If you identify property of a Designated Person or Entity, you must Freeze Without Delay and follow OFAC blocking and reporting requirements. Evaluate if the activity meets the threshold for a Suspicious Activity Report, filed on FinCEN SAR (Form 111) through the BSA E-Filing System. If activity continues after the initial filing, a Continuing Activity SAR is necessary.
Escalate immediately to your MLRO or BSA officer, and ensure the escalation record captures what you saw, when, and why you decided as you did. Keep customer-facing staff informed only as necessary. Tipping Off and SAR Confidentiality rules apply, and the Safe Harbor protections in the BSA cover good-faith reporting, not careless disclosure.
Why Is This Gaining More Attention?
While niche in volume, the consequences are significant. Geopolitical tension drives enforcement priorities, and sanctions evasion involving proliferation-linked states is a top concern. The broader lesson extends beyond one country: any sanctioned actor with a marketable skill can monetize it through ordinary employment and bank accounts. If your framework only catches obvious bad actors, it will miss a motivated adversary with a convincing front.
Your AML/CFT Framework should reflect this in the risk assessment. Consider where remote-work income, freelance platforms, and payment intermediaries intersect with your products, and whether your controls assume the account holder is who they claim to be.
Where to Go for More
- FATF Recommendation 7 and its interpretive note for proliferation financing sanctions standards.
- United Nations Security Council Resolution 2462 for the broader framework on countering financing of designated activities.
- OFAC and FinCEN advisories on this typology for current, regulator-endorsed indicators. Check the latest versions directly; indicators evolve with the scheme.
If you only do one thing this quarter, run a link-analysis pass on your existing customer base for shared devices and contact data. It's an effective way to determine if your clean-screening accounts are truly clean.





