www.cisa.gov Open in urlscan Pro
2a02:26f0:6c00:28e::447a  Public Scan

URL: https://www.cisa.gov/uscert/ncas/alerts/aa22-057a
Submission: On March 21 via api from US — Scanned from DE

Form analysis 3 forms found in the DOM

GET https://search.us-cert.gov/search

<form accept-charset="UTF-8" action="https://search.us-cert.gov/search" class="hidden-xs searchbox" method="get"><input name="utf8" type="hidden" value="✓"><input id="affiliate-desktop" name="affiliate" type="hidden" value="us-cert">
  <div class="form-group"><label class="sr-only" for="query-desktop">Enter Search Terms(s):</label>
    <div class="input-group"><input autocomplete="off" class="form-control form-control-custom input-lg" id="query-desktop" name="query" placeholder="Search" type="text">
      <div class="input-group-addon input-group-addon-custom"><button class="submit input-lg"><img alt="search icon" data-entity-type="" data-entity-uuid="" src="/sites/default/files/cert/search-icon.png" title="search icon"></button></div>
    </div>
  </div>
</form>

GET https://search.us-cert.gov/search

<form accept-charset="UTF-8" action="https://search.us-cert.gov/search" class="hidden-lg hidden-md searchbox" method="get"><input name="utf8" type="hidden" value="✓"><input id="affiliate-mobile" name="affiliate" type="hidden" value="us-cert">
  <div class="form-group"><label class="sr-only" for="query-mobile">Enter Search Terms(s):</label>
    <div class="input-group"><input autocomplete="off" class="form-control form-control-custom input-lg" id="query-mobile" name="query" placeholder="Search" type="text">
      <div class="input-group-addon input-group-addon-custom"><button class="submit input-lg"><img alt="search icon" data-entity-type="" data-entity-uuid="" src="/sites/default/files/cert/search-icon.png" title="search icon"></button></div>
    </div>
  </div>
</form>

https://public.govdelivery.com/accounts/USDHSCISA/subscribers/qualify

<form action="https://public.govdelivery.com/accounts/USDHSCISA/subscribers/qualify"><label class="visually-hidden" for="email-address-field">Enter your email address</label> <input class="signup-form" id="email-address-field" name="email"
    placeholder=" Enter your email address" title="Enter your email address" type="text"><br><input class="btn btn-primary" name="submit" title="Sign up for alerts" type="submit" value="Sign Up">&nbsp;</form>

Text Content

Skip to main content

An official website of the United States government Here's how you know

Official websites use .gov
A .gov website belongs to an official government organization in the United
States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share
sensitive information only on official, secure websites.
Enter Search Terms(s):

CISA.gov Services Report

--------------------------------------------------------------------------------

Toggle navigation

Enter Search Terms(s):

CISA.gov
Services
Report


CERTMAIN MENU

 * Alerts and Tips
 * Resources
 * Industrial Control Systems
 * Report

--------------------------------------------------------------------------------


TLP:WHITE
TLP:WHITE
 1. National Cyber Awareness System    >
 2. Alerts    >
 3. Destructive Malware Targeting Organizations in Ukraine

More Alerts


ALERT (AA22-057A)


DESTRUCTIVE MALWARE TARGETING ORGANIZATIONS IN UKRAINE

Original release date: February 26, 2022 | Last revised: March 01, 2022



SUMMARY

Actions to Take Today:
• Set antivirus and antimalware programs to conduct regular scans.
• Enable strong spam filters to prevent phishing emails from reaching end users.
• Filter network traffic.
• Update software.
• Require multifactor authentication.

Leading up to Russia’s unprovoked attack against Ukraine, threat actors deployed
destructive malware against organizations in Ukraine to destroy computer systems
and render them inoperable. 

 * On January 15, 2022, the Microsoft Threat Intelligence Center (MSTIC)
   disclosed that malware, known as WhisperGate, was being used to target
   organizations in Ukraine. According to Microsoft(link is external),
   WhisperGate is intended to be destructive and is designed to render targeted
   devices inoperable. 
 * On February 23, 2022, several cybersecurity researchers disclosed that
   malware known as HermeticWiper(link is external) was being used against
   organizations in Ukraine. According to SentinelLabs(link is external), the
   malware targets Windows devices, manipulating the master boot record, which
   results in subsequent boot failure. 

Destructive malware can present a direct threat to an organization’s daily
operations, impacting the availability of critical assets and data. Further
disruptive cyberattacks against organizations in Ukraine are likely to occur and
may unintentionally spill over to organizations in other countries.
Organizations should increase vigilance and evaluate their capabilities
encompassing planning, preparation, detection, and response for such an event. 

This joint Cybersecurity Advisory (CSA) between the Cybersecurity and
Infrastructure Security Agency (CISA) and Federal Bureau of Investigation (FBI)
provides information on WhisperGate and HermeticWiper malware as well as
open-source indicators of compromise (IOCs) for organizations to detect and
prevent the malware. Additionally, this joint CSA provides recommended guidance
and considerations for organizations to address as part of network architecture,
security baseline, continuous monitoring, and incident response practices.

Click here for a PDF version of this report.
Click here for STIX.


TECHNICAL DETAILS

Threat actors have deployed destructive malware, including both WhisperGate and
HermeticWiper, against organizations in Ukraine to destroy computer systems and
render them inoperable. Listed below are high-level summaries of campaigns
employing the malware. CISA recommends organizations review the resources listed
below for more in-depth analysis and see the Mitigation section for best
practices on handling destructive malware.   

On January 15, 2022, Microsoft announced the identification of a sophisticated
malware operation targeting multiple organizations in Ukraine. The malware,
known as WhisperGate, has two stages that corrupts a system’s master boot
record, displays a fake ransomware note, and encrypts files based on certain
file extensions. Note: although a ransomware message is displayed during the
attack, Microsoft highlighted that the targeted data is destroyed, and is not
recoverable even if a ransom is paid. See Microsoft’s blog on Destructive
malware targeting Ukrainian organizations(link is external) for more information
and see the IOCs in table 1. 

Table 1: IOCs associated with WhisperGate

Name File Category File Hash Source WhisperGate   stage1.exe 

a196c6b8ffcb97ffb276d04f354696e2391311db3841ae16c8c9f56f36a38e92(link is
external)

Microsoft MSTIC(link is external)   WhisperGate stage2.exe

dcbbae5a1c61dbbbb7dcd6dc5dd1eb1169f5329958d38b58c3fd9384081c9b78(link is
external)

Microsoft MSTIC(link is external)

 

On February 23, 2022, cybersecurity researchers disclosed that malware known as
HermeticWiper was being used against organizations in Ukraine. According to
SentinelLabs, the malware targets Windows devices, manipulating the master boot
record and resulting in subsequent boot failure. Note: according to Broadcom,
“[HermeticWiper] has some similarities to the earlier WhisperGate wiper attacks
against Ukraine, where the wiper was disguised as ransomware.” See the following
resources for more information and see the IOCs in table 2 below. 

 * ESET Research Tweet: Breaking. #ESETResearch discovered a new data wiper
   malware used in Ukraine today. ESET telemetry shows that it was installed on
   hundreds of machines in the country(link is external). 
 * SentinelLabs: HermeticWiper | New Destructive Malware Used In Cyber Attacks
   on Ukraine(link is external)
 * Broadcom’s Symantec Threat Hunter Team: Ukraine: Disk-wiping Attacks Precede
   Russian Invasion(link is external)

Table 2: IOCs associated with HermeticWiper

Name File Category File Hash Source Win32/KillDisk.NCV Trojan
912342F1C840A42F6B74132F8A7C4FFE7D40FB77
61B25D11392172E587D8DA3045812A66C3385451
  ESET research(link is external) HermeticWiper Win32 EXE
912342f1c840a42f6b74132f8a7c4ffe7d40fb77

SentinelLabs(link is external)

HermeticWiper Win32 EXE 61b25d11392172e587d8da3045812a66c3385451

SentinelLabs(link is external)

RCDATA_DRV_X64 ms-compressed a952e288a1ead66490b3275a807f52e5

SentinelLabs(link is external)

RCDATA_DRV_X86 ms-compressed 231b3385ac17e41c5bb1b1fcb59599c4

SentinelLabs(link is external)

RCDATA_DRV_XP_X64 ms-compressed 095a1678021b034903c85dd5acb447ad

SentinelLabs(link is external)

RCDATA_DRV_XP_X86  ms-compressed eb845b7a16ed82bd248e395d9852f467

SentinelLabs(link is external)

Trojan.Killdisk Trojan.Killdisk 
1bc44eef75779e3ca1eefb8ff5a64807dbc942b1e4a2672d77b9f6928d292591 Symantec Threat
Hunter Team(link is external) Trojan.Killdisk Trojan.Killdisk
0385eeab00e946a302b24a91dea4187c1210597b8e17cd9e2230450f5ece21da  Symantec
Threat Hunter Team(link is external) Trojan.Killdisk Trojan.Killdisk
a64c3e0522fad787b95bfb6a30c3aed1b5786e69e88e023c062ec7e5cebf4d3e Symantec Threat
Hunter Team(link is external) Ransomware Trojan.Killdisk
4dc13bb83a16d4ff9865a51b3e4d24112327c526c1392e14d56f20d6f4eaf382 Symantec Threat
Hunter Team(link is external)


MITIGATIONS

BEST PRACTICES FOR HANDLING DESTRUCTIVE MALWARE

As previously noted above, destructive malware can present a direct threat to an
organization’s daily operations, impacting the availability of critical assets
and data. Organizations should increase vigilance and evaluate their
capabilities, encompassing planning, preparation, detection, and response, for
such an event. This section is focused on the threat of malware using
enterprise-scale distributed propagation methods and provides recommended
guidance and considerations for an organization to address as part of their
network architecture, security baseline, continuous monitoring, and incident
response practices. 

CISA and the FBI urge all organizations to implement the following
recommendations to increase their cyber resilience against this threat.

POTENTIAL DISTRIBUTION VECTORS

Destructive malware may use popular communication tools to spread, including
worms sent through email and instant messages, Trojan horses dropped from
websites, and virus-infected files downloaded from peer-to-peer connections.
Malware seeks to exploit existing vulnerabilities on systems for quiet and easy
access.

The malware has the capability to target a large scope of systems and can
execute across multiple systems throughout a network. As a result, it is
important for organizations to assess their environment for atypical channels
for malware delivery and/or propagation throughout their systems. Systems to
assess include:

 * Enterprise applications – particularly those that have the capability to
   directly interface with and impact multiple hosts and endpoints. Common
   examples include:
   * Patch management systems,
   * Asset management systems,
   * Remote assistance software (typically used by the corporate help desk),
   * Antivirus (AV) software,
   * Systems assigned to system and network administrative personnel,
   * Centralized backup servers, and
   * Centralized file shares.

While not only applicable to malware, threat actors could compromise additional
resources to impact the availability of critical data and applications. Common
examples include:

 * Centralized storage devices
   * Potential risk – direct access to partitions and data warehouses.
 * Network devices
   * Potential risk – capability to inject false routes within the routing
     table, delete specific routes from the routing table, remove/modify,
     configuration attributes, or destroy firmware or system binaries—which
     could isolate or degrade availability of critical network resources.

BEST PRACTICES AND PLANNING STRATEGIES

Common strategies can be followed to strengthen an organization’s resilience
against destructive malware. Targeted assessment and enforcement of best
practices should be employed for enterprise components susceptible to
destructive malware.

COMMUNICATION FLOW

 * Ensure proper network segmentation.
 * Ensure that network-based access control lists (ACLs) are configured to
   permit server-to-host and host-to-host connectivity via the minimum scope of
   ports and protocols and that directional flows for connectivity are
   represented appropriately.
   * Communications flow paths should be fully defined, documented, and
     authorized.
 * Increase awareness of systems that can be used as a gateway to pivot (lateral
   movement) or directly connect to additional endpoints throughout the
   enterprise.
   * Ensure that these systems are contained within restrictive Virtual Local
     Area Networks (VLANs), with additional segmentation and network access
     controls.
 * Ensure that centralized network and storage devices’ management interfaces
   reside on restrictive VLANs.
   * Layered access control, and
   * Device-level access control enforcement – restricting access from only
     pre-defined VLANs and trusted IP ranges.

ACCESS CONTROL

 * For enterprise systems that can directly interface with multiple endpoints:
   * Require multifactor authentication for interactive logons.
   * Ensure that authorized users are mapped to a specific subset of enterprise
     personnel.
     * If possible, the “Everyone,” “Domain Users,” or the “Authenticated Users”
       groups should not be permitted the capability to directly access or
       authenticate to these systems.
   * Ensure that unique domain accounts are used and documented for each
     enterprise application service.
     * Context of permissions assigned to these accounts should be fully
       documented and configured based upon the concept of least privilege.
     * Provides an enterprise with the capability to track and monitor specific
       actions correlating to an application’s assigned service account.
   * If possible, do not grant a service account with local or interactive logon
     permissions.
     * Service accounts should be explicitly denied permissions to access
       network shares and critical data locations.
   * Accounts that are used to authenticate to centralized enterprise
     application servers or devices should not contain elevated permissions on
     downstream systems and resources throughout the enterprise.
 * Continuously review centralized file share ACLs and assigned permissions.
   * Restrict Write/Modify/Full Control permissions when possible.

MONITORING

 * Audit and review security logs for anomalous references to enterprise-level
   administrative (privileged) and service accounts.
   * Failed logon attempts,
   * File share access, and
   * Interactive logons via a remote session.
 * Review network flow data for signs of anomalous activity, including:
   * Connections using ports that do not correlate to the standard
     communications flow associated with an application,
   * Activity correlating to port scanning or enumeration, and
   * Repeated connections using ports that can be used for command and control
     purposes.
 * Ensure that network devices log and audit all configuration changes.
   * Continually review network device configurations and rule sets to ensure
     that communications flows are restricted to the authorized subset of rules.

FILE DISTRIBUTION

 * When deploying patches or AV signatures throughout an enterprise, stage the
   distributions to include a specific grouping of systems (staggered over a
   pre-defined period).
   * This action can minimize the overall impact in the event that an enterprise
     patch management or AV system is leveraged as a distribution vector for a
     malicious payload.
 * Monitor and assess the integrity of patches and AV signatures that are
   distributed throughout the enterprise.
   * Ensure updates are received only from trusted sources,
   * Perform file and data integrity checks, and
   * Monitor and audit – as related to the data that is distributed from an
     enterprise application.

SYSTEM AND APPLICATION HARDENING

 * Ensure robust vulnerability management and patching practices are in place. 
   * CISA maintains a living catalog of known exploited vulnerabilities that
     carry significant risk to federal agencies as well as public and private
     sectors entities. In addition to thoroughly testing and implementing vendor
     patches in a timely—and, if possible, automated— manner, organizations
     should ensure patching of the vulnerabilities CISA includes in this
     catalog.
 * Ensure that the underlying operating system (OS) and dependencies (e.g.,
   Internet Information Services [IIS], Apache, Structured Query Language [SQL])
   supporting an application are configured and hardened based upon
   industry-standard best practice recommendations. Implement application-level
   security controls based on best practice guidance provided by the vendor.
   Common recommendations include:
   * Use role-based access control,
   * Prevent end-user capabilities to bypass application-level security
     controls,
     * For example, do not allow users to disable AV on local workstations.
   * Remove, or disable unnecessary or unused features or packages, and
   * Implement robust application logging and auditing.

RECOVERY AND RECONSTITUTION PLANNING

A business impact analysis (BIA) is a key component of contingency planning and
preparation. The overall output of a BIA will provide an organization with two
key components (as related to critical mission/business operations):

 * Characterization and classification of system components, and
 * Interdependencies.

Based upon the identification of an organization’s mission critical assets (and
their associated interdependencies), in the event that an organization is
impacted by destructive malware, recovery and reconstitution efforts should be
considered.

To plan for this scenario, an organization should address the availability and
accessibility for the following resources (and should include the scope of these
items within incident response exercises and scenarios):

 * Comprehensive inventory of all mission critical systems and applications:
   * Versioning information,
   * System/application dependencies,
   * System partitioning/storage configuration and connectivity, and
   * Asset owners/points of contact.
 * Contact information for all essential personnel within the organization,
 * Secure communications channel for recovery teams,
 * Contact information for external organizational-dependent resources:
   * Communication providers,
   * Vendors (hardware/software), and
   * Outreach partners/external stakeholders
 * Service contract numbers – for engaging vendor support,
 * Organizational procurement points of contact,
 * Optical disc image (ISO)/image files for baseline restoration of critical
   systems and applications:
   * OS installation media,
   * Service packs/patches,
   * Firmware, and
   * Application software installation packages.
 * Licensing/activation keys for OS and dependent applications,
 * Enterprise network topology and architecture diagrams,
 * System and application documentation,
 * Hard copies of operational checklists and playbooks,
 * System and application configuration backup files,
 * Data backup files (full/differential),
 * System and application security baseline and hardening checklists/guidelines,
   and
 * System and application integrity test and acceptance checklists.

INCIDENT RESPONSE

Victims of a destructive malware attacks should immediately focus on containment
to reduce the scope of affected systems. Strategies for containment include:

 * Determining a vector common to all systems experiencing anomalous behavior
   (or having been rendered unavailable)—from which a malicious payload could
   have been delivered:
   * Centralized enterprise application,
   * Centralized file share (for which the identified systems were mapped or had
     access),
   * Privileged user account common to the identified systems,
   * Network segment or boundary, and
   * Common Domain Name System (DNS) server for name resolution.
 * Based upon the determination of a likely distribution vector, additional
   mitigation controls can be enforced to further minimize impact:
   * Implement network-based ACLs to deny the identified application(s) the
     capability to directly communicate with additional systems,
     * Provides an immediate capability to isolate and sandbox specific systems
       or resources.
   * Implement null network routes for specific IP addresses (or IP ranges) from
     which the payload may be distributed,
     * An organization’s internal DNS can also be leveraged for this task, as a
       null pointer record could be added within a DNS zone for an identified
       server or application.
   * Readily disable access for suspected user or service account(s),
   * For suspect file shares (which may be hosting the infection vector), remove
     access or disable the share path from being accessed by additional systems,
     and
   * Be prepared to, if necessary, reset all passwords and tickets within
     directories (e.g., changing golden/silver tickets). 

As related to incident response and incident handling, organizations are
encouraged to report incidents to the FBI and CISA (see the Contact section
below) and to preserve forensic data for use in internal investigation of the
incident or for possible law enforcement purposes. See Technical Approaches to
Uncovering and Remediating Malicious Activity for more information.


CONTACT INFORMATION

All organizations should report incidents and anomalous activity to CISA 24/7
Operations Center at central@cisa.dhs.gov(link sends email) or (888) 282-0870
and/or to the FBI via your local FBI field office or the FBI’s 24/7 CyWatch at
(855) 292-3937 or CyWatch@fbi.gov(link sends email).


RESOURCES

 * Joint CSA: Understanding and Mitigating Russian State-Sponsored Cyber Threats
   to U.S. Critical Infrastructure
 * Joint CSA: NSA and CISA Recommend Immediate Actions to Reduce Exposure Across
   Operational Technologies and Control Systems
 * Joint CSA: Ongoing Cyber Threats to U.S. Water and Wastewater Systems
 * CISA and MS-ISAC: Joint Ransomware Guide
 * CISA webpage: Russia Cyber Threat Overview and Advisories
 * NIST: Data Integrity: Detecting and Responding to Ransomware and Other
   Destructive Events
 * NIST: Data Integrity: Recovering from Ransomware and Other Destructive Events
 * CISA Cyber hygiene services: CISA offers a range of no-cost services to help
   critical infrastructure organizations assess, identify and reduce their
   exposure to threats, including ransomware. By requesting and leveraging these
   services, organizations of any size could find ways to reduce their risk and
   mitigate attack vectors.


REVISIONS

February 26, 2022: Initial Revision
March 1, 2022: Added STIX version.

This product is provided subject to this Notification and this Privacy & Use
policy.

Please share your thoughts.

We recently updated our anonymous product survey; we'd welcome your feedback.


CONTACT US

(888)282-0870

Send us email(link sends email)

Download PGP/GPG keys

Submit website feedback


SUBSCRIBE TO ALERTS

Receive security alerts, tips, and other updates.

Enter your email address
 


HSIN
Report

--------------------------------------------------------------------------------

Home   Site Map   FAQ   Contact Us   Traffic Light Protocol   PCII  
Accountability   Disclaimer   Privacy Policy   FOIA   No Fear Act  
AccessibilityPlain WritingPlug-ins   Inspector General   The White House  
USA.gov
 

CISA is part of the Department of Homeland Security