Spiceworks also hit by same attack as Solarwinds?

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

AaronK123

New member
Dec 23, 2020
2
0
Does anyone know if Spiceworks (also a monitoring platform) was hit by the same "vulnerability" as Solarwinds? Right now everyone is tightlipped about it.

All I know is that my firewall noticed pings from my Spiceworks server to one of the flagged domains the Solarwinds attack used. We've shut down the server (planning on retiring at some point anyways) and we don't see any evidence of an attack, but I wonder if this attack is more widespread then is being let on at this point.
 
Well, we did some follow up work on this.

The IP our firewall was detecting is a known malware blackhole from the firewall vendor (they will transpose it in as necessary).

During its scheduled scans, the Spiceworks server was pinging the IP to see if it was up. Not sure why, but it was. At this point, we think this is a huge false positive.