Picture a job seeker reading a listing for a customer-support role abroad. The company name looks familiar. The recruiter answers promptly. A video interview follows. Then the conversation moves to another messaging app. Travel and accommodation are arranged. The promises sound ordinary until the person reaches the destination and discovers the role is a lie.
Some people are then forced to carry out online fraud. They are victims of trafficking and forced criminality. They also become part of a cybercrime operation aimed at someone else. UN Human Rights Office
I keep seeing cybersecurity teams enter this story late. We see the fraudulent account, the suspicious payment, the burst of messages. The first control point may have been a job ad, a recruiter profile, or a familiar brand used to borrow credibility.
That is a security problem hiding in the hiring funnel.
Treat recruitment as trust infrastructure
Online job ads are not harmless content when a false offer can move a person toward forced labor. OHCHR's 2026 prevention guidance calls for targeted work to disrupt fraudulent recruitment and stronger evaluation of online job-ad practices. OHCHR, Breaking the Cycle
Platforms should make the identity behind a job listing legible. Verify that an advertiser is authorized to represent the named employer. Show a direct route to the employer's official careers page. Make it easy to report impersonation. Review repeat listings and recruiter accounts as a connected pattern, not as isolated posts.
Verification badges alone will not solve this. A badge can describe an account. It cannot guarantee that a specific job, recruiter, or travel arrangement is legitimate.
Give security a role before the fraud alert
For companies, brand impersonation in recruitment belongs in the external threat model. Ask who monitors fake job listings that use your name. Ask who can request a fast takedown after hours. Ask whether the HR team, security operations, legal, and platform contacts know how to preserve a post, recruiter handle, destination URL, and message history before it disappears.
The response has to protect the job seeker too. Do not ask someone to label themselves a trafficking victim before a report receives attention. Do not turn recruitment screening into broad surveillance of applicants. Keep sensitive information limited to the people who need it, and offer a clear path to qualified support when a person may be at risk.
The right design makes help possible without demanding a full account of someone's trauma in a form.
Three actions I want this quarter
First, inventory the places where your company recruits and the public accounts authorized to speak for it. Include social platforms, job boards, staffing partners, and regional affiliates.
Second, set an owner and response time for fraudulent recruitment reports. Test the path with a realistic impersonation example. Preserve the evidence. Confirm who has the authority to contact the platform and when.
Third, measure repeat abuse and response quality. Track how long it takes to review a report, how often a removed listing returns under a new account, and whether the job seeker receives a useful safety message. A takedown count alone tells me very little.
The UN Human Rights Office's 2026 work calls for better evaluation of fraudulent online recruitment and survivor-informed prevention. That is a reminder for technology leaders: useful controls need to be tested against how people actually encounter these offers, not how we imagine a clean report will arrive. OHCHR, Breaking the Cycle
I want CISOs to put recruitment channels on the risk map before the first suspicious payment arrives. A worker promised a job should not have to become a threat analyst to stay safe. Platforms and employers have more visibility and more power to interrupt the deception.
That is the prevention gap I am watching this quarter. Fellow CISOs and platform leaders, who owns a deceptive job-ad response when the recruiter is not on your payroll?
Lekshmy Sankar, PhD