Vulnerable Exchange Servers Special Report #2

Attacks against potentially vulnerable Microsoft Exchange Servers escalated after proof of concept exploit code was published online, moving incidents from APT to mainstream cybercrime activities. You can read more on the background of HAFNIUM and our previous two Special Reports about potential Exchange Server hacking victims in our recent blog posts here (HAFNIUM pre-patch release) and here (mass exploitation post patch release). This new Special Report is based on additional post patch release IPv4 scanning conducted by KryptosLogic, who have also kindly offered to quickly share their data with victims globally for maximum public benefit.

The blog entry announcing this report can be found here.

Shadowserver Special Reports are unlike all of our other standard free daily network reports. They do not cover a specific 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 – for example during high profile events such as the Solarwinds Orion/SUNBURST supply chain or HAFNIUM/Microsoft Exchange Server mass breaches, 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 them 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 since the data than can shared during one-off reporting events is sometimes different from our more standard shared datasets, this report format is subject to change – primarily through the addition of new fields to better describe a particular dataset.

Fields

  • timestamp
    Timestamp when the IP was seen in UTC+0
  • ip
    IP of the affected device
  • asn
    As 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 revDNS)
  • naics
    North American Industry Classification System Code
  • sector
    Sector of the IP in question
  • tag
    Additional tags for more insight
  • public_source
    Source of the data
  • status
    Status of the affected IP, for example, compromised
  • detail
    Additional details on the event
  • account
    Affected account, if any

Sample

"timestamp","ip","asn","geo","region","city","hostname","naics","sector","tag","public_source","status","detail","account"
"2021-03-12 19:30:00","96.68.x.x",792,"US","TEXAS","SUGAR LAND","96-68.example.net",517311,"Communications, Service Provider, and Hosting Service","exchange","KryptosLogic","compromised","http://96.68.x.x/owa/auth/***EN.aspx",
"2021-03-12 19:30:00","66.225.x.x",261,"CA","ONTARIO","ERIN","example.ca",,,"exchange","KryptosLogic","compromised","http://66.225.x.x/owa/auth/***EN.aspx",
"2021-03-12 19:30:00","199.15.x.x",148,"US","ILLINOIS","CHICAGO","example.com",,,"exchange","KryptosLogic","compromised","http://199.15.x.x/owa/auth/***EN.aspx",
"2021-03-12 19:30:00","223.255.x.x",981,"HK","HONG KONG","HONG KONG",,,,"exchange","KryptosLogic","compromised","http://223.255.x.x/owa/auth/***EN.aspx",

Our 124 Report Types