Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› What are the signs that a browser is…
Cyber Security

What are the signs that a browser is being used for hidden cryptocurrency mining?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Cyber Security

Common indicators include a fan spinning up unexpectedly, sustained high CPU usage while visiting certain sites, sluggish device performance, and browser activity that continues after the visible tab or window is closed. Those symptoms do not prove mining on their own, but together they are strong signals that a site may be running scripts that are abusing local processing power.

What browser-based cryptomining looks like on the endpoint

Browser mining is usually visible first as a performance problem, not a browser error. The practical signal is a device that suddenly behaves as if a heavy background workload has started, even though the user only opened a normal-looking site. That is why the strongest clues are behavioural: fan noise, sustained CPU load, and a browser process that keeps consuming resources longer than the page should.

Because the activity runs inside a browser session, users often miss it until the machine feels “hot” or unresponsive. The mining code may be embedded in a page, delivered through an ad script, or triggered by a compromised site component, so the browser can appear ordinary while the endpoint continues working hard in the background.

Which symptoms are most worth trusting?

Single symptoms are weak indicators. A laptop fan can spike for many legitimate reasons, and a browser tab can be heavy because of video, web apps, or poor site code. What matters is the pattern: multiple performance changes that start soon after visiting a site, persist while that site is open, and do not resolve when you would expect the workload to stop.

Pay particular attention when the browser remains active after the visible tab or window is closed, because that suggests scripts, workers, or other page-associated processes are still executing. In practice, that persistence is more suspicious than a brief CPU spike, especially if the same site causes repeatable slowdowns across sessions or devices.

How do you separate cryptomining from other browser problems?

Start by comparing browser behaviour against normal workload patterns. Heavy video playback, online meetings, complex dashboards, and many browser extensions can all increase CPU use, so the question is whether the load is proportional to what the page is doing. If a simple page causes a large, steady resource drain, the balance shifts toward abuse of local processing power rather than ordinary browsing.

Also look for consistency across browsers and profiles. If one browser profile or one specific site repeatedly causes the same resource pattern, that is stronger evidence than a general device issue. Site-specific persistence, especially when paired with reduced responsiveness and abnormal cooling activity, is often what turns a suspicion into a meaningful investigation.

Risk and Threat Considerations

Browser-based mining is attractive to attackers because it monetises visitor hardware without needing a traditional infection chain or obvious file-based malware. The immediate risk is degraded performance and user disruption, but the broader concern is that the same delivery path can coexist with other malicious script activity, tracking, or post-exploitation behaviour.

Failure mechanism: The page loads script that continuously consumes CPU in the browser context, often using the site visitor’s resources until the tab, session, or script execution path is interrupted.

Impact: Users experience sluggish systems, higher power draw, reduced battery life, and in some cases longer-term investigation is needed to determine whether the site was merely abusive or part of a wider compromise.

Practitioner Guidance

What to verify: Correlate the time the slowdown began with the exact site, tab, or extension in use. If the issue disappears when the browser is closed or the site is isolated, that is a stronger operational clue than an isolated CPU reading. Check whether the same behaviour follows one site across different sessions or endpoints.

Decision rule: If the browser shows sustained high CPU on a site that should be lightweight, treat it as suspicious and isolate the browsing context before assuming the device is simply under load. If the problem is repeatable, review active extensions, recently visited pages, and any script-heavy content that could be hosting the workload.

Practitioner takeaway: The most useful signal is not “the fan got louder,” but “the browser kept doing work that the user did not ask for, and it kept doing it after the visible page should have stopped.”

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org