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

Memory-Based Cryptojacking

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

Memory-Based Cryptojacking is cryptomining malware that runs mainly in memory rather than writing persistent files to disk. It typically injects into legitimate processes, uses a loaded miner module, and tries to hide from endpoint detection by avoiding obvious file artefacts and surviving only for as long as the process remains active.

What Memory-Based Cryptojacking Is and Why It Differs from Traditional Miners

Memory-based cryptojacking is a form of cryptomining malware that prioritises volatile execution over visible persistence. By staying resident in memory and blending into a legitimate process, it can mine until the process is terminated, while leaving fewer disk artefacts for defenders to inspect.

This makes the threat operationally different from a miner that installs files, services, or scheduled tasks. Defenders cannot rely only on disk triage, because the malicious logic may live inside an injected process, a loaded module, or a transient payload that disappears when the host is rebooted or the process exits.

The same evasion pattern appears in broader cryptojacking campaigns, which is why the Cryptojacking Guide is useful background for understanding how miners are deployed, hidden, and monetised in real environments.

How Memory-Based Cryptojacking Operates in Practice

In memory-based attacks, the miner is typically delivered by another loader, script, or initial access path and then runs inside the address space of a trusted process. That gives the malware a practical disguise: the host may still show normal process names, but the process now consumes CPU and memory in ways that do not match expected workload behaviour.

Injection and reflective loading are attractive because they reduce obvious file-system indicators and can complicate endpoint triage. Security tools may still detect suspicious behaviour, but the artefacts are often behavioural rather than file-based, which means process lineage, command line context, memory scans, and telemetry correlation matter more than simple file hunting.

That behaviour is closely related to fileless and loader-style malware tradecraft, so a broader understanding of malware families and evasion methods helps explain why in-memory miners are harder to spot than conventional droppers. The Malware Guide covers those patterns in a wider defensive context.

Why Memory Residency Makes Detection Harder

The main defensive challenge is that memory residency shortens the window for straightforward forensic discovery. If the process dies, the miner may vanish with it, leaving only indirect signs such as unusual CPU saturation, abnormal child-process trees, network connections to mining pools, or repeated re-injection after termination.

Because the malicious code is active only while the process is live, defenders often need endpoint telemetry, behavioural analytics, and runtime inspection to establish what happened. This is especially important when the miner is packed into a trusted process or a short-lived container where the underlying host image looks clean after the event.

Memory-centric execution also increases the chance of false confidence after a disk-only sweep. A clean filesystem does not prove the host was never mined, it only means the attacker may have avoided durable artefacts or removed them after use.

Common Exposure Paths and Security Implications

Memory-based cryptojacking usually depends on some earlier foothold, such as exposed services, weak credentials, vulnerable applications, or over-permissive cloud and container settings. Once inside, attackers prefer lightweight execution that can keep mining while staying under the radar.

That is why exposure review should include internet-facing assets, recent admin activity, container workloads, and any process that can be used to spawn or inject code. Organisations that only look for dropped binaries miss the control gap: the real issue is often the combination of initial access, execution, and weak runtime visibility.

Compromise may also leave the environment open to follow-on abuse. If the same foothold can be reused, the attacker can return, deploy a different payload, or expand from mining into broader host control.

Risk and Threat Considerations

Memory-based cryptojacking is risky because its short-lived, in-process design reduces visibility while preserving enough runtime to consume resources, hide in plain sight, and keep operating until the process is killed or the host is remediated. The same characteristics make post-incident review harder, especially when the environment lacks strong process telemetry or memory-focused monitoring.

Failure mechanism: Attackers exploit a trusted process boundary, inject or load the miner into memory, and rely on low-friction runtime execution to avoid durable artefacts that would otherwise support detection or containment.

Impact: The result is sustained resource theft, degraded host performance, possible alert fatigue, and a higher chance that the same access path is reused for additional malicious activity.

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 NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1496 — Resource HijackingDefines cryptomining abuse as resource hijacking.
Recommendation — Map mining activity to T1496 and hunt for abnormal compute consumption and mining-pool traffic.
NIST SP 800-53 Rev 5SI-4 — System MonitoringRequires monitoring host behaviour for malicious runtime activity.
AU-6 — Audit Review, Analysis, and ReportingSupports reviewing logs and telemetry after suspected in-memory compromise.
Recommendation — Monitor endpoint and process telemetry for injected miners and abnormal resource use. Review audit and endpoint logs to reconstruct execution and containment timelines.
CIS Controls v8CIS-8 — Audit Log ManagementSupports collecting and reviewing logs needed to spot transient miner behaviour.
CIS-10 — Malware DefensesAddresses malware detection and containment, including fileless or in-memory threats.
Recommendation — Centralise and review logs that reveal suspicious process behaviour and mining indicators. Apply malware-defence controls that detect malicious code running in memory.

Practitioner Guidance

Why practitioners should care: Memory-based cryptojacking is not just a mining problem, it is a visibility problem. If your detection strategy is file-centric, you will miss the cases where the miner exists only as live process state or injected code.

What to watch for: Prioritise abnormal CPU usage, suspicious parent-child process relationships, unexpected network egress to mining infrastructure, and processes whose behaviour does not match their signed binary, service role, or baseline workload profile.

Practitioner takeaway: Treat in-memory mining as a runtime compromise signal, not just a resource anomaly, and investigate the access path that allowed code execution in the first place.

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