Track Common Adversary Tasks Performed Using Bazar

By Ashwin Venugopal -

 







To know more about it, you can go through my detailed document by clicking here






Overview

Bazar has been in use since at least 2020 as a downloader and backdoor attacking the professional services, healthcare, manufacturing, IT, logistics, travel companies, etc. across the USA as well as Europe. It can also easily deploy the other malware or ransomware to steal the sensitive data via its TrickBot campaigns.

How Does It Works?

Just like every other backdoor, it spreads malware by using spearphishing emails disguised as customer complaints, payroll reports, employee termination lists, etc. containing the links to the Google Docs files. Now once the users click on the link, they will be redirected to a page stating that the said Word Document or Excel Spreadsheet or PDF cannot be viewed properly and they must click on another link to open it. After clicking it, the executable appearing in the form of icons or names related to the file will be downloaded which will later serves as the loader of the backdoor. Hence, when the payload will be injected successfully, the backdoor will be installed in the computer.

Defense

In order to mitigate the cyber threat, you can take following measures:

  • Secure all the possible entry points like malicious sites, spam, third-party components, etc. and be careful while dealing with the files from unknown sources.

  • Always change passwords and reboot the device as it can avoid fileless attacks that doesn't show any persistence when the device is restarted.

  • Make use of behavioral monitoring and analysis in order to block as well as detect any kind of malicious behaviors and routines that can be linked with the malware. 










To know more about it, you can go through my detailed document by clicking here










































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...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
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...
Read more