Skip to main content
Mallory
Malware10 associated CVEs

Magnitude Exploit Kit

Tracked since Nov 25, 2025 · Updated 3 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns10Associated
Actors0Associated
ATT&CK13Techniques
IOCs3Tracked
Type
Loader
Capabilities
Initial accessDefense evasionPrivilege escalationProcess injection
Delivery
MalvertisingLanding pageFake update
Platforms
Windows

Magnitude Exploit Kit is a long-running exploit kit and malvertising operation active since at least the early 2010s, best known for targeting Internet Explorer users in Asia-Pacific, especially South Korea, and for delivering ransomware payloads such as Magniber and earlier families including Cerber, Locky, CryptoWall, and GandCrab. It has been associated with opportunistic web-based compromise through malicious advertising chains and exploit landing pages, with campaigns frequently tailored to specific geographies, browser versions, and Windows builds.

Magnitude commonly uses malvertising and redirect chains to drive victims to exploit infrastructure, where browser-based code execution vulnerabilities in Internet Explorer are used to gain execution. Reported campaigns have exploited vulnerabilities including CVE-2019-1367 and CVE-2021-26411, and later stages have used Windows privilege-escalation vulnerabilities such as CVE-2020-0986 to escape browser sandboxes and elevate execution before deploying final payloads. Operations have used rapidly rotating infrastructure, victim-specific subdomains, and polymorphic JavaScript obfuscation to hinder detection and takedown.

The kit has been described as highly selective in targeting, with campaigns focused on South Korean Internet Explorer users and, at times, other Asia-Pacific countries including Taiwan and Japan. Distribution has included adult-themed malvertising and fake update lures, and later activity also included social-engineering delivery of Magniber through signed application packages. In observed chains, Magnitude has performed staged payload retrieval and process injection to launch ransomware in another process.

Magnitude is most notable as a delivery platform rather than as a payload family itself. Its core role is to provide initial access and execution for follow-on malware, especially ransomware. In later campaigns delivering Magniber, the overall intrusion chain included local privilege escalation, payload staging, and deployment of ransomware that encrypted files, dropped ransom notes, and in some cases exfiltrated limited deployment metadata. Magnitude remains one of the few exploit kits that continued meaningful in-the-wild activity after the broader decline of the exploit-kit ecosystem.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Associated CVEs

Associated vulnerabilities

10 CVEs Mallory has correlated with this family across public research and vendor advisories. Each card links to the full Mallory page for that vulnerability.

CVE-2019-1367via confiant blogScripting Engine Memory Corruption Vulnerability in Internet ExplorerMagnitude Exploit KIT : An opportunistic Malvertiser, mostly targeting south Korea. Magnitude EK has been there since 2013, and known to drop very known ransomware families including: Locky, Cerber, Magniber, CryptoWall, GranCrab..View vulnerability →Source ↗
CVE-2015-2419via blackhatExploited in the wildJScript9 Memory Corruption VulnerabilityThe first case study is CVE-2015-2419, a double-free in jscript9 and this particular vulnerability is being exploited in most of the popular exploit kits. This specific example depicted below was taken from the Magnitude exploit kit.View vulnerability →Source ↗
CVE-2020-0986via avast decodedExploited in the wildWindows GDI Print/Print Spooler Arbitrary Pointer Dereference Elevation of PrivilegeThe attackers behind the Magnitude Exploit Kit (or Magniťůdek as we like to call it) are exploiting this momentum by running malicious ads that are currently shown only to South Korean Internet Explorer users. | Magnitude currently exploits... a Windows memory corruption vulnerability, CVE-2020-0986, to subsequently elevate privileges... Magnitude escapes the EPM sandbox by exploiting CVE-2020-0986, a memory corruption vulnerability in splwow64.exe.View vulnerability →Source ↗
CVE-2021-26411via avast decodedExploited in the wildRemote Code Execution in Internet Explorer and Legacy Microsoft EdgeThe attackers behind the Magnitude Exploit Kit (or Magniťůdek as we like to call it) are exploiting this momentum by running malicious ads that are currently shown only to South Korean Internet Explorer users. | Magnitude currently exploits an Internet Explorer memory corruption vulnerability, CVE-2021-26411, to get shellcode execution inside the renderer process... A fully functional exploit for CVE-2021-26411 can be found on the Internet and Magnitude uses that public exploit directly, just with some added obfuscation on top.View vulnerability →Source ↗
CVE-2013-2551via malware dontneedcoffeeUse-after-free in Microsoft Internet Explorer 6–10Being asked for the CVE he wrotes : CVE-2012-0507 CVE-2013-2551 CVE-2013-2471View vulnerability →Source ↗
CVE-2013-0634via malware dontneedcoffeeMemory corruption in Adobe Flash PlayerFlash exploit was only a downloader, (not CVE-2013-0634)View vulnerability →Source ↗
CVE-2011-3402via malware dontneedcoffeeTrueType Font Parsing Vulnerabilityand no more CVE-2011-3402 (Duqu Like Font Drop)View vulnerability →Source ↗
CVE-2012-0507via malware dontneedcoffeeOracle Java AtomicReferenceArray Type Confusion Sandbox EscapeBeing asked for the CVE he wrotes : CVE-2012-0507 CVE-2013-2551 CVE-2013-2471View vulnerability →Source ↗
CVE-2013-2471via malware dontneedcoffeeOracle Java 2D Unspecified VulnerabilityBeing asked for the CVE he wrotes : CVE-2012-0507 CVE-2013-2551 CVE-2013-2471View vulnerability →Source ↗
CVE-2021-40444via jpcert blogMicrosoft MSHTML Remote Code ExecutionRintaro and Hajime gave an update on an exploit kit called Magnitude Exploit Kit observed in 2021 and the analysis results of ransomware called Magniber, which is executed by this kit.View vulnerability →Source ↗
MITRE ATT&CK

Techniques & procedures

13 distinct techniques documented for this family, organized by ATT&CK tactic.

Resource Development

1 technique
T1583Acquire InfrastructureEvidence1

The attackers behind the Magnitude Exploit Kit are exploiting this momentum by running malicious ads that are currently shown only to South Korean Internet Explorer users. The ads can mostly be found on adult websites, which makes this an example of so-called adult malvertising.

Initial Access

2 techniques
T1189Drive-by CompromiseEvidence4

the Magniber group has been using the Magnitude exploit kit to distribute its payloads since at least 2018, an exploit kit which it still uses today

T1190Exploit Public-Facing ApplicationEvidence2

Magnitude currently exploits an Internet Explorer memory corruption vulnerability, CVE-2021-26411, to get shellcode execution inside the renderer process and a Windows memory corruption vulnerability, CVE-2020-0986, to subsequently elevate privileges.

Execution

4 techniques
T1059.003Windows Command ShellEvidence1

The command that Magnitude executes in the call to system looks like this: icacls <dropped_64bit_PE> /Q /C /setintegritylevel Medium && <dropped_64bit_PE>

T1059.007JavaScriptEvidence2

returning Jscript encoded data... After decoding, we are greeted with the full CVE-2019–1367 exploit, but obfuscated

T1106Native APIEvidence1

As shown in the above screenshot, the exploit kit prefers not to use standard Windows API functions and instead often invokes system calls directly.

T1203Exploitation for Client ExecutionEvidence4

Setting IE8 compatibility mode, will force IE browser to use the legacy jscript.dll ( and trigger the vulnerable code of CVE-2019–1367 bug)

Privilege Escalation

2 techniques
T1055Process InjectionEvidence1

Once a suitable target process is found, the shellcode jumps through the Heaven’s Gate and injects the payload into the target process using the following sequence of syscalls: NtOpenProcess -> NtCreateSection -> NtMapViewOfSection -> NtCreateThreadEx -> NtGetContextThread -> NtSetContextThread -> NtResumeThread.

T1068Exploitation for Privilege EscalationEvidence1

Magnitude escapes the EPM sandbox by exploiting CVE-2020-0986, a memory corruption vulnerability in splwow64.exe.

Stealth

3 techniques
T1027Obfuscated Files or InformationEvidence2

base64 only data is returned, typical to Magnitude Exploit KIT landing page... returning Jscript encoded data... After decoding, we are greeted with the full CVE-2019–1367 exploit, but obfuscated

T1055Process InjectionEvidence1

Once a suitable target process is found, the shellcode jumps through the Heaven’s Gate and injects the payload into the target process using the following sequence of syscalls: NtOpenProcess -> NtCreateSection -> NtMapViewOfSection -> NtCreateThreadEx -> NtGetContextThread -> NtSetContextThread -> NtResumeThread.

T1620Reflective Code LoadingEvidence1

We analyzed the samples to verify that they employed a varied set of both Return-Oriented Programming (ROP) and “ROPless” techniques.

Command and Control

1 technique
T1105Ingress Tool TransferEvidence2

This will help us to get what further network requests were made after a successful exploitation and shellcode execution, ultimately to get to the dropped payload

Impact

1 technique
T1499.001OS Exhaustion FloodEvidence1

subsequent calls to CollectGarbage() for some heap feng shui

Indicators of compromise

Observables

3 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.

View all in app →
Indicator values are available in Mallory. Pivot on every hash, domain, URL, and IP, or pipe them straight into your SIEM.View all in Mallory
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching3Match every observed IP, domain, and hash against your live telemetry.
Associated threat actorsGroups linked to this family, with evidence pinned to each claim.
Associated vulnerabilities10CVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mapping13Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.