<?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 GagandeepB on Medium]]></title>
        <description><![CDATA[Stories by GagandeepB on Medium]]></description>
        <link>https://medium.com/@gagandeep8?source=rss-57e0560d27b4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by GagandeepB on Medium</title>
            <link>https://medium.com/@gagandeep8?source=rss-57e0560d27b4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:32:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gagandeep8/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[The NightSpire Operation: Inside the Infrastructure of a Growing Double-Extortion Syndicate]]></title>
            <link>https://medium.com/@gagandeep8/the-nightspire-operation-inside-the-infrastructure-of-a-growing-double-extortion-syndicate-6529001ba16e?source=rss-57e0560d27b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6529001ba16e</guid>
            <dc:creator><![CDATA[GagandeepB]]></dc:creator>
            <pubDate>Sat, 08 Nov 2025 06:25:26 GMT</pubDate>
            <atom:updated>2025-11-08T06:25:26.155Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Executive Summary</strong></p><p>NightSpire is a newly identified ransomware collective operating within the dark web ecosystem. First detected in early 2025, the group distinguishes itself through a structured leak portal, multi-channel communication framework, and a growing record of targeted data-leak incidents. Preliminary analysis indicates that NightSpire follows a double-extortion model, exfiltrating sensitive data prior to encryption and using public exposure as leverage in ransom negotiations.</p><p>Initial observations gathered through StealthMole’s dark web tracker reveal a consistent and organized operational presence. The group maintains a dedicated <strong>.onion</strong> site featuring segmented sections for announcements, data leaks, and communication methods. Its infrastructure reflects a deliberate approach to redundancy and anonymity, employing multiple secure channels such as OnionMail, Telegram, Tox, and Session to facilitate victim correspondence and ensure continuity despite potential takedown attempts.</p><p>Although the scale of NightSpire’s operations is still being established, early indicators suggest that its targeting is multi-sectoral and geographically diverse. The group’s communications, tone, and infrastructure suggest a degree of operational maturity inconsistent with a newly formed actor, implying that NightSpire may represent a rebranded or reorganized entity rather than a completely new entrant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-GBU1qdLbK8YEig_bxWO6Q.png" /></figure><p><strong>Investigation Background</strong></p><p>This investigation began on <strong>5 November 2025</strong>, when StealthMole’s Ransomware Monitoring Tool flagged a new set of leaks attributed to the ransomware group <strong>NightSpire</strong>. Among the listed victims was <strong>Best Log Logistics Solutions,</strong> a motor-freight company based in Brazil. On that same day, NightSpire also published data from five other organizations, suggesting an unusually active period for the group.</p><p>Although NightSpire has been active since <strong>March 2025</strong> and has claimed responsibility for more than <strong>80 attacks to date</strong>, this sudden cluster of disclosures pointed to a possible escalation in its operations. The volume and coordination of leaks indicated that NightSpire was not acting opportunistically but executing a planned release cycle, possibly to reinforce its visibility or strengthen its negotiating leverage.</p><p>The alert included a reference to the group’s leak site. To verify the domain’s activity and confirm its link to NightSpire, it was analyzed through StealthMole’s Dark Web Tracker. The tracker confirmed that the site was live and actively publishing new victim entries, matching the timing and details from the initial alert.</p><ul><li><strong>nsp*************************************onion</strong></li></ul><p>Given NightSpire’s established presence, its steady expansion, and the recent surge in coordinated attacks, the group was selected for a focused investigation. The aim was to document its infrastructure, operational methods, and technical assets, using verifiable intelligence collected through StealthMole’s monitoring and correlation tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsqg1SU6DV1LXER54CF96A.png" /></figure><p><strong>Infrastructure and Communications</strong></p><p>NightSpire’s operational surface is anchored by a Tor-based leak portal that functions as the group’s public publication and negotiation platform. The leak site is the obvious outward-facing element, but the actor’s communications architecture extends well beyond a single web presence and deliberately relies on multiple privacy-preserving channels to maintain resilience and operational continuity.</p><p>The group advertises a Session identifier for direct, encrypted messaging. It also publishes a long-form Tox identifier for peer-to-peer connections. Both values represent unique, high-fidelity artefacts for cross-platform correlation and should be treated as priority indicators when searching historical forum posts, paste sites, or other leak entries.</p><ul><li>Session ID:<br><strong>57********************************************************02</strong></li><li>Tox ID:<br><strong>3B**********************************************************E6</strong></li></ul><p>Telegram is used as a complementary, more interactive channel. The two handles observed in the actor’s materials are <strong>@night_spire_team</strong> and <strong>@nightspireteam2025</strong>. These accounts provide a faster, lower-friction route for contact and announcement distribution while preserving a degree of anonymity compared with clearnet email.</p><p>NightSpire’s published email contacts span both privacy-focused and conventional services, offering multiple avenues for correspondence. The addresses recorded in StealthMole’s crawl are:</p><ul><li><strong>ni**************************.me</strong></li><li><strong>ni***************************.org</strong></li><li><strong>ni***************************.me</strong></li><li><strong>ni*****************************om</strong></li><li><strong>ni******************************rg</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dtIlaX6wjNvNkniemRdDdQ.png" /></figure><p>The mix of ProtonMail and OnionMail alongside a standard Gmail account reflects a deliberate redundancy: privacy-centric accounts for secure negotiation and a clearnet fallback for accessibility or misdirection.</p><p>The secondary onion returned a set of Mega links that appear to function as the group’s external data repositories. These links are:</p><ul><li><a href="https://mega.nz/file/XAolnQga#XByCfYtqK3LEB0n03beeJWTpvW7KKjARejqBm8QLn08"><strong>ht************************************************08</strong></a></li><li><a href="https://mega.nz/file/6ZREhRzQ#ok3aQF34zyjXy9g3PX2C_YLWkGeuvrCAHMjNMAXbV1s"><strong>ht*************************************************1s</strong></a></li><li><a href="https://mega.nz/file/29gyGR6R#r24xdHvJtjvG8uI-1m51o_jFiiKZLN9p0OzG21k8AGI"><strong>ht**************************************************GI</strong></a></li><li><a href="https://mega.nz/file/SoAHXYbA#iQaKg9a-C0HUOhTOsKaZT780LW_rL87pl7siXWPEt3U"><strong>ht***************************************************3U</strong></a></li><li><a href="https://mega.nz/file/6VZlCYAT#dHUUt6Z7i9_KKI1CYAn4OyBp6yXITQWlvJ-6WeUr3DU"><strong>ht*****************************************************DU</strong></a></li><li><a href="https://mega.nz/folder/UwhlTSpR#jtn6dGIpb-HAZoa3pok75w"><strong>ht******************************************************5w</strong></a></li><li><a href="https://mega.nz/file/S55S2BxK#Vr-iR-gCUx75wr0bqQ_ZFQFj8t3KOoegg_4sPyOws6s"><strong>ht*******************************************************6s</strong></a></li><li><a href="https://mega.nz/folder/IlBgVCKT#TDzoMjP6o-h_8jJkM9r_Fg"><strong>ht********************************************************Fg</strong></a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AmG7b_y6y7CdWLFa1wGH7g.png" /></figure><p>These URLs should be treated as potential evidence stores and retrieved only within an isolated forensic environment; their contents may include proof-of-compromise samples or full data dumps and therefore require controlled handling, hash verification, and chain-of-custody preservation.</p><p>During the same time, StealthMole correlated NightSpire activity with a user profile on BreachForums. According to the forum entries captured, the actor registered on BreachForums in March 2025 and posted activity as early as 19 March 2025. Forum references provide additional context and timeline data, but they require cautious treatment: forum posts can be impersonated, edited, or removed, and should be corroborated with archived snapshots and cross-platform indicators before being used for attribution.</p><ul><li><a href="https://breachforums.st/User-night-spire-team"><strong>ht***********************************am</strong></a></li></ul><p>Operationally, the combined set of mirrored onion pages, off-platform Mega repositories, multi-rail communications, and public forum footprints represents a layered infrastructure designed for persistence, proof distribution, and resilient victim contact.</p><p><strong>Assessment</strong></p><p>NightSpire has evolved into a structured and persistent ransomware operation. Since its emergence in March 2025, the group has maintained steady activity, using multiple Tor domains, off-platform data repositories, and a web of encrypted communication channels. Its recent surge of attacks in early November 2025 — including the compromise of Best Log Logistics Solutions in Brazil — shows that NightSpire is capable of running several campaigns at once, a sign of growing capacity and coordination.</p><p>The infrastructure uncovered through StealthMole — particularly the onion sites, Mega repositories, and verified contact identifiers — provides a clear picture of how the group operates. NightSpire’s behavior follows a familiar double-extortion pattern: exfiltrating data, encrypting local systems, and then publishing the stolen material to pressure victims into payment. Its choice of victims across logistics, healthcare, and technology suggests opportunistic targeting with a focus on high-impact data.</p><p>At this stage, there is no confirmed link between NightSpire’s malware samples and any known ransomware family, but early analysis points to custom-built tools designed for encryption and data theft. The evidence collected gives moderate to high confidence in the group’s infrastructure mapping, though attribution to specific operators remains uncertain.</p><p>Overall, NightSpire represents a credible and expanding threat. Organizations that handle sensitive or proprietary data should treat its indicators as high-priority for detection and response. Continuous dark-web monitoring, proactive threat-hunting using the provided identifiers, and safe forensic analysis of linked repositories remain essential to tracking the group’s next phase of activity.</p><p><strong>Conclusion</strong></p><p>NightSpire’s activity over the past months reflects a ransomware group that is organized, adaptive, and intent on longevity. What began as another dark-web extortion portal has matured into a coordinated operation supported by redundant infrastructure, multiple encrypted communication channels, and custom-built malware. The group’s consistent publication cadence, multi-sector targeting, and use of external data repositories point to a sustained effort to establish itself among established ransomware brands.</p><p>While the technical evidence gathered through StealthMole confirms NightSpire’s operational capability, attribution to specific individuals or origins remains uncertain. The indicators collected — onion domains, communication IDs, Mega repositories, and malware hashes — provide reliable insight into how the group functions, but not yet who operates it.</p><p>NightSpire’s trajectory suggests that further activity is likely. Its recent surge in simultaneous victim disclosures indicates growing resources and confidence. Continued monitoring through StealthMole’s dark-web tracking and malware correlation tools will be essential to anticipate new campaigns, update indicators of compromise, and strengthen defensive readiness.</p><p>As with all dark-web investigations, attribution should be treated as probabilistic. However, the evidence gathered to date establishes NightSpire as a capable and active ransomware collective — one that merits ongoing attention from both security teams and intelligence analysts.</p><h3>Editorial Note</h3><p>As with any dark web investigation, absolute certainty is rarely possible. The information in this report is based on verified data collected through StealthMole’s tracking and analysis tools, combined with open-source intelligence available at the time of writing. While the findings provide a clear picture of <strong>NightSpire’s</strong> operations and infrastructure, cyber attribution should always be viewed as <strong>probabilistic</strong>, not conclusive.</p><p>Threat actors evolve quickly — they change domains, switch aliases, and reuse code across campaigns to hide their origins. The indicators presented here reflect NightSpire’s known activity as observed during the investigation period, but these details may shift as the group continues to adapt.</p><p>This report was written to document what is currently known and to support analysts, defenders, and researchers in understanding NightSpire’s tactics and footprint. Continued monitoring, cross-verification, and cautious interpretation are essential as this ransomware collective remains active and its operations continue to unfold.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6529001ba16e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From “Infantile” to “Juvenile”]]></title>
            <link>https://medium.com/@gagandeep8/from-infantile-to-juvenile-76be3870597a?source=rss-57e0560d27b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/76be3870597a</guid>
            <dc:creator><![CDATA[GagandeepB]]></dc:creator>
            <pubDate>Fri, 15 Aug 2025 14:25:20 GMT</pubDate>
            <atom:updated>2025-08-15T14:25:20.529Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Inside the Digital Footprint of a Dark Web Service Provider</em></p><h3>Overview</h3><p>It started with a dark web site buried in an online repository, listed under a category that instantly raised eyebrows. The name alone was enough to spark suspicion: provocative, suggestive, and impossible to ignore. At first glance, there was no evidence of the material that its listing implied, but the choice of branding felt deliberate. That curiosity was enough to dig deeper.</p><p>Using StealthMole’s tracking tools, the investigation began pulling on threads, small clues that led from one hidden service to another. What seemed like a single site gradually unfolded into a larger, more complex network. Along the way, the identity behind it shifted, adopting a new name and expanding its online presence. What emerged was a picture of a service that, while not hosting the illicit content its category suggested, carried an identity and operational structure that left more questions than answers.</p><h3>First Signs of a Larger Network</h3><p>The first real lead came from the dark web site operating under the name <strong>Infantile</strong>, accessible via http://in***********4.onion/. Its presence in an online repository sparked this investigation, largely because it had been placed under a category suggesting illicit material. While its actual content did not match that description, the platform appeared to be a hosting and service hub. Still, the choice of name was provocative, and in the context of the dark web, such branding is rarely accidental.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rOSScZnYsqBTzt0BEHYveg.png" /></figure><p>Using StealthMole’s dark web tracker, the investigation quickly uncovered two Bitcoin addresses linked to the site. Tracing these addresses revealed transactions associated with other onion domains, leading to one of the most notable connections: a second site under the name <strong>Juvenile</strong>, hosted at http://ju***************d.onion/. This shift in naming from <em>Infantile </em>to <em>Juvenile</em> suggested both continuity of operations and a deliberate choice to retain the same provocative theme.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c5VN6Q08XTVEqck9fDRbXw.png" /></figure><p>These connections emerged through methodical pivots, moving from the cryptocurrency ledger to domain infrastructure, and identifying overlaps in hosting and operational behavior. What began as a curiosity over a single oddly named domain had now evolved into a map of interconnected platforms, tied together by financial transactions and a shared branding strategy.</p><h3>Infrastructure and Link Mapping</h3><p>Once the trail extended from <strong>Infantile</strong> to <strong>Juvenile</strong>, the investigation focused on fully mapping the network that supported these services. The two Bitcoin addresses linked to <strong>Infantile: </strong>1************************i and 15***********************9, became key pivot points to trace transactions across the blockchain and uncover further operational ties. These addresses were not isolated, rather, they formed part of a broader cryptocurrency infrastructure that connected to additional hidden services.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wC0opCiZ0o3pDxYsovoGxA.png" /></figure><p>One significant finding was that multiple onion domains shared either hosting characteristics or direct transactional links. For example, tracing activity from the <strong>Infantile</strong> domain (http://in********4.onion/) led not only to <strong>Juvenile </strong>(http://ju***************id.onion/) but also to additional addresses and services that appeared to be run under the same operational control. This mapping was strengthened by cross-referencing domain registration timelines, SSL/TLS fingerprinting patterns, and cryptocurrency transaction flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hRmm4j-k5u2Cwa8V8q_bcA.png" /></figure><p>The picture that emerged was of an interconnected web of services, some directly visible, others existing only as hidden endpoints or mirrored resources. Each newly identified domain added to the operational profile of the actors behind this infrastructure, revealing that the seemingly standalone <strong>Infantile</strong> service was in fact a component of a larger, well-organized ecosystem.</p><h3>Kaizushi: The Central Operator Behind the Network</h3><p>Following the mapping of <strong>Infantile</strong> and <strong>Juvenile</strong> services, one figure emerges repeatedly as the central node connecting each domain, service, and operational decision: <strong>Kaizushi</strong>. Presented as the owner–administrator of <strong>KLOS (Kaizushi’s Little Onion Server)</strong>, Kaizushi’s presence is visible not only through public service announcements but also through signed canaries, mirrored infrastructure, and technical repositories. She identifies as a woman who “escaped from Arabia” and now lives in a secular society, openly associating her work with Agorist ideology. This personal narrative is woven into her technical and operational output, giving the services a singular and identifiable voice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HsfTK98zPvQcyu-8swmpEw.png" /></figure><p>The infrastructure under Kaizushi’s control is expansive, spanning clearnet, Tor, and I2P mirrors. KLOS’ main entry points are hosted at https://kl*****t.online/ and http://kaizu**************d.onion/, with additional content such as the signed “new main page” and the warrant canary (https://kl*********t.online/page.php?q=canary) providing a verifiable link between all mirrors. Historical instances, like http://kaizu*********z.onion/, demonstrate the longevity of this operation, while I2P hosting (kl*****t.i2p) offers redundancy beyond Tor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XnufGhm_6Ak58uTWFPL-Tw.png" /></figure><p>Kaizushi’s public services extend beyond hosting. The <strong>Infantile</strong> platform (http://in******4.onion/, in****e.**z) offers encrypted communications, including XMPP, IRC, and paid email. The branding and operational model are carried forward into <strong>Juvenile</strong>(http://ju********************id.onion/), which also hosts IRC services on ports 6667 and 6697 SSL. Across both, Kaizushi maintains strict privacy standards, hardened Gentoo builds with grsecurity/PaX and SELinux, PGP-signed announcements, and an operational preference for Monero.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BjQ1csKbQMNqUO7Znc-PsQ.png" /></figure><p>Her operational identity is reinforced by cryptographic artefacts. The PGP fingerprints for kaizushi@i******e.*s, kaizushi@i*******e.**z, kaizushi@****k.*i, and kaizushi@r*****p.net are publicly signed, while OMEMO keys, such as 8C*****7 CB****D 1*****D E******E F*****5 F*****F 9******F 3******6, authenticate her XMPP accounts. Associated staff accounts, such as <strong>ch******5</strong>, carry their own extensive OMEMO key sets and are visible across the same platforms. Session IDs, including 059****************************************7, further tie live chat identities to the broader network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BSduB3atuICLF6CgaMFu3w.png" /></figure><p>Public statements show an adaptive operational posture. One announcement explains the compromise of her xmpp.jpaccount, advising contacts to migrate to 404.city. Another notes a temporary pause in XMPP operations to mitigate timing-correlation risks before returning to service from KLOS infrastructure. Her “Retired / Blue Pony” post reflects years of onion service operation, development of web applications, XMPP services, and Monero nodes, alongside concerns over 2024 kernel-level exploit attempts by state-level actors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t3DQBTm0v0Khd-E_eHQblg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UlvUqQ88Qx7XDKCbWuiw_A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ah_67KsPzuMcQf7GKzlmbw.png" /></figure><p>Outside of service hosting, Kaizushi develops and publishes tools that align with her operational philosophy. The <strong>canary-gen</strong> project automates PGP-signed canary creation and deployment, integrating with her static CMS to add current news and prevent back-dating. The <strong>exitkit</strong> repository provides guidance for running private Tor exits. Her GitHub presence, including the p******e CMS, is linked to the name <strong>Kaizu Shibata</strong> (https://github.com/k******i/p******e/), connecting her development identity with her operational one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*modWkP8W1q7Ct4cLeho78w.png" /></figure><p>Her contact points are deliberately redundant: enquiries@k*****t.o*****e for general questions, kaizushi@i*******e.us for encrypted communications, and kaizushi@in**********4.onion for XMPP on the same server. Staff contact <strong>ch*******5</strong> uses ch**************h4.onion for XMPP and ch3**************e.us for email. These are supported by regular canary updates, ensuring authenticity and signalling operational continuity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IJ0W7iTrqytP1C0zK0h5VQ.png" /></figure><p>Every major asset traced in this case, from domain infrastructure and cryptographic keys to operational tooling, consistently resolves back to Kaizushi’s estate. This makes her not only the primary operator but also the most valuable pivot point in mapping the entire network.</p><h3>Operational Structure &amp; Behavioral Indicators</h3><p>The operational footprint of this network displays a deliberate compartmentalization strategy, with different services and functionalities distributed across multiple onion domains. This decentralization limits the impact of any single takedown and helps preserve service continuity even if one node is compromised. The two primary platforms identified during this investigation, in******4.onion and ju*************d.onion, appears to follow a consistent naming convention that is both provocative and potentially misleading.</p><p>The use of terms such as “Infantile” and “Juvenile” in domain naming is particularly striking. While neither platform displayed overt CSAM content during this investigation, their branding places them in a high-risk category for being flagged or misclassified in OSINT repositories, as initially happened when the I*******4.onion domain appeared under a child exploitation category. This raises questions about the operator’s intent, whether such naming is an attempt to exploit controversy for visibility, to repel certain kinds of scrutiny, or to mask operations behind shock value.</p><p>The mapping of connections between these domains, BTC wallets, and related infrastructure suggests an organized and intentional operational model. This model prioritizes both anonymity and resilience, using cryptocurrency transactions for financial operations, onion routing for service delivery, and a network of known associates, such as Kaizushi, to maintain reach and functionality across the dark web. The cross-linkage between these domains, combined with established actor profiles, indicates a shared or overlapping operational leadership, rather than isolated, independent actors merely sharing hosting resources.</p><p>By tracking not only the services but also the thematic and behavioral indicators embedded in their infrastructure, StealthMole’s tools were able to expose a layered operational structure that extends beyond mere hosting into an identifiable and traceable entity within the dark web ecosystem.</p><h3>The Role of StealthMole in Uncovering the Network</h3><p>The depth and clarity of this investigation would not have been possible without StealthMole’s advanced dark web intelligence capabilities. From the moment the in*******4.onion domain was flagged in a misclassified repository, StealthMole’s platform provided the pivot points needed to move from a single suspicious URL to an interconnected web of domains, payment channels, and key actors.</p><p>The tool’s dark web tracker was instrumental in mapping the relationship between in*****4.onion and ju**********d.onion, uncovering the Bitcoin and Monero wallets used for transactions, and linking them to previously unidentified infrastructure. Each pivot, from BTC addresses to hidden services, and from domains to associated profiles like Kaizushi, was made possible by the platform’s ability to cross-reference datasets and surface hidden correlations.</p><p>This case also highlights StealthMole’s effectiveness in navigating the subtleties of dark web intelligence gathering. Where manual OSINT methods might have overlooked or misinterpreted the domain naming strategy, StealthMole enabled a structured, fact-driven approach to mapping the ecosystem without losing sight of operational context. In doing so, it transformed what began as a single misclassified entry into a detailed intelligence profile, exposing the breadth of the network and its operators.</p><h3>Conclusion</h3><p>The investigation into the<strong> Infantile</strong> and<strong> Juvenile</strong> domains revealed far more than a questionable naming convention. What began as a single misclassified entry in a dark web repository unfolded into a deliberate and resilient infrastructure, tied together by shared operational traits, cryptocurrency channels, and the activity of a known dark web actor, Kaizushi.</p><p>The choice of provocative names, while not directly linked to CSAM content, has operational consequences, both in attracting unwanted law enforcement scrutiny and in creating a form of reputational camouflage. This ambiguity can serve as both a shield and a lure, complicating the task for investigators and potentially deterring casual exploration by threat actors outside the intended network.</p><p>From a threat intelligence perspective, the network’s decentralization, layered anonymity measures, and calculated cross-linking of infrastructure suggest a mature understanding of dark web risk mitigation. The identification of overlapping operators and services offers a rare opportunity for targeted disruption, should law enforcement or intelligence agencies choose to act. In an environment where most threat actors operate in fragmented silos, the cohesion observed here marks this group as a significant node in the broader dark web ecosystem.</p><h3>Editorial Note</h3><p>This report was compiled using verified OSINT methodologies and StealthMole’s proprietary dark web intelligence platform. All findings were based on open-source or publicly accessible information available at the time of investigation. At no stage was CSAM content accessed or distributed during this research. The naming conventions of the identified domains are discussed purely in the context of operational behavior and investigative relevance.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=76be3870597a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BlackLock: From El Dorado to a Structured Ransomware Enterprise]]></title>
            <link>https://medium.com/@gagandeep8/blacklock-from-el-dorado-to-a-structured-ransomware-enterprise-ed478bacf599?source=rss-57e0560d27b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed478bacf599</guid>
            <dc:creator><![CDATA[GagandeepB]]></dc:creator>
            <pubDate>Fri, 15 Aug 2025 14:23:57 GMT</pubDate>
            <atom:updated>2025-08-15T14:23:57.478Z</atom:updated>
            <content:encoded><![CDATA[<h3>Overview</h3><p><strong>BlackLock</strong> is the rebranded identity of the ransomware group once known as <strong>El Dorado</strong>, with the change observed in September 2024. This rebranding marked more than just a name change, it came alongside an upgrade in the group’s operations, the launch of a full ransomware-as-a-service (RaaS) platform called <strong>Mamona R.I.P</strong>, and the deployment of a wider network of hidden services to manage their activities.</p><p>Through Mamona R.I.P, BlackLock offers ransomware tools for Windows, Linux, FreeBSD, and ESXi systems to affiliates in exchange for a percentage of the ransom payments. The program comes with clear rules, such as banning attacks on CIS countries, China, non-profits, and critical infrastructure, as well as dedicated control panels and encrypted communication channels for each affiliate. The group uses multiple leak sites, control servers, and chat services, each hosted on separate Tor domains , to keep their infrastructure segmented and reduce the risk of losing all systems if one is compromised.</p><p>In addition to victim-focused operations, BlackLock has engaged in targeting rivals, most notably by leaking data from the Dragon Force ransomware group. This mix of operational discipline, technical capability, and willingness to challenge other cybercriminal actors shows that BlackLock is not only focused on profits but also on maintaining a strong and competitive position in the underground ransomware market.</p><h3>Incident Trigger</h3><p>The renewed attention on BlackLock began with the discovery of a dedicated leak portal on the Tor network:<br>http://datxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.onion/</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5cfIWONkJAN9YSo-CeMQ8w.png" /></figure><p>This portal displayed a combination of leaked system files, including /etc/passwd entries and .env configuration files, as well as chat dumps and imagery bearing BlackLock’s branding. QR codes on the site linked to secure communication channels, reinforcing the group’s reliance on encrypted, invitation-only contact methods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TLiwYeWgn9529Tgc9S7-ww.png" /></figure><p>Using StealthMole’s government monitoring tool, I connected this portal to El Dorado’s prior operations. The analysis also revealed a key alias <strong>“$$$”</strong> active on the RAMP underground forum. This alias became the central pivot in linking multiple pieces of infrastructure, communication channels, and the launch of the Mamona R.I.P affiliate program. The connection between the alias and the rebranded group was reinforced through RAMP postings, domain overlaps, and operational similarities, providing a clear line from El Dorado to BlackLock.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TqBKjKdppMi4KtqgECQgKQ.png" /></figure><h3>Initial Investigation</h3><p>As the investigation progressed, the depth of BlackLock’s infrastructure came into focus. The group’s online presence spans multiple categories of hidden services, including leak portals, affiliate control panels, encrypted chat back-ends, and distinct RaaS program interfaces.</p><p>Among the identified domains were not only the primary leak site but also additional hidden service URLs such as http://zdxxxxxxxxxxxxxxxxxxxxx.onion/ (and its subdirectory /Data_Download/Hxxxxxxxxxg), http://vgxxxxxxxxxxxxxxxxxxxxxx.onion/, panelq**********k****ad.onion, panel***********************.onion and gdxxxxxxxxxxxxxxxxxxxxxx.onion. These sites appear to serve different operational purposes, from storing stolen data to distributing malware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B15n5wD7nZvYT4hQownjrg.png" /></figure><p>BlackLock also operates specialized panel and control servers, including http://paxxxxxxxxxxxxxxxxxxxxxxxx.onion/ and 4oxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.onion. These servers are supported by separate chat infrastructure at domains such as http://paxxxxxxxxxxxxxxxxxxxxx.onion/, illustrating a deliberate segmentation of functions to reduce risk from a single point of compromise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7tJYk39fPTvGo8dqsHi0sQ.png" /></figure><p>The group’s external communication channels complement this internal infrastructure. BlackLock uses multiple Telegram channels, <strong>MamonaRIP</strong>, <strong>BlackLockChanel</strong>, and <strong>BlackLockGlobal, </strong>alongside ProtonMail and TutaMail addresses for contact, including bxxxxxx@cxxxxxx.com, bxxxxxxxxx_me@proton.me, exxxxxxxxxxxxx@tutamail.com, and bxxxxxxxxxxxxx@tutamail.com. A Tox ID (667xxxxxxxxxxxxxxxxxx9C) and session ID artifacts embedded in QR codes further support their encrypted communications framework.</p><h3>Malware Hashes: Critical Technical Discovery</h3><p>The most significant technical breakthrough in the investigation came from StealthMole’s Darkweb Tracker, which flagged a cluster of ransomware payloads tied directly to the onion service:</p><p>http://zdkexsh2e7yihw5uhg5hpsgq3dois2m5je7lzfagij2y6iw5ptl35gyd.onion/</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ezoysS-krodog5eiANI2Hw.png" /></figure><p>From this single node, I was able to extract <strong>five unique SHA-256 hashes</strong> linked to active ransomware campaigns:</p><p>b88c5dde0bd63bdf553babb1815eeb8d75f6752cf6f554e717dd7224cb0a6c0c<br>29d41420ce5ed0f0969efd1658417b43096092f51d4acdff13e0b4f6d445b979<br>c7b91de4b4b10c22f2e3bca1e2603160588fd8f829fd46103cf536b6082e310<br>dee0d2b1d808d36d229a54e2ee6d2b9b88be14b0b6e0df079cc654ab59956d91<br>57f7bfb5b37364563c03ed29228a43e44936edb4ea1f232b6c74c2ecd06cce1d</p><p>The discovery of multiple, distinct ransomware builds originating from the same endpoint is a strong indicator that this node functions as a <strong>multi-payload distribution hub</strong>. Such hubs are commonly seen in mature Ransomware-as-a-Service (RaaS) operations, where central operators provide a pool of deployable payloads to affiliated threat actors.</p><h4>Why This Matters for Intelligence Agencies</h4><p>This finding represents more than just a list of hashes, it offers a <strong>direct technical bridge</strong> between the infrastructure used by BlackLock and the operational tools it deploys. By correlating these hashes with malware samples stored in repositories such as VirusTotal, MalwareBazaar, or private law enforcement databases, agencies can:</p><ul><li><strong>Trace Builder Toolchains:</strong> Identify whether the payloads share unique code fragments, cryptographic routines, or builder fingerprints, linking them to previous ransomware families or known developers.</li><li><strong>Map Affiliate Ecosystems:</strong> Determine which affiliate groups are deploying which payloads, clarifying the division of labor and profit-sharing within BlackLock’s RaaS structure.</li><li><strong>Establish Infrastructure Overlap:</strong> Match C2 endpoints, encryption routines, or obfuscation techniques across unrelated campaigns, potentially unmasking hidden alliances between BlackLock and other ransomware syndicates.</li><li><strong>Enable Targeted Disruption:</strong> Using these hashes, agencies can seed YARA rules, intrusion detection signatures, and endpoint alerts across partner networks, allowing defenders to block the ransomware pre-execution.</li></ul><p>The linkage of a live operational onion domain to confirmed ransomware binaries is rare in open intelligence. It bypasses the usual opacity of Tor-based infrastructure and offers <strong>attribution-grade evidence, </strong>a trail that can be legally actionable in cross-jurisdictional cybercrime cases.</p><h3>The Mamona R.I.P RaaS Model</h3><p>BlackLock’s most significant development post-rebrand is the Mamona R.I.P ransomware-as-a-service program. First advertised on RAMP on March 11, 2025, by the alias <strong>“$$$”</strong>, the program offers affiliates access to lockers for Windows, ESXi, Linux, and FreeBSD systems. The Windows locker, written in C++ with a small build size of roughly 170 KB, supports percentage-based encryption and a “PANIC” mode for chunk-based encryption. It is capable of remote encryption using provided credentials, automatically scans networks to detect domains, and allows extensive customization via its builder including process termination, event log deletion, file extension changes, password protection, self-deletion, and custom ransom notes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WQQhDZ2lwgidHwo93TB52Q.png" /></figure><p>The ESXi variant shuts down virtual machines automatically before encrypting, while the Linux and FreeBSD versions support targeted path encryption and verbose operation modes. All variants integrate with the affiliate’s panel for management.</p><p>The affiliate program itself is structured with an 85/15 revenue split, giving affiliates the larger share while central operators retain a percentage for providing the infrastructure and lockers. Each affiliate receives a unique Tor-based control panel and a separate chat portal, which supports decryptor distribution, payment marking, file management, and authentication settings. Dedicated storage is provided for exfiltrated data, with capacity scaled according to affiliate performance. Inactive accounts are purged after ten days, and affiliates receive regular software updates and access to custom tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ObHUaCKx-8eUTpHYYPZvEw.png" /></figure><p>BlackLock enforces operational rules prohibiting attacks on CIS countries, China, non-profit organizations, and critical infrastructure. These rules are common among ransomware operators seeking to avoid certain geopolitical consequences and to present themselves as having a “code of conduct” within the criminal ecosystem.</p><h3>Activity and Rivalry</h3><p>One notable deviation from typical ransomware group behavior is BlackLock’s targeting of other cybercriminal entities. The group has publicly leaked data belonging to the Dragon Force ransomware group, suggesting an ongoing rivalry or a deliberate strategy to undermine competitors. This inter-group hostility reinforces the perception that BlackLock operates with both technical proficiency and a willingness to challenge peers in the underground economy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSO7y1KrKBHpxNZfd-4J8w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NrttI33jnqoDYRoOWkrC4w.png" /></figure><p>The group’s RAMP activity further underscores its prominence. In addition to the Mamona R.I.P advertisement, the alias <strong>“$$$”</strong> posted an auction for stolen data from cityofpensacola.com. On March 18, 2025, a banned user known as “Rivka” claimed that the Mamona R.I.P panel had been leaked online, potentially exposing sensitive operational information, an allegation that, if true, could represent a rare security breach for the group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7AqGIIio3Wcjvvp23Ostjw.png" /></figure><h3>Timeline of Key Events</h3><p>The earliest documented shift occurred in September 2024, when El Dorado rebranded as BlackLock. Six months later, on March 11, 2025, the group unveiled Mamona R.I.P on RAMP. Just a week later, the “Rivka” post alleged that the RaaS panel had been compromised. By May 27, 2025, new session account IDs were observed in QR code form on their infrastructure, and by July 15, 2025, a snapshot of their RAMP thread captured a complete list of affiliate features. In August 2025, dark web monitoring uncovered additional infrastructure, including onion domains, a public IP address (2.52.75.75), and addresses flagged as malware distribution points.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kZvjt6u6bxUiGZj9kUpv2A.png" /></figure><h3>Analysis</h3><p>BlackLock’s evolution from its previous identity, <strong>El Dorado</strong>, demonstrates a threat actor adapting its methods after prior exposure. The adoption of <strong>split infrastructure, </strong>isolating leak sites, ransomware panels, and communications hubs, appears to be a deliberate move to compartmentalize risk, making full takedown or attribution more challenging.</p><p>Its <strong>Ransomware-as-a-Service (RaaS)</strong> model is notably mature, with defined affiliate rules, a structured revenue-sharing model, and cross-platform locker support. This structure is attractive to a broad range of affiliates, from opportunistic operators to more established cybercriminal crews. The operational guidelines such as avoiding certain geographic regions and critical sectors, align with established practices of other high-profile ransomware syndicates seeking to limit political blowback or community backlash.</p><p>The discovery of <strong>multiple malware panel hashes</strong> tied to BlackLock’s infrastructure provides strong evidence of a <strong>shared backend ecosystem</strong>. This overlap suggests that BlackLock is not just running leak sites but also managing operational malware deployment panels, which form the backbone of their RaaS infrastructure. The repeated reappearance of certain panel addresses across different onion nodes reinforces the hypothesis of centralised management, despite the appearance of decentralisation.</p><p>Their claim that the <strong>RaaS panel was leaked</strong> introduces doubts about their internal security posture. If genuine, such a breach would expose sensitive affiliate data, encryption builder configurations, and potentially victim negotiation logs, an operational security failure that could damage affiliate trust. It could also provide law enforcement and rival groups with actionable intelligence on their operations.</p><p>Furthermore, their documented willingness to <strong>target and leak data from rival ransomware groups</strong>, such as Dragon Force, indicates a more aggressive and confrontational posture than is typical in the ransomware ecosystem. While this can enhance their reputation among certain cybercriminal circles, it also elevates the risk of retaliatory attacks from other high-capability threat actors.</p><p>In sum, BlackLock’s current operational state reflects both sophistication and volatility: a technically capable and well-organised RaaS operation that is simultaneously expanding its capabilities and courting unnecessary conflict, with a backend infrastructure whose security may not be as impenetrable as they would like to project.</p><h3>StealthMole’s Role in Unraveling BlackLock’s Operations</h3><p>The successful mapping of BlackLock’s activities, from its primary operations to its alternate identity as <strong>El Dorado</strong>, and even its targeted attack on rival group Dragon Force, was made possible through the capabilities of <strong>StealthMole’s intelligence platform</strong>.</p><p>By leveraging StealthMole’s <strong>government monitoring tools</strong>, <strong>dark web tracker</strong>, and <strong>TOR infrastructure mapping</strong>, I was able to:</p><ul><li>Identify <strong>cross-branding links</strong> between “BlackLock” and “El Dorado” by pivoting through usernames, Telegram channels, and onion service mirrors.</li><li>Correlate <strong>multiple communication channels</strong> (including ProtonMail, TutaMail, and Cyberfear emails) and their appearances across various darknet marketplaces and leak sites.</li><li>Trace <strong>hidden service relationships</strong> through session IDs, QR codes, and mirrored onion URLs, revealing how BlackLock maintained redundancy in its leak infrastructure.</li><li>Uncover <strong>competitive targeting behavior</strong>, such as the leak of Dragon Force’s data, which might otherwise have been overlooked without network-wide scanning.</li><li>Connect <strong>RAMP marketplace profiles</strong> (such as the “$$$” handle) to associated auctions and ransomware-as-a-service (RaaS) discussions.</li><li>Map <strong>malware panel hashes</strong> and shared onion infrastructure to establish technical links between BlackLock’s leak site, data distribution portals, and control panels.</li></ul><p>StealthMole’s ability to <strong>pivot seamlessly between datasets, </strong>moving from onion URLs to IP metadata, from cryptocurrency transactions to hidden marketplace posts, was crucial in reconstructing the group’s operational footprint. Without these capabilities, the transitions between identities, infrastructure, and affiliations would have remained fragmented and far more difficult to attribute to the same actor.</p><p>This investigation demonstrates that even highly resilient ransomware groups like BlackLock can be systematically dissected when equipped with advanced OSINT tooling and correlation engines like StealthMole. It stands as a case study in how coordinated, data-driven darknet analysis can expose complex threat actors in their entirety.</p><h3>Conclusion</h3><p>BlackLock represents a case study in ransomware adaptation. The group’s rebranding, infrastructure diversification, and formalized affiliate program position it as a significant player in the RaaS market. By blending operational discipline with an aggressive competitive stance, they have carved out a space that is both respected and resented in the cybercriminal ecosystem.</p><p>While their current infrastructure shows deliberate design to avoid single points of failure, the potential compromise of their RaaS panel and their engagement in inter-group conflicts could create vulnerabilities in the long term. Monitoring BlackLock’s onion services, forum activity, and affiliate recruitment will be critical to understanding both their future campaigns and the broader evolution of the ransomware marketplace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed478bacf599" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rise of Southeast Asia’s Cyber Militias: Cambodia vs. Thailand]]></title>
            <link>https://medium.com/@gagandeep8/the-rise-of-southeast-asias-cyber-militias-cambodia-vs-thailand-165c33e22c01?source=rss-57e0560d27b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/165c33e22c01</guid>
            <dc:creator><![CDATA[GagandeepB]]></dc:creator>
            <pubDate>Fri, 15 Aug 2025 14:11:06 GMT</pubDate>
            <atom:updated>2025-08-15T14:11:06.125Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How StealthMole Tracked the Digital Frontlines of a Real-World Conflict</em></p><h3>Executive Summary</h3><p>In late July 2025, what began as a territorial clash between Cambodia and Thailand rapidly evolved into a digital war waged across defaced government websites, Telegram channels, and compromised infrastructure. Within hours of the first border gunfire, an invisible front line emerged, this time, coded in IP addresses, passwords, and political manifestos.</p><p>Hacktivist groups from both nations, along with unexpected regional allies, launched reciprocal attacks that breached sensitive data, disrupted public systems, and exposed a deeper layer of geopolitical tension long simmering beneath the surface. Telegram became the central battlefield for coordination, propaganda, and digital warfare, where screenshots, leaks, and war slogans replaced bullets and official statements.</p><p>But this wasn’t just a string of random defacements or low-level trolling. It was an orchestrated campaign involving dozens of actors, many operating under unified banners, executing strategic digital strikes that coincided with on-the-ground military developments.</p><p>This report follows the escalation from its first spark through the key players, tactics, and targets involved and uncovers what these operations reveal about the future of regional cyber conflicts in Southeast Asia.</p><h3>Incident Trigger and Escalation Timeline</h3><p>The digital escalation between Cambodia and Thailand began in direct response to renewed military clashes along their shared border. On <strong>24 July 2025</strong>, armed confrontations broke out near the <strong>Preah Vihear</strong> and <strong>Ta Muen Thom</strong> temples: two historically contested landmarks that have previously triggered nationalist sentiment and regional tension. Unlike earlier disputes, however, the violence on the ground was immediately mirrored in cyberspace, signaling a new front in Southeast Asian conflict.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*XlQKuqFPyfWQC0rG.jpg" /><figcaption>Temple of Preah Vihear</figcaption></figure><h4>Trigger Event: Border Skirmish</h4><p>The physical confrontation catalyzed what would soon become a widespread and prolonged cyber campaign. Reports of military activity and civilian displacement in Cambodia circulated rapidly, accompanied by digital propaganda framing the hostilities as deliberate aggression by Thailand. Within hours, multiple cyber groups began positioning themselves for retaliation. Hacktivist collectives previously known only within isolated local circles emerged onto a regional stage with clear political motives, structured attack coordination, and ideological messaging.</p><h4>23–24 July 2025: Early Indicators and Mobilization</h4><p>Prior to the main digital offensive, Cambodian actors had already been circulating sentiments of retaliation. By <strong>23 July</strong>, early chatter appeared in dark web channels and Telegram groups affiliated with Cambodian-aligned hackers. While it remains unclear whether these groups had prior knowledge of the military flare-up, their readiness to respond was immediate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*21FY4Na_3EDk4erI9AD6ag.png" /></figure><p>On <strong>24 July</strong>, the Telegram channel <strong>“Thai is God”</strong> was created: an event now seen as the unofficial starting point of Thailand’s cyber response network. It marked a shift from ad hoc, individual retaliations to a more structured nationalist campaign.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6v9wTQb9wzMZiN6WvM36xw.png" /><figcaption>Thai is God Telegram Channel</figcaption></figure><h4>25–27 July 2025: Cyberattacks Begin in Tandem with Military Conflict</h4><p>By <strong>25 July</strong>, Cambodia-based groups such as <strong>NXBBSEC</strong>, <strong>H3C4KEDZ</strong>, and <strong>K0LzSec</strong> were actively defacing Thai government websites and leaking credentials obtained from prior breaches. One of the first publicly identified Thai assets in this wave of cyberattacks was the website <strong>kohsriboya.go.th</strong>, which was discovered during dark web monitoring on StealthMole. The attackers used the defacement to reference alleged Thai military aggression and issued calls for the “digital defense of the Khmer people.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9pKKCE3QIxN9IKohFynIEQ.png" /></figure><p>In parallel, <strong>KH Nightmare</strong>, a major pro-Thai group, emerged with a direct counteroffensive. By scanning Telegram activity, open-source intelligence, and paste site dumps, KH Nightmare began doxxing Cambodian hackers, leaking their personal information, and publishing active credentials. A now-deleted post on <strong>https://k*******s.*h</strong> titled “Leaks Hacker” contained data on several Cambodian-affiliated attackers, including usernames, real photos, compromised email-password pairs, and partial IP address logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g2TH-wlMRBheYHBQJjmfxA.png" /></figure><p>Thai hacktivist groups like <strong>T.R.A.N.C.E</strong>, <strong>BlackEye-Thai</strong>, and <strong>Black Iron</strong> soon joined the retaliation effort. The attack momentum quickly expanded to include not only known Cambodian systems but also third-party platforms tied to Cambodian governance, such as <strong>ASEAN’s AWGATE portal</strong>, which was later defaced by H3C4KEDZ.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1QsauCbUfLNLnD0PkqpeLQ.png" /></figure><h4>28–31 July 2025: Transnational Alliances and Intensification</h4><p>A defining shift in the nature of the campaign occurred toward the end of July, as the cyber battle moved beyond national boundaries. On <strong>31 July</strong>, the group <strong>Keymous+</strong> declared a formal alliance with <strong>Thai is God</strong>. This indicated the first confirmed transnational collaboration, suggesting the conflict was no longer limited to domestic cyber militias but was drawing support from regional actors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAoUJzBnAzdMLwrrYOU7-A.png" /></figure><p>Evidence from open Telegram channels showed that <strong>Anonymous SRVN</strong>, a Vietnamese group, was actively supporting Thailand’s campaign. The group claimed responsibility for hacking the <strong>Institute of Technology of Cambodia (adm.itc.edu.kh)</strong> and released screenshots of internal dashboards and admin credentials.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/928/1*RpMBvR3kA2z9d2pU6VgZjA.png" /></figure><p>By this stage, Cambodian groups were also consolidating their networks. Channels associated with <strong>BL4CK CYB3R</strong>, <strong>KHMERGHOST</strong>, and <strong>NULLSEC PH</strong> joined NXBBSEC and K0LzSec in their operations. Coordinated messaging began appearing across these platforms, framing Thailand as an aggressor and issuing calls for continuous digital retaliation using hashtags like #OpThailand and #ThailandStartedTheWar.</p><h4>Early August 2025: Tactical Shifts and Psychological Warfare</h4><p>By early <strong>August 2025</strong>, the campaign shifted tactics. Rather than focusing solely on defacements and data dumps, groups began engaging in psychological operations through their Telegram channels. <strong>NXBBSEC</strong> posted taunting messages and “RIP” threats directed at Thai counterparts, while <strong>KH Nightmare</strong> began monitoring and exposing the Telegram channels of Cambodian-affiliated hackers in a clear attempt to shame, intimidate, and destabilize their opponents publicly. These posts marked a shift from technical disruption to narrative warfare using social pressure and exposure as weapons.</p><p>New accounts and channels rapidly emerged, often disappearing within days, making attribution more difficult. However, by analyzing naming patterns, overlapping admin accounts, and leaked credentials, links could still be drawn between older groups and newly formed fronts.</p><h4><strong>Summary of Tactical Escalation:</strong></h4><p>| — — — — — — — —<strong>Date</strong> — — — — — — — |—— — — —— — <strong>Event — — — — — — — — </strong>|<br>— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — <br><strong>23 July 2025: </strong>Early leak threats appear in Cambodian-aligned channels<br><strong>24 July 2025: </strong>Border clash erupts; “<strong>Thai is God</strong>” Telegram channel created<br><strong>25–27 July 2025: </strong>First wave of cyberattacks from both sides<br><strong>28–31 July 2025: </strong>Alliances formed, regional actors join conflict<br><strong>Early August 2025: </strong>Psychological ops, strategic leaks, intense propaganda — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —</p><h3>Actors and Alliances</h3><p>As military hostilities ignited along the Cambodia–Thailand border, a parallel escalation unfolded across the digital front. What initially appeared to be spontaneous cyberattacks evolved into a structured campaign with command hubs, information warfare tactics, and rival networks. The investigation using StealthMole revealed a well-defined operational architecture. Two actors emerged as the undisputed leaders of their respective sides: <strong>NXBBSEC</strong> representing Cambodia, and <strong>KH Nightmare</strong> spearheading the Thai retaliation.</p><h4>Cambodian Cyber Front: NXBBSEC’s Central Role</h4><p>NXBBSEC was not only the most prolific group on the Cambodian side, but also the most structured. It operated as the primary dissemination point for leaks, attack announcements, defacements, and cross-group coordination. StealthMole’s analysis of Telegram behavior, IP mentions, and credential dumps confirms that this group is responsible for defacing or compromising over <strong>52 Thai government and military-affiliated digital assets</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l6HDZOoGxFcGazoI_Ks0Hw.png" /></figure><p>NXBBSEC’s Telegram channel (t.me/N********1) functioned as a battlefield command post, publishing access logs, defacement screenshots, government databases, and even instructions to Cambodian followers to support the cyber offensive. The channel also hosted symbolic posts such as RIP messages targeting Thai hackers, psychological messaging intended to demoralize Thai-aligned groups.</p><p>Unlike loosely tied hacktivist collectives, NXBBSEC demonstrated sustained operational control. Through StealthMole’s passive data correlation, their account infrastructure was found to intersect with other known Cambodian clusters, including <strong>Dark Storm Team</strong>, <strong>K0LzSec</strong>, and <strong>KHMERGHOST</strong>. These groups frequently mirrored or reposted NXBBSEC’s materials, underscoring their leadership status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*3mqDNtUQGMRa2proHqYfmw.png" /></figure><p>NXBBSEC also broadcast IP addresses of claimed targets and showcased operational confidence by taunting specific Thai actors directly. Their communications suggested both technical sophistication and a clear intent to frame the conflict as a digital war of sovereignty.</p><h4>Thai Response Led by KH Nightmare</h4><p>On the Thai side, KH Nightmare took the lead in retaliatory cyber operations. This group moved beyond the typical deface-and-dump model to implement an identity-based warfare approach. Using tactics uncovered through StealthMole’s Telegram tracker and dark web intelligence, KH Nightmare specialized in exposing the real-world identities of Cambodian actors.</p><p>One of their most prominent operations included the publication of personal photos, email credentials, and Telegram metadata tied to members of NXBBSEC, Independent Hacker and H3C4KEDZ. These were released through channels such as t.me/K*********e and mirrored via external leak sites like k*****s.*h. Their strategy introduced reputational risk into the cyber battlefield, shifting the conflict into the psychological and social domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rH-AGY6INQosgO6QPpsVBg.png" /></figure><p>KH Nightmare also maintained a running tally of Cambodian assets breached, at last count, <strong>89 government and military platforms</strong> had been compromised by their efforts. Their activity often targeted the digital underpinnings of Cambodian infrastructure: provincial administration sites, state-linked educational networks, and intra-governmental portals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Mq2JOQA5C5H6ftx7xvWrtA.png" /></figure><p>StealthMole’s tracking tools revealed that KH Nightmare not only led breaches but also engaged in active surveillance of Cambodian hacker channels, including NXBBSEC and H3C4KED. They would publicly monitor enemy Telegram channels, document affiliations, and occasionally issue warnings in Khmer-language posts, suggesting fluency in regional cyber-warfare dynamics.</p><h4>Doxxing Retaliation: Cambodian Hacker Profiles Leaked by KH Nightmare</h4><p>As a major component of Thailand’s cyber retaliation strategy, the threat actor <strong>KH Nightmare</strong> launched a sustained doxxing operation that publicly exposed the identities of key Cambodian hackers involved in the cross-border cyber conflict. StealthMole’s dataset and tracking tools helped trace, verify, and expand on these leaks, confirming the scope of compromise and revealing how reused credentials linked these actors across platforms and breaches.</p><h4>1. H3C4KEDZ</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jbAOZIjqB8p1YA_9YV4o5w.png" /><figcaption>Reported Photograph of H3C4KEDZ</figcaption></figure><p><strong>Real Name:</strong> <strong><em>B*****y T***n</em></strong><em> <br></em><strong>Affiliation:</strong> <em>AnonSecKH collective</em><br><strong>Leaked Email:</strong> <em>de**********@gmail.com</em><br><strong>Personal Tik Tok Profile: </strong><em>B******y_n*******k</em><br><strong>Personal Telegram Account:</strong> <em>B*****_*******l<br></em><strong>Telegram Handles:</strong></p><ul><li>@h******z</li><li>@H***Z_***A_S*****T</li><li>@*e_H********1</li><li>@h*******0</li><li>@H*******Z_**C</li></ul><p><strong>Leaked Artifacts:</strong></p><ul><li><strong>Photograph</strong> (face clearly visible)</li><li>Active participation in propaganda and operational content posted via multiple TG channels</li><li>Seen claiming responsibility for hacks on Thai government domains</li><li>Dox linked H3C4KEDZ to the larger AnonSecKH cluster</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jsj2KP1EK427DagTBHbweQ.png" /></figure><h4>2. NXBBSEC</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Frqt6qTmWfa6GL1aw6rXxw.png" /><figcaption>Reported Photograph of NXBBSEC</figcaption></figure><p><strong>Real Name:</strong> <strong><em>K*** V****l</em><br>Affiliation:</strong> <em>Senior operator in AnonSecKH</em><br><strong>Telegram Handle:</strong> <em>@N*******1</em><br><strong>Leaked Email Address:</strong> <em>K**************1@gmail.com</em><br><strong>Portfolio:</strong><em> https://www.yo*****e.com/project/f******z</em><br><strong>Facebook:</strong> <em>https://www.facebook.com/****.v****a</em><br><strong>Tik Tok: <em>*********</em></strong><em>a</em><br><strong>Personal Telegram Handle:</strong> <em>*********a</em><br><strong>Credential Breach (via StealthMole):</strong></p><ul><li>Source: <a href="https://uddompanglearning.com/signin"><em>https://uddompanglearning.com/signin</em></a></li><li>Leak Date: August 2024</li></ul><p>Credentials:</p><ul><li><strong>Email:</strong> <em>K************1@gmail.com</em></li><li><strong>Password:</strong> <em>v*******4</em></li><li><strong>Computer Username:</strong> <em>V***L-PC\V***L</em></li><li><strong>IP Address:</strong> 1**.7*.**8.**</li></ul><p><strong>Further Exposure:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ixrWJyP00P1XyxZlDpxagQ.png" /></figure><p>Running the leaked IP and email in StealthMole revealed —</p><ul><li><strong>137 leaked password records</strong> linked to reused credentials</li><li>Several of those tied to subdomains of Thai infrastructure</li><li><strong>7 additional IPs</strong> were found via posts in the NXBBSEC Telegram channel, some possibly used for hosting dumps, defacements, or command and control</li><li>Leaked <strong>masked profile image</strong> matched the TG handle</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XBEae1YuIW9bPpsVFvYVFw.png" /></figure><h3>3. Independent Hacker</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hxo5pCpAD16EcE-RHPCRsg.png" /></figure><p><strong>Real Name:</strong> <strong><em>R*** **n<br></em>Affiliation:</strong> <em>Unconfirmed, but Cambodian-aligned; grouped with AnonSecKH<br></em><strong>Leaked Email Address:</strong> <em>br**********8@gmail.com<br></em><strong>Tik Tok: </strong><em>an*****1<br></em><strong>Personal Telegram:<em> </em></strong><em>r************1<br></em><strong>Group Telegram: </strong>No direct channel discovered but referenced in opposing groups’ leaks<br><strong>GitHub:</strong> <em>https://github.com/a******1/AnonKH-D****S<br></em><strong>Portfolio:</strong> https://r***********o.pages.dev/<br><strong>Facebook:</strong> <em>https://www.facebook.com/**n.a**********h.1<br></em><strong>YouTube: </strong><em>https://www.youtube.com/@a********1</em><br><strong>Leaked Artifacts:</strong></p><ul><li><strong>Photograph</strong> exposed</li><li><strong>Hash string leaked:</strong><br>81*******************************************************d</li><li>Name and email not previously indexed in major OSINT or breach platforms. This exposure likely represents first-party doxxing by KH Nightmare</li><li>No credential reuse confirmed through this email so far</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zuPmOTiXe4aK04O7amAAxA.png" /></figure><p>These cases represent how deep the conflict’s personal cost has become, transforming threat actors from anonymous usernames into exposed individuals with traceable digital footprints. What once was pseudonymous participation in cyber warfare has now turned into lasting personal exposure. Real names, operational aliases, emails, and even photographs have emerged in the open, often without the actors realizing how deeply their digital hygiene has been compromised. This is not just about tactical wins; it’s psychological warfare through identity dismantling.</p><p>Crucially, many of these leaks, especially in the case of NXBBSEC, originated from now-defunct infrastructure. The website created by KH Nightmare to release AnonSec hackers data is no longer accessible. However, <strong>StealthMole’s ability to index and preserve historical breach data </strong>allowed me to uncover and verify the leak even after the source had disappeared from the surface. This capability to recover long-deleted breach artifacts proved instrumental in tracing reused credentials, exposed IPs, and password patterns, painting a more complete and verifiable picture of these actors’ operational behavior and failures.</p><h4>Expanded Network Dynamics</h4><p>While NXBBSEC and KH Nightmare formed the operational cores on their respective sides, a host of auxiliary actors played critical roles in amplifying the cyber campaign. These supporting groups were not mere followers, they carried out targeted attacks, signal-boosted strategic leaks, and sustained information warfare across dozens of Telegram channels and underground forums.</p><p>On the Cambodian side, <strong>H3C4KEDZ</strong> operated as the most visible supporting actor. Though not as technically coordinated as NXBBSEC, it maintained multiple Telegram channels such as @h*******z, @H********Z_D***A_S******T, and @H*******Z_SEC, focused on content distribution, branding, and identity reinforcement. H3C4KEDZ specialized in government defacements and data leaks, some of which targeted ASEAN digital infrastructure, as observed in their breach of the ASEAN Working Group on Agricultural Training &amp; Extension (AWGATE) and ASEAN Learning Center.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*PMl8iVME2X49f9Tz1nSBkg.png" /></figure><p>Groups like <strong>NullSec </strong>and<strong> K0LzSec </strong>acted as parallel disruptors. Although operating in separate lanes, these collectives frequently referenced or rehosted materials originally published by NXBBSEC, suggesting decentralized yet ideologically aligned operations. Through StealthMole’s compromised data sets and Telegram tracker, multiple cross-posting patterns and recycled credential leaks were traced back to these groups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*Zt23bPOR_1ozP1ksfEU4tQ.png" /></figure><p>KHMERGHOST, in particular, showed an emphasis on psychological and symbolic attacks, focusing on public-facing domains tied to Thai provincial and local administrations. Dark Storm Team, meanwhile, demonstrated early-stage coordination through joint declarations and digital posters aligning with Cambodian military rhetoric.</p><p>On the Thai side, <strong>Thai Is God</strong> (@t**********t), <strong>BlackEye‑Thai</strong>, <strong>T.R.A.N.C.E</strong>, and <strong>Black Iron</strong> functioned as specialized attack cells. Thai Is God focused on narrative warfare, often announcing breaches with strong political messaging. BlackEye‑Thai and Black Iron carried out technically sophisticated domain takeovers and database wipes. <strong>T.R.A.N.C.E</strong>, while less publicly visible, was linked through shared Telegram engagement and appeared to operate as a support unit for infrastructure disruption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bbl1Tb5_WJ_moBGTul4pSg.png" /></figure><p>Regional and international actors also stepped in. Vietnamese-affiliated collective <strong>Anonymous SRVN</strong> launched its own breach campaigns against Cambodian platforms. Although not formally integrated into the Thai network, their actions were synchronized in timing and theme. Likewise, <strong>Keymous+</strong>, an independent offensive unit, declared open alliance with Thai groups and participated in symbolic propaganda drops.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ka6snEijlTjwTMcWhztMjQ.png" /></figure><p>What’s clear from the evidence surfaced via StealthMole’s multi-dimensional intelligence framework is that while the campaign lacked formal command structures, the digital alliances on both sides operated with surprising synchronization built on Telegram activity, shared targets, and mirrored propaganda strategies. These weren’t isolated cyber incidents. They were coordinated acts of digital alignment under the shadow of a regional military conflict.</p><h3>Attack Vectors and Infrastructure</h3><p>While public attention often centers on defaced websites and dumped credentials, the real architecture behind this cyber conflict was far more layered. The campaigns waged between Cambodian and Thai actors revealed a sophisticated deployment of overlapping tactics, toolsets, and digital infrastructure. By examining the attack chains, hosting platforms, breach behavior, and Telegram orchestration, exclusively through StealthMole’s deep visibility into threat surfaces, we can decode how these operations sustained themselves at scale.</p><h4>Early-Stage Breaches: Defacements and Cred Harvesting</h4><p>By 25 July, Cambodian groups had initiated full-scale defacement campaigns against Thai government websites. The breach of <a href="https://www.kohsriboya.go.th/">kohsriboya.go.th</a> marked one of the earliest publicly visible intrusions. NXBBSEC and H3C4KEDZ uploaded deface banners calling for retaliation against Thai military actions and shared slogans invoking “digital war” and Khmer nationalism. These defacements weren’t just symbolic; several were accompanied by dumps of admin credentials, some of which, upon review through StealthMole’s compromised data archive, had been circulating in underground forums since early 2024.</p><p>NXBBSEC alone claimed responsibility for breaching <strong>52 distinct Thai domains</strong>, primarily government portals, local law enforcement systems, municipal databases, and public utility dashboards. In many cases, credentials were extracted using SQL injection, basic misconfigurations, or credential stuffing against reused passwords from older breach data, tactics confirmed through matching IPs and hash strings surfaced in StealthMole’s tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K4TkL_zO62Q3AlC07YM5vQ.png" /></figure><p>Thai groups soon retaliated. By tracing parallel leaks through their Telegram channels, it became evident that KH Nightmare and allies executed breaches of <strong>89 Cambodian domains</strong>, including ministry-level sites, provincial educational boards, and digital admin systems. KH Nightmare’s tactics were more attributional, they did not just leak databases but linked data dumps with identity doxxing of opposing hackers, revealing personal emails, Telegram handles, and even masked photos. These leaks were often staged across multiple platforms for maximum pressure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjgBhux_eb4i0SQPMJqdEg.png" /></figure><h4>Deepening the Conflict: Telegram as Operational HQ</h4><p>Telegram wasn’t just a broadcast tool, it was the central nervous system of both campaigns. Through StealthMole’s Telegram tracker, more than a dozen active channels tied to this conflict were identified. Each functioned as a command node, data drop site, or morale-boosting echo chamber.</p><p>Key Cambodian channels included:</p><ul><li><strong>@N******01</strong> (Primary channel for breach claims, dumps, and targeting lists)</li><li><strong>@h*******z</strong> and its variants (used for narrative branding and coordinated threats)</li><li><strong>@N*********T</strong>, hosting group chatter and cross-affiliate banter</li><li><strong>@R**********s</strong>, a lesser-known presence spotted participating in NXBBSEC threads</li></ul><p>On the Thai side:</p><ul><li><strong>@K********e</strong> (central hub for Cambodian leaks and targeting)</li><li><strong>@t***********t</strong>, launched on 24 July 2025, appears purpose-built for wartime activity</li><li><strong>BlackEye‑Thai</strong> and <strong>T.R.A.N.C.E</strong> affiliated channels, which distributed breach confirmations and hosted victim screenshots</li></ul><p>The campaign was marked by timing precision, defacements would often be followed within hours by dump announcements, identity exposure, or IP mapping. This coordination was not improvised. StealthMole’s data cross-matching revealed identical IP logs and infrastructure strings across multiple Cambodian group leaks, suggesting shared tools, access brokers, or cloned backdoors.</p><h4>Leaked Credentials, IPs, and Infrastructure Ties</h4><p>Among the most critical technical finds were the compromised data trails tied to individual threat actors. One such case involved Cambodian actor <strong>NXBBSEC</strong>, whose operational email address (<strong>K**********1@gmail.com</strong>) was initially exposed through <strong>KH Nightmare’s leaks</strong>. When this email was run through StealthMole’s compromised data sets, it was found to have already been exposed in a breach tied to <strong>uddompanglearning.com</strong>, with metadata dating back to <strong>August 2024</strong>. Further analysis revealed that the actor had reused this credential set extensively, leading to over <strong>137 leaked password records</strong>, some tied to Thai-facing platforms, and interestingly, a subdomain associated with <strong>Punjab.gov</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyBcLfEXgIaCnemhEBYMrg.png" /></figure><p>A post shared in NXBBSEC’s own Telegram channel revealed <strong>seven public IP addresses</strong>, likely associated with <strong>remote command-and-control servers</strong> or <strong>leak file hosting</strong>. Matching file hashes between leaks published by NXBBSEC, <strong>H3C4KEDZ</strong>, and <strong>K0LzSec</strong> suggested infrastructure overlap or lateral coordination across Cambodian-affiliated groups.</p><p>On the Thai side, StealthMole traced a series of newly surfaced Cambodian platform breaches, many of which were accompanied by <strong>unique hashes</strong>, <strong>deface confirmations</strong>, and <strong>administrative access logs, </strong>directly back to KH Nightmare’s infrastructure. Notably, many of the affected domains were <strong>not indexed</strong> in existing commercial breach aggregators, reinforcing that the data originated from <strong>first-party access</strong> and not from recycled leak archives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LKA8Y41tq_1Cn7YJiMA8dw.png" /></figure><h3>Impact Assessment</h3><p>The scale and sophistication of the Cambodia–Thailand cyber skirmish in July–August 2025 left measurable damage across both digital and institutional landscapes. While both nations sustained hits, the <strong>impact was asymmetrical, </strong>with Cambodia facing heavier breaches across critical infrastructure and Thailand experiencing broader digital retaliation in terms of threat actor volume and defacement incidents.</p><h4>Government Targets and Institutional Disruption</h4><p>A key operational priority for both camps was targeting <strong>government and military-linked websites</strong>. Cambodian group <strong>NXBBSEC</strong> alone claimed the defacement and/or breach of <strong>52 Thai government and military agency websites</strong>, with leaked data spanning admin credentials, deface messages, and public service email leaks. These included municipal systems, education portals, and subdomains of national ministries.</p><p>On the Thai side, <strong>KH Nightmare</strong> led retaliatory operations, publicly claiming the compromise of <strong>89 Cambodian government and defense-related domains</strong>. Unlike Cambodian actors who often favored symbolic defacements, KH Nightmare’s tactics focused on identity exposure, including Telegram doxxing campaigns, leaked email-password pairs, and infrastructure mapping. In several instances, sensitive internal documents were dumped to publicly accessible file-sharing platforms.</p><p>Notably, Cambodian actors <strong>NXBBSEC</strong> and <strong>H3C4KEDZ</strong> also released additional datasets from Thai institutional logins, with supporting indicators like database schema screenshots, user tables, and admin control panels. In contrast, KH Nightmare demonstrated a wider range of offensive cyber tactics, including hash cracking and public dissemination of hacker identities.</p><h4>Sector-Wide Ramifications in Thailand</h4><p>Thailand’s digital infrastructure endured at least <strong>438 unique cyber incidents</strong> during the peak escalation window. StealthMole revealed waves of DDoS activity, defacements, and unauthorized CMS access. Government portals saw temporary outages, and public-facing domains were replaced with political messaging and offensive imagery.</p><p>The symbolic breach of ASEAN Working Group on Agricultural Training &amp; Extension (AWGATE), which represents both Cambodian and Thai stakeholders, highlighted the campaign’s regional implications and drew attention to vulnerabilities in intergovernmental collaboration platforms.</p><p>As a direct result, Thailand initiated several reactive steps:</p><ul><li>Accelerated <strong>cybersecurity audits</strong> across its digital government services</li><li>Issued <strong>public advisories</strong> warning of phishing campaigns tied to breached state domains</li><li>Launched <strong>arrest operations</strong> targeting suspected domestic sympathizers or actors behind pro-Cambodian defacements</li><li>Urged <strong>international coordination</strong> via ASEAN and Interpol to identify and track cross-border cybercriminals</li></ul><h4>The Cambodian Front: Heavier Breaches, Limited Response</h4><p>Cambodia’s situation was arguably more severe. The breaches it suffered coincided with internal political tension, <strong>military mobilization</strong>, and regional displacement events near the Preah Vihear border. At least <strong>20 hacker groups</strong> are believed to have launched offensive campaigns against Cambodian institutions, and internal chatter from Cambodian groups like Dark Storm Team and K0LzSec suggested that defenses were stretched thin.</p><p>Key leaks included:</p><ul><li>Ministry and provincial government email dumps</li><li>Leaked credentials from judicial, health, and transport agencies</li><li>Telegram posts exposing back-end access to Cambodian databases</li></ul><p>In response, Cambodian authorities began a <strong>cybercrime crackdown</strong>, reportedly detaining low-level actors and moving to restrict access to international Telegram channels. However, with core groups like NXBBSEC operating openly from multiple channels and rallying public support, the crackdown did little to stem the flow of leaks.</p><h3>Conclusion and Strategic Implications</h3><p>The Cambodia–Thailand cyber conflict of July–August 2025 represents one of the most coordinated and ideologically charged digital escalations in Southeast Asia’s recent history. What began as reciprocal defacements between fringe actors rapidly matured into an asymmetric cyber campaign, with each side drawing on a diverse ecosystem of nationalistic hacker groups, open-source leak platforms, and Telegram-based propaganda channels.</p><p>This confrontation was not just about state infrastructure; it was a war for digital legitimacy. Thai-aligned groups like <strong>KH Nightmare</strong>, <strong>Thai Is God</strong>, and <strong>BlackEye-Thai</strong> turned to doxxing and identity warfare, outing rival hackers, leaking Telegram links, and exposing personal infrastructure. Cambodian groups, led by <strong>NXBBSEC</strong>, <strong>H3C4KEDZ</strong>, and others, focused heavily on symbolic attacks, wide-scope credential leaks, and narrative-building through consistent use of terms like <em>“Digital Defense of Khmer People.”</em></p><p>Despite having fewer attacking groups, Cambodia endured more consequential breaches, losing control over government portals, personal data, and internal networks at a time of military tension and political sensitivity. In contrast, Thailand’s digital exposure was broader but more recoverable, supported by a stronger internal cybersecurity posture and better incident containment.</p><p>This campaign also exposed the <strong>operational maturity of non-state actors</strong>, the speed at which online coalitions can form, and the ongoing shift in regional cyberwarfare from traditional APT-style intrusions to fast-moving, ideologically driven conflicts powered by Telegram, darkweb data, and pre-existing leak intelligence.</p><p>Crucially, it also demonstrated how <strong>proactive cyber intelligence capabilities,</strong> especially those that integrate darkweb tracking, Telegram monitoring, infrastructure mapping, and credential leak correlation, are essential not just for after-action reports, but for real-time attribution, exposure mitigation, and strategic defense. The ability to uncover actors, trace their operations, and contextualize them with infrastructure-level evidence proved central to understanding this digital war in its full scope.</p><p>As the dust settles, the Cambodia–Thailand cyberwar leaves behind a warning: in an era where border clashes can trigger digital avalanches overnight, no military escalation will remain isolated from its cyber shadow.</p><h3>Update: Emergence of the AnonSecKH Coalition</h3><p>Following the initial publication of this investigation, new intelligence surfaced pointing to a more coordinated Cambodian cyber apparatus than previously understood. A dedicated Telegram folder titled <strong>AnonSecKH</strong> has been identified, grouping together five key threat actors: <strong>NXBBSEC</strong>, <strong>K0LzSec</strong>, <strong>BL4CK CYB3R</strong>, <strong>H3C4KEDZ</strong>, and <strong>NRSTSEC</strong>. These groups have been publicly promoting their alliance, using shared infrastructure, mutual promotion, and synchronized channel activity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*1R8vnY43b-Q5TJ1jJm8EMw.png" /></figure><p>While each group has carried out its own attacks and dumps, internal Telegram polls and shared administrative control suggest that <strong>NXBBSEC</strong> is acting as primary leader within this coalition. The visibility of NXBBSEC in leading AnonSecKH communications, combined with its extensive follower count, reinforces this assumption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5thTXqagW-r7Edj16JFobg.png" /></figure><p>This update significantly reframes the understanding of Cambodia’s cyber response. What once appeared to be a loosely aligned set of independent actors now reflects <strong>a semi-organized digital front</strong>. AnonSecKH represents not only a tactical consolidation of Cambodian offensive groups but also an escalation in how cyberspace is being used as a unified resistance theater.</p><h3>Editorial Note</h3><p>This report was developed as part of StealthMole’s OSINT Calling Program 2, with the goal of showcasing how real-time intelligence gathering, infrastructure tracing, and actor profiling can transform fragmented threat signals into a cohesive narrative. Every piece of data used in this investigation, from Telegram messages and defacement logs to credential leaks and compromised infrastructure, was uncovered, validated, and analyzed using StealthMole’s darkweb, Telegram trackers and other intelligence tools. The report reflects an independent, investigator-led effort to demonstrate the power of structured open-source intelligence when applied at scale during rapidly unfolding cyber conflicts.</p><p>The Cambodia–Thailand cyberwar case is ongoing, with new Telegram channels, affiliations, and leaks emerging even as this report neared completion. The findings here serve both as a snapshot of a historic regional cyber confrontation and a blueprint for OSINT-driven attribution in complex multi-actor environments. As digital hostilities become increasingly intertwined with geopolitical events, the ability to track, contextualize, and map threat actor behavior in real time will define the next generation of cyber intelligence operations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=165c33e22c01" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSINT Intelligence Report: Threat Actor — DigitalGhost]]></title>
            <link>https://medium.com/@gagandeep8/osint-intelligence-report-threat-actor-digitalghost-4d312835a5fc?source=rss-57e0560d27b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d312835a5fc</guid>
            <dc:creator><![CDATA[GagandeepB]]></dc:creator>
            <pubDate>Thu, 24 Jul 2025 06:55:46 GMT</pubDate>
            <atom:updated>2025-07-24T06:55:46.555Z</atom:updated>
            <content:encoded><![CDATA[<h3>OSINT Intelligence Report: Threat Actor — DigitalGhost</h3><h3>Case Title: Breach of Polri.GO.ID &amp; DigitalGhost Network Mapping</h3><p><strong>Date of Report</strong>: 24 July 2025<br><strong>Reported by</strong>: OSINT Analyst, StealthMole OSINT Program 1<br><strong>Case Type</strong>: Threat Actor Profiling / Government Cyberattack / Network Tracing<br><strong>Tools Used</strong>: StealthMole Platform (Telegram Tracker, Web Tracker, Dark Web Monitoring), Manual Monitoring, Open-Source Recon</p><h3>Executive Summary</h3><p>On <strong>14 July 2025</strong>, the Indonesian government website <strong>Polri.GO.ID, </strong>official portal of the <strong>Indonesian National Police</strong> , was compromised by a threat actor using the alias <strong>DigitalGhost</strong>. What began as a site defacement led to a larger uncovering of DigitalGhost’s network across Telegram, dark web forums, and public platforms like Instagram and X (Twitter).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/1*nGvnYc3OLudUj8GcI7iTsw.png" /></figure><p>The investigation connected DigitalGhost to multiple crypto wallets, TOX ID, and dark web infrastructure. Notably, <strong>impersonation tactics</strong> were employed, using the identity of a Russian woman to mislead followers and disguise their true origin. There is also a <strong>confirmed link to the Indonesian hacker group Xsvshacker</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ANooM9bsfMjpM3iJqMrREA.png" /></figure><h3>Background and Context</h3><h4>Government Website Compromise</h4><p>The compromise of Polri.GO.ID was not an isolated defacement. Rather, it was part of a chain of activities involving information leaks, dark web postings, and a digital identity engineered for deception.</p><h3>Investigation Timeline</h3><p>The investigation into DigitalGhost began on <strong>14 July 2025</strong>, when the Indonesian National Police’s official domain, <strong>Polri.GO.ID</strong>, was compromised. The attack, which included a public defacement and potential document leaks, was promptly claimed by a Telegram user under the alias <strong>DigitalGhost</strong>. Their messages on Telegram indicated a targeted, intentional strike against the Indonesian government.</p><p>On <strong>15 and 16 July</strong>, using StealthMole’s Telegram tracking tools, a network of related channels was uncovered. These included aliases such as <strong>@op</strong>******, <strong>@di</strong>*********,** and <strong>@cy</strong>*********,** which were all actively disseminating propaganda, breach evidence, and further linking to other forums and social media profiles.</p><p>By <strong>17 July</strong>, hash values, cryptocurrency wallet addresses, and dark web identifiers connected to DigitalGhost began surfacing in chatter on both Telegram and underground forums. This was the first sign that the actor was embedding themselves deeper in the cybercrime economy beyond just hacktivism.</p><p>The following day, on <strong>18 July</strong>, investigators traced one of the Telegram handles to a <strong>linked Instagram account</strong> and a <strong>TOR site</strong> that appeared to host additional content and contact details. The same Telegram account also revealed a <strong>TOX ID</strong>, further confirming a layered infrastructure built for anonymity and persistence.</p><p>Between <strong>19 and 21 July</strong>, a notable shift occurred in the investigation. Through manual content analysis, it became evident that DigitalGhost was using <strong>photos and videos of a Russian woman</strong> to craft a fake persona — likely for deception and trust-building. This raised red flags about possible <strong>identity theft</strong> or <strong>AI-enhanced disinformation tactics</strong>.</p><p>On <strong>22 July</strong>, deeper OSINT cross-referencing revealed potential links between DigitalGhost and the <strong>Indonesian hacker group Xsvshacker</strong>. This included shared Telegram group moderators, overlapping themes in visual content, and indications of tool or audience sharing.</p><p>Finally, by <strong>23 July</strong>, the investigative team completed a full consolidation of DigitalGhost’s infrastructure including masked social media profiles, forums, wallet addresses, impersonation content, and inter-group connections, confirming the actor as part of a <strong>multi-platform threat network</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6VAgJCDmKLCQgtTqYFtSIQ.png" /></figure><h3>Threat Actor Profile: DigitalGhost</h3><p><strong>Alias: </strong>DigitalGhost</p><p><strong>Type: </strong>Hacktivist / Cybercriminal</p><p><strong>Affiliation: </strong>Linked to <strong>Xsvshacker</strong> (Indonesia)</p><p><strong>Persona: </strong>Impersonating a Russian woman</p><p><strong>Goal: </strong>Disruption, extortion, social engineering</p><p><strong>Communication: </strong>Telegram, Dark Web, TOX</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3O4dF3eOvawHXPZm5_TqJw.png" /></figure><h3>Indicators of Compromise (IOCs): Masked for Security</h3><h4>Telegram Channels</h4><ul><li>t.me/op******</li><li>t.me/di*********</li><li>t.me/+O32sZ-*********** <em>(Main group)</em></li><li>t.me/cy*********</li></ul><h4>Dark Web Presence</h4><ul><li>DarkForums Profile: darkforums.st/User-D*********</li><li>TOR URL: <a href="http://uvzn5xa***********.onion/">http://uvzn5xa***********.onion</a></li></ul><h4>Social Media</h4><ul><li>Instagram: instagram.com/ha***********</li><li>X/Twitter: x.com/gh***********</li></ul><h4>Crypto Wallets</h4><ul><li><strong>Ethereum 1</strong>: 0x8e6d5***********b5bf</li><li><strong>Ethereum 2</strong>: 0x07b06e***********3019</li><li><strong>Bitcoin</strong>: bc1q5v7y5r5fk***********736r</li><li><strong>Stellar</strong>: GCRAOWEMGUW7***********CGVNH</li></ul><h4>Other Identifiers</h4><ul><li><strong>Hash 1</strong>: af0117***********2f6</li><li><strong>Hash 2</strong>: 07b06e***********3019</li><li><strong>Hash 3</strong>: b5bb79***********5606f</li><li><strong>TOX ID</strong>: AEC803DC44***********5085D</li><li><strong>Card Info</strong>: 6013 01** **** 2333</li></ul><h3>Behavioral Patterns</h3><ul><li><strong>Fake Identity</strong>: Posts photos/videos of a ******<strong>n woman</strong> to deceive and mislead.</li><li><strong>Dark Web Commerce</strong>: Involved in <strong>tool sharing</strong>, <strong>data leaks</strong>, and <strong>payment services</strong> via crypto.</li><li><strong>Language Use</strong>: Primarily English; occasional Indonesian suggests Southeast Asian linkage.</li></ul><h3>TTPs: Tactics, Techniques &amp; Procedures</h3><p><strong>Initial Access &amp; Exploitation</strong><br>DigitalGhost likely gained access to Polri.GO.ID through <strong>known web vulnerabilities</strong>, possibly leveraging outdated CMS plugins or server misconfigurations. The attack method resembles earlier Southeast Asian defacements where CVEs (Common Vulnerabilities and Exposures) are exploited using automated scripts or kits sourced from underground forums. The swift public defacement followed by data leak threats indicates both technical access and a strategy aimed at maximum disruption and visibility.</p><p><strong>Communication &amp; Coordination</strong><br>Once the breach was complete, DigitalGhost used multiple <strong>Telegram channels</strong> as the primary communication vector. These channels served to claim responsibility, disseminate breach-related content, and direct users to additional services or platforms. The actor also operates on <strong>DarkForums</strong>, maintains a <strong>TOR site</strong>, and possesses a <strong>TOX ID</strong>, enabling encrypted peer-to-peer communication. This diversified communication approach demonstrates an understanding of operational security (OPSEC) and a desire to maintain resilience against takedowns or censorship.</p><p><strong>Anonymity &amp; Deception</strong><br>To obscure attribution, DigitalGhost employs a highly curated fake persona, impersonating a <strong>young ******n woman </strong>across their Telegram and social media content. This includes deploying personal photos, videos, and lifestyle imagery, likely harvested or deepfaked. The tactic is intended to confuse investigators, attract naive followers, and build emotional trust for social engineering. Additionally, the use of <strong>TOR, TOX, and burner accounts</strong> further strengthens their digital anonymity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*-lQMGyMq65gR95iosVjGXA.png" /></figure><p><strong>Monetization &amp; Cybercrime Integration</strong><br>While ideological motivations may be part of DigitalGhost’s persona, the infrastructure also supports <strong>financial motives</strong>. The actor has posted <strong>Ethereum and Bitcoin wallet addresses</strong> across Telegram and dark web platforms, potentially to receive donations or payments for services like breached data access, cyber tools, or doxxing jobs. In one Telegram post, DigitalGhost also shared <strong>credit card data</strong>, suggesting involvement in carding or the resale of financial information.</p><p><strong>Infrastructure Sharing &amp; Group Affiliation</strong><br>DigitalGhost’s tactics suggest that they are <strong>not operating in isolation</strong>. Cross-platform analysis of Telegram groups and user overlaps points to shared infrastructure with <strong>Xsvshacker</strong>, an Indonesian hacktivist/criminal syndicate. Evidence includes coordinated posting schedules, use of similar graphic branding, mutual referrals between channels, and potential toolkits shared between parties. These links indicate DigitalGhost may be either a <strong>spinoff operator</strong> within the group or a collaborator participating in broader campaigns.</p><h3>Conclusion</h3><p>The case of <strong>DigitalGhost</strong> underscores the evolving nature of modern cyber threats, where attackers blend technical skill with psychological manipulation, cross-platform identities, and deceptive narratives. What began as a targeted defacement of <strong>Polri.GO.ID</strong> rapidly unraveled into a multi-faceted operation involving dark web infrastructure, cryptocurrency laundering, impersonation tactics, and likely coordination with the <strong>Xsvshacker</strong> threat group.</p><p>DigitalGhost is not merely a hacker, it is a constructed digital persona built for reach, resilience, and misdirection. From Telegram channels to TOR sites, from social media to financial addresses, every layer of this threat actor’s ecosystem reveals a deliberate intent to operate <strong>below the radar</strong>, while maximizing influence, disruption, and financial opportunity.</p><p>This investigation demonstrates the critical importance of <strong>cross-platform OSINT, multilingual monitoring, and dark web intelligence tools</strong>. As threat actors become more agile and anonymous, defenders must rely on <strong>correlated signals, behavioral indicators, and infrastructure mapping</strong> to expose and neutralize such actors before more serious damage is done.</p><p>DigitalGhost’s exposure offers not just a profile but a <strong>playbook</strong> for how lone-wolf personas and regional hacker groups are converging in 2025. Vigilance, intelligence-sharing, and proactive monitoring remain the best defense against threats that move as fluidly and deceptively as this one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d312835a5fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>