Organizations are constantly under target of cyber attacks and data breaches. New attacks keep coming. Sometimes the older attacks end up working and other times, these older attacks get some modification to perform a zero-day to compromise an organization. In today’s post, we will learn about a very interesting attack - the SupplyChain attack.
You can check my previous blog posts here where I discussed some good security jargons and attacks that a security professional should be aware of.
While comprehending Supply Chain Attacks, we will take a sneak peek at two organization’s attack scenarios.. So, let’s get started. :)
Let us first understand what a SupplyChain means before we start.
A supply-chain is a process of making commercial products from scratch including the supply and manufacturing of the materials, till the selling of them. Every stage is important and counted in a supply chain process and hence the name.
In supply Chain every step is critical hence compromising any stage leads to supply chain attacks. The attacks focus on the less-secure elements in the process. This is an universal attack scenario for organizations. Most of the time, the attackers tamper with the manufacturing processes.
APTs play a very vital role here. You can learn about APTs from here. For now, we can understand that APTs are Advanced Persistent Threat which looks for the weakest link in a product or network in an organization to sit over there and gradually take control of the active directory or other admin domains. SupplyChain attacks generally begin from here.
There are some infamous victims here: British Airways, Solarwinds, Microsoft exchange server
Now let’s dive a bit deeper into two infamous supply chain attacks and try to understand what happenes.
We all are aware of the very well-known Solarwinds Supply chain hack that happened recently. First of all, let us understand what Solarwind is? Solarwind is an American-based company that develops software to help companies to maintain their IT infrastructure like networking. The company has various products used for monitoring networks. The attackers targeted the Orion System and inserted a malicious code in there, with the help of a supply chain attack. They made use of the Sunburst backdoor that was a digitally signed plugin of the Solarwinds Orion plugin, which is called SolarWinds.Orion.Core.BusinessLayer.dll. The plugin communicates to the third-party servers through HTTP. The backdoor remains quiet for about 2 weeks before performing further attacks like executing commands, transferring files, and many more. It keeps the information to be used later for future attack stages.
This is how the attackers found the weakest link to set up the backdoor. This led to the supply chain attack that further affected those companies which used the Solarwind product for their use.
Let us understand another scenario of a supply chain attack.
Open source projects are no way more secure than any commercial ones. A Supply chain attack has affected one GitHub project too that targeted the NetBeans IDE repositories. The malware used was Octopus Malware which was designed to infect the NetBeans projects.
The malware would use a cache.dat file to infect the nbproject directory. And every time the project is built, it infects the .class and the jar files which are generated inside the jar file during the build process. Malwares don’t just infect the files , they also create a backdoor to the system and communicate with the command and control server. This command and control server can build communication whenever it wants to and execute commands and move files as it wants.
To conclude, nothing can be 100% secure but we can always take precautions to reduce the risk. We will have to keep monitoring and patching each component of the tool or project so that any weak link can be taken care of before getting under the control of a malicious user. We can always learn from the previous examples and reduce the risk as far as possible.