Blog · Employee Monitoring

← All posts

How to Detect a Mouse Jiggler Fairly and Accurately

1 Nov 2026 · 9 min read · Employee Monitoring

Navy computer mouse on a pad with a magnifying glass beside it

A manager has the timesheet open. It says nine hours active. The sprint board says nothing moved all day. She has a message half typed that starts, "Were you actually working?" She should wait before sending it, because a moving cursor tells you the mouse moved. It does not tell you anyone worked.

Learning how to detect a mouse jiggler is useful, but a detection is only a lead. Treat every flag as a reason to ask a question, never as proof of a dishonest person.

This guide names the three types of jiggler and the evidence each leaves on Windows and Mac. It lists the honest cases that look like a jiggler but are not. Then it gives managers a calm path: talk first, judge output, fix the incentive, and correct the time record in the open.

Table of Contents

What a Mouse Jiggler Actually Is

A mouse jiggler fakes computer activity. There are three kinds, and each leaves different evidence.

  • Software jigglers are small programs that move the cursor or send fake input. They may show up as installed apps, startup items or running processes.
  • USB hardware jigglers plug in and act like a mouse. They can appear in USB and device records, but many look like an ordinary peripheral.
  • Physical movers nudge a real mouse. They leave no software trace and no odd device, so behaviour is the only clue.

On Windows, you can sometimes check device lists and process lists. On Mac, device lists help less, so detection leans on behaviour.

Why people use them

Most jigglers are an incentive problem before they are a discipline problem. Take an agency that pays by logged hours and marks staff "idle" after five minutes without input. A designer reading a long brief, or a developer waiting on a build, goes idle and loses paid time.

The rule rewards input, not work, so sooner or later someone plugs in a jiggler to supply the input. Remove the rule that punishes quiet work, and most of the reason for the device goes with it.

Why an idle timer misses them

An operating system keeps an idle clock. Any mouse input resets it, even fake input. So "active" on an idle report means input arrived. It does not mean work happened.

A jiggler is a signal about the setup. It is not automatic proof of a dishonest person.

How to Detect a Mouse Jiggler Step by Step

Detection uses two kinds of evidence. The data shows how the cursor behaves. The machine shows what is installed or plugged in. Use both, on company devices, and tell the employee you are checking.

Three signs in the data

  1. Perfectly regular movement. Same speed, same distance, same timing, in circles or straight back-and-forth paths. Real hands are uneven. Detection tools look for very low variation in speed and timing over a long, unbroken stretch of movement. Each tool sets its own limits, and there is no industry standard.
  2. Movement with no keyboard input. A cursor that moves for hours while nothing is typed, clicked or scrolled deserves a closer look.
  3. Activity with no app or window change. Real work usually changes something over a long stretch, such as a tab, a file or a window. How long is too long depends on the role. Support and data entry staff switch windows all day, so a short stretch in one window is odd. Developers and designers can stay in one window much longer, so give them more room. No single threshold should start a conversation. Ask when regular movement, no keystrokes and no window change line up, the stretch repeats across several days, and task updates show nothing for the same hours.

Cross-check other records

Compare the flagged interval with task updates, meetings, code commits and client messages. If the cursor moved but nothing else did, you have a lead.

Screenshots need honest handling. An unchanged screen shows that nothing changed. It does not prove a jiggler. Where your policy allows them, screenshot monitoring is one more piece of context, nothing more.

Check devices and software

Run these checks on a company-owned computer, under a policy that says you may.

On Windows:

  1. Open Device Manager. Expand "Mice and other pointing devices" and "Human Interface Devices". Look for a second mouse entry when only one mouse is in use, or a vendor name nobody recognises.
  2. Open PowerShell and run Get-PnpDevice -Class Mouse -PresentOnly. Each line is a pointing device Windows sees right now.
  3. Open Task Manager and go to the Startup apps tab. Look for jiggler apps such as Mouse Jiggler, Move Mouse or Caffeine. Check Settings, then Apps, then Installed apps for the same names.

On Mac:

  1. Open Activity Monitor and search for "caffeinate" or the same app names.
  2. Open System Settings, then General, then Login Items. Look for items nobody can explain.
  3. Open Terminal and run pmset -g assertions. It lists the processes keeping the Mac awake. A caffeinate entry means someone asked the Mac to stay awake. It does not move the cursor, and video calls create similar entries, so read it as a clue.

A hardware jiggler can pass as an ordinary mouse, but it still leaves traces you can check.

  • Read the USB IDs. In Device Manager, open the device's Properties, then Details, then Hardware Ids. Note the VID and PID values and look them up. A vendor that is not a known mouse brand is worth a question. On a Mac, open System Information and select USB to see the vendor ID.
  • Check the plug-in time. In Event Viewer, open Applications and Services Logs, then Microsoft, Windows, Kernel-PnP, then Configuration. A second HID entry that appears just before a suspicious stretch is a lead.
  • Compare people. Identical timing across several employees points to a shared device or setup. That is a policy problem, not one person's.

None of these settles the matter alone. Pair them with the behaviour signs above.

Why a Flag Is Not Proof

Many honest people look "quiet" or "too steady" for good reasons. Three cases trip flags most often, and each has a way to tell it apart from a jiggler.

  • Developers on a long build. The screen sits still and the keyboard is silent. But CPU load stays steady and a terminal process is running. A jiggler shows regular cursor motion with neither.
  • People on calls. Little typing, one window, a mouse that barely moves. The calendar shows a meeting, and a call app is open with audio in use. A jiggler leaves the cursor moving while no call exists.
  • Staff using accessibility tools. Head trackers, eye-gaze systems and switch devices can produce steady or odd input. The tool is usually known in advance, and the person still changes apps and files across the day. Ask before assuming, and never penalise someone for an adjustment they need.

Reading-heavy roles, a second monitor and approved automation can also trip a flag. A flag shows a pattern, and a pattern has more than one explanation. Review timestamps, keyboard and mouse breakdowns, and apps and URLs before you decide anything. That is a fair standard for everyone.

A simple decision path

Keep four steps separate, and do not skip ahead:

  1. Suspicious. A signal appears. Collect more context.
  2. Under review. The pattern repeats and other signals are absent. Set a review interval and look at the wider record.
  3. Confirmed. Someone found an unauthorised process or device, or the employee confirmed it. Keep the evidence and follow policy.
  4. Time correction. Only now decide whether paid time or invoices change.

How Clockade handles it

Clockade flags possible fake activity and known jiggler patterns on Mac and Windows, and it can show a "Still working?" check on the employee's screen. Admins make the call, not the software.

Here is what an admin sees. A stretch of the afternoon is marked as possible fake activity, with the pattern behind it, such as steady cursor movement and no keystrokes in one window. The admin then asks the employee and decides whether that stretch counts as work, counts in part, or comes off the record.

Clockade does not claim that idle data or optional screenshots can prove a jiggler. They are context for a conversation.

What a Manager Should Do Next

Start with people, not penalties. Four moves, in order, resolve most cases.

Talk first

Hold a private, calm and specific conversation. Say what you saw, then ask what was going on. Many cases end right there with a simple explanation, such as a long build or a call.

Judge output, not mouse movement

Agree on deliverables, deadlines and check-ins, so cursor activity stops being the measure. If you pay by hours, keep a note of the interval you reviewed and what you found.

Fix the incentive

If staff fear an "away" status or idle alerts, the rule is the problem. Set clear working hours. Allow breaks. Say what is and is not expected.

Handle the record openly

Document the interval. Decide with HR whether to adjust paid time or a client invoice. Never delete time silently, because a hidden edit damages trust more than the jiggler did.

A short policy checklist keeps this fair:

  • Tell staff what is tracked and when.
  • Keep screenshots optional where you can.
  • Limit who can see the data.
  • Set how long records are kept.
  • Name who reviews flags.
  • Give staff a way to appeal.

Knowing how to detect a mouse jiggler matters less than having this process ready before the first flag. If you bill clients by the hour, a silent edit to a flagged interval also changes an invoice, so write the process down first.

The workflow is simple. An admin opens the flagged interval, checks it against task updates, talks to the employee, and then corrects the time record with a visible note.

In Clockade, tracked hours from the Mac and Windows apps feed attendance, leave, payroll and invoices in one login, so that correction carries through to every record. You can start with Clockade to review flagged intervals before they become paid time or a billable hour.

Whatever tool you use, the rule is the same. Talk first, judge the output, and correct the record in the open. A flag earns a question, and the answer decides what happens next.

Frequently Asked Questions

Can an employer tell if a mouse jiggler is hardware or software?

Often, by behaviour and by device or process records. Software may show as a program or process, and hardware may show in USB logs. It is not always certain, so treat the result as a clue.

Does a USB mouse jiggler show up in Device Manager or endpoint logs?

It can. But many hardware jigglers look like a normal mouse, so a listing is a clue, not proof. Pair it with behaviour patterns before you act.

Can a jiggler keep a Teams or Slack status active?

Those apps use their own idle rules, so results vary by app and settings. Do not promise either way. Check how your own tools treat input.

Can employers detect a jiggler on a Mac?

Yes, mainly through behaviour patterns. Device lists are less useful on a Mac, so look at movement regularity, keyboard activity and app changes together.

Will screenshots prove someone used a jiggler?

Not alone. They show what was on screen. An unchanged screen is one signal to weigh with the others, and only where your policy allows screenshots.

Track real hours, not guesses.

Clockade turns your team's tracked time into attendance, leave, payroll and invoices. From $3 per person a month.

Start with ClockadeSee pricing

More from the blog