Careto Malware

By Ashwin Venugopal -

 






Introduction

Careto is a highly sophisticated and professional malware, which was detected by Kaspersky Labs in 2014.  The name Careto is a Spanish slang for "ugly face" or "mask" and is derbied from and ancient Portuguese ritual. The malware was also nicknamed as The Mask. 

It is a piece of cyber espionage malware, that has targeted many diplomatic offices and embassies, gas and oil companies, scientific research organizations, and political activists. Kaspersky believes that its creators are Spanish-speaking and hence it is being operated from Spain. Its victims are mainly Spanish speaking and it had heavily targeted Morocco and Gibraltar. 

More than 380 infected victims have been discovered worldwide. They were infected by simply clicking on the spear phishing mails that redirects them to the websites containing software, like Adobe Flash Player, that Careto can exploit. However, the player had been already patched and can no longer be exploited by Careto. The malware contains multiple backdoors to Linux, Mac OS X, and Windows. It is now common knowledge that the attacks ceased in January 2014.

Characteristics

This malware installs a second and more complex backdoor program called SGH. This program can be easily modified and contains a variety of tools capable of doing many things, like- intercepting system events, file operations, and performing a wider range of surveillance features. Careto and SGH gathers information that can include encryption keys, virtual private networks configurations, and SSH keys and the other communication channels. 

Detection and Mitigation

Due to its stealth capabilities and digitally signed samples, Careto was hard to discover and remove. This malware was discovered when it tried to circumvent Kaspersky security products. Since it was caught while trying to exploit their software, Kaspersky further investigated it. They collected statistics and placed multiple sinkholes on the command and control servers during the process. As of now, the most updated Antivirus software can easily detect and remove this malware. 


To know more, please read- Careto




























































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