
By the Jobbers Editorial Team · Published November 2026 · Last reviewed November 2026
Most freelancers picture a hacker as someone breaking through firewalls. The reality is far less dramatic. Usually it’s a message that looks like a new client, a zip file called “project_brief_final,” or a password you used on a forum years ago that ended up in a breach. Nobody breaks in. You get asked to open the door, and the request looks completely normal.
That matters because a freelancer has no IT department behind them. You are the help desk, the security team and the person who explains to a client why their files leaked. This guide covers the mistakes that actually get freelancers compromised in 2026, the numbers behind them, and the habits that close those gaps without turning your workday into a security project.
Important notice: The statistics and regulatory details in this article come from the public sources linked throughout and were checked in November 2026. Figures, guidance and platform policies change over time. Please verify any number or data point with the original source before relying on it for legal, financial, insurance or contractual decisions. This article is general information, not legal or professional security advice.
The 2026 threat picture in numbers
Before getting to the mistakes, it helps to see how big the problem is. These figures come from the main official and industry reports published this year.
| Data point | Figure | Source |
|---|---|---|
| Internet crime complaints received by the FBI in 2025 | 1,008,597 (up from 859,532 in 2024) | FBI IC3 2025 Internet Crime Report |
| Reported losses to the FBI in 2025 | About $20.9 billion, a 26% increase on 2024 | FBI IC3 2025 Internet Crime Report |
| Most reported crime type to the FBI in 2025 | Phishing/spoofing (191,561 complaints) | FBI IC3 2025 Internet Crime Report |
| Complaints mentioning AI in 2025 | 22,364 complaints, about $893 million in losses | FBI IC3 2025 Internet Crime Report |
| Fraud reported to the FTC in 2025 | 3 million reports, $15.9 billion in losses | FTC testimony, March 2026 |
| Breaches involving a human element | 62% | Verizon 2026 DBIR |
| Top initial access vector in breaches | Vulnerability exploitation (31%), ahead of credential abuse (13%) | Verizon 2026 DBIR |
| Breaches involving ransomware | 48% | Verizon 2026 DBIR |
| Reduction in account-compromise risk with MFA | 99.22% | Microsoft Research (2023) |
Two things are worth noticing. First, the FBI’s Internet Crime Complaint Center received more than a million complaints in a single year for the first time, and phishing was again the most reported crime type. Second, the Verizon 2026 Data Breach Investigations Report found that exploited software vulnerabilities overtook stolen credentials as the most common way into a breach, the first time that has happened in the report’s 19 editions. Put simply: tricking people and exploiting unpatched software are the two big doors. Both are mostly within your control.
Why freelancers are an attractive target
Freelancers sit at a convenient junction for attackers. You hold access to several clients’ systems, files and accounts at once. You talk to strangers every week as part of normal business. You download files people send you. You get paid online, often internationally. And you usually manage all of this on one laptop that also handles your personal email and banking.
Attackers know that compromising one freelancer can give them a route into several companies. Verizon’s 2026 report found that breaches involving a third party rose to 48% of the total. From a client’s point of view, a contractor with a compromised laptop is a third-party risk.
The most common security mistakes freelancers make
1. Running a “client’s” code or test project on your main machine
This one deserves the top spot because it hits developers specifically, and it is surprisingly effective. A recruiter or client contacts you with a well-paid contract and asks you to complete a short coding task: clone a repository, fix a bug, add a feature, run npm install. The project contains hidden malware. Within minutes it can collect saved browser passwords, session cookies and crypto wallet data.
This is a documented, ongoing campaign. ESET researchers have described a North Korea-aligned operation, which they track as DeceptiveDevelopment, that targets freelance developers through fake recruiters on job-hunting and freelancing sites and uses trojanized coding challenges to steal wallets and login data. In 2026, Sophos also warned about a group using LinkedIn, Upwork and Fiverr to deliver malware through fake interviews.
How to avoid it:
- Never run unfamiliar code on the machine where your password manager, email and banking live.
- Use a disposable virtual machine, a dev container or a cloud sandbox for any test project from someone you haven’t worked with before.
- Read
package.jsonscripts, install hooks and any obfuscated files before running anything. - Be wary when a “recruiter” insists on a specific repo, a specific video-call app you have to download, or a tight deadline.
2. Opening attachments and links because they look like work
Freelancers get unexpected files all the time: briefs, invoices, contracts, reference images. Attackers exploit that. Common lures include a “brief” in a password-protected zip (so email scanners can’t inspect it), a shortcut file disguised as a PDF, a document that asks you to “enable content,” or a link to a shared drive login page that is actually a copy.
Phishing remained an initial access vector in 16% of the breaches Verizon analyzed, and its 2026 report notes that in phishing simulations, median click rates for mobile-focused methods (voice and text) were 40% higher than for email. That fits what freelancers see: the WhatsApp message from a “client,” the SMS saying your platform account is suspended.
How to avoid it:
- Preview files in the browser or a cloud viewer before downloading them.
- Turn on file extensions in your operating system so “brief.pdf.lnk” can’t hide.
- If a link asks you to log in, close it and go to the site by typing the address yourself.
- Treat “urgent,” “account suspended” and “payment on hold” messages as suspicious until verified.
3. Reusing passwords across platforms
Freelancers often juggle dozens of accounts: marketplaces, email, payment apps, cloud storage, design tools and client CMS logins. Reusing a password across them means one breach anywhere can unlock everything. Attackers run leaked email and password pairs against popular services automatically; this is called credential stuffing.
The current standard from the US National Institute of Standards and Technology, NIST SP 800-63B-4, finalized in 2025, moved away from forced complexity rules and periodic resets. It requires a minimum of 15 characters when a password is the only factor protecting an account (8 when combined with MFA), and it says passwords should be changed when there’s evidence of compromise, not on a schedule.
How to avoid it:
- Use a password manager and let it generate a unique, long password for every account.
- Check whether your email appears in known breaches on Have I Been Pwned.
- Store client credentials in a shared vault or the client’s own access-management system, never in a notes app, spreadsheet or chat thread.
4. Skipping multi-factor authentication (or relying only on SMS)
If you do one thing after reading this, turn on MFA for your email first. Your inbox receives the password-reset links for almost everything else, so whoever controls it controls the rest.
The evidence is strong. A Microsoft Research study of Azure Active Directory accounts showing suspicious activity found that MFA reduced the risk of compromise by 99.22% across the population, and by 98.56% even where credentials had already leaked. The same study found that authenticator apps outperformed SMS codes, although both beat having no second factor.
How to avoid it:
- Enable MFA on email, freelance platforms, banking, payment apps, cloud storage and your domain registrar.
- Prefer passkeys, a hardware security key or an authenticator app over SMS where the service allows it.
- Save your backup codes offline. Losing your phone shouldn’t lock you out of your business.
- Never approve a login prompt you didn’t start, even if it keeps popping up.
5. Falling for payment and overpayment scams
Not every hack involves malware. Some just take your money. The classic version for freelancers is the overpayment scam: a new client “accidentally” pays you more than agreed, then asks you to refund the difference by wire, crypto or gift cards. The original payment bounces or gets reversed days later. The FTC’s guidance on fake check scams is blunt: if someone you don’t know sends you money and asks you to send some back, it’s a scam.
Job and work-opportunity scams are a growing category too. The FTC reported that consumers filed 3 million fraud reports in 2025 with $15.9 billion in losses, up from just over $12 billion the year before. Earlier FTC data showed reported losses to job and employment agency scams alone rising from $90 million in 2020 to $501 million in 2024.
How to avoid it:
- Never refund an “overpayment.” Ask the client to cancel and resend the correct amount instead.
- Agree payment terms in writing before work starts: amount, currency, method, milestones and deadlines.
- For new clients, ask for an upfront deposit or work in small paid milestones.
- Be skeptical of anyone who asks you to pay a fee for “equipment,” “training” or “account activation” before you can start.
6. Putting off software updates
“Remind me tomorrow” is how a lot of breaches begin. Verizon’s 2026 report found that exploiting vulnerabilities is now the leading initial access vector in breaches, at 31%. For a freelancer, the exposed software is usually the operating system, the browser, browser extensions, plugins on a WordPress site you maintain, and old apps you forgot were installed.
How to avoid it:
- Turn on automatic updates for your OS, browser and phone.
- Remove browser extensions and apps you no longer use. Each one is something that can be compromised.
- If you manage client websites, keep core, themes and plugins updated, and agree in your contract on who is responsible for maintenance.
7. Having no backups (or only one)
Ransomware was involved in 48% of the breaches in the 2026 DBIR. For a solo professional, losing access to your files right before a delivery deadline can hurt your reputation more than any ransom. Hardware failure and theft can be just as damaging.
How to avoid it:
- Follow the 3-2-1 approach: three copies of important data, on two different types of storage, with one kept offsite or in the cloud.
- Keep at least one backup disconnected or versioned so ransomware can’t encrypt it too.
- Actually test a restore once in a while. A backup you’ve never restored is only a guess.
8. Oversharing identity documents and personal data
A “client” asks for a passport scan for “compliance,” a selfie holding your ID, or your bank login “to set up payroll.” Identity documents are valuable to fraudsters. Researchers covering the fake-recruiter campaigns have reported that stolen developer identities are fed into fraudulent remote-IT-worker schemes, where impostors get hired using a real person’s name and documents.
How to avoid it:
- Share ID only when there is a legitimate, verifiable reason, and only after confirming who the client is.
- Add a visible note across any ID copy stating who it’s for, the purpose and the date.
- Never share banking passwords or one-time codes. No legitimate client needs them.
9. Trusting voices, videos and messages without verifying
AI has made impersonation cheap. For the first time, the FBI’s 2025 report included a section on AI, covering 22,364 complaints that referenced it and roughly $893 million in reported losses. For freelancers, this shows up as cloned voice notes from a “client” asking to change payment details, deepfaked video calls, and AI-polished phishing with no spelling mistakes left to give it away.
How to avoid it:
- Verify any change to payment details, deadlines or access through a second channel you already trust.
- Agree on a simple verification step with long-term clients, such as a call back to a known number.
- Don’t rely on writing quality to spot phishing anymore. Check the sender, the domain and the request itself.
10. Mixing client work, personal life and public Wi-Fi
One laptop shared with family, the same browser profile for client CMS logins and personal browsing, and working from a café hotspot. None of this is unusual, and all of it increases the impact of a single mistake.
How to avoid it:
- Use a separate user account or browser profile for client work.
- Encrypt your disk (BitLocker on Windows, FileVault on macOS) and set a short auto-lock.
- On public Wi-Fi, prefer your phone’s hotspot or a reputable VPN, and never enter logins on a portal page that appears after connecting.
- When a contract ends, ask the client to remove your access, and delete files you no longer need to keep.
A 15-minute security checklist for freelancers
If the list above feels like a lot, start here. Most of this takes one sitting.
- Turn on MFA for your main email account (authenticator app or passkey).
- Install a password manager and change your email and banking passwords to unique ones.
- Enable automatic updates on your laptop, phone and browser.
- Turn on full-disk encryption and a screen lock.
- Set up an automatic cloud backup of your work folder.
- Write one rule on a sticky note: “No unknown code on this machine. No refunds of overpayments.”
For more structured guidance, the UK’s National Cyber Security Centre Cyber Aware programme and CISA’s Secure Our World campaign both offer free, practical advice aimed at individuals and small businesses.
What to do if you’ve been hacked
Speed matters more than perfection. In rough order:
- Secure your email first, from a clean device. Change the password, sign out all sessions, check forwarding rules and recovery options, and turn on MFA.
- Change reused passwords anywhere you used the same or a similar password.
- Disconnect the infected device from the internet if you suspect malware, and don’t use it for logins until it has been cleaned or reinstalled.
- Tell affected clients through a channel the attacker can’t access, especially if client credentials or files may be exposed. Depending on where you and your clients are based, data-protection laws such as the GDPR may impose notification duties; check with the client or a qualified advisor.
- Call your bank or payment provider if money or payment details are involved.
- Report it: in the US to ic3.gov or ReportFraud.ftc.gov, in the UK to Action Fraud, in France to cybermalveillance.gouv.fr, or to your national authority elsewhere. Also report fake accounts to the platform where they contacted you.
Staying safe while finding work on Jobbers
On jobbers.io, freelancers and clients connect directly. The platform does not take a commission on your earnings, and both sides discuss and agree payment terms themselves. For many freelancers that is the main appeal: you keep what you earn and choose the arrangement that suits the project.
That freedom comes with responsibility. Since the platform doesn’t sit between you and the client’s money, the habits in this guide matter even more. In practice, freelancers who do well on direct-payment platforms tend to:
- Confirm the client’s identity and company details before starting work.
- Put scope, price, payment method and milestones in writing.
- Ask for a deposit or milestone payment from new clients.
- Refuse to run unknown code, install unfamiliar software or refund overpayments.
- Report suspicious profiles or messages to the platform so others are protected too.
If you are looking for freelance jobs where you keep 100% of what you agree with the client, you can build your profile, browse projects and talk to clients directly (proposals use the platform’s credit system). Just bring your security habits with you.
Final thoughts
Freelancer security isn’t about becoming a cybersecurity expert. It comes down to a few habits: unique passwords in a manager, MFA everywhere, updates switched on, backups that actually work, and a healthy suspicion of anything that asks you to run, open, pay or share in a hurry. The attackers are counting on you being too busy to check. A thirty-second pause before you click is usually enough to stop them.
Frequently Asked Questions
How do freelancers usually get hacked?
Most freelancer compromises start with a person being tricked rather than a system being broken. The usual entry points are phishing messages that imitate a client or a platform, malicious files or code sent as part of a fake job or coding test, reused passwords that leak in someone else’s breach, and devices that haven’t been updated. Verizon’s 2026 DBIR found a human element in 62% of the breaches it analyzed.
Are fake coding tests really used to hack freelance developers?
Yes. Security researchers at ESET and Sophos have documented North Korea-linked groups that pose as recruiters on LinkedIn, Upwork, Fiverr, Freelancer.com and similar sites, then send a coding assignment hosted on GitHub or as an npm package. Running the project installs malware that steals browser passwords and cryptocurrency wallets. Review unfamiliar code before running it, and run it only inside a disposable virtual machine or container.
Is two-factor authentication really worth it for a solo freelancer?
Yes. A Microsoft Research study of Azure Active Directory accounts found that MFA reduced the risk of account compromise by 99.22% across the population studied, and by 98.56% for accounts whose passwords had already leaked. An authenticator app, passkey or hardware key is stronger than SMS codes, but even SMS is far better than nothing.
How long should my passwords be in 2026?
NIST’s current guidance (SP 800-63B-4, finalized in 2025) requires at least 15 characters when a password is the only thing protecting an account, and at least 8 when it is combined with a second factor. Length matters more than symbols. The simplest approach is to let a password manager generate a unique, long password for every account.
What is the overpayment scam targeting freelancers?
A ‘client’ sends a check or payment for more than the agreed amount, then asks you to refund the difference by wire transfer, crypto or gift cards. The original payment later bounces or is reversed, and you lose the refund. The FTC’s rule of thumb applies: if someone you don’t know sends you money and asks for some of it back, it is a scam.
Should I send a copy of my ID or passport to a new client?
Generally no, unless there is a clear legal reason (for example a regulated onboarding process) and you have independently verified who the client is. Identity documents are valuable to fraudsters, and researchers have reported fake recruiters harvesting developers’ identities for fraudulent remote-work schemes. If you must share one, watermark the copy with the recipient and purpose and send it through a secure channel.
Is public Wi-Fi safe for client work?
Most websites now use HTTPS, which protects the content of your traffic, so public Wi-Fi is less dangerous than it used to be. The bigger risks are fake hotspots, captive portals that ask for credentials, and shoulder surfing. Use your phone’s hotspot or a reputable VPN for sensitive work, and never enter platform or banking logins on a portal page that appears after connecting.
What should I do in the first hour after my account is hacked?
From a clean device, change the password of your email account first, because it controls the reset links for everything else. Then sign out all sessions, turn on MFA, check email forwarding rules and recovery details, and change passwords on any account that shared the same password. Warn your clients through a channel the attacker doesn’t control, contact your bank if payments are involved, and report the incident (for example to ic3.gov in the US or Action Fraud in the UK).
Does Jobbers.io handle payments between freelancers and clients?
No. Jobbers.io does not take a commission on work, and freelancers and clients discuss and agree payment terms directly. That gives you more freedom and keeps your full earnings, but it also means you are responsible for choosing a safe payment method, using written agreements and milestones, and checking who you are working with before starting.
How can I tell if a freelance client is fake?
Common warning signs: pressure to move quickly to another app, vague project details paired with unusually high pay, requests to install software or run code before any contract exists, payment offered before work starts and paired with a refund request, and email domains that don’t match the company’s real website. Verify the person through an independent channel such as the company’s official site or a known contact before sharing files, logins or documents.
Sources
- FBI Internet Crime Complaint Center, 2025 Internet Crime Report (April 2026)
- Verizon, 2026 Data Breach Investigations Report (May 2026)
- Federal Trade Commission, testimony before the Joint Economic Committee (March 2026)
- Federal Trade Commission, How to spot, avoid and report fake check scams
- NIST, SP 800-63B-4 Digital Identity Guidelines: Authentication (2025)
- Microsoft Research, How effective is multifactor authentication at deterring cyberattacks? (2023)
- ESET Research, DeceptiveDevelopment targets freelance developers
- UK NCSC, Cyber Aware · CISA, Secure Our World
About this article: written and fact-checked by the Jobbers Editorial Team, which covers freelancing, platform safety and the business of independent work. Figures were checked against the primary sources listed above in November 2026. If you spot an outdated figure, let us know and we’ll review it.
Create your freelance profile
Join Jobbers and start applying to projects today. No commission.
