Track Common Adversary Tasks Performed Using BendyBear

By Ashwin Venugopal -

 



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








Overview

BendyBear, an x64 shellcode used for a stage-zero implant that's designed to download malware from a C2 server, was first detected in 2020 and also shares some of its features with Waterbear.

Capabilities

Some of the important capabilities of BendyBear are:
  • It can easily transmit payloads into modified RC4-encrypted chunks because one RC4 key can't decrypt the entire payload. 

  • It's very difficult to detect as it can perfectly hide from cybersecurity by checking its environment for signs of debugging.

  • It can clear the host's DNS cache whenever it tries to communicate with C2 server, hence, resolving the current IP address of the malicious C2 domain every time.

  • Exclusive session keys are generated for every C2 server connection.

  • As it uses polymorphic code, it can completely change its runtime footprint during code execution in order to thwart memory analysis and avoid sign signaturing.

  • It regularly encrypt or decrypt function blocks as required to avoid detection.

  • It makes use of Position Independent Code (PIC) to throw off static analysis tools.

Prevention

The following measures might help in mitigating the cyber threat:
  • Regularly review as well as update the existing security rulesets. 
  • Block unknown outbound TCP traffic in security policies whenever required.
  • Always update the software and mitigate any identified vulenarbilities.
  • You can also enhance perimeter and endpoint defense with the help of the techniques like whitelisting, behavior analysis, and sandboxing via advanced endpoint & network security solutions.







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