Skip to main content


Showing posts from June, 2021

REvil ransomware gang attacks US nuclear weapons contractor

Ransomware gang REvil breached Sol Oriens at some point last month. Sol Oriens is described consulting firm that works with government agencies to carry out 'complex programs'. As noted in the article, they appear to also work with nuclear weapons systems like the W80-4. If the information stolen by the ransomware gang includes schematics or sensitive information regarding these weapons or other military projects that Sol Oriens may have been working on, that information may now be in the hands of the highest bidder. REvil has said that may forward the information they have to military agencies of their choice. Without a doubt, the situation is precarious as U.S. nuclear weapons information may now be in the hands of seemingly profit-focused threat actors. If an enemy of the country gets ahold of this information the results could be catastrophic. REvil has released information featuring employee payroll records, including social security numbers. They have also released contra

IP header formatting and finding and understanding the content of a packet

 My plan for this week was to go over and talk about IP headers and datagrams. However, while looking through some resources, I find a document that can explain it far better than I can. So instead of diving into the technical nitty-gritty of packets and headers, I'll let Burton Rosenberg of the University of Miami's Computer Science departmen t handy article explain it.  With my original plans for this article taken care of, I instead thought that it would be a good idea to cover how to actually examine a packet and apply this information. It is one thing to know the theory, and another entirely to apply it. With that in mind, I decided to play around with Wireshark and throw together a little demonstration depicting the process.  This is a Wireshark window that shows the HTTP traffic to and from my VM. To generate this information, I started Wireshark, confirmed in the capture options that it was using the correct adapter, and performed a google search. The packet that I'