Back to all blogs
Learn what a laptop farm is, how it works in remote employment fraud, its warning signs, cybersecurity risks, and ways organizations can prevent it.
A company hires a remote software developer, completes its onboarding checks, and ships a laptop to the address provided. The device connects from an expected location, security software remains active, and assignments arrive on time. Everything appears normal. However, the person controlling that laptop may be somewhere else, using an identity or working arrangement the employer has never verified.
This is the problem behind laptop farms. In employment fraud, a facilitator hosts company laptops while undisclosed individuals operate them remotely. The arrangement can make a worker appear to be based in an approved location even when the person performing the job is elsewhere. It can also conceal who actually has access to the employer's systems.
The threat has appeared in documented criminal investigations. In July 2025, the U.S. Department of Justice reported that a scheme involving a laptop farm and fraudulent remote IT employment generated more than $17 million in illicit revenue. The scheme involved remote IT positions at more than 300 U.S. companies, demonstrating how trusted equipment can help sustain a larger deception.
For employers, the difficult question is not simply whether a company laptop is genuine, secure, or connecting from the right address. It is whether the person operating that device is the individual the organization interviewed, hired, and authorized to perform the work. A trusted endpoint cannot establish that identity on its own.
The term can also describe coordinated online account activity, although not every multi-device arrangement involves fraud. Investigators must distinguish legitimate operations from unauthorized activity using reliable evidence.
This guide explains what a laptop farm is, how it works, real-world risks, warning signs, detection measures, and security practices that support responsible prevention and investigation. It also distinguishes legitimate arrangements from circumstances requiring further verification.
What Is a Laptop Farm?
In remote employment fraud, a laptop farm is an arrangement in which a facilitator receives and hosts company-issued computers so that unauthorized individuals can operate them remotely. The physical laptops remain in locations expected by employers, while the people actually controlling them may be elsewhere.
This allows the laptop's visible location to differ from the actual operator's location. An employer may see activity coming from its own managed laptop on a familiar domestic connection, even though an undisclosed individual is using that device from another country. Several companies' devices may be hosted together, but a large room filled with laptops is not required.
The term is also sometimes used more broadly for groups of physical computers supporting coordinated online account activity. In either context, the central concern is whether the devices help conceal who is actually conducting the activity. Legitimate device-testing facilities, disclosed subcontracting, and approved remote technical support should not be treated as fraudulent merely because they involve multiple computers.
Example: A business hires a developer who claims to work locally. Its laptop is delivered to a facilitator's home, where it remains powered on while an undisclosed overseas operator accesses it remotely and completes the assigned work.

How Does a Laptop Farm Work?
A laptop farm used for employment fraud connects a misleading hiring arrangement with a physical company device and an operator who is not properly disclosed or authorized. Work may continue normally, making the arrangement difficult to recognize through productivity measures alone.
Step 1: An Applicant Secures a Remote Role
An applicant obtains a position using stolen, borrowed, falsified, or otherwise misleading identity information. In some schemes, the identity listed in the application does not belong to the individual who will perform the work. In others, the primary deception concerns the worker's location or unauthorized delegation.
A person may have genuine technical skills while still misrepresenting their identity or employment arrangement. Passing an assessment therefore does not establish that all hiring information is accurate.
Step 2: A Facilitator Receives the Equipment
The employer sends its laptop to an address associated with the apparent employee. A facilitator receives and maintains the computer, helping create the impression that the worker is physically based there.
A successful delivery confirms that the equipment reached an address. It does not prove that the named employee lives there or personally holds the device.
Step 3: The Device Becomes Remotely Accessible
An undisclosed operator connects to the hosted laptop through remote-access software or external hardware. The organization may observe activity from the company computer rather than directly from the operator's personal device.
Remote control may occur through software or internet-connected keyboard, video, and mouse (KVM) equipment. The laptop remains at the facilitator's location while someone elsewhere operates it. Because external hardware may leave no installed application to identify, software checks alone may not reveal the arrangement.
Step 4: Work and Access Continue Under the Apparent Identity
The operator completes assignments and uses the permissions attached to the employee account. The facilitator may keep the laptop connected, maintain access, and handle equipment-related requests.
From an employer's perspective, timely work and routine account activity can make the arrangement appear normal. Effective detection depends on comparing identity verification, equipment custody, and authorized access rather than relying solely on performance.
Laptop Farm Examples and Use Cases
Laptop farms can support different forms of deception. The following illustrative scenarios distinguish false identities, concealed working locations, unauthorized proxy access, and coordinated account misuse. They are examples of possible arrangements, not claims that every multi-device setup is fraudulent.
1. Remote Employment Under a False Identity
In this scenario, an employer believes it has hired one individual, but a different, undisclosed person performs the work. The facilitator hosts the company laptop and helps maintain the apparent employee's presence.
The hiring information might involve a stolen identity or fabricated professional details. The laptop farm then supports the deception after onboarding by providing a device at an expected address. Because completed assignments can appear legitimate, the difference between the named employee and the actual operator may remain unnoticed.
Example: A company hires a remote engineer based on an application and interview. Its equipment is shipped to a domestic address, but another person abroad controls the laptop and submits work under the hired identity.
2. Concealing a Worker's Actual Location
The deception may concern location rather than identity. The individual doing the work can be the person named in the employment agreement but may be operating from a location the employer has not approved.
Keeping the laptop at an expected address can make a basic IP-location check misleading. However, an unauthorized change in working location does not automatically establish identity theft, data theft, or malicious intent. Employers should first establish the applicable location requirements and determine whether an approved move, temporary travel, or documented technical arrangement explains the discrepancy.
Example: An employee approved to work from one country leaves a company laptop with a facilitator there and accesses it from another country without obtaining the approval required by the employer.
3. Unauthorized Proxy Access to Company Devices
A legitimate employee or contractor may allow another person to use a company device and complete work without disclosing that arrangement. Unlike false-identity hiring, the original worker may have been hired legitimately.
The security problem arises when someone who has not been authorized can view confidential information or act through another person's account. Approved subcontracting normally requires documented responsibilities and appropriate access controls. Secretly sharing an active session removes that accountability.
Example: A contractor lets an unapproved assistant remotely operate a hosted company laptop to resolve support tickets. The assistant can now view customer records even though only the contractor was granted access.
4. Operating Multiple Fraudulent Accounts
Outside employment fraud, the term laptop farm can describe multiple physical devices used to operate accounts that appear independent but are centrally coordinated. Possible abuses include repeated promotional claims or manipulated platform engagement.
Using genuine laptops may make coordinated activity harder to identify through checks aimed only at obvious automation. Nevertheless, the number of devices does not prove misconduct. Testing labs, shared offices, and training facilities routinely operate many computers.
Example: A group controls several devices and separate account identities to repeatedly claim a promotion restricted to eligible new customers, presenting the claims as unrelated transactions.
Why Do Laptop Farms Matter in Cybersecurity?
A laptop farm can let an unauthorized person operate through devices and accounts that the organization already recognizes as legitimate. The resulting gap between device trust and operator trust can affect identity assurance, confidentiality, and financial security.

1. False Trust in Company-Issued Devices
A managed laptop may have encryption enabled, security software running, and the latest updates installed while being controlled by an individual the company has not approved. These controls protect the endpoint but do not independently verify who is operating it.
Organizations therefore need reliable equipment-custody records and access procedures that establish both the device's security status and the authorization of the person using it.
Example: A company laptop passes routine compliance checks, but an undisclosed operator uses its active session to view internal project documents.
2. Unauthorized Access to Sensitive Information
An unauthorized operator may gain access to the permissions available through the apparent employee's account or active session. Depending on the role, this may include source code, customer records, internal communications, and financial information.
The risk becomes more serious when broad permissions are granted during onboarding or expanded without review.
Example: A newly hired developer receives access to repositories unrelated to the assigned project, allowing an undisclosed operator to view information beyond the worker's legitimate responsibilities.
3. Identity Fraud and Financial Losses
Organizations may incur costs through fraudulent wage payments, investigations, account recovery, equipment replacement, and reviews of potentially exposed information. If stolen identities were used, the people impersonated may also face inaccurate employment or tax records.
Employers should separate the innocent identity owner from the person responsible for the deception and avoid assuming that financial or data theft occurred without supporting evidence.
Example: After uncovering unauthorized remote access, a company must revoke sessions, recover equipment, examine account logs, and determine whether confidential files were accessed or copied.
Why Traditional Security Checks Can Miss Laptop Farms
Conventional security controls still matter, but each one answers a specific question. Problems arise when a successful check is treated as proof that the entire hiring and working arrangement is legitimate.
Security Check | What It Helps Establish | What It May Leave Unresolved |
|---|---|---|
IP geolocation | Approximate location of the visible connection | Where the person remotely controlling the laptop is actually located |
Device compliance | Whether the endpoint meets configured security standards | Whether its current operator is authorized |
Multifactor authentication | Whether the required authentication factors were presented | Whether onboarding identity was genuine or an authenticated session was subsequently shared |
Background screening | Whether selected background claims can be verified | Whether the screened individual continues to perform the work |
Skills assessment | Whether someone demonstrated the tested skills | Whether that person is the ongoing operator of the company device |
Performance review | Whether work output meets expectations | Whether identity, location, and access arrangements remain authorized |
Warning Signs of Laptop Farm Activity
Laptop farm activity can be difficult to identify because the company laptop may remain online, pass security checks, and produce expected work. Warning signs often emerge when hiring information, equipment records, and account activity do not fit together. These inconsistencies should prompt verification, since many also occur in legitimate remote work.
Unexplained equipment redirection: Delivery details change shortly before dispatch, or an employee repeatedly requests shipment to addresses with no clear connection to their approved working arrangement. Requests to send equipment to an undisclosed third party deserve clarification, particularly when the explanation conflicts with onboarding records.
Inconsistent identity information: Names, employment records, contact details, or verification documents conflict across recruitment and onboarding. A discrepancy becomes more concerning when the applicant provides contradictory explanations or the supporting information cannot be independently verified. Name changes and administrative errors should be considered before drawing conclusions.
Unapproved remote-control activity: Remote-access software, unexplained installations, or connections appear outside documented support arrangements. Security teams should check whether the activity has an approved business purpose and identify who initiated it. Hardware-based remote access may require additional investigation because it may leave no remote desktop application on the laptop.
Unclear device custody: The employee cannot clearly explain where the company laptop is kept, who has physical access to it, or why another person manages its delivery and availability. An undisclosed third party repeatedly handling equipment may indicate that the device is being hosted separately from the person performing the work.
Multiple connected anomalies: Apparently unrelated workers share equipment destinations, phone numbers, or other contact details alongside unresolved identity discrepancies. These overlaps become more useful when examined together. A shared address alone may reflect a household, coworking space, or approved staffing arrangement.
Unexpected account behavior: An account requests permissions unrelated to the employee's responsibilities, accesses unfamiliar projects, or shows activity inconsistent with the assigned role. These events can have ordinary explanations, but they warrant closer review when combined with concerns about identity, device custody, or unauthorized remote access.
Repeated unexplained changes: Frequent changes to addresses, payment details, contact information, or other employment records create a pattern that the employee cannot reasonably explain. Teams should compare these changes with approved relocation, payroll, and contractor arrangements rather than treating each update as suspicious by itself.
Difficulties confirming the working arrangement: Routine verification requests repeatedly produce contradictory answers about who performs the work, where it takes place, or who controls the equipment. The concern is the unresolved inconsistency, rather than a preference for written communication, scheduling difficulty, or a request for an accessible verification method.
How Organizations Can Detect and Prevent Laptop Farms?
Reducing laptop farm risk requires coordination between recruiting, human resources, IT, security, and payroll teams. The goal is to connect hiring identity, equipment custody, and ongoing access rights so important inconsistencies are investigated before they lead to greater exposure.

1. Verify Candidate Identity Throughout Hiring
Define what hiring teams need to establish: who the candidate is, who will perform the role, what qualifications matter, and which working locations or subcontracting arrangements are approved. Apply comparable verification standards to comparable positions.
Verify material employment and education claims using independently obtained contact information. Maintain appropriate continuity between the person verified during hiring and the individual completing onboarding. Provide reasonable alternatives for accessibility needs and follow applicable privacy and employment rules.
Key actions:
Assign responsibility for reviewing identity discrepancies.
Verify material experience, qualifications, and work authorization where required.
Document approved locations and third-party working arrangements.
Establish an escalation process for concerns that remain unresolved.
2. Validate Equipment Delivery and Device Custody
Treat equipment delivery as part of onboarding, not simply a shipping task. Maintain asset records linking each device to an assigned worker, authorized destination, and delivery confirmation.
Review material address changes before dispatch. Establish who may physically hold or operate a laptop and how employees should report relocation, repairs, approved support, loss, and returns. These records help distinguish normal equipment transfers from undisclosed third-party hosting.
Key actions:
Confirm shipping details and the assigned employee before dispatch.
Review significant last-minute delivery changes.
Investigate repeated destinations across unrelated hires when other evidence warrants review.
Record approved transfers, repairs, returns, and device-custody exceptions.
3. Monitor Unauthorized Remote Access
Establish which remote-support tools are permitted, who may operate them, and when access must be recorded. Approved technical support should have identifiable operators and a documented business purpose.
Review unexplained remote sessions and unauthorized installations. Because external KVM hardware may not appear in a software inventory, risk-appropriate checks should also consider physical equipment and device custody. Monitoring practices should respect employee privacy, accessibility, and applicable legal obligations.
Key actions:
Restrict installation of unapproved remote-access software where appropriate.
Maintain a documented remote-support approval process.
Investigate connections that lack an authorized business purpose.
Review unexplained changes in device configuration or physical custody.
4. Review Account, Device, and Session Activity Together
Create a controlled process for reviewing related evidence held by different departments. HR may have an unresolved identity mismatch, IT may have recorded a delivery diversion, and security may have observed an unusual remote session. The combination can be more informative than any event on its own.
Monitor only what is justified for security and employment purposes. Restrict access to records, establish suitable retention periods, and document who is responsible for cross-team review.
Key actions:
Link employee, account, device, and shipping records where appropriate.
Examine combinations of anomalies rather than treating isolated signals as proof.
Review privileges when employees change roles or responsibilities.
Assign an investigation owner to coordinate relevant teams.
5. Investigate Concerns Before Taking Action
Establish a response process before a suspicious case arises. The process should cover evidence preservation, immediate access risk, clarification requests, escalation, and proportionate decisions.
If active compromise is reasonably suspected, security teams may need to restrict access while preserving logs and relevant records. Employment decisions should follow an evidence-based review and offer an appropriate opportunity to explain discrepancies. HR, security, and legal stakeholders should be involved when needed.
Key actions:
Preserve relevant hiring, equipment, account, and communication records.
Assess whether temporary access restrictions are necessary.
Seek clarification through verified contact channels.
Document findings and the rationale for each decision.
Address confirmed security exposure and improve the affected controls.
These measures work best when organizations consistently connect candidate identity, device custody, account permissions, and access activity across the employment lifecycle.
Conclusion
A laptop farm can allow people to operate company computers remotely while concealing who is actually using them or where the work is being performed. In employment fraud, this arrangement can make an unauthorized operator appear to be a legitimate worker at an approved location.
Preventing laptop farm fraud requires more than verifying a device's security status or checking its IP address. Organizations should connect candidate identity verification, equipment custody, account permissions, and access monitoring to identify inconsistencies and investigate potential risks.
By applying consistent security controls and evidence-based investigations, employers can reduce unauthorized access and remote employment fraud while protecting legitimate remote working arrangements.





