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

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more