Track Common Adversary Tasks Performed Using Android/AdDisplay.Ashas

By Ashwin Venugopal -

 





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







Overview

Android/AdDisplay.Ashas is a type of adware abundantly found in the multiple apps of google store. After successfully launched, this app communicates with C&C server and send data (like language, number of installed apps, etc.) of the infected device to the operator in order to display fraudulent ads.

Techniques & Tactics

In order to attack stealthily, the threat actors follow the steps given below:
  • Firstly, the attackers or the app determines if they will be tested by the Google Play security mechanism, and if they does, then, the app will not trigger the adware payload or vice versa.

  • After launching, the app can also set custom delays between the displaying ads which will not be detected, as typical test methods takes around 10 minutes to test any kind of unwanted behavior.

  • The app can also hide its icon by creating a shortcut and when a user tries to delete it, only the shortcut will be removed while the app will continue to harm the device secretly. This one is the most popular among the other techniques. 

Effects

As the agenda of these app developers is hidden, they are considered untrustworthy and their adware can do the following along with the other things:
  1. Annoy users with intrusive advertisements, including scam ads.
  2. Waste the device's battery resources.
  3. Generate increased network traffic.
  4. Gather users' personal information.
  5. Hide their presence on the affected device to achieve persistence.
  6. Generate revenue for their operator without any user interaction.






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