Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› Host-Based Cryptojacking
Threats, Abuse & Incident Response

Host-Based Cryptojacking

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Threats, Abuse & Incident Response

Host-Based Cryptojacking is unauthorised cryptomining that runs on a host system such as a server, workstation or cloud instance. It uses the host's CPU or GPU resources through a miner process, scheduled task, service or script, and often causes performance degradation, higher costs and abnormal resource consumption.

What Host-Based Cryptojacking Means on a Compromised System

Host-based cryptojacking is usually a resource-hijacking problem first and a classic malware problem second: the attacker wants steady compute on an endpoint, server, or cloud instance without drawing attention. On hosts, the miner may be delivered through a script, service, scheduled task, or dropper, then tuned to survive reboots and blend into ordinary processes.

Because the payload runs where business workloads already live, it competes for CPU, GPU, memory, and sometimes disk or network capacity. That makes the abuse harder to notice than browser-only mining, especially when the host is already busy or poorly monitored.

How Host-Based Cryptojacking Takes Hold

The infection path is often opportunistic rather than sophisticated. Attackers commonly arrive through exposed management interfaces, stolen credentials, weak cloud configuration, vulnerable software, or another foothold that lets them execute code on the host. The miner itself is only the final stage; the real value is durable execution on infrastructure the defender expects to trust.

Once inside, operators may create persistence with startup items, cron jobs, Windows services, cloud-init scripts, or scheduled tasks. Some families also disable security tooling, tamper with logs, or kill competing miners to preserve performance and profitability. The same host can be used for cryptomining and for credential theft, lateral movement, or staging other malware.

For cloud and container environments, the risk increases when compute is elastic and cost visibility is weak. A small foothold can scale into significant bill shock if the attacker can spawn more instances, mine across multiple workloads, or reuse the same access path across the environment.

Operational Signs and Why It Is Hard to Spot

The most common signals are abnormal CPU or GPU saturation, fan spikes, unexplained thermal load, process names that look generic, and degraded service performance. On cloud instances, cost anomalies and unexpected autoscaling can be early indicators even when endpoint telemetry looks ordinary.

Detection is complicated because miners are often low-noise and commodity in nature. They may throttle themselves when administrators log in, run only at certain times, or hide behind legitimate processes. That is why resource telemetry, process lineage, autorun inspection, and egress review matter more than a single antivirus alert.

Good compromise review goes beyond removing the miner. If the host was mined, it may also have been used to load tooling, steal keys, or pivot into adjacent systems. A post-removal review should therefore treat cryptojacking as a possible sign of broader intrusion, not just an isolated nuisance.

Containment, Recovery, and Cost Control

Effective response starts with isolating the host, preserving evidence, and identifying the entry path before rebuilding or cleaning the system. If the attacker gained execution through a credential, token, or service account, that access path must be treated as compromised, because the miner is often just one payload in a larger campaign.

Recovery should include patching the initial weakness, removing persistence, rotating exposed secrets where relevant, and restoring baseline monitoring for resource usage. In cloud environments, teams should also review billing data, instance inventory, and autoscaling events so they can separate the infected host from any broader cost impact.

Where rapid eradication is not yet possible, temporary containment can reduce damage: restrict outbound mining traffic, limit unnecessary egress, constrain execution rights, and tighten host-level monitoring so renewed miner activity is visible quickly. Those steps do not replace root-cause repair, but they can stop repeat abuse while the environment is cleaned.

Risk and Threat Considerations

Host-based cryptojacking is risky because it turns trusted infrastructure into unpaid mining capacity while masking a deeper compromise path. In practice, the damage is not limited to slower systems, because the same access used to launch a miner can also be reused for credential theft, persistence, or lateral movement.

Failure mechanism: Attackers obtain host execution, plant a persistent miner, and use ordinary-looking system processes or scripts to consume resources while avoiding obvious security alarms. If the host is shared, auto-scaled, or cloud-billed, the abuse can spread into direct financial loss and wider operational disruption.

Impact: Organisations may see degraded application performance, increased infrastructure cost, hidden persistence, and a higher chance that the host is only one node in a broader intrusion chain.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1496 — Resource HijackingDefines host cryptomining as resource hijacking behavior.
Recommendation — Map mining activity to T1496 and hunt for persistence, process abuse, and abnormal resource consumption.
CIS Controls v8CIS-4 — Secure Configuration of Enterprise Assets and SoftwareHost cryptojacking often follows weak host configuration and exposed services.
Recommendation — Harden hosts, remove exposed services, and enforce secure configuration baselines to reduce miner footholds.
NIST SP 800-53 Rev 5SI-4 — System MonitoringHost mining is detected through abnormal process and resource monitoring.
CM-6 — Configuration SettingsPersistence and hidden mining often rely on insecure host settings and startup paths.
IA-5 — Authenticator ManagementInitial host compromise often depends on stolen or weak credentials that enable miner deployment.
Recommendation — Monitor host behavior for anomalous process, CPU, GPU, and network activity that indicates miner execution. Enforce approved configuration settings and review startup mechanisms that miners can abuse. Rotate compromised credentials and reduce long-lived authenticator exposure after cryptojacking incidents.

Practitioner Guidance

Why practitioners should care: Host-based cryptojacking is rarely just a “miner cleanup” event. Treat it as a signal to verify host integrity, examine the initial access path, and check whether the same compromise could still exist elsewhere in the environment.

What to watch for: Persistent resource spikes, unfamiliar autoruns, unexpected services, new scheduled tasks, and cloud spend that does not match workload demand are the most useful clues. The key judgment is whether the miner is the only symptom or simply the visible part of a wider intrusion.

Practitioner takeaway: The fastest safe response is usually to contain the host, investigate the entry vector, and rotate any secrets or service credentials that could have enabled repeated access.

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 November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org