prompt
stringclasses 508
values | procedure
stringlengths 20
478
|
---|---|
Command and Scripting Interpreter:JavaScript
|
It has used JavaScript files to execute its POWERSTATS payload.
|
Command and Scripting Interpreter:JavaScript
|
NanHaiShu executes additional Jscript code on the victim's machine.
|
Command and Scripting Interpreter:JavaScript
|
During Operation Dust Storm, the threat actors used JavaScript code.
|
Command and Scripting Interpreter:JavaScript
|
POWERSTATS can use JavaScript code for execution.
|
Command and Scripting Interpreter:JavaScript
|
The QakBot web inject module can inject Java Script into web banking pages visited by the victim.
|
Command and Scripting Interpreter:JavaScript
|
It has used JavaScript to drop and execute malware loaders.
|
Command and Scripting Interpreter:JavaScript
|
It has used JS scripts.
|
Command and Scripting Interpreter:JavaScript
|
SpicyOmelette has the ability to execute arbitrary JavaScript code on a compromised host.
|
Command and Scripting Interpreter:JavaScript
|
It has used JavaScript for code execution.
|
Command and Scripting Interpreter:JavaScript
|
It has used various JavaScript-based backdoors.
|
Command and Scripting Interpreter:JavaScript
|
Valak can execute JavaScript containing configuration data for establishing persistence.
|
Command and Scripting Interpreter:JavaScript
|
Xbash can execute malicious JavaScript payloads on the victim’s machine.
|
Command and Scripting Interpreter:Cloud API
|
It has leveraged the Microsoft Graph API to perform various actions across Azure and M365 environments. They have also utilized AADInternals PowerShell Modules to access the API
|
Command and Scripting Interpreter:Cloud API
|
Pacu leverages the AWS CLI for its operations.
|
Command and Scripting Interpreter:Cloud API
|
It has leveraged AWS CLI to enumerate cloud environments with compromised credentials.
|
Container Administration Command
|
Hildegard was executed through the kubelet API run command and by executing commands on running containers.
|
Container Administration Command
|
Kinsing was executed with an Ubuntu container entry point that runs shell scripts.
|
Container Administration Command
|
Peirates can use kubectl or the Kubernetes API to run commands.
|
Container Administration Command
|
Siloscape can send kubectl commands to victim clusters through an IRC channel and can run kubectl locally to spread once within a victim cluster.
|
Container Administration Command
|
It executed Hildegard through the kubelet API run command and by executing commands on running containers.
|
Deploy Container
|
Doki was run through a deployed container.
|
Deploy Container
|
Kinsing was run through a deployed Ubuntu container.
|
Deploy Container
|
Peirates can deploy a pod that mounts its node’s root file system, then execute a command to create a reverse shell on the node.
|
Deploy Container
|
It has deployed different types of containers into victim environments to facilitate execution. It has also transferred cryptocurrency mining software to Kubernetes clusters discovered within local IP address ranges.
|
Exploitation for Client Execution
|
It has exploited client software vulnerabilities for execution, such as Microsoft Word CVE-2012-0158.
|
Exploitation for Client Execution
|
Agent Tesla has exploited Office vulnerabilities such as CVE-2017-11882 and CVE-2017-8570 for execution during delivery.
|
Exploitation for Client Execution
|
It has exploited numerous ActiveX vulnerabilities, including zero-days.
|
Exploitation for Client Execution
|
It has exploited CVE-2012-0158 and CVE-2010-3333 for execution against targeted systems.
|
Exploitation for Client Execution
|
It has exploited multiple vulnerabilities for execution, including Microsoft Office vulnerabilities (CVE-2009-3129, CVE-2012-0158) and vulnerabilities in Adobe Reader and Flash (CVE-2009-4324, CVE-2009-0927, CVE-2011-0609, CVE-2011-0611).
|
Exploitation for Client Execution
|
It has exploited Microsoft Office vulnerability CVE-2017-0262 for execution.
|
Exploitation for Client Execution
|
It has used multiple software exploits for common client software, like Microsoft Word, Exchange, and Adobe Reader, to gain code execution.
|
Exploitation for Client Execution
|
It has exploited the Adobe Flash Player vulnerability CVE-2015-3113 and Internet Explorer vulnerability CVE-2014-1776.
|
Exploitation for Client Execution
|
It has used RTF document that includes an exploit to execute malicious code. (CVE-2017-11882)
|
Exploitation for Client Execution
|
It has attempted to exploit a known vulnerability in WinRAR (CVE-2018-20250), and attempted to gain remote code execution via a security bypass vulnerability (CVE-2017-11774).
|
Exploitation for Client Execution
|
It has used exploits for Flash Player (CVE-2016-4117, CVE-2018-4878), Word (CVE-2017-0199), Internet Explorer (CVE-2020-1380 and CVE-2020-26411), and Microsoft Edge (CVE-2021-26411) for execution.
|
Exploitation for Client Execution
|
It leveraged the follow exploits in their operations: CVE-2012-0158, CVE-2015-1641, CVE-2017-0199, CVE-2017-11882, and CVE-2019-3396.
|
Exploitation for Client Execution
|
It has used exploits for multiple vulnerabilities including CVE-2014-0322, CVE-2012-4792, CVE-2012-1889, and CVE-2013-3893.
|
Exploitation for Client Execution
|
Bankshot leverages a known zero-day vulnerability in Adobe Flash to execute the implant into the victims’ machines.
|
Exploitation for Client Execution
|
It has exploited Microsoft Office vulnerabilities CVE-2012-0158, CVE-2017-11882, CVE-2018-0798, and CVE-2018-0802.
|
Exploitation for Client Execution
|
It has exploited multiple vulnerabilities for execution, including Microsoft Office vulnerabilities CVE-2012-0158, CVE-2014-6352, CVE-2017-0199, and Adobe Flash CVE-2015-5119.
|
Exploitation for Client Execution
|
It has exploited Microsoft Office vulnerabilities CVE-2014-4114, CVE-2018-0802, and CVE-2018-0798 for execution.
|
Exploitation for Client Execution
|
It had exploited multiple vulnerabilities for execution, including Microsoft’s It Editor (CVE-2017-11882), an Internet Explorer vulnerability (CVE-2018-8174), CVE-2017-8570, CVE-2017-0199, and CVE-2017-8759.
|
Exploitation for Client Execution
|
Cobalt Strike can exploit Oracle Java vulnerabilities for execution, including CVE-2011-3544, CVE-2013-2465, CVE-2012-4681, and CVE-2013-2460.
|
Exploitation for Client Execution
|
It has exploited Microsoft Office vulnerabilities, including CVE-2015-1641, CVE-2017-11882, and CVE-2018-0802.
|
Exploitation for Client Execution
|
It has exploited Adobe Flash vulnerability CVE-2015-8651 for execution.
|
Exploitation for Client Execution
|
DealersChoice leverages vulnerable versions of Flash to perform execution.
|
Exploitation for Client Execution
|
It has exploited CVE-2011-0611 in Adobe Flash Player to gain execution on a targeted system.
|
Exploitation for Client Execution
|
It has used exploitation of endpoint software, including Microsoft Internet Explorer Adobe Flash vulnerabilities, to gain execution. They have also used zero-day exploits.
|
Exploitation for Client Execution
|
It has exploited Microsoft Office vulnerability CVE-2017-11882.
|
Exploitation for Client Execution
|
EvilBunny has exploited CVE-2011-4369, a vulnerability in the PRC component in Adobe Reader.
|
Exploitation for Client Execution
|
It has used malicious documents containing exploits for CVE-2021-40444 affecting Microsoft MSHTML.
|
Exploitation for Client Execution
|
During Frankenstein, the threat actors exploited CVE-2017-11882 to execute code on the victim's machine.
|
Exploitation for Client Execution
|
HAWKBALL has exploited Microsoft Office vulnerabilities CVE-2017-11882 and CVE-2018-0802 to deliver the payload.
|
Exploitation for Client Execution
|
It has exploited CVE-2018-0798 for execution.
|
Exploitation for Client Execution
|
It has exploited CVE-2012-0158, CVE-2014-1761, CVE-2017-11882 and CVE-2018-0802 for execution.
|
Exploitation for Client Execution
|
InvisiMole has installed legitimate but vulnerable Total Video Player software and wdigest.dll library drivers on compromised hosts to exploit stack overflow and input validation vulnerabilities for code execution.
|
Exploitation for Client Execution
|
It has exploited Adobe Flash vulnerability CVE-2018-4878 for execution.
|
Exploitation for Client Execution
|
It has exploited multiple Microsoft Office and .NET vulnerabilities for execution, including CVE-2017-0199, CVE-2017-8759, and CVE-2017-11882.
|
Exploitation for Client Execution
|
It has exploited the Office vulnerability CVE-2017-0199 for execution.
|
Exploitation for Client Execution
|
It has exploited CVE-2017-0199 in Microsoft Word to execute code.
|
Exploitation for Client Execution
|
During Operation Dust Storm, the threat actors exploited Adobe Flash vulnerability CVE-2011-0611, Microsoft Windows Help vulnerability CVE-2010-1885, and several Internet Explorer vulnerabilities, including CVE-2011-1255, CVE-2012-1889, and CVE-2014-0322.
|
Exploitation for Client Execution
|
It uses malicious documents to deliver remote execution exploits as part of. The group has previously exploited CVE-2017-8570, CVE-2012-1856, CVE-2014-4114, CVE-2017-0199, CVE-2017-11882, and CVE-2015-1641.
|
Exploitation for Client Execution
|
Ramsay has been embedded in documents exploiting CVE-2017-0199, CVE-2017-11882, and CVE-2017-8570.
|
Exploitation for Client Execution
|
It has exploited vulnerabilities in Microsoft PowerPoint via OLE objects (CVE-2014-4114) and Microsoft Word via crafted TIFF images (CVE-2013-3906).
|
Exploitation for Client Execution
|
It has exploited vulnerabilities to gain execution including CVE-2017-11882 and CVE-2020-0674.
|
Exploitation for Client Execution
|
SpeakUp attempts to exploit the following vulnerabilities in order to execute its malicious script: CVE-2012-0874, CVE-2010-1871, CVE-2017-10271, CVE-2018-2894, CVE-2016-3088, JBoss AS 3/4/5/6, and the Hadoop YARN ResourceManager.
|
Exploitation for Client Execution
|
SUPERNOVA was installed via exploitation of a SolarWinds Orion API authentication bypass vulnerability (CVE-2020-10148).
|
Exploitation for Client Execution
|
It has exploited Microsoft Word vulnerability CVE-2017-0199 for execution.
|
Exploitation for Client Execution
|
It has taken advantage of a known vulnerability in Microsoft Word (CVE 2012-0158) to execute code.
|
Exploitation for Client Execution
|
It has exploited CVE-2018-0798 in It Editor.
|
Exploitation for Client Execution
|
It has exploited Microsoft vulnerabilities, including CVE-2018-0798, CVE-2018-8174, CVE-2018-0802, CVE-2017-11882, CVE-2019-9489 CVE-2020-8468, and CVE-2018-0798 to enable execution of their delivered malicious payloads.
|
Exploitation for Client Execution
|
It has crafted malicious files to exploit CVE-2012-0158 and CVE-2010-3333 for execution.
|
Exploitation for Client Execution
|
It has executed commands through Microsoft security vulnerabilities, including CVE-2017-11882, CVE-2018-0802, and CVE-2012-0158.
|
Exploitation for Client Execution
|
Woody RAT has relied on CVE-2022-30190 (Follina) for execution during delivery.
|
Exploitation for Client Execution
|
Xbash can attempt to exploit known vulnerabilities in Hadoop, Redis, or ActiveMQ when it finds those services running in order to conduct further execution.
|
Inter-Process Communication
|
Cyclops Blink has the ability to create a pipe to enable inter-process communication.
|
Inter-Process Communication
|
HyperStack can connect to the IPC$ share on remote machines.
|
Inter-Process Communication
|
When executing with non-root permissions, RotaJakiro uses the the shmget API to create shared memory between other known RotaJakiro processes. This allows processes to communicate with each other and share their PID.
|
Inter-Process Communication
|
Uroburos has the ability to move data between its kernel and user mode components, generally using named pipes.
|
Inter-Process Communication:Component Object Model
|
Bumblebee can use a COM object to execute queries to gather system information.
|
Inter-Process Communication:Component Object Model
|
DarkTortilla has used the WshShortcut COM object to create a .lnk shortcut file in the Windows startup folder.
|
Inter-Process Communication:Component Object Model
|
FunnyDream can use com objects identified with CLSID_ShellLink(IShellLink and IPersistFile) and WScript.Shell(RegWrite method) to enable persistence mechanisms.
|
Inter-Process Communication:Component Object Model
|
It malware can insert malicious macros into documents using a Microsoft.Office.Interop object.
|
Inter-Process Communication:Component Object Model
|
Gelsemium can use the IARPUinstallerStringLauncher COM interface are part of its UAC bypass process.
|
Inter-Process Communication:Component Object Model
|
HermeticWizard can execute files on remote machines using DCOM.
|
Inter-Process Communication:Component Object Model
|
InvisiMole can use the ITaskService, ITaskDefinition and ITaskSettings COM interfaces to schedule a task.
|
Inter-Process Communication:Component Object Model
|
Milan can use a COM component to generate scheduled tasks.
|
Inter-Process Communication:Component Object Model
|
It has used malware that has the capability to execute malicious code via COM, DCOM, and Outlook.
|
Inter-Process Communication:Component Object Model
|
Neoichor can use the Internet Explorer (IE) COM interface to connect and receive commands from C2.
|
Inter-Process Communication:Component Object Model
|
POWERSTATS can use DCOM (targeting the 127.0.0.1 loopback address) to execute additional payloads on compromised hosts.
|
Inter-Process Communication:Component Object Model
|
Ramsay can use the Windows COM API to schedule tasks and maintain persistence.
|
Inter-Process Communication:Component Object Model
|
TrickBot used COM to setup scheduled task for persistence.
|
Inter-Process Communication:Component Object Model
|
Ursnif droppers have used COM objects to execute the malware's full executable payload.
|
Inter-Process Communication:Dynamic Data Exchange
|
It has delivered JHUHUGIT and Koadic by executing PowerShell commands through DDE in Word documents.
|
Inter-Process Communication:Dynamic Data Exchange
|
It has used Windows DDE for execution of commands and a malicious VBS.
|
Inter-Process Communication:Dynamic Data Exchange
|
It has executed OLE objects using Microsoft It Editor to download and run malicious payloads.
|
Inter-Process Communication:Dynamic Data Exchange
|
It has sent malicious Word OLE compound documents to victims.
|
Inter-Process Communication:Dynamic Data Exchange
|
It spear phishing campaigns have included malicious Word documents with DDE execution.
|
Inter-Process Communication:Dynamic Data Exchange
|
It attempted to exploit Microsoft’s DDE protocol in order to gain access to victim machines and for execution.
|
Inter-Process Communication:Dynamic Data Exchange
|
GravityRAT has been delivered via Word documents using DDE for execution.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.