CRITICAL: IcedID/Latrodectus Historical Bot Infections Special Report

LAST UPDATED: 2024-06-10


The first Special Report run on 2024-05-30 contained information about IP addresses and computer systems that are believed to have been infected with IcedID/Latrodectus malware during the period 2023-11-30 to 2024-05-28. It is a result of the international Law Enforcement action called Operation Endgame which was announced on May 30th 2024.

The second Special report run on 2024-06-10 covered the period 2024-01-23 to 2024-05-28.

Shadowserver Special Reports are unlike all of our other standard free daily network reports. They do not cover a specific daily 24-hour time period.

Instead, we send out Special Reports in situations where we are able to share one-time, high value datasets that we feel should be reported responsibly for maximum public benefit. Sometimes there are incidents when it would be useful to be able to notify potential victims about events or breaches that may have impacted them outside of the previous 24-hour period, when it may take a number of days for incident responders to conduct forensic investigations and analyzed data becomes available for sharing with potential victims. Although the events included in these Special Reports will fall outside of our usual 24-hour daily reporting window, we believe that there would still be significant benefit to our constituents in receiving and, hopefully, acting on the retrospective data.

If you have missed a Special Report because you were NOT yet a subscriber at the time a report was pushed out, simply subscribe for your network now and specifically request all recent Shadowserver Special Reports – and we will regenerate them specifically for your network, at no cost.

Note that the data shared across special reports may differ on a case by case basis, hence the report formats for individual Special Reports may be different.

The data in this IcedID/Latrodectus Historical Bot Infections Special Report was provided to Shadowserver by the Operation Endgame Law Enforcement partners to disseminate to National CERTs/CSIRTs and network owners globally, to maximize remediation efforts.

Note that exact timestamps were not available for individual events, so the timestamp field is set to “2024-05-28 00:00:00”. Since only the first and last seen time for an infection was recorded in the IcedID/Latrodectus database, the first and last seen dates for an infected victim system represent a date range when an infection was likely active. However, there could have been multiple infections during that time period for shorter individual time periods (and therefore periods without an active infection).

This special report has severity level CRITICAL set on all events.  Severity levels are described here.

Filename prefix: 2024-05-30-special and 2024-06-10-special. Note: this is accessible in the API using 2024-05-30 and 2024-06-10 as the search date.


  • timestamp
    The timestamp has been set to "2024-05-28 00:00:00" or "2024-06-10 00:00:00" to represent when these one-off data sets were collected
  • ip
    IP address of the affected device. In this case, the last IP address an infected victim bot was using at the last seen time (note that the bot may have changed IP addresses over time, but only the last seen IP address is available)
  • port
    TCP or UDP port identified
  • protocol
    Protocol associated with the malicious activity
  • asn
    Autonomous System Number of the affected device
  • geo
    Country of the affected device
  • region
    Region of the affected device
  • city
    City of the affected device
  • hostname
    Hostname of the affected device (may be from reverse DNS)
  • naics
    North American Industry Classification System Code
  • sector
    Sector of the IP in question
  • tag
    Additional tags for more insight
  • infection
    Description of the malware/infection
  • public_source
    Source of the data
  • status
    Status of the affected IP, for example, "infeceted" (was historically infected with the IcedID/Latrodectus malware)
  • detail
  • account
    The Microsoft Windows user name of the infected users on the infected victim system
  • method
    Request method (client.notifyDevInfo)
  • severity
    Severity level
  • hostname_source
    Hostname source
  • first_seen_time
    The time an infected victim bot was first seen by the IcedID/Latrodectus backend
  • last_seen_time
    The time an infected victim bot was last seen by the IcedID/Latrodectus backend (note that there could have been multiple infections, but only the last seen time is available)
  • potential_exposure_time
    The number of seconds between first and last seen times for this bot
  • machine_name
    The machine name of the infected victim system
  • os_version
    The operating system version of the infected victim system, as reported by the operating system directly
  • mac_address
    The MAC address of the infected device in the botnet control panel
  • client_guid
    The GUID associated with the infected device in the botnet control panel
  • event_id
    The ID associated with the infected device in the botnet control panel


"2010-02-10 00:00:00",,,,64512,ZZ,Region,City,,0,,icedid-latrodectus,icedid-latrodectus,operation-endgame,,,,,critical,ptr,"2023-11-30 18:52:06","2024-05-28 11:47:29",15526523,node01,,20:cf:30:94:8f:37;e8:48:b8:c8:20:00;,968C9EE706B74EF67E662E565EC6,2.948521866
"2010-02-10 00:00:01",,,,64512,ZZ,Region,City,,0,,icedid-latrodectus,icedid-latrodectus,operation-endgame,,,,,critical,,"2023-12-01 10:17:47","2024-05-28 12:25:56",15473289,node02,,00:e0:4c:10:36:e2;,E4A8946B846EB424D4C4F4641404,2.2071383423
"2010-02-10 00:00:02",,,,64512,ZZ,Region,City,,0,,icedid-latrodectus,icedid-latrodectus,operation-endgame,,,,,critical,ptr,"2023-12-06 04:58:56","2024-05-28 15:58:24",15073168,node03,,48:e7:af:26:aa:a4;b6:8c:9d:a6:0e:a3;b6:8c:9d:a6:0e:b3;,AA4FA2C73AAFF24AC2DA12EAE27A,2.3116642504

Our 128 Report Types