Track Common Adversary Tasks Performed Using Asacub

By Ashwin Venugopal -

 







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





Overview

Asacub is a banking trojan and alike the other banking trojans, it steals money from the victim's bank account via SMS messages from already compromised devices. It was first recognized in 2015 and targeting the Android users since then. Although it generally targets Russia, but, there are evidences that it also targets banks of various countries like USA, Poland, the Czech Republic, Ukraine, etc.

How Does it Spreads?

The threat actors of Asacub covers their creation in the guise of MMS or SMS application with generic names like, 'Message', 'Avito Offer', 'Photo', 'SMS Message', etc. and urges the users to download an '.APK' file in order to view its content, that always contains payload of the Asacub Banking Trojan and if the users fall for it, then they can easily perform their malicious activities, and even if the users doesn't fall into the trap, then, the bogus application continues to spam the device until they (users) agree. The Asacub Trojan can:
  • Collect data from the contacts list.
  • Read the text messages of the user.
  • Send text messages.
  • Stop the activity of any anti-malware apps present in the device.
  • Halt the activity of any banking apps present in the device.

Remedy

The most feasible way to protect a device from Asacub is to use a robust antivirus which is capable of detecting as well as blocking all the existing versions of it. However, if you prefer to use a free version of an antivirus, then, you have to run the manual scans regularly to prevent any kind of infection.  









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