Can you get fired for using a mouse jiggler?
Yes, people have been fired for it. The clearest example is Wells Fargo, which in 2024 dismissed more than a dozen employees after a review found "simulation of keyboard activity creating the impression of active work." So the short answer is that this is possible and it has happened.
But the reason those people were let go is worth understanding, because it is not quite the reason most headlines imply. It was not that a jiggler is impossible to hide. It is that using one can breach a company policy, and breaching policy is what gets you fired.
Two different questions
"Can I get caught" and "can I get fired" are separate, and mixing them up is where people get the risk wrong.
- Detection is a technical question: can the tool be seen. That depends on what you use and what monitoring is installed, and we cover it in full in are mouse jigglers detectable.
- Termination is a policy question: does your employer treat "appearing active while away" as misconduct. This has almost nothing to do with the tool and everything to do with the rulebook you agreed to.
You can be fired without the jiggler ever being detected — for example, if output doesn't match the hours your activity log claims. And you can run a jiggler that is never noticed at a company that wouldn't have cared anyway. The tool is rarely the deciding factor.
What an employer can actually see
Most workplace monitoring does not watch your mouse for tell-tale patterns. It watches outcomes. The things a typical setup records:
- Active vs. idle time — which is the thing a jiggler is designed to influence.
- Which application is in the foreground, and for how long.
- Periodic screenshots, on some trackers.
- Actual work product — commits, tickets closed, calls handled, documents edited.
A jiggler moves the mouse. It does not open a document, write code, or answer a ticket. So the failure mode that gets people caught is almost never "the security team spotted a jiggler." It is a manager noticing that eight logged-in hours produced two hours of output.
Read the policy, not the forum threads
The document that matters is your own acceptable-use or remote-work policy. Look for language about "misrepresenting activity," "circumventing monitoring," or "unauthorized software." If any of that is in there and it's enforced, a jiggler is a policy breach regardless of whether it is ever detected, and the fact that it worked is not a defence.
This is also why the answer is genuinely different from job to job. A salaried role measured on deliverables, where nobody looks at an activity dashboard, is a completely different situation from a role where an idle-time metric feeds directly into performance reviews or pay. Same tool, very different risk.
Software vs. hardware changes detection, not the policy
If you've decided the risk is acceptable, the type of tool changes only the detection side of the equation:
- Software runs as a process on the machine, which an endpoint-monitoring agent that inventories running programs can in principle see. On a personal or lightly-managed machine that inventory usually isn't happening. The free tool on our homepage is the no-install starting point.
- A hardware dongle enumerates as an ordinary USB mouse, so there's no process on the PC to inventory. The Vaydeer S4 metal USB jiggler is the common pick here — driverless, with a physical on/off switch. The honest caveat, covered in software vs. hardware, is that a tightly-managed laptop can still refuse unknown USB devices, and hardware does nothing about the output-vs-hours problem above.
Neither one changes the policy question. A dongle that is never detected is still against the rules at a company that bans "simulating activity."
The lower-risk version of the same goal
A lot of jiggler use isn't about faking work at all — it's about a status light flipping to Away during a long build, a call, or ten minutes reading a document, and a manager reading that light as slacking. That's a presence problem, not a productivity one, and it's worth separating because the honest fixes carry no policy risk:
- Keep the screen awake while you read or present with a browser wake lock — see stopping Windows from sleeping.
- Understand why chat apps flip you to Away in the first place, in keeping your Teams status green.
Bottom line
- Yes, firings have happened — most notably at Wells Fargo in 2024.
- The trigger is almost always a policy breach, not the tool being technically detected.
- Read your acceptable-use policy. That document decides your real exposure.
- What gets people caught is output not matching logged hours — something no jiggler fixes.
- Hardware lowers detectability; it changes nothing about the rules.
We're not going to tell you what to do with your job. But be clear-eyed: the risk lives in your employment agreement far more than in the software, so read that first and decide from there.