Track Common Adversary Tasks Performed Using BadPatch

By Ashwin Venugopal -

 





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













Overview

BadPatch, a Windows trojan that was used in a Gaza Hackers-linked campaign was first detected in 2017 and spreads via phishing emails containing the macro-laced attachments with payload of the malware. Although it attacks only Windows systems, but, there are evidences of it being used in targeting Android devices via a bogus app.

Capabilities

After successful infiltration, BadPatch may allow the attackers to:
  • Collect information related to the hardware and software host.
  • Look for certain filetypes and filenames, which will be targeted for exfiltration.
  • Swap between SMTP and HTTP C&C (Command & Control) servers.
  • Take screenshots of the active windows and the user's desktop.
  • Execute a keylogging module that would trace the keystrokes of the victim.


Remedy

The following measures may help in the prevention and mitigation of this trojan:
  • Regular application update is necessary in order to protect against known vulnerabilities;

  • User input validation should be employed so that local as well as remote file inclusion vulnerabilities can be restricted;

  • Use of web application firewall, regular signature virus checkups, application fuzzing, code reviews, server network analysis, etc. can be of much help;

  • Regular system and application vulnerability scans can also highlight any possible areas of concern; etc...


















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