Threat library

Cryptominers: investigate resource abuse

Investigate suspected unauthorized mining by separating browser, installed-software and cloud activity, ordinary workloads, persistence and compromised access.

Unauthorized cryptocurrency mining uses computing resources without the owner’s informed permission. The concern is that use and the access behind it, not merely the existence of mining software. A miner someone deliberately runs is a different situation from one installed through a deceptive download or deployed using stolen cloud access.

Start by locating the activity: a browser task, installed software, or a cloud account. High CPU use, fan noise and a large bill are leads to investigate, not standalone mining verdicts. This guide covers desktop investigation on Windows and Mac and the point at which a cloud or organizational incident needs its responsible administrator. It is not a script for deleting every task with a mining-related name.

Decide which resources and access are affected

Record when the issue began, what was running, and any recent installer or security finding. Observe a normal task you already need; do not open a suspect file or revisit a suspicious site to recreate the activity. Active remote control or file damage needs urgent triage before performance investigation.

Where activity appearsEvidence to examineAppropriate investigation
A browser accounts for resource useKnown tabs, extensions and browser-task identityWebsite/extension behavior without revisiting risky content
An installed app or process remains busyOrigin, workload, timing and recorded security findingsPlatform-specific process and device assessment
Activity returns after restartStartup/app controller and recurring findingsPersistence investigation with supported controls
Cloud resources or bills change unexpectedlyAuthorized deployments, identity and resource recordsCloud owner, provider and incident-response process
High use corresponds to wanted processingKnown task progress and comparable ordinary useWorkload or performance troubleshooting first

The locations can overlap. A compromised device can expose credentials used elsewhere, while a cloud account can be misused even if the laptop is quiet. Do not treat an improvement in one resource display as a resolution of all associated access.

Rule in evidence rather than treating high use as proof

Use high-CPU diagnosis and slow-computer checks to identify an ordinary workload, memory/storage constraint or unexplained task. On Windows, Task Manager gives the processes and broader resource picture; on Mac, Activity Monitor provides the relevant activity view. Compare the same display at the time of the issue and after a known legitimate task ends.

Video work, games, updates and scans can consume processing capacity. An unfamiliar process can be legitimate, while a familiar name can be copied. Record identity and context rather than deleting the busiest executable. If deeper Windows inspection is warranted, Process Explorer helps examine processes; its client requirements currently list Windows 11 and higher. It does not itself supply a malware-removal verdict.

CPU is not the only resource relevant to mining. Microsoft’s May 2026 GPU-mining investigation describes a Windows campaign targeting graphics hardware and changing activity around user workloads or analysis tools. A quiet snapshot therefore cannot exclude that documented behavior. The example is evidence about one campaign, not a rule that every quiet GPU is compromised.

Use inspection tools to answer a defined question about a recorded task, rather than running benchmarks or reopening suspect content to provoke activity. If observations leave the activity unexplained, preserve them and get suitable help. A resource threshold or a copied filename is not enough to identify a family or its whole scope.

Separate browser protection from device cleanup

If the observation belongs to a known ordinary tab, closing it normally can support a workload comparison. If the page is suspicious, leave it closed. Avoid disabling protections and returning to it to check whether mining resumes. A drop in activity after closing a tab establishes an association to examine; it does not establish the page’s intent or everything it did.

Mozilla’s Enhanced Tracking Protection documentation includes blocking known cryptominers. Microsoft’s Edge tracking-prevention guidance also describes potentially harmful cryptomining trackers and exception limits. These are browser protections within their documented scope, not tools that remove an installed miner or secure a cloud tenant.

For an unwanted browser component, use extension removal and the appropriate Chrome, Edge, Firefox or Safari guide. A notification block and an ad blocker are different controls again. Avoid adding more extensions as a way to assess software that already executed on the computer.

Examine persistence and remote access as separate concerns

An unwanted installed process may return because an app, service, scheduled task or other controller starts it. Record when that happens and which supported finding or entry identifies the component. On Windows, Autoruns is an inspection aid for startup locations; on Mac, platform guidance covers login/background items and management. Neither is a reason to delete unfamiliar entries in bulk.

Microsoft’s 2026 example also describes abuse of ScreenConnect, a legitimate remote-management product, and multiple persistence mechanisms that recreate removed entries. The product name alone is not evidence of abuse; the installation’s purpose and controller matter. If access was not authorized, treat it as a broader incident rather than assuming that stopping a miner ended remote control.

Use the existing security product’s supported actions and check that those actions completed. Windows users can follow the scan guide; Mac users need their own supported controls. Keep uncertain quarantined items isolated. Do not disable antivirus or add an exclusion because a suspected miner says it needs that change.

For work devices, involve IT promptly. For a personal device, get qualified help if access continues, findings recur or the original installer’s scope is unclear. Restored performance is not proof that persistence, exposed data or unauthorized administration was removed.

Treat unexplained cloud compute as an access incident

Microsoft’s July 2023 cloud research describes compromised identities creating or controlling compute for mining. It highlights deployment anomalies, resource permissions and identity protection. This remains a useful investigation model; it is not a current incident verdict or an instruction to copy old indicators into every environment.

If you own the affected account, reach the cloud provider and responsible administrator through their established routes. Preserve billing and resource identifiers, deployment times and relevant activity records. Distinguish wanted workloads from unexplained resources before removing anything that could support production services or evidence.

The responsible team needs to address both unauthorized workloads and the access that allowed them. Stopping a virtual machine does not revoke a credential or prevent another deployment. Use provider-specific incident procedures for identities, privileged roles, keys, application grants and remaining resources; this article does not provide interchangeable console instructions for every service.

From a trusted device, use account and secret recovery for exposed access and escalate cloud keys to their responsible owner. A local antivirus scan cannot settle remote compute charges or revoke cloud permissions. Avoid publishing tenant details or secrets in a public troubleshooting request.

Verify resource, device and access outcomes

After a justified change, compare ordinary use under similar conditions. Record whether the unwanted task stays absent after restart, whether the responsible controller was addressed, and whether supported security actions remain complete. Do not use a suspicious website or sample as the verification workload.

For a cloud incident, the owner also needs to confirm intended deployments, authorized access and the provider’s handling of continuing charges. Preserve unresolved uncertainty rather than reporting “miner removed” after ending one process. Use recovery verification with the platform and access scope actually involved.

Reduce recurrence through independently reached software sources, supported updates and deliberate extension/permission choices. This is researched guidance. No mining sample, GPU benchmark, mining-pool connection or cloud deployment was used to prepare it, and no product-effectiveness result is claimed.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy