<?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 f0xy_pr0xy on Medium]]></title>
        <description><![CDATA[Stories by f0xy_pr0xy on Medium]]></description>
        <link>https://medium.com/@f0xypr0xy?source=rss-d17fc4c5a1e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fRPhWV32XHeNxGn1ulHSHA.png</url>
            <title>Stories by f0xy_pr0xy on Medium</title>
            <link>https://medium.com/@f0xypr0xy?source=rss-d17fc4c5a1e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:36:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@f0xypr0xy/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[A Story to Remember : Inside the $6.43 Billion Binance Crypto Heist]]></title>
            <link>https://f0xypr0xy.medium.com/a-story-to-remember-inside-the-6-43-billion-binance-crypto-heist-555a6e4705e2?source=rss-d17fc4c5a1e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/555a6e4705e2</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[binance]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[f0xy_pr0xy]]></dc:creator>
            <pubDate>Sat, 07 Nov 2026 05:28:21 GMT</pubDate>
            <atom:updated>2026-11-07T05:30:38.531Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F6ExassxS2kHDtNUkA78Ig.png" /></figure><p>A <strong>sophisticated </strong>threat group targeted one of the world’s largest cryptocurrency exchanges : Binance through a carefully planned, multi-stage attack campaign, resulting in an estimated $6.43 billion in unauthorized transactions and financial losses.</p><p>Attackers no longer rely on a single entry point. Instead, they combine multiple techniques, such as supply chain , recruitment-based social engineering, credential expose, misuse of internal AI tools, and rouge service deployments, to eventually gain access to critical wallet signing infrastructure. This highlights how complex and interconnected modern adversarial attacks have become.</p><p>The initial compromise originated from a distributed supply-chain attack involving a trojanized Homebrew installer, which the Wallet DevOps engineer : Binance unknowingly downloaded from a deceptive website.</p><figure><img alt="Binance : Supply Chain" src="https://cdn-images-1.medium.com/max/940/1*qcJ-kVn89EusEjubeCY4vw.png" /></figure><p>The malicious installer was designed to compromise the engineer’s workstation and expose credentials/secrets associated with the DevOps engineer.</p><p>Few Months Later !</p><p>A sophisticated social engineering campaign used by a high realsitic fake recruitment interviews to target Binance : software engineers by impersonating a project director and conducting fake HR screenings and executive interviews, Later as part of the recruitment process, they shared a malicious coding assignment with the employee. The malicious code was executed on the corporate workstation during the project repository setup.</p><p>This gave the attackers another potential entry point into the corporate environment.</p><figure><img alt="From Developer Compromise to Wallet Breach" src="https://cdn-images-1.medium.com/max/1024/1*1DhF0GxAvezU11GWZVsvfQ.png" /></figure><p>The malicious code was heavily obfuscated and evasive . Once executed, it established external C2 communication with the attacker’s infrastructure, collected sensitive information and credentials, and removed forensic artifacts to hinder detection and incident investigation.</p><p>The attack did not stop there. Previously, attackers often abused privileged servers to move deeper into the network. However, they are now also targeting internal AI tools and agents, which often have high-level privileges and command execution capabilities.</p><p>The attackers began exploring and abusing access to these AI tools to support their lateral movement. Although the exact tools and techniques were not publicly disclosed, the reported outcome was the compromise of another software engineer’s workstation from the Binance : Software Engieer Walet team .</p><p>The compromised workstation of another software engineer, along with credentials stolen from a Wallet DevOps engineer during the earlier supply chain attack, gave attackers further access to the organization’s internal environment. They used the stolen DevOps credentials to gain access to systems with higher privileges, particularly those related to deployment.</p><p>These permissions were abused to deploy unauthorized or rogue containers within the infrastructure. By chaining compromised developer identities, stolen credentials, and infrastructure permissions, the attackers eventually reached the wallet signing service.</p><p>Supply chain attacks and internal AI tools with excessive privileges can pose serious security risks. As attack techniques and the threat landscape continue to evolve, detecting these threats is becoming increasingly challenging.</p><p>As technology stacks continue to evolve with advancements like AI, the security landscape expands, bringing new risks, challenges, and attack surfaces.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=555a6e4705e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can AI-Generated Malware Survive in the Wild?]]></title>
            <link>https://infosecwriteups.com/can-ai-generated-malware-survive-in-the-wild-18540924e88d?source=rss-d17fc4c5a1e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/18540924e88d</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[malware-analysis]]></category>
            <category><![CDATA[detection-engineering]]></category>
            <dc:creator><![CDATA[f0xy_pr0xy]]></dc:creator>
            <pubDate>Sat, 12 Sep 2026 05:50:14 GMT</pubDate>
            <atom:updated>2026-09-12T05:50:14.154Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JZ6s_H5CChbPPVVF2p8xGw.png" /></figure><p>Before the evolution of AI, adversaries often had to invest significant time and technical expertise to build their Offsec Infra. Developing custom payloads, backdoors, loaders, C2 and supporting infra required substantial knowledge, development effort, and operational experience.</p><p>That barrier is beginning to change. AI can significantly reduce the time and effort required to develop offensive tooling, including stealers, backdoors, loaders, and other malicious payloads. An adversary can now turn a basic idea or requirement into an initial implementation within seconds, dramatically lowering the development barrier for offensive operations.</p><p>But there is a significant gap between the <strong>AI</strong> <strong>generating malicious code</strong>,</p><p>Building malware that can actually operate effectively in the wild. Is it really worth it if <strong>AI generated malware</strong> are capable of producing a functional payload, yet reliability, evasion, persistence, communication, and interaction with an adversary’s environment ? this became a huge question</p><p>This becomes particularly interesting when examining a malware sample that appears to have been developed with AI assistance. Instead of looking for a definitive “AI-generated” signature, we can approach the problem from a reverse-engineering perspective: <strong>Does the code structure, design decisions, implementation style, and overall architecture reveal characteristics consistent with AI-assisted development?</strong></p><p>That is exactly what we will investigate in this analysis. We will break down the sample, understand how its components work, examine its capabilities and implementation patterns, and identify the characteristics that make this particular malware interesting from an AI-assisted malware development perspective.</p><p>The initial analysis of the binary shows that it is a 64-bit Linux ELF shared object compiled for the x86–64 architecture. It is dynamically linked, uses the standard Linux dynamic loader, and is built for GNU/Linux 3.2.0 or later.</p><blockquote>ELF 64-bit LSB shared object, x86–64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86–64.so.2, BuildID[sha1]=1f617f2ea259a7ec724d7bbc01627982dc2f0495, for GNU/Linux 3.2.0, not stripped</blockquote><h4><strong>File Identification &amp; Metadata</strong></h4><p>A quick <strong>Binwalk </strong>analysis provides some initial references to system-related locations such as /var/run/utmp and kernel tracing paths under /sys/kernel/debug/tracing. These references could indicate interaction with system state and Linux kernel tracing facilities.</p><p><strong>Strings &amp; Embedded Artifacts</strong></p><p>The string analysis gives us a better picture of the binary’s functionality. It contains several Linux system and process-related paths, including /proc, /dev/pts, /proc/self/exe, and /proc/net/tcp. It also references the socket API and GLIBC_2.2.5.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*hC6IriWzFZbNA1zR88gt1w.png" /></figure><p>These indicators suggest that the binary is capable of inspecting running processes, active network connections, pseudo-terminals, and its own executable path. Such functionality can be relevant to system reconnaissance and process or network monitoring.</p><p><strong>Disassembly</strong></p><p>The disassembly gives us a better understanding of the malware’s network communication logic. The binary attempts to establish a connection to the hard-coded IP address and prints a message after successfully connecting to the destination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ZoJzwOBJJ2fsO1NBDzo_g.png" /></figure><p>The binary also contains a visible error message, <strong>“connect() failed: trying to reconnect.”</strong> Interestingly, AI-assisted malware often leaves behind similar artifacts, such as descriptive comments, verbose error messages, and straightforward debugging remnants that would typically be removed or obfuscated in more mature malware.</p><p>Following a failed connection, the binary introduces a delay before attempting the connection again. This indicates that the malware has a reconnection mechanism for maintaining communication with its remote endpoint.</p><p>A quick review of the exposed functions provides a strong indication of the malware’s overall capabilities. The function names suggest that the binary contains a remote command-and-control component capable of system reconnaissance, privilege escalation, process control, file operations, and self-removal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/167/1*qsk9T-8Cdy8sjlBVy9PBXg.png" /></figure><p>Some of the identified functions include:</p><ul><li>User/System Enumeration: cmd_users, cmd_ps</li><li>File/Data Operations: cmd_get, cmd_recv</li><li>Command Processing: process_cmd, cmd_me</li><li>Process/Session Control: cmd_kick, cmd_exit</li><li>Privilege Escalation: cmd_privesc</li><li>Destructive Capability: cmd_selfdestruct</li><li>Kernel/Persistence-related Functionality: cmd_killbf</li></ul><p><strong>Self-Destruction</strong></p><p>The binary also contains strings that provide additional context around its execution and cleanup behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/637/1*foNDFQvvJAyKkTYEFlmVsw.png" /></figure><p>suggest that the malware can identify itself as an agent, establish communication, and potentially terminate or remove itself.</p><p>The /proc/self/exe reference is particularly interesting because it points to the currently executing binary, which can be used by a program to locate or manipulate its own executable.</p><p><strong>Overall Observation</strong></p><p>Putting all of these findings together, the binary appears to be a Linux-based remote-access and c2c implant developed with AI assistance. While AI can significantly accelerate the process of producing a functional payload, the underlying implementation observed in this sample remains relatively simple and follows several familiar malware patterns.</p><p>Even with packing and other attempts to obscure the binary, the overall structure and behavior remain fairly recognizable. This suggests that generating malware with AI may still require precise prompting, detailed instructions, and significant human guidance to achieve a more capable result.</p><p>This ultimately raises the bigger question: Is AI actually capable of independently producing malware that is sophisticated, reliable, and operationally effective or is it primarily accelerating the work of an attacker who already understands how to build it?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18540924e88d" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/can-ai-generated-malware-survive-in-the-wild-18540924e88d">Can AI-Generated Malware Survive in the Wild?</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Malchain : Tactic-Based Detection]]></title>
            <link>https://f0xypr0xy.medium.com/malchain-tactic-based-detection-679717c69f96?source=rss-d17fc4c5a1e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/679717c69f96</guid>
            <category><![CDATA[malware-hunting]]></category>
            <category><![CDATA[malware]]></category>
            <category><![CDATA[malware-analysis]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[detection-engineering]]></category>
            <dc:creator><![CDATA[f0xy_pr0xy]]></dc:creator>
            <pubDate>Fri, 28 Nov 2025 17:53:33 GMT</pubDate>
            <atom:updated>2025-11-28T17:53:33.795Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lDjRiDbMRv26RVRsGS70gw.png" /></figure><p>The emerging trends of malware-targeted attacks have led to the observation of distinct patterns frequently used by adversaries. Based on these observations, Impact has designed a malware-specific kill chain to track and understand the tactics employed throughout various stages of an attack, from initial access to exfiltration.</p><h3><strong>Mapping Malware Behavior Across Attack Tactics</strong></h3><p>MalChain serves as a reference to the MITRE ATT&amp;CK framework, visually aligning malware behaviors with their corresponding tactics and techniques. In this model, the tactics are arranged as columns, with each one representing the attacker’s goal during a particular phase of the malware lifecycle.</p><p>The malware matrices are dynamic in nature and are intended to be updated regularly to incorporate newly observed behaviors, techniques, and attack patterns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4QZ7CTm8GMCZux9HDdoKZw.png" /><figcaption><a href="https://github.com/Malwarehunts/Malchain/blob/main/docs/FRAMEWORK.md">Tactic-Based Detection</a></figcaption></figure><p>Ref: <a href="https://github.com/Malwarehunts/Malchain/blob/main/docs/FRAMEWORK.md">https://github.com/Malwarehunts/Malchain/blob/main/docs/FRAMEWORK.md</a></p><h3>How MalChain Works</h3><p>The framework breaks down malware behavior into six phases, each representing an attacker’s tactical objective:</p><ul><li>Initial Access: How the malware enters your system</li><li>Execution: Getting malicious code to run</li><li>Persistence: Maintaining a foothold after reboot</li><li>Defense Evasion: Staying hidden from detection</li><li>Lateral Movement: Spreading through the network</li><li>Exfiltration: Stealing the data</li></ul><p>Each phase maps to specific techniques with detection methods and real-world examples. The framework is intentionally dynamic — designed to evolve as new attack patterns emerge.</p><h3><strong>Malware Tactical Awareness</strong></h3><p>Traditional detection strategies, such as intelligence feeds and continuous monitoring, are often bypassed by modern malware. These malware variants are specifically engineered to evade conventional detection mechanisms, using techniques like polymorphism, encryption, or fileless methods to remain undetected.</p><p>To counter these evolving threats, implementing tactic-based detection — which focuses on understanding the adversary’s goals and behaviors at each phase of the attack — becomes crucial. By leveraging a kill chain framework and aligning detection efforts with the malware tactics and techniques,</p><p>organizations can more effectively hunt for advanced malware. This approach allows security teams to move beyond signature-based detection, focusing on the underlying behavior of the malware throughout its lifecycle.</p><p>Strengthening detection strategies through tactic-based methods not only improves the ability to identify sophisticated malware early but also enhances an organization’s overall threat-hunting capabilities. It enables security professionals to recognize subtle indicators of compromise, even when traditional detection tools fail, and respond proactively to mitigate the risks posed by advanced threats.</p><p>For more engaging malware-related content, be sure to check out https://malwarehunts.com/.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=679717c69f96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hunting Threats in the Software Supply Chain: A Practical Guide]]></title>
            <link>https://infosecwriteups.com/hunting-threats-in-the-software-supply-chain-a-practical-guide-b8a15b1fb36b?source=rss-d17fc4c5a1e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8a15b1fb36b</guid>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[supply-chain]]></category>
            <dc:creator><![CDATA[f0xy_pr0xy]]></dc:creator>
            <pubDate>Thu, 18 Sep 2025 18:39:49 GMT</pubDate>
            <atom:updated>2025-09-19T06:14:18.495Z</atom:updated>
            <content:encoded><![CDATA[<p>Gaining initial access into enterprise environments continues to pose significant challenges for adversaries, as organizations increasingly adopt proactive security measures designed to detect, restrict, and block connections initiated from external networks. In response to these strengthened defenses, threat actors have shifted their focus toward exploiting trusted third-party relationships and software dependencies — leveraging supply chain attacks as a more effective avenue to infiltrate targeted enterprises while bypassing traditional security controls.</p><h4>Supply Chain Attacks Explained</h4><p>Supply-chain attacks are a tactic adversaries use to gain an initial foothold in a target enterprise by compromising third-party applications or services the organisation depends on. Even when an enterprise’s own defenses are strong, vulnerabilities or misconfigurations in those trusted components can be exploited to bypass security controls and lead to a full compromise.</p><h4>Unmasking APT Groups: Supply Chain Attack Strategies</h4><ol><li><strong>APT29 (Nobelium / Cozy Bear)</strong> — Compromised SolarWinds Orion updates during the 2020 supply-chain intrusion, inserting malicious code that granted wide-scale access to targeted organisations.</li><li><strong>Sandworm (Russian GRU)</strong> — Delivered the destructive NotPetya attack in 2017 by exploiting the ME/doc update mechanism, making it one of the most damaging supply-chain incidents to date.</li><li><strong>Winnti / APT41 (China-linked)</strong> — Known for targeting software vendors and gaming companies, frequently embedding backdoors such as ShadowPad into legitimate software updates to maintain persistent access. (Source: We Live Security)</li><li><strong>Lazarus Group (North Korea)</strong> — Leveraged supply-chain techniques including trojanised developer tools, compromised installers, and malicious packages to deploy backdoors and steal credentials.</li><li><strong>Barium / Wicked Panda (China-linked)</strong> — Conducted multiple high-profile intrusions by tampering with vendor build systems and legitimate installers, enabling them to infiltrate targeted enterprises via trusted software supply chains.</li></ol><h4>Anatomy of a Supply Chain Compromise</h4><figure><img alt="Supply Chain Compromise" src="https://cdn-images-1.medium.com/max/1024/1*ow27HJyZUXZGugi3HiIZAw.png" /></figure><p>Adversaries have increasingly weaponised software packages that are frequently used by developers. If a developer or victim unknowingly downloads and installs such a malicious package, the embedded code is executed automatically. This can result in the deployment of backdoors, the exfiltration of sensitive data, or even the establishment of stable persistence through communication with command-and-control (C2) servers. Such attacks exploit the inherent trust developers place in widely used package repositories and third-party libraries, turning common development tools into vectors for compromise.</p><h4><strong>Python and its package</strong></h4><p>Packages are essentially collections of predefined functions bundled together into a single unit. Once packaged, developers or users can easily import them into their projects and invoke the associated functions. The diagram below provides a clearer illustration of this concept.</p><figure><img alt="Python and its package" src="https://cdn-images-1.medium.com/max/1024/1*S7wVKnw6lu56L2u0DmISTw.png" /></figure><p>As illustrated, packages are collections of predefined functions designed to perform specific operations. For example, the package named maths includes multiple functions such as add, sub, and mul, each responsible for a different calculation. Once the maths package is imported into a project, it provides access to these built-in functions. The user simply needs to supply the required input, and the function executes accordingly, returning the desired result</p><p>Note: As of September 2025, the Python Package Index (PyPI) lists 678,726 projects</p><h4><strong>Understanding Supply Chain Compromise: Detection and Investigation Strategies</strong></h4><p>Identifying and investigating supply-chain attacks is highly complex due to significant detection gaps and the limited traces they often leave behind. As noted, weaponised packages are commonly used to deploy backdoors that establish stable communication with attacker-controlled C2 servers.</p><p>Once such a package is imported and executed within a project, it can silently compromise the environment.</p><p>To strengthen detection, defenders should focus on monitoring for</p><ol><li>Monitoring suspicious process creation,</li><li>Inspecting and decoding Python packages to uncover hidden or malicious components.</li></ol><p><strong>Monitoring suspicious process creation</strong></p><p>Initial investigations into suspicious processes can be challenging, as enterprises generate a high volume of process creation events, many of which may lead to false positives. To minimise noise, it is important to analyse the context of process execution. For instance, when Python scripts are run, they typically rely on an execution medium such as cmd or PowerShell, which can serve as valuable indicators during an investigation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*MIBDtL1vJnjSvCGpapjs1g.png" /></figure><p>Prioritising and identifying suspicious processes requires multiple layers of correlation and analysis. Simply reviewing process creation events is not enough to confirm malicious activity; it is equally important to examine related events such as file creation and network communication. For instance, file creation activities linked to Python scripts can be particularly suspicious, as adversaries often leverage script execution to deploy backdoors or other malicious payloads.</p><pre>event.code : 11 AND (process.name : &quot;python.exe&quot; OR process.name : &quot;powershell.exe&quot; OR process.name : &quot;cmd.exe&quot; OR process.name : &quot;wscript.exe&quot; OR process.name : &quot;cscript.exe&quot;)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*JcSw-8RLlFmpcoyN1pOCag.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*-KEkVBffqY_OTxRRy35grw.png" /></figure><p>From the above results, it is clear that visibility is limited — for example, we cannot directly determine which specific script wrote a file on the host. To address this, we prioritise analysing process creation events associated with the identified process name python.</p><p>By correlating these events with their timestamps, we can effectively trace back and identify the script responsible for the file creation activity.</p><pre>event.code : &quot;1&quot; and process.name: &quot;python.exe&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/826/1*DWe_Eyr98wJ5goyw4Gm6Yg.png" /></figure><p>By reviewing the collected logs, we can accurately identify the specific Python script associated with the file creation activity.</p><h4><strong>Decoding the python packages</strong></h4><p>As part of determining the root cause and understanding the adversary’s actual behaviour, we focus on analysing the identified suspicious Python script.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*qELanRXyvz_Wvw-LuI0V3g.png" /></figure><p>Upon review, the script appeared to contain nothing more than a simple print statement for testing. This is where the trick lies — during investigations, such tactics can easily mislead analysts. However, on closer inspection, we noticed that a package named downloader had been imported.</p><p>To uncover the script’s true functionality, the next step is to decode this package and analyse its actual behaviour.</p><p>The following list highlights the directories where Python libraries are located</p><pre>C:\Users\&lt;username&gt;\AppData\Local\Programs\Python\Python&lt;XY&gt;\Lib\site-packages</pre><pre>C:\Python27\Lib\site-packages\pip\_internal</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/1*9Bh0G-laQvEfuBQrpnulJQ.png" /></figure><p>By navigating to the package folder, we were able to successfully locate the package that had been imported into the suspicious project.</p><p>Upon decoding the package, we discovered that its header was deliberately designed to communicate with an external network, enabling the download of a malicious payload.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/1*9CsyQ5jKB6N4CwR7rWf2cQ.png" /></figure><p>The above simulation demonstrates a classic example of a supply-chain attack, where adversaries intentionally develop and distribute a malicious package. If such a package is unknowingly integrated into a project, the hidden payload is executed as designed, leading to compromise.</p><p>This highlights the critical importance of securing the software supply chain. Developers and security teams must remain vigilant by validating package sources, monitoring dependencies, and implementing robust detection strategies. Even a single unverified package can serve as an entry point for adversaries, turning trusted tools into powerful attack vectors.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8a15b1fb36b" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/hunting-threats-in-the-software-supply-chain-a-practical-guide-b8a15b1fb36b">Hunting Threats in the Software Supply Chain: A Practical Guide</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Telegram as a Stealth C2: Investigation & Analysis]]></title>
            <link>https://f0xypr0xy.medium.com/telegram-as-a-stealth-c2-investigation-analysis-f91b42965e36?source=rss-d17fc4c5a1e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f91b42965e36</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[command-and-control]]></category>
            <category><![CDATA[detection-engineering]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <dc:creator><![CDATA[f0xy_pr0xy]]></dc:creator>
            <pubDate>Sat, 09 Aug 2025 23:10:20 GMT</pubDate>
            <atom:updated>2025-08-10T05:31:00.360Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HzsPu1QZ9FGqMhIsYAtOgw.png" /><figcaption>Telegram as a Stealth C2</figcaption></figure><p>Achieving persistent and reliable communication with a target host machine is a primary objective for adversaries. One of the most commonly used techniques to accomplish this is establishing a Command and Control (C2) channel.</p><p>As we know, there are many C2 tools like Cobalt Strike, Mythic, Sliver, etc. Since these are widely used among adversaries, they are now closely watched through pattern and behavior analysis. To detect them, organizations create custom monitoring strategies to spot and identify such C2 activity.</p><p>However, adversaries are often one step ahead in their attack execution. One of the more underrated strategies they use is leveraging a Telegram Bot as a C2 channel, enabling stealthy operations that are much harder to detect.</p><p>Let’s explore the complete set of detection strategies tailored specifically for Telegram Bot C2 activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/0*b6Q6vhETtjx77xa6" /></figure><h3>Functioning of a Telegram Bot</h3><p>Before diving into detection methods, let’s first break down how a Telegram Bot’s actually works.</p><p>A Telegram bot is essentially a program that communicates with Telegram’s servers using the Telegram Bot API. Unlike a normal user account, it doesn’t require a phone number; instead, it operates using a unique authentication token provided by BotFather.</p><p>This token acts like the bot’s password and allows it to send and receive messages programmatically.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Eo2s0jvqspLNqpSQ" /></figure><p>In essence, the process works like a normal chat interaction: a request is sent to the Telegram server, which then forwards the API call to the configured bot. Adversaries take advantage of this mechanism by mimicking the same communication flow, but instead of legitimate use, they turn it into a Command and Control (C2) channel.</p><ul><li>They create a bot and connect it to a Telegram chat or channel under their control.</li><li>Malware on the victim’s machine is programmed to communicate with this bot through the Bot API.</li><li>The attacker sends commands via Telegram (encrypted over HTTPS), which the infected host processes as if they were legitimate instructions.</li><li>The compromised system can then return data, execution results, or even files — all concealed within normal Telegram traffic.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tjyiU8u_wRHUvtM6" /></figure><h3>Detection Challenges</h3><p>Detecting Telegram-based C2 activity poses unique challenges. Unlike traditional C2 servers, which often leave multiple traces, Telegram bot–based C2 channels are far more difficult to spot. Below are some of the key detection challenges.</p><ol><li>Communication is routed through official Telegram domains and IP addresses,</li><li>Limited network traffic visibility makes it harder to distinguish malicious activity from normal usage.</li><li>Some malware leverages libraries like Python’s Telethon or Pyrogram, Node.js’s node-telegram-bot-api, or even direct MTProto connections — without requiring the Telegram application to be installed.</li></ol><h3>Telegram C2 Network Pattern</h3><p>From a network pattern perspective, it can be observed that the targeted victim initiates a DNS request to api[.]telegram[.]org. This is a strong indicator that the request is being directed to a Telegram bot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vNRE1ukCwnnd7Ajr" /></figure><pre>dns and dns.qry.name == &quot;api.telegram.org&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BKrtwQZo9d39oCxs" /></figure><p>A detailed analysis reveals stable communication over port 443 to the Telegram domain. Additionally, an FDASS network flag is observed. When adversaries execute a command, the Telegram bot initiates a SYN request, followed by a SYN/ACK from the victim. Once the bot receives the ACK, it transmits the data — which contains the command the adversary intends to run on the targeted victim. After execution is complete, the connection is terminated with a FIN flag.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*FAFPwJxq0G0W7ZuH" /></figure><p>As mentioned earlier, the communication occurs over HTTPS/TLS, meaning the traffic is encrypted by default. As a result, very little information can be extracted directly from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kGqQknn--4ocalOa" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*joPZIm9SeGrmhup9" /></figure><h3>Telegram C2 Host traces</h3><p>As noted, we have not observed significant traces at the host level either. However, the execution does trigger network communication, which can be actively monitored by many EDR and XDR solutions. Such monitoring can help identify the specific script or executable initiating the connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/917/0*9g5WGi7Ttzi5uJnj" /></figure><p>If you are able to identify the script or executable initiating the connection, you can proceed with decompiling or reviewing it to extract the associated API token. Successfully obtaining this token would allow you to send your own requests to the Telegram bot, which in some cases can help reveal the C2 chatbot or might be the commands the adversaries are attempting to execute.</p><pre>https://api.telegram.org/bot&lt;API&gt;/getUpdates</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jibx88UR1xF4e-MS" /></figure><h3>Hunting Telegram BOT C2</h3><p>Telegram bot–based C2 are highly stealthy and remain challenging to detect, as there are no well-established or widely adopted detection rules for them. Below are a few hypotheses that could help in identifying Telegram bot C2 activity.</p><ol><li>Look for DNS requests initiating connections to api[.]telegram[.]org.</li><li>Monitor network traffic to IP ranges 149.154.160.0/23 through 149.154.166.0/23, which are known to be used for Telegram bot communication.</li><li>Hunt for executables or scripts that initiate network connections to Telegram-related domains or IP addresses.</li></ol><p>Ref Link: <a href="https://github.com/D0rDa4aN919/TelegramBot_C2C_Py/tree/main">https://github.com/D0rDa4aN919/TelegramBot_C2C_Py/tree/main</a></p><p>Feel free to share your own hunting strategies and detection techniques for Telegram Bot C2.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f91b42965e36" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[End-to-End ELK + MCP Integration: A Beginner’s Deployment Guide]]></title>
            <link>https://infosecwriteups.com/end-to-end-elk-mcp-integration-a-beginners-deployment-guide-f2c3e36a0aeb?source=rss-d17fc4c5a1e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2c3e36a0aeb</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[mcp-server]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[f0xy_pr0xy]]></dc:creator>
            <pubDate>Sat, 12 Jul 2025 11:28:23 GMT</pubDate>
            <atom:updated>2025-07-14T11:22:16.554Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v160O5fl_oBPJeB62jqsMQ.png" /><figcaption>End-to-End ELK + MCP Integration: A Beginner’s Deployment Guide</figcaption></figure><p>As the evolution of the futuristic of threat hunting and Investigation is been tremodusly get growing, it’s essential to explore the architectural implementation of the ELK MCP Server and its role as a powerful engine for detecting, analyzing, and responding to threats across diverse environments.</p><p>In this blog, we’ll dive into how this advanced setup is driving the future of cybersecurity operations.</p><h4>Pre-requsites</h4><p>Before we dive into the deployment process, let’s quickly recap the essential prerequisites needed for setting up and configuring a futuristic threat hunting and investigation environment.</p><p><strong>ELK Server integrated with pre-collected logs</strong></p><ul><li>Before proceeding with the configuration of the MCP , it’s important to ensure that ELK is already installed over the server and preconfigured to collect logs from various endpoints or servers.</li></ul><p><strong>MCP Client/Server deployement and configuration</strong></p><ul><li>To give a brief summary of the MCP client — it acts as an intermediary between the user and the server, similar to how a ChatGPT UI allows users to input prompts. However, in our case, we are designing prompts specifically tailored for investigating and hunting security events</li></ul><h3>MCP Client/Server deployement and configuration</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fqVBUsSDLJwvdR26satvUQ.png" /><figcaption>ELK MCP Client/Server deployement and configuration</figcaption></figure><p>In our setup, we are using Claude as the MCP Client, which serves as the front-end interface for user interaction and acts as the intermediary between the user and the MCP Server.</p><p>By default, Claude offers both online and local deployment options. For our specific use case involving the deployment and configuration of the MCP, it is recommended to download and install Claude on a local machine to ensure better control, performance, and integration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K4T6xB5gDion79KoMyNIDw.png" /></figure><p>Once Claude is successfully installed on the local host, we can proceed with configuring and deploying the MCP Server on top of it. To do so, follow the steps outlined below.</p><p>Navigate to the <strong>file </strong>→ <strong>settings </strong>→ <strong>Developer </strong>→ <strong>Edit config</strong></p><p>By opening config file it will get redirect to the <strong>claude_desktop_config[.]jso</strong>n which get located under the local directory mentioned below<br>C:\Users\&lt;username&gt;AppData\Roaming\Claude</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/1*8UDOvhWr9ODCXmCx9Z4SOQ.png" /></figure><p>Once redirected, we’ll begin configuring the MCP server file within the Claude client. The required configuration has been designed by Elastic MCP itself. You can refer to the provided link to get retrive the json config structure. By simply pasting the JSON configuration below, you can quickly set up your MCP server.</p><pre>{<br>  &quot;mcpServers&quot;: {<br>    &quot;elasticsearch-mcp&quot;: {<br>      &quot;command&quot;: &quot;npx&quot;,<br>      &quot;args&quot;: [<br>        &quot;-y&quot;,<br>        &quot;@awesome-ai/elasticsearch-mcp&quot;<br>      ],<br>      &quot;env&quot;: {<br>        &quot;ES_HOST&quot;: &quot;&lt;elastic_URL&gt;&quot;,<br>        &quot;ES_API_KEY&quot;: &quot;&lt;API_Key&gt;&quot;<br>      }<br>    }<br>  }<br>}</pre><p>The configuration primarily requires two key pieces of information: <strong>ES_HOST</strong>, where you specify the URL of the Elasticsearch instance running on port 9200, and the corresponding API endpoint for interaction. Additionally, if authentication is enabled, you can configure the credentials using <strong>ES_USERNAME</strong> and <strong>ES_PASSWORD</strong> to securely connect to the Elasticsearch server.</p><p>Once we get successfully get configured we will be get promptedwith the elasticsearch-mcp server running</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wu-DSwlmXhQnp92p1z0g0g.png" /></figure><p>Once the status prompt appears, it confirms that the MCP client and server have been successfully configured and deployed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fDdP9SFICsa4UPMMulWj5Q.png" /></figure><p>Key Features and Capabilities</p><p><strong>Cluster Management</strong></p><ul><li><strong>elasticsearch_health</strong>: Get Elasticsearch cluster health status, optionally including index-level details</li></ul><p><strong>Index Operations</strong></p><ul><li><strong>list_indices</strong>: List available Elasticsearch indices, support regex</li><li><strong>create_index</strong>: Create Elasticsearch index with optional settings and mappings</li><li><strong>reindex</strong>: Reindex data from a source index to a target index with optional query and script</li></ul><p><strong>Mapping Management</strong></p><ul><li><strong>get_mappings</strong>: Get field mappings for a specific Elasticsearch index</li><li><strong>create_mapping</strong>: Create or update mapping structure for an Elasticsearch index</li></ul><p><strong>Search &amp; Data Operations</strong></p><ul><li><strong>search</strong>: Perform an Elasticsearch search with the provided query DSL</li><li><strong>bulk</strong>: Bulk data into an Elasticsearch index</li></ul><p><strong>Template Management</strong></p><ul><li><strong>create_index_template</strong>: Create or update an index template</li><li><strong>get_index_template</strong>: Get information about index templates</li><li><strong>delete_index_template</strong>: Delete an index template</li></ul><p>Deploying and integrating AI intelligence with Elasticsearch has become much easier with the evolution of MCP servers.</p><p>To simplify the process even further, watch the video demo below — it will help you understand the entire setup step by step.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fc_7vHk4VrCA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dc_7vHk4VrCA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fc_7vHk4VrCA%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/21aad755f675c7704c9d495138d427c2/href">https://medium.com/media/21aad755f675c7704c9d495138d427c2/href</a></iframe><p>In our upcoming post, we’ll take a deeper dive into a various hunting startiges and prompt which hep the to perform deep dive analysis and investigation</p><p>Ref: <a href="https://github.com/awesimon/elasticsearch-mcp">https://github.com/awesimon/elasticsearch-mcp</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2c3e36a0aeb" width="1" height="1" alt=""><hr><p><a href="https://infosecwriteups.com/end-to-end-elk-mcp-integration-a-beginners-deployment-guide-f2c3e36a0aeb">End-to-End ELK + MCP Integration: A Beginner’s Deployment Guide</a> was originally published in <a href="https://infosecwriteups.com/">InfoSec Write-ups</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Future of Threat Hunting and Investigation : ELK MCP Server]]></title>
            <link>https://f0xypr0xy.medium.com/the-future-of-threat-hunting-and-investigation-elk-mcp-server-caef1c184024?source=rss-d17fc4c5a1e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/caef1c184024</guid>
            <category><![CDATA[threat-hunting]]></category>
            <category><![CDATA[threat-detection]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[f0xy_pr0xy]]></dc:creator>
            <pubDate>Fri, 04 Jul 2025 03:31:45 GMT</pubDate>
            <atom:updated>2025-07-04T03:45:53.315Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZKYsnNtw6NzSy_adO0CrNw.png" /></figure><p>AI-based services are advancing rapidly, with integration across various domains becoming increasingly common. Imagine the transformative impact if AI were fully embedded within the realm of cyberspace.</p><p>Let’s explore how AI could be effectively integrated into the cybersecurity space — enabling capabilities such as anomaly and behavioral detection, data correlation, etc.</p><p>However, this leads us to the next critical question: <strong>how can these capabilities be effectively implemented?</strong></p><p>Let’s discuss the challenges and how AI actually works.</p><p>AI systems are increasingly being integrated with powerful LLM modules designed to understand and generate human language. These LLMs rely on deep learning — typically using transformer architectures — and require training on massive text datasets to function effectively.</p><p>Now that we have a dataset enriched with the required knowledge, the next step is to connect our pre-collected logs to it. By providing user input, the AI can process the query and effectively search through the stored logs to perform various anomaly and behavioral detection, data correlation, etc. .</p><p>Here comes another important question: how can we bridge the gap between user input, the LLM modules, and the pre-collected logs that have been stored?</p><p><strong>Module Context Protocol</strong></p><p>To answer to such question we get to see the evlotion of the Module Context Protocol, its nothing but the intermediate bridge between services and LLM modules. The image below illustrates the complete workflow and provides a clear understanding of how MCP functions within the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g1haLW1u7gNIvwAc-7SZAg.png" /><figcaption>Overview of MCP Client/Server Functionality</figcaption></figure><p>The architecture can be classified into three main phases: MCP Client, MCP Server, and Local Data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/442/1*WNdTb_4KrRgvxDT036SByw.png" /></figure><p>The MCP Client acts as the interface between the user and the system. It captures the user’s natural language input and routes it to an LLM module (such as ChatGPT or a privately hosted GPT-based model). The LLM interprets this input and converts it into a structured query.</p><p>This structured query is then sent to the MCP Server, which has the necessary privileges to interact with local or connected services. The MCP Server facilitates bi-directional communication, allowing seamless interaction between the LLM-generated logic and the backend services or data stores.</p><p>Following the evolution of MCP, many companies — including several in the cybersecurity space — began developing their own MCP servers. Among them, Elastic (ELK Stack) introduced its own implementation of MCP.</p><p>Let’s explore how ELK integrated MCP into its architecture and evaluate the effectiveness of their approach.</p><p>The ELK Stack is a widely used open-source platform for logging, monitoring, and data visualization. In the realm of cybersecurity, ELK serves as a core component for building a SIEM system. Organizations use it to ingest, process, and analyze large volumes of security logs and events in real time. Additionally, by implementing basic detection rules, ELK enables proactive monitoring and early identification of potential security threats. as in such case the security teamwill get to be interating with the ELK to get qiery and investigate secueity thresta,</p><p>Until now, much of our daily security operations have relied on manual querying and investigation. But imagine a scenario where this entire process is automated and managed by an AI-powered service !</p><p>To bring this vision to life, ELK has introduced its own MCP (Module Content Protocol) server, designed to support a variety of use cases. Let’s explore how we can effectively integrate ELK:SIEM with AI capabilities using Elastic’s MCP, enabling smarter, automated security operations.</p><h4><strong>Introducting The ELK MCP</strong></h4><p>This module <a href="https://github.com/elastic/mcp-server-elasticsearch?tab=readme-ov-file#elasticsearch-mcp-server">ELK MCP</a> allows you to connect directly to your Elasticsearch data from any MCP Client (such as Claude Desktop) using the Model Context Protocol (MCP).</p><p>The ELK MCP comes pre-configured with a set of features, which are listed below.</p><ol><li><strong>list_indices</strong>: List all available Elasticsearch indices</li><li><strong>get_mappings</strong>: Get field mappings for a specific Elasticsearch index</li><li><strong>search:</strong> Perform an Elasticsearch search with the provided query DSL</li><li><strong>get_shards:</strong> Get shard information for all or specific indices</li></ol><p>According to their release notes, the server connects agents to your Elasticsearch data using the MCP, enabling interaction with Elasticsearch indices through natural language conversations.</p><p>This unlocks several powerful capabilities: agents can retrieve index data, access mapping details, and — most importantly — perform searches across multiple indices. They also support data correlation across various existing indices within the Elastic environment, significantly enhancing investigation and analysis efficiency.</p><p><strong>Deployment overview of ELK MCP</strong></p><p>Before integrating with ELK MCP, there are several important prerequisites that must be completed. The following list outlines the necessary steps to prepare for a successful integration:</p><ol><li>Deploy and configure the ELK Stack</li><li>Deploy monitoring agents on the target host machines</li><li>Pre-install the Claude service (MCP Client)</li><li>Establish connections between the ELK MCP server, the ELK service, and the MCP Client</li></ol><p>Basically, the input you provide is first sent to the MCP Client, which analyzes the request and determines the appropriate Elasticsearch operations required. The MCP Server then executes these operations — such as listing indices, retrieving mappings, and performing searches. Finally, the MCP Client processes the output and displays the results in a user-friendly format.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1AHslDLZDSpz3Hud_Us78Q.png" /><figcaption>Architecture and Workflow of the ELK MCP Client/Server System</figcaption></figure><p>We aim to build a conceptual understanding of how futuristic Threat Detection and Response can be implemented using AI.</p><p>In this blog, we’ll explore the key features and prerequisites of the ELK MCP Server. In our upcoming post, we’ll take a deeper dive into a step-by-step deployment of the architecture and evaluate its performance in real-world scenarios. Stay tuned for a hands-on walkthrough and detailed performance insights</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caef1c184024" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>