Ransomware Shadow

By Ashwin Venugopal -

 




What is Shadow?

Shadow is known as a new variant of a high-risk ransomware, BTCWare, discovered by Michael Gillespie. It infiltrate the network and encrypts most of the stored files. After that, it appends the filenames with its extensions. Once the encryption happens, Shadow opens a pop-up window with a ransom demand message. 

The type of cryptography used by Shadow is unknown. The popped-up ransom message informs the victims about current situation and asks them to a pay a ransom in Bitcoins or Dollars, to restore the encrypted files. They also provide an email address to contact the Shadow's developers. 

However, sending money to cybercriminals simply encourage their malicious activities. They often ignore their victims and there is a high chance that files will not be decrypted even after the reception of the said ransom. Unfortunately, files encrypted by Shadow cannot be restored with the present tools as of now. The only way to restore everything is via backup. 

Note- The backup file must be stored in a remote server (like Cloud) or in an external storage, otherwise the ransomware might infect the backup as well.

How does it works?

Threat actors spreads ransomware via spam emails, unofficial software download sources networks, fake software updaters, and trojans. These files contains infectious attachments in the format of JavaScript files or MS Office documents. When these attachments are opened, they automatically download and install the malware in the system. 

Hence, the cybercriminals tricks the users into downloading and installing the malware. Fake software update tools exploits the bugs or flaws of an outdated software and corrupt the system. Trojans are the simplest, as they simply open "backdoors" for malware to infiltrate the system. 

How to protect against these ransomwares?

Lack of knowledge and mishandling of the system is the key cause of computer infections. Hence, one should be very cautious while browsing the internet and follow following instructions for safety:
  1. Don't open attachments from suspicious email addresses and delete them without reading.
  2. Download applications from official sources only.
  3. Stay up-to-date and use legitimate antivirus or antispyware suite. 
  4. Store backup in a remote server or an external storage. 
  5. Train regularly to handle these situations. 
  6. Update and maintain the backups regularly.



























































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more