![]() ![]() The following source code screenshot shows how this is implemented.įigure 4. The watermarking technique is implemented through the module attributes of the assembly. When ConfuserEx performs its obfuscation routine, one of the operations creates a watermark – a unique identifier within the software-that is present in the final binary. Since the string “ConfuserEx v1.0.0-custom” is present in the module property: ”, we can surmise that the version of ConfuserEx that was used for CyaX_Sharp was indeed built outside of Git. Code taken from a ConfuserEx version created outside GIT However, if ConfuserEx is built outside Git, the version update tool will just generate the value “version-custom” as shown below.įigure 3. This build command line has a function to update the final binary versions based on the last Git-tagged version. By examining one of the community-supported versions, we can see there is a tool to build ConfuserEx from the command line. While ConfuserEx is able to apply multiple transformations to the target binary, we are interested in two particular functions that we can use for correlation:ĬonfuserEx is an open-source tool with multiple versions hosted on Github. From there, we can establish a hypothesis as to their source. To understand where this value is coming from, let’s take a look at the open-source ConfuserEx tool to see how the values are created. The module’s property name is “KurdishCoderProducts”, with a value shown to be “ConfuserEx v1.0.0-custom”. The following image shows an assembly module property that was generated for this sample.įigure 2. The infection chain for Capesand that also shows the obfuscation mechanismsįor this particular sample, CyaX_Sharp is obfuscated with a customized version of ConfuserEx. The simplified diagram taken from the previous blog shows the combination of ConfuserEx and Cassandra via the second layer of obfuscation protection, which involves the DLL CyaX_Sharp Assembly (both CyaX_Sharp and CyaX are part of the Cassandra protector).įigure 1. Both of these tools are used in combination to provide an array of fully undetectable capabilities to the deployed njRat malware variant. NET protectors ConfuserEx and Cassandra (CyaX). We found that were multiple layers of obfuscation using a combination of two tools: the. We took a look at one of the samples captured from Capesand that was used to deploy the njRat malware – notably its main executable NotepadEx. We decided to name the potential campaign associated with these IoCs as “KurdishCoder”, based on the property name of an assembly module found in one of the samples. We saw a rising usage of tools that provide fully-undetectable obfuscation capabilities – signifying that the authors behind the samples designed their malware variants to be as stealthy as possible. ![]() ![]() During our analysis of the indicators of compromise (IoCs) in the deployed samples that were infecting the victim’s machines, we noticed some interesting characteristics: notably that these samples were making use of obfuscation tools that made them virtually undetectable.Īfter some data collection we found more than 300 samples that correlate to the mentioned indicators that were recently very active our first detections occurred in August, with the campaign itself still ongoing (having occasional spikes in between). To help users save development costs, you can now pause and resume any non-production cluster while retaining all the stored data.In November 2019, we published a blog analyzing an exploit kit we named Capesand that exploited Adobe Flash and Microsoft Internet Explorer flaws. Cassandra 4.0 is now the default when deploying clusters using the Azure portal or CLI. Check out the important changes in Apache Cassandra 4.0 here. This version of Apache Cassandra is now GA for this service. Watch this space for more updates in the future! In this blog, we’ll give you an update on some of the latest features we’ve released for this service. The service allows you to spend more time focusing on developing your solution while keeping everything you love about Apache Cassandra, and gaining all the benefits of the cloud! Welcome to Azure Managed Instance for Apache Cassandra! A first-party service in Azure, built by Azure Cosmos DB engineers, hosting and maintaining pure open-source Apache Cassandra clusters. Are you self-hosting open-source Apache Cassandra on-premises or in the cloud? What if you could have patching, deployment, scaling, platform security, cloud infrastructure, and live site support taken care of for you… for not much more than the cost of running virtual machines in the public cloud? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |