<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by S3N4T0R on Medium]]></title>
        <description><![CDATA[Stories by S3N4T0R on Medium]]></description>
        <link>https://medium.com/@S3N4T0R?source=rss-9a3478d109f8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*p61BfW_9xbtbqe3L</url>
            <title>Stories by S3N4T0R on Medium</title>
            <link>https://medium.com/@S3N4T0R?source=rss-9a3478d109f8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:22:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@S3N4T0R/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Helix Kitten APT Adversary Simulation]]></title>
            <link>https://medium.com/@S3N4T0R/helix-kitten-apt-adversary-simulation-da69f67fc018?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/da69f67fc018</guid>
            <category><![CDATA[helix-kitten]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[adversary-simulation]]></category>
            <category><![CDATA[adversary-emulation]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 08:23:11 GMT</pubDate>
            <atom:updated>2026-10-11T08:23:11.413Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a simulation of attack by (Helix Kitten / APT34 / OilRig) APT group targeting multiple sectors across the Middle East including finance, government, energy, chemical industry, and telecommunications entities. The campaign uses a fake marketing services company called “GGMS” (Ganjavi Global Marketing Services) and malicious Word documents to deliver “SystemFailureReporter” — a GCC-compiled variant of the SideTwist Trojan. The attack campaign was active as early as August 2023. The attackers have relied on base64-encoded payloads and scheduled tasks for initial access and persistence. The introduction of GCC-compiled variants represents a notable tooling evolution toward more portable and low-noise backdoor capabilities. I relied on NSFOCUS to figure out the details to make this simulation: <a href="https://nsfocusglobal.com/apt34-unleashes-new-wave-of-phishing-attack-with-variant-of-sidetwist-trojan/">https://nsfocusglobal.com/apt34-unleashes-new-wave-of-phishing-attack-with-variant-of-sidetwist-trojan/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*MP4p9HbFlIKFoDK20G5QuA.jpeg" /></figure><p>Throughout, the macro itself is heavily obfuscated to dodge static detection, and the overall chain emphasizes low-noise execution with anti-sandbox tricks built into the Trojan. This progression — phishing email → malicious doc → base64-encoded dropper → SideTwist variant — shows Helix Kitten’s shift toward more resilient modular tooling in recent campaigns targeting Middle East sectors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*00Ndma_wY37h9X08PoPLgw.png" /></figure><ol><li>Delivery Technique: Create a document file named GGMS_Overview.doc which is used in the next stage to embed and execute a VBA macro loader that extracts and drops the subsequent payload.</li><li>Malicious VBA macro: The malicious VBA macro embedded in the document is heavily obfuscated, extracting a base64-encoded payload hidden within the document structure, decoding it, and writing it to disk.</li><li>SystemFailureReporter Trojan: The final payload dropped by the VBA macro loader is a GCC-compiled executable (SystemFailureReporter.exe), a variant of the SideTwist Trojan, featuring anti-sandbox checks and HTTP-based C2 communication.</li><li>C2 infrastructure: relies on HTTP protocol for all communications, using a custom URI path containing the victim ID. Data payloads are structured as HTML responses with hidden instructions between script tags, encoded in Base64 followed by a multi-byte XOR encryption layer (key: “notmersenne”) to obfuscate traffic and complicate analysis.</li></ol><h4>The first stage Kill Chain (delivery technique)</h4><p>The attack kicks off with a spear-phishing email disguised as a legitimate marketing services company. The decoy file is called “GGMS Overview.doc”, and the document’s body shows an introduction to a so-called “Ganjavi Global Marketing Services” company. The introduction claimed that the company was able to provide worldwide marketing services. Apparently, it targets enterprises. There are twice upload records, located in the United States, demonstrating that APT34 was actually targeted at United States businesses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PeSGxlq7kOZqhFhH5LsUgQ.jpeg" /></figure><p>The email carries an attachment named GGMS_Overview.doc which acts as the initial payload. When the recipient opens the document and enables macros (as prompted), an obfuscated VBA macro runs. This macro extracts a base64-encoded blob hidden in the document’s structure, cleans it up, converts it to binary, and drops it as SystemFailureReporter.exe in the %LOCALAPPDATA%\SystemFailureReporter\ directory. It also creates a text file named update.xml under the same directory, acting as the start switch of the Trojan program</p><h4>The second stage (Malicious VBA macro and Base64-encoded)</h4><p>A special thanks to <a href="https://www.linkedin.com/in/m4v3x/"><strong>Mahmoud Mohamed</strong></a> for his valuable contribution to this adversary simulation project. He was responsible for developing and refining the VBA macro components used throughout this simulation. His expertise and contributions played an important role in making this project possible.</p><h3>1. Sub AutoOpen()</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zjhpbpnMtBvSTWu2c9928Q.png" /></figure><p>It executes the code automatically when the document is opened. Then the following actions run automatically:</p><ol><li>Asks Windows for the %LOCALAPPDATA% path → gets C:\Users\&lt;User&gt;\AppData\Local, then adds \SystemFailureReporter\ to it. This spot is hidden and needs no admin rights. It then checks if that folder exists — if not, it creates it.</li><li>Takes the Base64 string (the payload) and decodes it back into raw EXE bytes using Base64Decode(), then writes those bytes to disk as SystemFailureReporter.exe inside the folder.</li><li>Creates an empty update.xml file as a decoy.</li><li>Runs a hidden schtasks command that registers a task named SystemFailureReporter to launch the EXE every 5 minutes. No window pops up.</li></ol><h3>2. REGISTRY PERSISTENCE</h3><p>Once the anti-analysis checks pass, SystemFailureReporter.exe establishes robust persistence via a scheduled task to ensure it survives system reboots:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vgCoPoX8nBRtWBlk6B89kQ.png" /></figure><p>The implant cleverly disguises itself as a legitimate Windows component (SystemFailureReporter), making it less suspicious to casual observers. The persistence mechanism includes:</p><ul><li>Scheduled task named “SystemFailureReporter” that runs every 5 minutes</li><li>Path validation to ensure the executable exists at the specified location</li><li>Startup verification to confirm the scheduled task was successfully created</li></ul><p>This ensures that every time the scheduled task is triggered, SystemFailureReporter.exe automatically executes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*JQ7RdOru4CfTHodV0b95UA.png" /></figure><h4>The third stage (SystemFailureReporter implanting technique)</h4><p>SystemFailureReporter represents the main payload and the backbone of the entire adversarial operation in Helix Kitten group attacks. SystemFailureReporter is a GCC-compiled executable (SystemFailureReporter.exe) known as a variant of the SideTwist Trojan, featuring strong anti-sandbox evasion and HTTP-based C2 communication.</p><h4>1. ANTI-ANALYSIS</h4><p>SystemFailureReporter.exe implements an anti-analysis system that actively probes the execution environment for signs of monitoring or sandboxing. Each layer acts as a filter ensuring the payload only detonates on a genuine target.</p><p><strong>Layer 1: update.xml Check</strong></p><p>After the Trojan runs, it will first check whether there is a file named update.xml in the same directory. If not, output a line of prompt text through the debugging port and exit. This is a typical anti-sandbox operation.</p><p><strong>Layer 2: Victim Fingerprinting</strong></p><p>The Trojan will then collect the user name, computer name and local domain name of the victim’s host, assemble and calculate a 4-byte hash as the unique ID of the victim.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zanMnYqFVQyhUuU-2vXj_A.png" /></figure><h4>2. C2 COMMUNICATION</h4><p>The final and most sophisticated capability is C2 communication over HTTP, allowing the implant to receive commands and exfiltrate data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XX2SR33eO4fe2lPSoeHpVg.png" /></figure><p>SystemFailureReporter.exe implements a classic but effective C2 communication technique:</p><ul><li><strong>Process Discovery:</strong> The Trojan attempts to establish communication with the C2 and obtain return information using the generated victim ID.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-UYP3gyyeHva9B6KQQRvg.png" /></figure><ul><li><strong>Instruction Extraction:</strong> If the C2 path is online, the Trojan will extract and parse specific contents in the HTML code returned by C2 into C2 instructions. These specific contents are hidden between &lt;script&gt;/* and */&lt;script&gt; tags of the HTML code.</li><li><strong>Decryption:</strong> The C2 instruction is stored in base64 encoding and decrypted as a multi-byte XOR key with the string “notmersenne”.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s9w2m6kGXbiQ9_pNeoL43w.png" /></figure><p><strong>Execution:</strong> The decrypted C2 instruction is divided into three segments, namely C2 number, C2 instruction code and operating parameters, which are separated by the symbol “|”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SyLvtn_2tdyRa3uiYdQumw.png" /></figure><p>This technique allows the attackers to hide their malicious instructions inside seemingly benign HTML responses, making detection significantly more difficult for security solutions.</p><p><strong>C2 Instruction Codes:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r2lsS25FSH6GziFS3xq0bQ.png" /></figure><p><strong>Important:</strong> The 102 instruction code of this Trojan will trigger a subsequent C2 communication behavior. The Trojan program will initiate an HTTP GET request according to the remote file name in the C2 instruction parameters, obtain and decrypt the files in the remote location “/getFile/[file name]”. The decryption method is also base64 transcoding and multi-byte XOR.</p><p>After all the above C2 instructions are completed, the Trojan will reply an HTTP POST request to the C2 to report the instruction execution result. The POST request body contains information in the following format:</p><pre>{&quot;[C2 number]&quot;:&quot;[C2 instruction execution result]&quot;}</pre><p>Unlike common Trojan programs, this Trojan does not have a cyclic or sleep mechanism and will automatically exit after a C2 communication, waiting for the scheduled task to invoke the Trojan again 5 minutes later.</p><p>Open <a href="https://github.com/S3N4T0R-0X0/BEAR-C2">BEAR-C2</a>, go to Reapr Node. In the Prepend field put &lt;script&gt;/*, and in the Append field put */&lt;script&gt;</p><h4>Example</h4><p><strong>Prepend:</strong></p><pre>&lt;body&gt;<br>    &lt;h1&gt;Welcome&lt;/h1&gt;<br>    &lt;script&gt;/*</pre><p><strong>Append:</strong></p><pre>&lt;p&gt;Some normal content&lt;/p&gt;<br>  &lt;/body&gt;<br>&lt;/html&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-2hfj176mLhSHOoh6iUPzQ.png" /></figure><h4>Final result: (Actual payload connect to BEAR-C2 server)</h4><p>This payload establishes an HTTP connection to a remote server for command execution. It communicates using custom-formatted messages, with all data encrypted using XOR key “notmersenne”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nCymvEdVTQD9Vjo7BHnxfA.png" /></figure><p>The client authenticates with a predefined victim ID and executes commands received from the server supporting both CMD and PowerShell commands. Output from executed commands is XOR encrypted and sent back to the server in HTML format. Data is also Base64 encoded for safe transmission.</p><h4>Pivoting technique</h4><p><strong>VBA Macro Code Reuse:</strong> The macro code extracted from GGMS_Overview.doc exhibits striking similarities to previously documented APT34 campaigns. Specifically, the base64-encoded payload embedding and the scheduled task creation patterns, including the distinctive use of %LOCALAPPDATA%\SystemFailureReporter\ directory.</p><p>The campaign analysed in this report shares significant overlap with another report. Similar TTPs can be observed in that chain too where the initial email was impersonating a legitimate marketing services company.</p><h4>MITRE ATT&amp;CK Techniques</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-oEj3OmRTTvSHfc9wZe6zw.png" /></figure><p>Github repository: <a href="https://github.com/S3N4T0R-0X0/APTs-Adversary-Simulation/tree/main/Iranian%20APT/Helix%20Kitten">https://github.com/S3N4T0R-0X0/APTs-Adversary-Simulation/tree/main/Iranian%20APT/Helix%20Kitten</a></p><p>X: <a href="https://x.com/S3N4T0R_0X0">https://x.com/S3N4T0R_0X0</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da69f67fc018" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Muddy Water APT Adversary Simulation]]></title>
            <link>https://medium.com/@S3N4T0R/charming-kitten-apt-adversary-simulation-fa6257b42811?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa6257b42811</guid>
            <category><![CDATA[adversary-simulation]]></category>
            <category><![CDATA[adversary-emulation]]></category>
            <category><![CDATA[red-team]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 07:27:49 GMT</pubDate>
            <atom:updated>2026-09-14T21:15:10.402Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a simulation of an attack by the APT group Muddy Water, targeting multiple sectors including government, military, and critical infrastructure across the Middle East. The group’s targeting has expanded beyond government entities to include the maritime, aviation, and financial sectors, reflecting a growing interest in regional logistics and critical economic infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/1*NEfNILKAu9L2xzW6UMjMhw.png" /></figure><p>Recent campaigns (Operation Olalampo) have targeted entities in Egypt, Saudi Arabia, the UAE, Turkey, Hungary, Turkmenistan, Israel, and South America. These attacks demonstrate the group’s ability to pivot between sectors while conducting multiple operations simultaneously. The campaign was active throughout 2025 and 2026. This simulation is based on research from</p><p>Palo Alto Unit 42: <a href="https://unit42.paloaltonetworks.com/boggy-serpens-threat-assessment/">https://unit42.paloaltonetworks.com/boggy-serpens-threat-assessment/</a></p><p>and Group-IB: <a href="https://www.group-ib.com/blog/muddywater-operation-olalampo/">https://www.group-ib.com/blog/muddywater-operation-olalampo/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ncTKOePlYZwy2ChRjgYCmA.png" /></figure><p>In this campaign, the blurred document lure delivers a new payload as a custom HTTP backdoor. To maintain persistence, the group has evolved its development approach by leveraging AI-generated code and Rust-based tools, such as the BlackBeard backdoor, to rapidly deploy custom implants. Additionally, the group uses standard HTTP status codes, customized UDP based traffic, and the Telegram API for C2 communications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*zcIjAsfaSCzxMoUYukTb_Q.png" /></figure><h3>The first stage (delivery technique)</h3><p>The initial campaign targeted project engineers using industry-specific terminology for subsea pipelines. The lure document was blurred in order to deceive targets into clicking “Enable Content” thereby triggering the execution of the embedded macro.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1K4ApOE295QCvQ2zXgAx3A.png" /></figure><p>In another wave the attack group delivered a malicious Excel and Word files designed to mimic the target’s internal financial records. The lure appeared as a legitimate spreadsheet containing payment details and cash flow projections.</p><p>The infected document included specific references to “Engineering, Construction &amp; Marine Services” and used local currency (AED), along with realistic transaction descriptions such as “Payroll Payments via WPS” making it highly convincing to the target.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*UzmgpsNEk6LP5q6una4Zaw.png" /></figure><p>• Exploiting Trusted Relationships for Payload Delivery</p><p>Throughout the past year, Muddy Water systematically abused trusted relationships by hijacking official government and corporate email accounts to bypass traditional email security controls and filtering mechanisms. This technique was observed in more than 15 targeted operations conducted across multiple regions worldwide.</p><p>In August 2025, the group leveraged a compromised mailbox belonging to the Omani Ministry of Foreign Affairs to distribute malicious documents to foreign ministries and diplomatic entities in several countries. The delivered files were disguised as legitimate diplomatic communications and official government correspondence, increasing the likelihood of recipient interaction and trust.</p><p>Following the regional conflicts in June 2025, the group also launched a themed phishing campaign using a “Sustainable Peace” seminar invitation as a lure. The invitation was crafted to appear as a legitimate geopolitical or diplomatic event, aiming to encourage engagement from targeted individuals within government, policy, and international relations sectors.</p><p>These operations demonstrate the group’s continued reliance on social engineering, trusted relationship abuse, and geopolitical themes to enhance credibility and improve payload delivery success rates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*4OATREgzlT1mNCR1VvzpNA.png" /></figure><h3>The second stage (Malicious VBA Macro with Conditional Download and Execution)</h3><p>A special thanks to <a href="https://www.linkedin.com/in/m-montaser?utm_source=share_via&amp;utm_content=profile&amp;utm_medium=member_android"><strong>Mohamed Montaser</strong></a> for his valuable contribution to this adversary simulation project. He was responsible for developing and refining the VBA macro components used throughout this simulation. His expertise and contributions played an important role in making this project possible.</p><p><strong>Sub </strong><strong>love_me_____():</strong> Acts as the primary controller for the entire macro, coordinating the payload workflow from start to finish. The routine begins by decoding an obfuscated file path from a hexadecimal string, concealing the actual location until runtime to reduce static detection. It then checks whether the target payload already exists on the system. If the file is found, the macro immediately transfers execution to the execution routine. If the file is not present, it invokes the download routine to retrieve the payload before executing it. This conditional logic allows the macro to support both first-time infections and subsequent executions without downloading the payload multiple times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_bY2-WOrqWmo4rDAhnQjIg.png" /></figure><p><strong>Sub </strong><strong>DownloadAndRun:</strong> Responsible for retrieving the payload when it is not already available on the system. The function decodes a hexadecimal-encoded URL at runtime and uses the Windows HTTP API (WinHttp.WinHttpRequest) to request the remote file. If the download succeeds, the response is written to disk in binary format at the previously decoded file path. Once the file has been successfully saved, the function immediately invokes the execution routine, allowing the newly downloaded payload to run without requiring additional user interaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UQ6qK18wbjz2wBKIHtUpOw.png" /></figure><p><strong>Function </strong><strong>DecodeHex:</strong> Provides the string deobfuscation mechanism used throughout the macro. Rather than storing sensitive strings such as file paths or network locations in plain text, the macro represents them as hexadecimal data and reconstructs them only when needed. This technique is commonly used to obscure static indicators and reduce the visibility of embedded strings during basic inspection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xaiEe8e7uBP5y7mKLG2i4A.png" /></figure><p><strong>Sub </strong><strong>ExecuteFile:</strong> Serves as the execution component of the macro. After receiving the target file path, it attempts to launch the payload using multiple execution methods. The routine first executes the file through the VBA Shell function with a hidden window and then invokes a secondary execution method through Windows Script Host, providing an alternative launch mechanism. Using more than one execution technique increases execution reliability if one method encounters an error.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4bJt3H5g6InvX7YW_IvpLQ.png" /></figure><p><strong>Sub </strong><strong>AutoOpen:</strong> Acts as the automatic entry point for the macro. When the Office document is opened and macros are enabled, this procedure is triggered automatically and immediately calls love_me_____(), initiating the complete workflow without requiring any further interaction from the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jNlaUfstDUg-TAgr8n26fA.jpeg" /></figure><h3>The Third Stage (Telegram-based Agent)</h3><p>The initial objective of this stage is to enhance the realism of the adversary simulation by replacing the traditional direct command and control communication channel with a Telegram-based communication layer. Instead of requiring operators to interact with the payload through a dedicated control server, commands are exchanged through a Telegram bot, allowing the simulation to emulate an alternative communication workflow commonly observed in modern threat campaigns.</p><p>This phase focuses on demonstrating how a trusted cloud messaging platform can serve as an intermediary communication channel between the operator and the simulated implant. By leveraging Telegram as the transport layer, the simulation highlights how legitimate online services may be used to blend command and control traffic with normal network activity while maintaining reliable bidirectional communication.</p><p>All adversary simulations are powered by <a href="https://github.com/S3N4T0R-0X0/BEAR"><strong>BEAR-C2</strong></a> a custom command and control framework designed for realistic threat simulation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-EGr0j9LX0eT1UF2webGMg.png" /></figure><p>The operator communicates with the Telegram bot by sending commands through a private Telegram chat. The bot acts as the communication gateway, relaying operator instructions to the simulated implant and returning execution results through the same encrypted channel. From the operator’s perspective, Telegram becomes the primary interface for tasking the implant, while the underlying communication remains transparent to the simulation workflow.</p><p>This enhancement demonstrates an alternative command and control architecture that relies on widely used cloud messaging infrastructure instead of dedicated C2 servers, enabling defenders to better understand, analyze, and detect communication patterns associated with cloud-based adversary simulations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*2b_OS80xPi9CsfLS5eJARw.png" /></figure><p>To simulate the communication workflow observed during the analysis, I created a dedicated Telegram bot using <strong>BotFather</strong>, Telegram’s official bot management service. Unlike traditional command and control infrastructures that depend on dedicated servers, fixed IP addresses, or custom domains, this simulation communicates exclusively through the Telegram Bot API over encrypted HTTPS connections.</p><p>Following the same communication model, I configured the bot with the <strong>Display Name</strong> Olalampo and the <strong>Username</strong> stager_51_bot. The bot token generated by BotFather serves as the authentication mechanism, allowing BEAR-C2 to establish communication with the Telegram Bot API without requiring a dedicated C2 server. This approach demonstrates how cloud messaging platforms can be incorporated into adversary simulations to emulate alternative command and control architectures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yw1eXagJXEzYcm2zwgMBLQ.png" /></figure><p>Telegram API Setup</p><p>To enable BEAR-C2 to communicate with the Telegram account controlling the bot, I generated a Telegram <strong>API ID</strong> and <strong>API Hash</strong> through Telegram’s developer portal. After registering a new application, these credentials were configured inside BEAR-C2, allowing the framework to authenticate and interact with the Telegram account used throughout the simulation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L3w5ZSRmn9sb5NexD0NwLw.jpeg" /></figure><p>CHAR.cpp Configuration</p><p>The final stage consisted of configuring the Telegram communication module inside <strong>CHAR.cpp</strong>. The <strong>Bot Token</strong> generated by BotFather was embedded into the agent, allowing it to authenticate with the Telegram Bot API and establish bidirectional communication with the operator.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*CV4VlsUHDCmPOiwy2MRvbg.png" /></figure><p>Since Telegram limits a single text message to <strong>4096 characters</strong>, the maximum message size was configured to <strong>4000 characters</strong> to provide a safe transmission margin. Whenever a command produces output larger than the configured limit, <strong>CHAR.cpp</strong> automatically splits the data into multiple sequential messages before transmitting them. This mechanism ensures reliable delivery of large command outputs while remaining fully compatible with the Telegram Bot API and maintaining continuous communication throughout the simulation.</p><p><strong>main():</strong> Serves as the entry point of the payload and initializes the entire agent. After startup, it continuously communicates with the configured Telegram bot, periodically checking for new operator messages. Every incoming command is processed through the command dispatcher, while responses are returned back to the operator through the same communication channel. This continuous polling mechanism allows the agent to remain responsive throughout its execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tHsx-j_RbVMbcH5XXbKJvg.png" /></figure><p><strong>get_updates:</strong> Acts as the communication receiver for the agent. It establishes secure HTTPS connections using the Windows WinHTTP API and continuously polls the Telegram Bot API for new messages. Each received update is parsed from JSON format before being forwarded to the message processing routine, allowing the payload to receive operator instructions remotely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hOVG5Kkd7IDXgSL2BdzNUQ.png" /></figure><p><strong>process_message:</strong> Functions as the command processor responsible for handling operator requests. It reconstructs multi-part messages, processes encoded commands when required, and forwards completed commands to the execution engine. Once execution is complete, large outputs are automatically divided into smaller chunks before being transmitted back to the operator, allowing lengthy responses to be delivered reliably through Telegram.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QuiOAq0meslCY8_e32xZcA.png" /></figure><p><strong>execute_command:</strong> Serves as the central dispatcher for all incoming tasks. It determines which internal functionality should be used based on the received instruction and routes the request to the appropriate component. Depending on the command type, it can invoke built-in file management capabilities, directory browsing routines, or the command execution engine before returning the collected results to the communication layer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0dsGJ1ccHJb8X1VfLe3ygg.png" /></figure><p><strong>run_command:</strong> Acts as the local command execution engine. It creates hidden child processes, captures their standard output, and returns the generated results to the agent. The collected output is then passed back through the communication channel, allowing the operator to receive execution results remotely.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X4iHRTbFH8RzOQNJUSVNDQ.png" /></figure><p><strong>browse_directory:</strong> Provides remote directory enumeration capabilities by traversing the requested folder and collecting information about its contents. The gathered information is organized into structured JSON data before being returned to the communication layer, allowing the operator to remotely inspect directory structures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/1*KuyHFKjdqtXcsqlb-nA7vQ.png" /></figure><p><strong>download_file, </strong><strong>upload_file, </strong><strong>delete_file, and </strong><strong>rename_file:</strong> Together these routines provide the agent&#39;s file management capabilities. They are responsible for handling file transfer operations, filesystem modifications, and basic file management tasks. Data exchanged during file transfers is encoded to ensure it can be transmitted safely through the communication channel before being reconstructed on the receiving side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*muX4QIY8MVLcfIgEhyYdEA.png" /></figure><p><strong>base64_encode, </strong><strong>base64_decode, and </strong><strong>decode_base64_command:</strong> These helper functions provide the encoding and decoding mechanisms used by the agent. They convert data between its original binary representation and Base64 format, allowing commands, files, and structured data to be safely transmitted through the messaging channel while supporting message reconstruction for larger payloads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gNY71yJCz3QM9qDds92O6Q.png" /></figure><p><strong>send_telegram_message:</strong> Acts as the outbound communication component of the agent. It formats execution results, prepares outgoing messages, and sends them back to the configured Telegram chat using HTTPS requests through the Telegram Bot API. Large outputs generated by the payload are transmitted in multiple parts to accommodate Telegram message size limitations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GocYK-DCe-9TTBnikcaaLw.png" /></figure><h3>The fourth stage (Payload Hosting and VBA Integration)</h3><p>After completing the Telegram communication component, the next stage is to compile the payload, producing the final executable that will be delivered during the simulation. Once the build process is complete, the generated executable is uploaded to a file hosting service, which provides a direct download URL that can be accessed over HTTPS.</p><p>The generated download URL is then integrated into the VBA macro by replacing the placeholder URL with the actual hosting link. This allows the macro to retrieve the latest payload dynamically instead of embedding it directly inside the Office document, making the simulation more modular and allowing payload updates without modifying the macro itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4CExeBqUza10mVMPupBOg.png" /></figure><p>When the document is opened and the macro is executed, it checks whether the payload already exists on the target system. If the file is not present, the macro silently downloads it from the configured hosting URL in the background, stores it in the predefined location, and immediately launches it. The entire process is performed without requiring additional user interaction, providing a seamless delivery workflow that closely resembles the staged payload delivery techniques commonly demonstrated in adversary simulation scenarios.</p><h3>BEAR C2 — Telegram Command and Control</h3><p>The final result of this enhancement is a fully integrated <strong>Telegram Command-and-Control (C2) channel</strong> within <strong>BEAR C2</strong>. Rather than serving as a standalone proof of concept, Telegram becomes a native communication channel that allows operators to manage active sessions directly from the BEAR C2 interface. The integration is powered by the <strong>Telethon</strong> library, enabling seamless interaction with the Telegram platform while abstracting the underlying communication from the operator.</p><p>Authentication and secure communication are handled through <strong>Telegram’s MTProto protocol</strong>, which provides encrypted communication between BEAR C2 and the Telegram infrastructure. Operators simply configure their <strong>API ID</strong>, <strong>API Hash</strong>, <strong>phone number</strong>, and <strong>bot username</strong> within the Authentication settings, after which BEAR C2 establishes the connection and manages all Telegram-based communications automatically.</p><p>Once the integration is enabled, operators can issue commands, receive execution results, and monitor active sessions through the Telegram C2 channel without interacting directly with the Telegram Bot API. Command outputs are automatically collected and returned to the BEAR C2 interface, providing a centralized operational experience while leveraging Telegram as the underlying transport layer.</p><p>Telegram is one of several communication channels supported by <strong>BEAR C2</strong>. The framework is designed with a multi-channel C2 architecture that also supports other communication methods, such as <strong>Discord</strong>, allowing operators to choose the most appropriate transport for their adversary simulation scenarios.</p><p>More importantly, the Telegram integration extends beyond basic command relay. Once a session is established, operators gain access to the full capabilities of <strong>BEAR C2</strong>, including its <strong>Arsenal</strong> of post-exploitation tools and automation features. This enables operators to execute integrated tools, perform post-exploitation activities, manage sessions, and coordinate complex adversary simulation workflows from a single interface, providing a complete command-and-control experience rather than a simple proof-of-concept communication channel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*LejZGwYU5qhuUBS-xBQWBA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa6257b42811" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Static Kitten APT Adversary Simulation]]></title>
            <link>https://medium.com/@S3N4T0R/static-kitten-apt-adversary-simulation-8f595aa74118?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f595aa74118</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[adversary-emulation]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[apt-group]]></category>
            <category><![CDATA[adversary-simulation]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Sun, 17 May 2026 13:04:24 GMT</pubDate>
            <atom:updated>2026-05-17T13:08:44.224Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a simulation of attack by (Static Kitten) APT group targeting multiple sectors across the Middle East including diplomatic, maritime, financial, and telecom entities. The campaign uses icon spoofing and malicious Word documents to deliver &quot;RustyWater&quot; a Rust-based implant representing a significant upgrade to their traditional toolkit, the attack campaign was active early as January 2026. The attackers has relied on PowerShell and VBS loaders for initial access and post-compromise operations. The introduction of Rust based implants represents a notable tooling evolution toward more structured modular and low noise RAT capabilities. I relied on cloudsek to figure out the details to make this simulation: https://www.cloudsek.com/blog/reborn-in-rust-muddywater-evolves-tooling-with-rustywater-implant</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*-rulozZiFpX-W_08XgQyAQ.jpeg" /></figure><p>Throughout, the macro itself is heavily obfuscated to dodge static detection, and the overall chain emphasizes low-noise execution with strong anti-analysis tricks built into the Rust binary. This progression — phishing email → malicious doc → obfuscated macro dropper → RustyWater implant — shows Static Kitten’s shift toward more resilient modular tooling in recent campaigns targeting Middle East sectors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*rWvXhfgGe4NEwfu1CGhEJg.jpeg" /></figure><ol><li>Delivery Technique: Create a document file named Cybersecurity.doc which is used in the next stage to embed and execute a VBA macro loader that extracts and drops the subsequent payload.</li><li>Malicious VBA macro: The malicious VBA macro embedded in the document is heavily obfuscated using string concatenation, hex-encoded payloads hidden in UserForm controls, multiple Replace() calls to strip whitespace and line breaks.</li><li>RustyWater implant: The final payload dropped by the obfuscated VBA macro loader is a Rust-compiled executable (disguised as reddit.exe with a fake Cloudflare icon), known as RustyWater (or linked to Archer RAT/RUSTRIC), featuring strong AV/EDR evasion through process injection, registry based persistence.</li><li>C2 infrastructure: relies on HTTP protocol for all communications, leveraging the Rust reqwest library with configurable timeouts, connection pooling, and retry mechanisms for reliability. Data payloads are structured as JSON, then encoded in Base64 followed by a final XOR encryption layer to obfuscate traffic and complicate analysis.</li></ol><h4>The first stage Kill Chain (delivery technique)</h4><p>The attack kicks off with a spear-phishing email sent from the compromised info@tmcell address a legitimate domain tied to TMCell (Altyn Asyr CJSC), Turkmenistan’s main mobile telecom provider. The subject line reads &quot;Cybersecurity Guidelines&quot; making it look like an official advisory from a trusted source.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iH2A2VgKuMKrxzr9lNegmQ.png" /></figure><p>The email carries an attachment named Cybersecurity.doc which acts as the initial payload. When the recipient opens the document and enables macros (as prompted), an obfuscated VBA macro runs. This macro extracts a hex-encoded blob hidden in the document’s structure (often within UserForm elements) cleans it up by stripping spaces and line breaks, converts it to binary and drops it as CertificationKit.ini in the ProgramData folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*qT_O-kvjbOCnWvSDpkJ2xA.png" /></figure><h4>The second stage (Malicious VBA macro and Hex-encoded)</h4><p>Sub love_me_____(): This subroutine serves as the main controller of the macro managing the entire payload workflow from start to finish. It begins by decoding a hidden file path from a hexadecimal string which was deliberately obfuscated to evade security software and string based detection methods. Once the real path is revealed the code checks if the payload file already exists on the victim’s system. Based on this check it makes a strategic decision: if the file is present it executes it immediately if not it calls the download function to fetch the payload from a remote server before running it. This two pronged approach ensures the payload can operate whether the file is already on the system or needs to be delivered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RbA4TcQncMxPQpmtccXYiQ.jpeg" /></figure><p>must specify the file path that is being checked and executed. For example you can use the path C:\ProgramData\CertificationKit.ini where CertificationKit.ini is the payload file. You can use https://www.hexhero.com/converters/text-to-hex to convert the path to HEX format for hiding it in the code.</p><p>Sub DownloadAndRun: This is the download manager of the payload responsible for reaching out to the internet and pulling down the file. It begins by decoding another hidden hexadecimal string that contains the actual URL where the payload is hosted. Using Windows HTTP services it establishes a connection to the remote server and downloads the file in binary format. Once the download completes successfully the code saves the file to the location specified earlier and immediately triggers its execution ensuring the payload becomes active on the system without any delay.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jMRgDHNMI0-asI3vIZIONA.jpeg" /></figure><p>must put the download link for the payload file where CertificationKit.ini is the payload file. You must convert this link to HEX format just like we did with the file path.</p><p>Function DecodeHex: Serves as the decoder ring for the entire operation. This clever obfuscation technique helps hide true intentions by keeping file paths and download URLs encrypted until the very moment they&#39;re needed.</p><p>Sub ExecuteFile: Is the execution engine that ensures the payload file runs on the system. It employs multiple methods to launch the file first using the Shell command with hidden window settings then falling back to Windows Script Host for redundancy. Both approaches run silently in the background leaving no visual indicators for the victim to notice.</p><p>Sub AutoOpen: It executes the code automatically when the document is opened.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xJ4GnLlhCFojRRmcwZnjOw.jpeg" /></figure><h4>The third stage (RustyWater implanting technique)</h4><p>RustyWater represents the main payload and the backbone of the entire adversarial operation in Static Kitten group attacks. RustyWater is a Rust compiled executable (disguised as reddit.exe with a fake Cloudflare icon) known as RustyWater (or linked to Archer RAT/RUSTRIC) featuring strong AV/EDR evasion through process injection, registry based persistence.</p><ol><li>ANTI-ANALYSIS Reddit.exe implements a comprehensive 8 layer anti-analysis system that actively probes the execution environment for signs of monitoring, virtualization, or debugging. Each layer acts as a filter ensuring the payload only detonates on a genuine target.<br>Layer 1: CPU Core Count Verification</li></ol><p>Initially the RustyWater soldier looks around to gauge the power of the machine it finds itself on. It asks itself: How many cores does this processor have? Analysis environments, like sandboxes, are typically resource limited and often have two cores or fewer. If the soldier finds the machine is this weak it immediately decides the environment is unsafe and vanishes without a trace wasting all the analysts&#39; efforts.</p><p>In the provided image a section of the Reddit.exe program&#39;s code illustrates this mechanism. The arrow points to the line checking the &quot;cpu count&quot; where the program examines the number of processor cores. If the count is two or less it means the surrounding environment is suspicious and execution is halted immediately.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1018/1*bwi6H-6eCm9_gFIBGay5AA.jpeg" /></figure><p>Layer 2: Virtual Machine Artifact Detection</p><p>Not convinced by the CPU check alone the soldier digs deeper. It knows that virtual machines leave behind specific digital footprints like a trail of breadcrumbs. It scans the list of running processes looking for familiar names associated with virtualization software: vmtoolsd.exe (VMware) vboxtray.exe (VirtualBox) and xenservice.exe (Xen). It also checks for the existence of specific driver files on disk such as vmmouse.sys or VBoxGuest.sys.</p><p>The logic is simple: if a machine is running VMware tools it is likely a VM. If it is a VM it is likely an analysis environment. If it is an analysis environment the soldier aborts the mission.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*-yUhKGxCkPicaqkf7_7UDg.jpeg" /></figure><p>Layer 3: Analysis Tool Registry Scanning</p><p>The soldier then ventures into the Windows Registry a vast database of system settings. It knows that security analysts often leave their tools behind and these tools leave artifacts. It searches for registry keys associated with debugging and monitoring software like Wireshark, Process Hacker, OllyDbg, and IDA Pro. The presence of any of these keys confirms the environment is hostile triggering an immediate shutdown.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*6JPyYEwhMTQkF9PPNu9iMA.jpeg" /></figure><p>Layer 4: RAM Size Analysis</p><p>the system reports less than 4GB, the soldier suspects a resource starved sandbox and halts execution. This check is a reliable way to filter out many automated analysis systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*E00assQX67xV5XvNmS_lEQ.jpeg" /></figure><p>Layer 5: Debugger Detection</p><p>The soldier now checks its immediate surroundings. It uses a simple but effective Windows API call—IsDebuggerPresent—to determine if it is being run under the control of a debugger. A debugger is like a microscope; if one is present, it means someone is watching the soldier&#39;s every instruction. The soldier will not perform under such surveillance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*1tr5wHzzAMfEZDkNihj8ow.jpeg" /></figure><p>Layer 6: System Uptime Check</p><p>Time itself becomes a factor. The soldier checks how long the system has been running since the last boot. Sandboxes and analysis environments are often freshly booted, right before a sample is executed. If the system uptime is less than 15 minutes, the soldier flags it as a suspicious, short lived environment and retreats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*of2QlPDSejX5WzZBGPKWXw.jpeg" /></figure><p>Layer 7: Username Analysis</p><p>The soldier then checks the identity of the user. It compares the current username against a blacklist of common analysis accounts: &quot;sandbox&quot;, &quot;virus&quot;, &quot;malware&quot;, &quot;analysis&quot;, &quot;vmware&quot;, and &quot;test&quot;. These usernames are frequently used in isolated analysis environments. If the username matches any entry on the list, the mission is immediately aborted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*7Nk6gkFD3tU67czNZrPSDg.jpeg" /></figure><p>Layer 8: MAC Address and Hardware Profile Verification</p><p>Finally the soldier looks at the machine&#39;s network card. It checks the MAC address against known vendor prefixes used by virtualization software. A MAC address starting with 00:0C:29 belongs to VMware, while 08:00:27 belongs to VirtualBox. It also scans hardware profiles for strings like &quot;VMware&quot; or &quot;VirtualBox&quot; in the system&#39;s description. If any of these are found, the soldier knows it is inside a virtual machine and pulls the plug.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*dU2M1wFUR18rDadLk-Mr7w.jpeg" /></figure><p>2.REGISTRY PERSISTENCE Once the anti analysis checks pass, Reddit.exe establishes robust registry persistence to ensure it survives system reboots:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*vHJ4WX8Yj9en4UOjMfpl3A.png" /></figure><p>The implant cleverly disguises itself as a legitimate Windows Update component, making it less suspicious to casual observers. The persistence mechanism includes:</p><p>● Error handling for permission issues (fallback to HKCU if HKLM access fails)</p><p>● Path validation to ensure the executable exists at the specified location</p><p>● Startup verification to confirm the registry entry was successfully created</p><p>This ensures that every time the user logs in Reddit.exe automatically executes with their privileges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/998/1*sXJDFqnEeeSU5Dh0KztDrA.jpeg" /></figure><p>3. PROCESS INJECTION<br>The final and most sophisticated capability is process injection into explorer.exe, allowing the implant to execute shellcode within a trusted system process.</p><p>Reddit.exe implements a classic but effective remote thread injection technique:</p><p>● Process Discovery: Scans running processes to locate explorer.exe and obtain its Process ID (PID).</p><p>● Handle Acquisition: Opens the target process with PROCESS_ALL_ACCESS privileges.</p><p>● Memory Allocation: Uses VirtualAllocEx to allocate RWX memory (Read, Write, Execute) within explorer.exe’s address space.</p><p>● Shellcode Transfer: Writes the malicious payload using WriteProcessMemory.</p><p>● Execution: Creates a remote thread via CreateRemoteThread that points to the injected shellcode.</p><p>This technique allows the attackers to hide their malicious code inside a trusted system process, making detection significantly more difficult for security solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G_mxK2PiGH-fP3KKHjCfvQ.jpeg" /></figure><p>Why Attackers Use explorer.exe for Process Injection?</p><p>the attackers deliberately chose to target explorer.exe for injecting their malicious shellcode. This choice was not random—it was based on strategic advantages:</p><p>● Legitimate system process - Its presence is normal and doesn’t raise alarms.</p><p>● Always running - Guaranteed availability on all Windows systems.</p><p>User context - Inherits the current user&#39;s privileges.</p><p>● Persistence - Survives even if the main malicious process is terminated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Z8sgld429DSm9q8oAJT4g.jpeg" /></figure><p>Put an HTTP payload: Encrypt it using XOR encryption to avoid detection over the network.</p><p>Modifying File Metadata to Evade Detection</p><p>After building the reddit.exe payload, we must modify its metadata to make it appear as a legitimate, non-suspicious program. Security solutions and EDR tools examine these metadata fields, so changing them is essential for evasion.</p><p>What Metadata Do Target?</p><p>File Version: The version number of the file Product Version: The version number of the product File Description: What the file describes itself as (appears in Task Manager) Product Name: The name of the product Company Name: The name of the developing company LegalCopyright: Copyright information OriginalFilename: The original name of the file</p><p>The tool used: rcedit</p><p>To perform these modifications, we use a lightweight, free tool called rcedit, officially available on GitHub. link: https://github.com/electron/rcedit/releases/download/v2.0.0/rcedit-x64.exe</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*gT0jw8aRqdmifDAbh8pjmA.jpeg" /></figure><p>● Dropper : CertificationKit.ini<br>I observed that the attackers do not execute reddit.exe directly on the target system. Instead they rely on an intermediary program known as CertificationKit.ini (Dropper) which carries the encrypted payload decrypts it at runtime and executes it on the victim is machine.</p><p>and that the dropper was written in Rust. Although it disguises itself as a seemingly harmless configuration file (CertificationKit.ini) it is in reality a compiled binary responsible for deploying and executing the main payload on the target system.</p><p>This technique provides several advantages:</p><ol><li>Evasion: The actual payload remains encrypted making it more difficult for antivirus and security tools to detect it.</li><li>Analysis Bypass: Even if the dropper is discovered or analyzed the main payload remains encrypted and protected.</li><li>Multi Stage Execution: The attack operates in multiple stages which complicates the analysis process and slows down incident response for security teams.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*E8ZNqL3TGgO4S5RpE21s8A.jpeg" /></figure><p>Payload Encryption: The main payload (reddit.exe) is stored in the ENCRYPTED_PAYLOAD section and encrypted using the XOR key defined in the dropper (XOR_KEY). This ensures that the payload remains protected until runtime.</p><p>Target Path: The dropper writes the decrypted payload to the location specified in the dropper configuration (TARGET_PATH). This path must be correctly set to the intended directory on the victim is system.</p><p>Runtime Decryption: Upon execution the dropper decrypts the payload using the XOR key and deploys it as CertificationKit.ini at the target location.</p><p>This setup allows the attackers to maintain stealth, evade detection, and ensure the payload is only accessible when executed on the victim is system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-y2nP35jTijjxTOH0GxZhw.jpeg" /></figure><h4>Final result: (Actual payload connect to BEAR-C2 server)</h4><p>This payload establishes an HTTP connection to a remote server for command execution. It communicates using JSON formatted messages, with all data encrypted using XOR key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*jCo4RtNAZHcDNbbvknfg-Q.jpeg" /></figure><p>The client authenticates with a predefined ID and executes commands received from the server supporting both CMD and PowerShell commands. Output from executed commands is XOR encrypted and sent back to the server in JSON format. Data is also Base64 encoded for safe transmission.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CqdAovQD9BB1mRzq5DEWQA.jpeg" /></figure><p>Github repository: https://github.com/S3N4T0R-0X0/APTs-Adversary-Simulation/tree/main/Iranian%20APT/Static%20Kitten</p><p>X: https://x.com/S3N4T0R_0X0</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f595aa74118" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ricochet Chollima APT Adversary Simulation]]></title>
            <link>https://medium.com/@S3N4T0R/ricochet-chollima-apt-adversary-simulation-b0258be69c37?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0258be69c37</guid>
            <category><![CDATA[adversary-emulation]]></category>
            <category><![CDATA[adversary-simulation]]></category>
            <category><![CDATA[apt]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Tue, 27 Jan 2026 10:52:47 GMT</pubDate>
            <atom:updated>2026-01-27T10:54:30.020Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a simulation of an attack by the (Ricochet Chollima) APT group, targeting several activists focused on North Korea. The attack campaign began in March 2025. The attack chain started with spear-phishing. The email contained a Dropbox link leading to a compressed archive that included a malicious shortcut (LNK) file. When extracted and executed, the LNK file activated additional malware containing the keyword &quot;toy.&quot; The content was disguised as an academic forum invitation from a South Korean national security think tank to attract attention.</p><p>This simulation is based on research from Genians: https://www.genians.co.kr/en/blog/threat_intelligence/toybox-story</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*b7iQ4UTeR2ufW5inPBKPng.png" /></figure><p>Based on the characteristics of the threat, Genians Security Center (GSC) named the campaign “Operation: ToyBox Story”</p><p>The attacker impersonated a North Korea-focused expert based in South Korea, and the email used the subject line “러시아 전장에 투입된 인민군 장병들에게.hwp” (To North Korean People’s Army Soldiers Deployed to the Russian Battlefield.hwp) with the attachment carrying the same file name, the attachment mimicked a Hangul (HWP) document by displaying the HWP icon image used by Naver Mail, and the attacker leveraged this icon to make the attachment appear as a legitimate file link, however the actual download link redirected to Dropbox, which led to a ZIP archive named “러시아 전장에 투입된 인민군 장병들에게.zip” (To North Korean People’s Army Soldiers Deployed to the Russian Battlefield.zip).</p><ol><li>Delivery Technique: Create document file masquerading as information on North Korean troops deployed to Russia.</li><li>Malicious shortcut: make single shortcut (LNK) file. This LNK file executes malicious code and shares the same name as the ZIP archive, with only the file extension being different.</li><li>PowerShell Commands: The shortcut (LNK) file is configured to run via PowerShell commands embedded arguments.</li><li>Toy.Bat: When the PowerShell command in “toy03.bat” file is executed, it loads “toy02.dat” file created in temporary folder, functioning as a loader.</li><li>Dropbox C2: Get Command and Control through payload uses the Dropbox API to upload data including command output to Dropbox.</li><li>TCP payload: This payload that establishes a TCP connection to a remote server for command execution.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*0hkUeMByka7jw0bTfBN-SQ.png" /></figure><h4>The first stage (delivery technique)</h4><p>The attacker impersonated a North Korea-focused expert based in South Korea. The spear-phishing email employed the subject line “러시아 전장에 투입된 인민군 장병들에게.hwp” (To North Korean Soldiers Deployed to the Russian Battlefield.hwp), with an attachment carrying the identical file name. The attachment was crafted to mimic a Hangul (HWP) document by leveraging the HWP icon image commonly associated with Naver Mail, thereby increasing its credibility. The threat actor intentionally used this icon to make the file appear as a legitimate document; however, the embedded link redirected the victim to a Dropbox-hosted payload instead of delivering a benign file. The Dropbox URL ultimately provided a compressed archive containing additional malicious components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*fYvb2I7O7xZnBzRDeCKGsA.png" /></figure><h4>The second stage (Malicious shortcut)</h4><p>The archive named “관련 포스터.zip” (Related Poster.zip) contained a benign JPG image alongside a malicious LNK shortcut. Upon execution of the LNK file, a hidden PowerShell command embedded within the shortcut was triggered, initiating the malicious activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*Gj-_4sCQfeYSY6eL4EUm3g.png" /></figure><p>Now I need to create a JPG image that looks like a normal picture, but in the background when the image is opened the PowerShell command starts running silently. At this stage I used WinRAR to bind the JPG with a command line execution via CMD so that when the image is opened it triggers the hidden activity, and I also used an icon format to make the file appear legitimate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*F1s3cEIKANMZ-15iGwhDMw.jpeg" /></figure><p>After using WinRAR to compress the file, I will create a shortcut to this file and place it in another folder together with the actual images, then convert the folder into a ZIP file using standard ZIP compression.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*EzTQ82I61ad0HrSJj9kF9g.png" /></figure><h4>The third stage (execution technique)</h4><p>Because I put the command line in the setup (Run after extraction) menu in the Advanced SFX options of the WinRAR program, now when the victim opens the ZIP file to view the images, they also see an HWP document containing a letter addressed to North Korean soldiers deployed to Russia.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qsQWzjc3eyOoU5KcCPHGrQ.jpeg" /></figure><h4>The fourth stage (Toy.bat - shellcode)</h4><p>When the PowerShell command in “toy03.bat” executes, it loads the “toy02.dat” file created in the temporary folder to function as a loader; the embedded PowerShell within “toy02.dat” then runs and loads “toy01.dat” from the same folder, during which XOR transformed data is decoded and mapped into memory and a new thread is spawned; as a result, the shellcode is placed in memory and the region is made executable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*mqxGKKKgHO3v_bEHlF-rJg.png" /></figure><p>After which another thread is created to run the memory-resident code constituting a fileless technique for dynamic code execution and runtime malware injection.</p><p>As a result, the shellcode is loaded into memory and the memory area becomes executable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3EbZiYZtxd9ORFece3M9pg.png" /></figure><p>I used shellcode to execute calc.exe for testing but later after compiling the base payload I will use the host-file program included in BearC2 to upload the payload and obtain a masked URL. As shown in the server header for Dropbox in the figure, opening that link causes the payload to download automatically without any interaction from the victim. I will then use the (start) command, insert the URL that carries the payload convert it to shellcode and place it in the shellcode slot instead of the calc.exe shellcode.</p><h4>The fifth stage (Data Exfiltration) over Dropbox API C2 Channe</h4><p>The attackers used the Dropbox C2 (Command and Control) API as a means to establish a communication channel between their payload and the attacker’s server. By using Dropbox as a C2 server, attackers can hide their malicious activities among the legitimate traffic to Dropbox, making it harder for security teams to detect the threat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*wiCYnvDQyItB2ahQHAJ-Dw.png" /></figure><p>First, I need to create a Dropbox account and activate its permissions, as shown in the following figure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oVOAFjQ53EuCV-lzPYyVlA.png" /></figure><p>After that, I will go to the settings menu to generate the access token for the Dropbox account, and this is what we will use in Dropbox C2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HaxIpmD4I9OPcVLu0RoPTA.jpeg" /></figure><h4>The sixth stage (payload with injected Shellcode)</h4><p>This payload that establishes a TCP connection to a remote server for command execution. It uses AES encryption in CBC mode to secure communication, with a 128-bit key for encrypting and decrypting data. The client authenticates with a predefined ID and executes commands received from the server, supporting both CMD and PowerShell commands. Output from executed commands is encrypted and sent back to the server. The program includes a Dropbox API function for file upload and employs Base64 encoding for data handling.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*xZtvXe9ddqeXLql6myDfjw.png" /></figure><p>This payload uses the Dropbox API to upload data, including command output to Dropbox. By leveraging the Dropbox API and providing an access token the payload hides its traffic within the legitimate traffic of the Dropbox.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*T13KaV5fDEXLcULoTYV9nw.png" /></figure><p>Now I will upload the file to BearC2’s host-file, use the start command with the URL, convert it to shellcode, and place it in the main payload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CWii4wB3izK18r-lRhSw0A.png" /></figure><h4>Final result: payload connect to BEAR-C2 server</h4><p>The final step in this process involves the execution of the final payload. After being decrypted and loaded into the current process, the final payload is designed to beacon out to both Dropbox API-based C2 server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QAkQyuAuLiFkaq5p-D_StQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0258be69c37" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Silent Chollima APT Adversary Simulation]]></title>
            <link>https://medium.com/@S3N4T0R/silent-chollima-apt-adversary-simulation-e661a601901a?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e661a601901a</guid>
            <category><![CDATA[adversary-emulation]]></category>
            <category><![CDATA[adversary-simulation]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[apt]]></category>
            <category><![CDATA[red-team]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 11:57:50 GMT</pubDate>
            <atom:updated>2026-01-26T11:58:52.757Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a simulation of attack by (Silent Chollima) APT group targeting several customers and their users in North America, Asia, and Europe. The attack campaign was active in June 2025, have sent a link leading to a ZIP or RAR archive file. Inside this file would be a legitimate executable that was given a filename relevant to the targeted organization or tied to the theme of the spear phish email.When executed, this legitimate executable would load a malicious payload in an included Dynamic Link Library (DLL), via search order hijacking which provided operators with the ability to remotely execute commands on infected devices. I relied on volexity to figure out the details to make this: https://www.volexity.com/blog/2025/10/08/apt-meets-gpt-targeted-operations-with-untamed-llms/</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VJnjvvCM0V_lQsXkXiYqaA.jpeg" /></figure><ol><li>Social engineering technique: The attackers sent phishing emails containing HTML that included an image to make it appear a document was attached to the email. If the image were clicked, it led to the download of a remotely hosted archive file.</li><li>GOVERSHELL: All implants were DLL files that were loaded via search order hijacking from the legitimate version of either the 32- or 64-bit version of an open-source project.</li><li>Persistence &amp; C2 traffic: Each variant of GOVERSHELL sets up persistence via a scheduled task on its first execution and includes a command-line flag in that persistence execution, which is required to execute the logic that includes C2 communication.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*wYO3a0rj7ax4i0vUFnu-uQ.png" /></figure><h4>The first stage (social engineering technique)</h4><p>Silent Chollima primary and sole method for targeting organizations is by conducting spear phishing campaigns. Between June and August 2025, Silent Chollima sent phishing emails containing HTML that included an image to make it appear a document was attached to the email. If the image were clicked, it led to the download of a remotely hosted archive file. Users would then need to open and execute the executable file within the archive in order to become infected. An example body from one such email is included below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/1*xqlbfjUChB3mq2HqA5ivww.png" /></figure><p>I recreated an HTML file identical to that used by the attackers. When the PDF icon is clicked, it redirects the user to a browser link that downloads the malicious payload hosted by the BEAR-C2 project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Onul4o6FvxL0Dvn0O2oOmw.png" /></figure><h4>The second stage (GOVERSHELL payload)</h4><p>Throughout various campaigns Volexity observed active changes in the malware, with significant differences in how the malware communicated and functioned. All variants observed by Volexity make use of a scheduled task for persistence and provide the operator the ability to execute arbitrary commands on the target’s device. With the exception of the first variant, all GOVERSHELL implants were DLL files that were loaded via search order hijacking from the legitimate version of either the 32- or 64-bit version of an open-source project called Tablacus Explorer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*xTjtbuhiu5E5x5ddf-zuMg.png" /></figure><p>GOVERSHELL is a stealthy Windows implant that communicates over HTTPS with a remote command and control server.It uses XOR encryption combined with Base64 to protect all network traffic and payloads from casual inspection. Upon first execution without its specific argument, it silently copies itself to a random folder in C:\ProgramData and establishes persistence via a hidden scheduled task. Once persistent, it repeatedly checks in with the server, receives encrypted commands, executes them locally (via cmd or PowerShell), and sends back results. The implant applies configurable jitter delays between communications to evade pattern-based detection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*QKqnoGWeyTSoLKxVtt4cqQ.png" /></figure><h4>The third stage (Persistence &amp; C2 traffic)</h4><p>This function creates a hidden scheduled task named &quot;SystemHealthMonitor&quot; using schtasks.exe executed silently via CreateProcessA. It builds a command string that runs the copied malware with -SilentChollima every 5 minutes at highest privileges. The process is launched with CREATE_NO_WINDOW and SW_HIDE flags to prevent any visible console or window. It safely copies the command into a fixed buffer, null-terminates it, and waits up to 5 seconds for completion. Returns true on success, ensuring stealthy, self-healing persistence without dropping additional files.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fiIbzXAy8WgTVQRqnOam3g.png" /></figure><p>C&amp;C server on HTTPS (port 465): The implant communicates exclusively over encrypted HTTPS channels with the remote command-and-control server. All network traffic, including check ins, task retrieval, and results, is protected using XOR encryption (key: 11) combined with Base64 encoding before transmission. When a command is received, it is first XOR decrypted, then checked for the &quot;EP&quot; prefix to determine if it should be executed via PowerShell or cmd.exe. PowerShell commands are properly escaped and run silently using powershell.exe -NoProfile -NonInteractive -Command, with full stdout/stderr capture. The command output is captured, XOR encrypted with the same key, Base64 encoded and securely sent back to the C2 server over HTTPS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Ph1eeJC0yNYDehXLf5FwQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e661a601901a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adversary Simulation Is Not a Methodology It’s the Outcome of Experience]]></title>
            <link>https://medium.com/@S3N4T0R/adversary-simulation-is-not-a-methodology-its-the-outcome-of-experience-4dfeafdba6da?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dfeafdba6da</guid>
            <category><![CDATA[apt]]></category>
            <category><![CDATA[adversary-simulation]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[adversary-emulation]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 14:32:21 GMT</pubDate>
            <atom:updated>2025-12-29T14:32:21.454Z</atom:updated>
            <content:encoded><![CDATA[<p>Adversary Simulation is one of the most misunderstood concepts in modern offensive security. It is often presented as a structured discipline that can be learned through frameworks, labs, or tooling. This misunderstanding is dangerous, because it reduces a complex operational capability into a simplified, repeatable process something real adversaries have never been.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*3WvF-3T9B_-3dtcQ0P4-sw.png" /></figure><p>Adversary Simulation is not something you study and then “apply.” It is the natural outcome of years spent understanding how attacks actually happen in the real world, how attackers adapt, how defenders respond, and how both sides continuously evolve.</p><p>This article is not written to teach Adversary Simulation.<br> It is written to explain why it cannot be taught in the first place.</p><h3>The Core Misconception: Learning the “How” Instead of Understanding the “Why”</h3><p>Most people approach adversary simulation with the wrong question:<br> “How do I simulate an APT?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/863/1*w6He97VYTKUuVtE4LpTLgQ.jpeg" /></figure><p>Real adversaries never ask this question.</p><p>They ask:</p><ul><li>Why did this environment fail?</li><li>Why was this control bypassed?</li><li>Why did detection happen here but not there?</li><li>Why was this delivery vector chosen instead of another?</li></ul><p>Adversary Simulation begins when you stop copying techniques and start analyzing <strong>decision making</strong>.</p><p>That decision-making is not found in tools or frameworks. It is found in real world incidents, breach reports, malware analysis, and post exploitation tradecraft published by organizations such as Palo Alto Unit 42, Cisco Talos, Microsoft Threat Intelligence, CrowdStrike, Kaspersky, Mandiant, and Trellix.</p><p>These reports are not educational material.<br>They are <strong>operational intelligence</strong>.</p><h3>Real Attack Campaigns Are Chaotic But Not Random</h3><p>Although attackers do not follow clean diagrams, real campaigns still exhibit consistent operational phases. These phases are not rigid steps; they are overlapping activities that adapt to conditions on the ground.</p><p>A realistic adversary simulation must reflect <strong>the entire lifecycle</strong>, not isolated techniques.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/673/1*Pa5Wton7HoomkxAC0FbTNg.jpeg" /></figure><h4>Delivery Is Not “Phishing”</h4><p>Delivery is the result of understanding the target’s ecosystem.</p><p>In recent real-world campaigns, especially those attributed to North Korean actors, delivery mechanisms moved far beyond traditional phishing. We saw:</p><ul><li>Malicious npm packages embedded into developer workflows</li><li>Trojanized VS Code extensions</li><li>Abuse of trusted open-source ecosystems</li><li>HTML smuggling and container based payload delivery</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*fUS9uSfYUazZ4q9D7bKSrw.png" /></figure><p>These techniques worked because attackers understood how developers work not because the tools were sophisticated.</p><p>Simulating this requires understanding <strong>context</strong>, not payloads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*SW2_9USH3V2_kBO2TDQRuA.jpeg" /></figure><h3>Implantation Is About Trust, Not Execution</h3><p>The implant phase is often misunderstood as “payload execution.”<br> In reality, it is about establishing <em>trust</em> inside the system.</p><p>Modern implants are designed to:</p><ul><li>Look legitimate</li><li>Behave patiently</li><li>Blend into existing processes</li><li>Abuse native APIs and system services</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*611nSGXJW6uzUENBjIBfHA.png" /></figure><p>This is where most shallow simulations fail. Dropping a binary and calling it “implantation” does not reflect reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H82qsbjDftlabKq91yBTNA.jpeg" /></figure><p>True adversary simulation requires understanding how implants survive updates, reboots, user behavior, and monitoring tools and how they adapt when something breaks.</p><h3>Execution Without C2 Is Meaningless</h3><p>Execution is irrelevant without command-and-control.</p><p>Modern adversaries do not rely on static infrastructure. They build C2 systems that:</p><ul><li>Rotate domains dynamically (DGA-based logic)</li><li>Abuse legitimate cloud APIs</li><li>Use custom encrypted protocols</li><li>Implement fallback channels and beacon jittering</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jAXvVq_KcrWiRGb7wAWnOg.jpeg" /></figure><p>This mindset is exactly why projects like <strong>Bear-C2</strong> exist not as malware, but as <strong>a controlled simulation of modern adversary C2 behavior</strong>, designed to reflect resilience, stealth, and adaptability rather than raw functionality.</p><p>Adversary Simulation without C2 engineering knowledge is incomplete by definition.</p><h3>Defense Evasion Is a Continuous Process, Not a Trick</h3><p>Evasion is not “bypass AV.”</p><p>Real attackers shape behavior over time:</p><ul><li>Delayed execution</li><li>API-level obfuscation</li><li>Memory-only techniques</li><li>Legitimate parent child process chains</li><li>Low-and-slow operational pacing</li></ul><p>They study defenders just as much as defenders study them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IuTyWrpmhGUifUvNXM6pNA.png" /></figure><p>If your simulation does not adapt to detections, alerts, or environmental changes, then it is not simulating an adversary it is simulating a script.</p><h3>Lateral Movement Is Driven by Identity, Not Tools</h3><p>Inside the network, attackers move based on:</p><ul><li>Identity misconfigurations</li><li>Excessive permissions</li><li>Broken trust relationships</li><li>Human behavior</li></ul><p>Tools are interchangeable. Logic is not.</p><p>Adversary Simulation requires understanding Active Directory abuse, identity federation, privilege escalation paths, and operational patience not just running lateral movement modules.</p><h3>Exfiltration Is Quiet, Intentional, and Context Aware</h3><p>Exfiltration is rarely dramatic.</p><p>Real attackers:</p><ul><li>Use legitimate APIs</li><li>Abuse cloud synchronization</li><li>Chunk data slowly</li><li>Blend traffic into normal patterns</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k6Re1x6Gt7WWO6uFnDV-WA.jpeg" /></figure><p>This phase is often ignored in simulations, yet it is one of the most important indicators of real attacker intent.</p><h3>MITRE ATT&amp;CK and Caldera: Language, Not Capability</h3><p>MITRE ATT&amp;CK provides a vocabulary.<br> MITRE Caldera provides orchestration.</p><p>Neither provides understanding.</p><p>Without the ability to:</p><ul><li>Develop malware</li><li>Engineer C2 infrastructure</li><li>Analyze real incidents</li><li>Understand detection logic</li></ul><p>Frameworks become empty diagrams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pR9pO3GeDiE9Cd4sCtopeg.png" /></figure><p>Adversary Simulation is not about mapping techniques.<br> It is about <strong>reproducing attacker reasoning</strong>.</p><h3>APTs Adversary Simulation: Research, Not Replication</h3><p>The <strong>APTs Adversary Simulation</strong> repository was never designed to be a tutorial or a ready made attack kit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f75eGTTF-__w6U7DTo2kew.png" /></figure><p>It exists to:</p><ul><li>Model real world adversary behavior</li><li>Reflect how campaigns evolve</li><li>Provide contextual simulation grounded in reality</li><li>Bridge research, tooling, and operational logic</li></ul><p>It is not meant to be copied.<br>It is meant to be understood.</p><h3>The Hard Truth</h3><p>If someone believes adversary simulation can be learned step by step, they are already disqualified.</p><p>Adversary Simulation is the result of:</p><ul><li>Building C2 servers</li><li>Writing malware</li><li>Studying real attacks</li><li>Failing repeatedly</li><li>Understanding both attacker and defender mistakes</li></ul><p>It is not a course.<br>It is not a framework.<br>It is not a tool.</p><p>It is a capability forged through exposure to reality.</p><p><strong>Always Remember: <em>“Be The Threat To Defeat It”</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dfeafdba6da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adversary Simulation VS Adversary Emulation]]></title>
            <link>https://medium.com/@S3N4T0R/adversary-simulation-vs-adversary-emulation-381b920a12f6?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/381b920a12f6</guid>
            <category><![CDATA[adversary-emulation]]></category>
            <category><![CDATA[adversary-simulation]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Sun, 05 Oct 2025 15:02:34 GMT</pubDate>
            <atom:updated>2025-10-18T12:38:53.383Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s cybersecurity landscape, traditional penetration testing and red teaming are no longer enough to counter sophisticated adversaries. To stay ahead, organizations are turning to <strong>adversary simulation</strong> and <strong>adversary emulation</strong> two powerful approaches to test and strengthen defenses. While both mimic real-world threats, they differ in scope, methodology, and purpose. As someone deeply immersed in the world of APT attack simulation, I’ll break down the differences and why they matter for building resilient defenses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*grSciCGj2uxOjh06p2MSAQ.jpeg" /></figure><h3>Adversary Simulation: The Big Picture</h3><p>Adversary simulation is about recreating the <em>entire lifecycle</em> of a real-world cyberattack to stress-test an organization’s security posture. It’s not just about finding vulnerabilities or breaching systems — it’s about understanding how attackers plan, evade, persist, and operate over months, exploiting both technical and human weaknesses.</p><p><strong>What It Does</strong>: Simulates the tactics, techniques, and procedures (TTPs) of adversaries using frameworks like MITRE ATT&amp;CK and the cyber kill chain. It tests technology, people, and processes against complex, multi stage attacks.</p><p><strong>Key Features</strong>:</p><ul><li>Covers the full attack lifecycle: reconnaissance, defense enumeration, payload delivery, persistence, lateral movement, and data exfiltration.</li><li>Exposes detection blind spots, such as adversaries abusing trusted platforms (e.g., Dropbox, Google Drive, or Visual Studio Code Live Share) or legitimate features (e.g., NPM packages, Windows processes like Notepad.exe).</li><li>Tests how defenders connect weak signals, escalate alerts, and respond to sophisticated tactics like fake CAPTCHAs or social engineering via fake job offers.</li><li><strong>Example</strong>: Simulating an APT campaign where attackers pose as recruiters, deliver a Python script backdoor to developers, stage malware on Dropbox, and establish persistence via scheduled tasks — all while evading EDR and SIEM detections.</li><li><strong>Goal</strong>: Answer the critical question, <em>“How does my organization fare against an advanced, persistent adversary, not just a CVE?”</em></li><li><strong>Use Case</strong>: Perfect for organizations wanting to validate their entire security ecosystem against realistic, evolving threats, including supply chain attacks and human-targeted exploits.</li></ul><h3>Adversary Emulation: Precision Targeting</h3><p>Adversary emulation takes a laser-focused approach, replicating the <em>specific TTPs</em> of a known threat actor or group based on detailed threat intelligence. It’s about mirroring the exact playbook of a real adversary to test defenses against a particular threat.</p><p><strong>What It Does</strong>: Mimics the documented behaviors, tools, and techniques of a specific threat actor (e.g., APT28, a ransomware gang, or a financially motivated group) with high fidelity.</p><p><strong>Key Features</strong>:</p><ul><li>Relies on granular threat intelligence to recreate precise attack patterns, such as specific malware, command-and-control (C2) infrastructure, or lateral movement techniques.</li><li>Uses MITRE ATT&amp;CK to map and execute the adversary’s known TTPs, ensuring accuracy in replicating their methods.</li><li>Focuses on testing detection and response capabilities against a well-defined threat profile.</li><li><strong>Example</strong>: Emulating an APT group by staging a toolkit on a trusted platform, using social engineering tailored to a specific industry, and deploying custom implants designed to bypass a known EDR solution.</li><li><strong>Goal</strong>: Assess how well an organization can detect and stop a specific, real-world adversary.</li><li><strong>Use Case</strong>: Ideal for high-risk sectors (e.g., critical infrastructure, finance, or government) facing targeted threats from known actors.</li></ul><h3>Why the Difference Matters</h3><p>Modern adversaries don’t just exploit vulnerabilities — they weaponize trust and abuse legitimate tools. For example:</p><ul><li><strong>Trusted Platforms</strong>: Attackers use Dropbox or GitHub to host malware, blending malicious traffic with normal operations.</li><li><strong>Social Engineering</strong>: Fake job offers deliver Python scripts to developers, exploiting their trust and existing software environments.</li><li><strong>Supply Chain Attacks</strong>: Malicious NPM packages or compromised dependencies sneak backdoors into enterprises.</li><li><strong>Feature Abuse</strong>: Tools like Visual Studio Code Live Share are repurposed as covert C2 channels, evading detection because they’re legitimate.</li></ul><p>Adversary simulation exposes these gaps by recreating realistic, multi-faceted attack campaigns. It challenges defenders to connect subtle signals like “odd Slack onboarding traffic” or registry key persistence and act before it’s too late. Adversary emulation, on the other hand, ensures you’re prepared for a specific threat actor’s playbook, which is critical when you know who’s targeting you.</p><h3>Key Differences at a Glance</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IdfWcAQ7oAG7F2oKZuttvQ.png" /></figure><h3>Moving Beyond Compliance</h3><p>Penetration testing finds vulnerabilities. Red teaming sharpens detection and response. But neither fully prepares you for the sophisticated tactics of today’s APTs or ransomware operators. Adversary simulation and emulation bridge this gap by mirroring real-world threats whether it’s a broad, unpredictable attack or a targeted campaign from a known actor.</p><p>The question isn’t <em>“Do I need these approaches?”</em> It’s <em>“Am I truly secure, or just checking compliance boxes?”</em> By combining simulation’s broad resilience testing with emulation’s precision, organizations can build defenses that stand up to the most advanced threats.</p><p>Let’s fight back be the threat to defeat it.</p><p><a href="https://github.com/S3N4T0R-0X0/APTs-Adversary-Simulation">GitHub — S3N4T0R-0X0/APTs-Adversary-Simulation: This repository is a compilation of all APT simulations that target many vital sectors,both private and governmental. The simulation includes written tools, C2 servers, backdoors, exploitation techniques, stagers, bootloaders, and many other tools that attackers might have used in actual attacks. These tools and TTPs are simulated here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=381b920a12f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Adversary Simulation?]]></title>
            <link>https://medium.com/@S3N4T0R/why-adversary-simulation-a1c69e8bd93a?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1c69e8bd93a</guid>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Sat, 20 Sep 2025 16:05:35 GMT</pubDate>
            <atom:updated>2025-11-01T09:29:19.999Z</atom:updated>
            <content:encoded><![CDATA[<h4>Between Penetration Testing, Red Teaming, and Adversary Simulation</h4><p>When we hear about an attack earlier this year that abused VSCode to establish command and control and dump credentials from LSASS, and then only a few months later the same attack is repeated with different outcomes but using the very same technique; when we recall the NPM package supplychain attack of December 2022 against U.S. organizations, and now in 2025 we see the same vector resurfacing once again; when we observe the abuse of everyday user interactions such as CAPTCHAs, exploited through the so called ClickFix (Fake-Captcha) technique first seen in early 2025 and then reused during the recent military tensions between India and Pakistan tensions that only began six months after the technique was first deployed and when we witness indirect intrusions through fake job postings and interviews, where attackers pose as recruiters to compromise IT engineers and other roles, later abusing even something as simple as an employee’s corporate email to gain access to sensitive systems… a fundamental question arises:</p><p>👉 Why do these attacks keep succeeding and being reused, even though they are not new?</p><p>If your answer is “because the payload changed” or “because the C2 infrastructure was rotated,” that is not the root cause. Those are expected evasive tactics. The deeper issue is this: do organizations and government sectors truly lack defense technology, detection mechanisms, or security awareness? After all, many of them invest in penetration testing, Red/Blue team exercises, and security services yet the attacks still succeed. So the real question is not whether defenses exist, but why they continue to fail despite being in place.</p><p>In today’s climate where companies chase ROI, clients demand nothing more than passing audits, and compliance certificates like ISO are treated as the finish line the question becomes: who is genuinely pursuing security, and who is just checking boxes?</p><p>The answer is not the same for every organization. Motives and objectives differ. But in this article, I want to highlight one point clearly: the true value of Adversary Simulation.</p><p>For more than two decades, organizations have relied on penetration testing as the gold standard of cybersecurity assessment. Pentesters examine networks, applications, and systems for exploitable vulnerabilities, then deliver reports on remediation. This has undeniably raised security standards, but its scope is inherently limited it focuses on technical weaknesses (CVEs, misconfigurations, vulnerabilities) rather than the broader operational threats organizations face.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*2kG3FttHCBwkakT3TEbirg.jpeg" /></figure><p>Red teaming advanced the field by simulating real adversaries. Red teams don’t just find vulnerabilities; they employ social engineering, privilege escalation, and lateral movement to test the blue team’s ability to detect, respond, and contain. This was a leap forward, but red team engagements still face constraints. They are time-boxed, often rely on known tools and techniques, and focus more on “can we get in?” than “are we replicating a well-resourced APT?”</p><p>This is where adversary simulation emerges. Instead of thinking like a pentester or a red teamer, adversary simulation replicates the entire lifecycle of a real world adversary using the MITRE ATT&amp;CK framework and the cyber kill chain. The purpose isn’t just to breach, but to replicate how attackers plan, evade defenses, persist, and operate over months.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/919/1*K4uN6dA6qaAmGIH_atFsBg.jpeg" /></figure><p>👉 It answers the real question:<br>What happens when my organization faces an advanced, persistent adversary not just a CVE?</p><h4>The Modern Threat Landscape</h4><p>Sophisticated adversaries begin with deep reconnaissance, fingerprinting both the technology stack and the human environment. They quietly enumerate exposed APIs, CDN usage, and certificate chains while also mapping employees’ digital footprints on GitHub, LinkedIn, and professional networks.</p><p>A central step is defense enumeration: identifying what antivirus, EDR, or SIEM tools are in use before deploying payloads. Attackers query WMI on Windows, study running processes, inspect loaded drivers, and analyze logging endpoints. With this knowledge, they craft implants that bypass those exact defenses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_di_Ko20v_Afqt-vGQtBKA.jpeg" /></figure><p>To remain stealthy, adversaries abuse trusted platforms. Malicious payloads are staged on GitHub, Google Drive, or Dropbox. In one campaign, the Machete APT group uploaded a full toolkit to Dropbox targeting financial institutions in the Middle East. Because Dropbox is widely trusted, malicious traffic blended seamlessly into normal operations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P2dOti48HJa5u0a-s7bkcg.png" /></figure><p>Even more subtly, attackers insert malicious dependencies into package managers. Malicious **NPM packages** disguised as developer utilities have been used to smuggle backdoors into enterprises. Since developers routinely install open-source libraries, this method weaponizes trust in the software supply chain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5w3J2ohJZ1LKlBgbJI_RUw.jpeg" /></figure><p>Attackers also exploit legitimate features. A striking example is **Visual Studio Code Live Share**, intended for real-time collaborative coding. Adversaries have repurposed it into a covert command-and-control (C2) channel, allowing them to execute commands, escalate privileges, and exfiltrate credentials under the guise of collaboration traffic. Because Live Share is a legitimate feature, no alerts are raised making this a powerful detection blind spot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g_xyyeDaPbf9LqAEjq_DKQ.png" /></figure><h4>Social Engineering: The Fake Job Offer Playbook</h4><p>While technical exploits are powerful, the human factor often remains the easiest entry point. Fake recruitment campaigns are now a staple of APT playbooks.</p><p>Attackers pose as recruiters from global tech firms, reaching out through LinkedIn or email. They conduct realistic interviews and eventually “offer” the target a position. As part of onboarding, the victim is asked to install an application or script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*stiWkhTdlkEiGDa6JZRjyQ.png" /></figure><p>In one campaign, attackers deliberately used **Python scripts** instead of compiled executables. Why? Because they knew they were targeting software developers, who already had Python and its dependencies installed. The result was seamless execution without the friction of missing libraries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*acAbgYXL6YO70uYZVvQSeA.png" /></figure><p>Other lures include:</p><p>Adding the victim to a fake Slack server for “team onboarding.”<br>* Asking them to install a “specialized tool” needed for work.<br>* Even telling them to learn a new language and providing a “learning app” that silently drops a backdoor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q9nLEJwiEXFYdjidGgFAWA.png" /></figure><p>The outcome: the attacker gains persistent access, while the victim believes they are simply preparing for a new job. Importantly, the real target is often data from previous employers projects, credentials, and documents making this tactic both indirect and devastating.</p><h4>Beyond Vulnerabilities: Abusing Features and Supply Chains</h4><p>Traditional pentesting looks for exploitable weaknesses. But modern adversaries often bypass vulnerabilities entirely by **abusing legitimate features**:</p><p>**VSCode Live Share** → covert C2 channel.<br>**Dropbox/Google Drive** → malware hosting.<br>**NPM package dependencies** → supply chain compromise.<br>**Windows processes (Notepad.exe, svchost.exe)** → process hollowing and in-memory payloads.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*o0zTEHOROVZxav2Bw6ubRQ.png" /></figure><p>These are not vulnerabilities they are features. This makes detection far more difficult, since defenders cannot simply “patch” or “block” them without disrupting business operations.</p><p>One of the more creative methods used by modern threat actors is the <strong>Fake-Captcha technique</strong>, sometimes referred to as <strong>ClickFix</strong>. In this scenario, the attacker lures the victim to a compromised website or a malicious landing page. Instead of directly serving malware, the page first displays what appears to be a <strong>CAPTCHA verification</strong> a common “I am not a robot” check.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cwpWhI3E4BZl5Ge9ahTApQ.png" /></figure><p>Victims, accustomed to solving CAPTCHAs on legitimate websites, click to proceed without suspicion. But behind the scenes, that single click silently triggers the execution of malicious JavaScript or initiates a <strong>drive-by download</strong>. The CAPTCHA is fake it does not verify anything. Instead, it serves as <strong>social engineering camouflage</strong>, buying legitimacy and lowering the victim’s guard before the real payload is delivered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/992/1*SW2_9USH3V2_kBO2TDQRuA.jpeg" /></figure><h4>Why Detection Alone Fails</h4><p>Enterprises often focus on detection deploying SIEM, EDR, and XDR. But advanced adversaries design attacks that generate **benign-looking signals**. Even if an alert is raised, analysts may dismiss it as noise if the event appears to be normal Dropbox traffic or VSCode collaboration.</p><p>Adversary simulation highlights these blind spots by recreating **real campaigns end-to-end**. It forces defenders to answer:</p><p>* Could they connect weak signals into a bigger picture?<br>* Would they escalate an alert about “odd Slack onboarding traffic”?<br>* Could they detect persistence hidden in scheduled tasks or registry keys?</p><p>The real measure is not “was it detected?” but “was it understood and stopped in time?”</p><h4>Conclusion: From Compliance to Reality</h4><p>Pentesting improves vulnerability management. Red teaming sharpens detection and response. But neither fully prepares organizations for the tactics used by **APT groups and ransomware operators** today.</p><p>These adversaries exploit human trust, abuse legitimate services, and hijack everyday tools like NPM and VSCode to stay invisible.</p><p>Adversary simulation closes this gap. It mirrors the methods of real-world adversaries, validating not just technology but the readiness of people and processes.</p><p>The key question is no longer: *“Do we need adversary simulation?”*<br>It is:<br>👉 “Am I genuinely secure, or merely compliant?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/504/1*mqAb2ivMhM3BSUF80YUkDQ.jpeg" /></figure><p>I think it’s time to fight back, and the escalation will come from our side. Always remember: &quot;Be the threat to defeat it.&quot;<br>https://github.com/S3N4T0R-0X0/APT-Attack-Simulation</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1c69e8bd93a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stardust Chollima APT Adversary Simulation]]></title>
            <link>https://medium.com/@S3N4T0R/stardust-chollima-apt-adversary-simulation-d5c115a89ab9?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5c115a89ab9</guid>
            <category><![CDATA[adversary-emulation]]></category>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[apt-attack]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[adversary-simulation]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Sun, 10 Aug 2025 12:50:37 GMT</pubDate>
            <atom:updated>2025-08-10T12:52:43.643Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a simulation of attack by (Stardust Chollima) APT group targeting Chilean interbank network, The attack campaign was active in December 2018, have used PowerRatankba, a PowerShell-based malware variant that closely resembles the original Ratankba implant. The Redbanc corporate network was infected with a version of the PowerRatankba that was not detected by anti-malware. The way attackers delivered the malware, according to Flashpoint a trusted Redbanc IT professional clicked to apply to a job opening found on social media (linkedin). I relied on Security Affairs to figure out the details to make this: https://securityaffairs.com/79929/breaking-news/chilean-research-redbank-lazarus.html</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*QvJ30w_jW2yRjyHhQLSLEw.png" /></figure><p>Stardust Chollima Operations performed: https://apt.etda.or.th/cgi-bin/showcard.cgi?g=Subgroup%3A%20Bluenoroff%2C%20APT%2038%2C%20Stardust%20Chollima&amp;n=1</p><p>The dropper used to deliver the malware is related to the PowerRatankba, a Microsoft Visual C#/ Basic .NET compiled executable associated with Stardust Chollima APT. The dropper was used to download a PowerRatankba PowerShell reconnaissance tool, the dropper displays a fake job application form while downloads and executes PowerRatankba in the background by useing (Base64).</p><p>Zdnet resources: https://www.zdnet.com/article/north-korean-hackers-infiltrate-chiles-atm-network-after-skype-job-interview/</p><p>The PowerRatankba sample used in the Chilean interbank attack, differently from other variants, communicates to the C&amp;C server on HTTPS, This latter code is registered as a service through the “sc create” command as, the malware gain persistence by setting an autostart.</p><p>BushidoToken</p><p>Threat Intel: https://blog.bushidotoken.net/2021/08/the-lazarus-heist-where-are-they-now.html</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*XgMfKYyLi6WgSCGUDItcCQ.png" /></figure><ol><li>Social engineering technique: The attackers delivered the malware, according toFlashpoint a trusted Redbanc IT professional clicked to apply to a job opening found on social media.</li></ol><p>2. Fake job application form: The dropper displays a fake job application form while downloads and executes PowerRatankba in the background by useing (Base64).</p><p>3. PowerRatankba.ps1: The main backdoor creates a connection between the targeted device and gives the attacker full control via C2 server and latter code is registered as a service through the “sc create” command as,“ the malware gain persistence by setting an autostart .</p><p>4. C&amp;C server on HTTPS: When a command is received, it is executed using the PowerShell command in Windows. The output of the command is captured and sent back to the C2 server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*V_l9prPJ9tAjDHtZjkBvHQ.png" /></figure><h3>The first stage (social engineering technique)</h3><p>The attackers delivered the malware, according to Flashpoint a trusted Redbanc IT professional clicked to apply to a job opening found on social media.The person that published the job opening then contacted the employee via linkedin Skype, etc for an interview and tricked him into installing the malicious code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/801/1*fUS9uSfYUazZ4q9D7bKSrw.png" /></figure><p>The group addressed several employees of the company through LinkedIn&#39;s messaging. Passing himself as a Meta recruiter, the attacker used a lure of job offer to attract the attention and confidence of the target</p><p>This attack is based on a scenario that seems very natural and realistic. The attackers conduct job interviews in a completely normal way, and then inform the victim that they’ve been accepted for the position. Naturally, when someone gets accepted for a job, it’s expected that they will receive access to a company email or be asked to install certain programs required to start their tasks.</p><p>The scenario appears completely logical they might add you to the company’s Slack server, or ask you to download specialized tools or software. In some cases, they even ask you to start learning a new language like Spanish, and they tell you that they’ve already purchased a chair for you. All you need to do is install a certain application and enter your personal information into it.</p><p>But in reality, that application runs in the background and silently downloads a backdoor, giving the attackers unauthorized access to your device.</p><p>And the real objective of the attack is not the job itself, but the information on your personal device. Many people still keep sensitive data from their previous jobs on their laptops such as documents, projects, or login credentials. So, the attacker is indirectly targeting the company the victim previously worked at, or even the one they’re currently working for, by using the victim’s personal machine.</p><p>Instead of launching a direct attack on the company, they exploit normal human behavior like the desire to find a better job and target individuals who already have access or sensitive knowledge. This gives the attacker a hidden entry point to breach organizations without raising suspicion.</p><h3>The second stage (Fake job application - Backdoor Downloader by base64)</h3><p>This Stager is a graphical user interface (GUI) designed to look like a registration form for a fake company called &quot;Global Processing Center, LTD.&quot; However, in reality, it contains malicious code that executes a hidden PowerShell script when run. The dropper downloads and executes PowerRatankba in the background by useing (Base64).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*611nSGXJW6uzUENBjIBfHA.png" /></figure><p>Breakdown of the Malicious Code Execution:</p><ol><li>Automatic Execution: When the program starts, it automatically calls the function ExecuteBase64Script(), which is responsible for decoding and executing the malicious payload.</li></ol><p>2. Base64-Encoded PowerShell Script: The program contains Base64-encoded data, which is often used to hide malicious commands from antivirus and security software.</p><p>3. Execution with Unrestricted Policy: The PowerShell script is executed with bypassed execution policy (-ExecutionPolicy Bypass), meaning it ignores any security restrictions on running scripts.</p><p>This is a known technique used by attackers to execute unauthorized PowerShell commands without user consent.</p><p>4. Decoding and Writing to File: The Base64 string is decoded and saved as a PowerShell script file named &quot;PowerRatankba.ps1&quot; which is then used as the attack payload.</p><h3>The third stage (PowerRatankba.ps1 - Backdoor)</h3><p>This PowerShell script is a reverse shell with persistence, meaning it allows an attacker to gain remote access to the infected machine and ensures it runs every time the system starts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e0bOherdTCvtkDPPFdKK9g.png" /></figure><p>Once connected:</p><ol><li>waits for commands from the attacker.</li></ol><p>2. executes the commands on the victim’s machine.</p><p>3. sends the command output back to the attacker.</p><p>Persistence (Runs at Startup): The script modifies the Windows Registry (Run key) to automatically start on reboot. Every time the user logs in, the malicious script executes again, ensuring the attacker regains control.</p><h3>The fourth stage (payload connect to HTTPS-C2 Server)</h3><p>C&amp;C server on HTTPS: When a command is received, it is executed using the PowerShell command in Windows. The output of the command is captured and sent back to the C2 server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8h98_pAJqNqDDHSalsrX-Q.jpeg" /></figure><p>Github repository: https://github.com/S3N4T0R-0X0/APT-Attack-Simulation/tree/main/North%20Koreans%20APT/Stardust%20Chollima</p><p>Twitter: https://x.com/S3N4T0R_0X0</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5c115a89ab9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Famous Chollima APT Adversary Simulation]]></title>
            <link>https://medium.com/@S3N4T0R/famous-chollima-apt-adversary-simulation-58fbdf241d0e?source=rss-9a3478d109f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/58fbdf241d0e</guid>
            <category><![CDATA[red-team]]></category>
            <category><![CDATA[famous-chollima]]></category>
            <category><![CDATA[adversary-simulation]]></category>
            <category><![CDATA[apt]]></category>
            <category><![CDATA[adversary-emulation]]></category>
            <dc:creator><![CDATA[S3N4T0R]]></dc:creator>
            <pubDate>Sat, 02 Aug 2025 22:21:32 GMT</pubDate>
            <atom:updated>2025-08-02T22:30:09.983Z</atom:updated>
            <content:encoded><![CDATA[<p>This is a simulation of attack by (Famous Chollima) APT group targeting job seekers to accomplish their goals and wide variety of United States (US) companies, the attack campaign was active early as December 2022, The attack chain starts with attackers invites the victim to participate in an online interview. The attackers likely uses video conferencing or other online collaboration tools for the interview. During the interview, the attackers convinces the victim to download and install an NPM-based package hosted on GitHub. The actors likely presents the package to the victim as software to review or analyze, but it actually contains malicious JavaScript designed to infect the victim’s host with backdoor malware. I relied on paloalto unit42 to figure out the details to make this <a href="https://unit42.paloaltonetworks.com/two-campaigns-by-north-korea-bad-actors-target-job-hunters/">https://unit42.paloaltonetworks.com/two-campaigns-by-north-korea-bad-actors-target-job-hunters/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*9NmSGBu4VGtSISruGpXlbA.png" /></figure><p>This attack included several stages including During the interview, the attackers convinces the victim to download and install an NPM-based package hosted on GitHub. The attackers likely presents the package to the victim as software to review or analyze, but it actually contains malicious JavaScript designed to infect the victim’s host with backdoor.</p><p>HackerNews: <a href="https://thehackernews.com/2023/11/north-korean-hackers-pose-as-job.html">https://thehackernews.com/2023/11/north-korean-hackers-pose-as-job.html</a></p><p>1. Social Engineering Technique: The Attackers attempts to infect software developers with malware through a fictitious job interview.</p><p>2. GitHub Abuse (Supply-Chain): The Attackers exploited GitHub, a trusted platform used daily by developers, to deliver or distribute malicious packages, leveraging its legitimacy and widespread adoption. When developers clone and run the project, the malware executes in their environment.</p><p>3. NPM-based package hosted on GitHub: Create obfuscated JavaScript-based payload hidden inside Node Package Manager (NPM) packages. InvisibleFerret is a simple but Python-based backdoor. Both are cross-platform malware that can run on Windows, Linux and macOS.</p><p>4. Python backdoor: The component for InvisibleFerret deploys remote control and information stealing capabilities. Once executed, it prepares the environment by installing the Python packages, if they are not already present on the system.</p><p>5. TCP-C2 Server with XOR key: The C2 server returns JSON data instructing the backdoor with the next actions to take. The JSON response contains the same XOR key.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I1CtLB6stDnz7_TVGLYTMg.png" /></figure><h3>The first stage (Social Engineering Technique)</h3><p>The attackers lure their victims by inviting them to job interviews. In other cases, the attackers themselves apply for jobs using fake identities. They exploit the idea that people are in need of work or are seeking better opportunities, impersonating individuals applying for a position at a company. This is a clever tactic, as exploiting resources is far more valuable than just simply using them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zGSaSnVvoHEEVB1hjkNIDQ.png" /></figure><p>The logic behind this type of attack lies in the idea that instead of launching a direct attack on a company, an attacker can target an individual such as someone who was recently laid off and is actively seeking job opportunities. This person might still have access credentials to their former company’s email or possess sensitive company information. By compromising them, the attacker can gain indirect access to the organization.</p><p>Additionally, even without these specific circumstances, the second part of the logic is that many individuals in the IT and software development community commonly look for freelance work alongside their main job. This is a perfectly normal behavior, making it a natural and less suspicious entry point for attackers to exploit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J4cTB43WwZGj6vbuhvq2VQ.png" /></figure><h3>The second stage (delivery technique GitHub-Abuse)</h3><p>The attackers took advantage of the fact that their victims were part of the software development and IT community, possessing technical expertise and regularly working with GitHub. At the same time, using an open source project during a technical interview doesn’t seem unusual. Asking the victim to share their screen and test some code to assess their technical skills appeared to be a reasonable and clever tactic, especially when targeting victims from the IT field.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5MW3Ionrf9l9OF-cTW5BrQ.png" /></figure><p>However, in some of the repositories created by the attackers, they forgot to disable comments on the project. As a result, some users and security researchers discovered the malicious technique and left comments on the repository warning that it contained malware and should not be used. This mistake was not identified early enough. Additionally, there were other repositories where the attackers should have deleted the comments after uploading the malicious code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wfKMt3_4y14mOSKPo9DHlA.png" /></figure><h3>The third stage (implanting technique NPM-package)</h3><p>The attackers created an NPM package that, in turn, executes obfuscated JavaScript code, You can use these commands to create the NPM package.json file.</p><p>sudo apt-get install npm</p><p>mkdir my-malicious-package<br>cd my-malicious-package<br>npm init -y</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*TLVDnneDUgJcCyD1aSIrHQ.png" /></figure><p>Now i will create the JavaScript file using the command touch payload.js. Then, i paste the following code inside it, which contains only the whoami command just to test that everything is working correctly before adding the main payload and obfuscate Java Script code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/918/1*o7NXZAdfC0y2VqmHxl76nw.png" /></figure><h3>The fourth stage (Python Backdoor)</h3><p>The attackers created a simple payload that performs two main tasks:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/919/1*IgaV2drPa2XBxbtFEVK7xA.png" /></figure><p>1.The first task is establishing a connection to a C2 server over TCP with XOR encryption.</p><p>2.The second task is stealing credentials from the victim’s browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*1YECC0M8JAjSRDfNoafZIg.png" /></figure><p>This Python payload creates a reverse TCP shell that connects to a command-and-control (C2) server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2xEGfb8nqgZRyPgoNaytOg.png" /></figure><p>1. The script imports libraries for socket communication, subprocess execution, base64 encoding, and web browser interaction.</p><p>2. It defines XOR encryption/decryption functions to secure data exchange with a hardcoded key.</p><p>3. Upon execution, it opens url in a web browser and establishes a TCP connection to a specified C2 server (ip:port).</p><p>4. The script authenticates with the server, receives encrypted commands, executes them locally, and sends back encrypted results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*MJktiZqem5rAb3QAuQor_A.png" /></figure><p>The question here is: Why do attackers choose Python, even though it is not a built-in language in Windows like PowerShell scripts or CMD, meaning it cannot run without installing the necessary packages?</p><p>The answer lies in the target itself mainly software engineers. These individuals already have all the required packages installed, as Python is one of the most commonly used programming languages. Additionally, Python offers another advantage: scripts can be as short as just 60 lines, making modifications to any script hosted on GitHub nearly undetectable with obfuscated JavaScript and deleted the comments after uploading the malicious code.</p><h3>The fifth stage (execution technique with obfuscated JavaScript-based payload hidden inside NPM)</h3><p>Now i will replace the whoami command with the actual payload inside the JavaScript file and obfuscate it using BEAR-C2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*msx2oRymHXozlVsNE1ToGg.png" /></figure><p>Now I will open the obfuscation tool included in BEAR-C2, select the JavaScript file to obfuscate it, then upload the payload to GitHub and begin the Command and Control operation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oh8XFhKeJWBzj6bg-51NyA.png" /></figure><p>The JavaScript file is now obfuscated using the built-in obfuscation tool provided by BEAR-C2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TDt500jc1575hau4xstXNQ.png" /></figure><p>It’s important to ensure that the payload file has the same name as defined inside the NPM package before uploading it to GitHub.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H82qsbjDftlabKq91yBTNA.jpeg" /></figure><p>The final result is the successful establishment of a Command and Control channel. This is achieved by delivering a phishing link that mimics Microsoft login pages using BEAR-C2’s phishing module combined with an obfuscated JavaScript payload. Once executed, the payload initiates a reverse TCP connection to the attacker’s server, encrypted with XOR, allowing secure data exfiltration and remote command execution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wiUFj-25xz8NcsWs6Nc3mg.png" /></figure><p>Github repository: https://github.com/S3N4T0R-0X0/APT-Attack-Simulation/tree/main/North%20Koreans%20APT/Famous%20Chollima</p><p>Twitter: https://x.com/S3N4T0R_0X0/</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58fbdf241d0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>