Fake Telegram Proxy Repositories on GitHub Deliver Stealer Malware to Home Users Seeking to Bypass Restrictions
Home users searching for ways to bypass Telegram restrictions are falling victim to a new wave of malware distributed through GitHub and its mirror sites. Experts from Solar 4RAYS, part of GC Solar, have identified numerous fake repositories that appear in top positions of Russian search engine results and deliver information-stealing trojans instead of functional proxy tools.
Attackers have rapidly capitalized on increased demand for Telegram proxies. When legitimate repository links disappear from search results, malicious pages immediately occupy the freed space. Users encounter familiar names, polished descriptions, and seemingly authentic project pages, leading them to download what they believe is legitimate software.
The counterfeit repositories are crafted with considerable attention to detail. Fraudsters replicate the original README files, project layout, and even the donation information of genuine developers, making the deception difficult to detect at first glance. Once executed, the payloads—identified as Salat Stealer, Santa Stealer, and similar variants—harvest browser sessions, login credentials, and files of targeted formats.
How the Infection Works
The attack chain begins with users seeking proxy solutions to restore access to Telegram. Instead of obtaining working tools, they receive malware capable of extracting sensitive data that can be used for account hijacking and further fraud. The high level of trust placed in GitHub as a reputable hosting platform significantly increases the success rate of these campaigns.
While GitHub provides the infrastructure, the platform cannot always review the large volume of newly uploaded files in real time. This gap is actively exploited by threat actors who create convincing replicas of popular utilities.
Recommendations from Researchers
Security experts advise against downloading utilities automatically. Key red flags include:
- A brand-new author account with no history
- Absence of stars, forks, or issue reports
- Lack of commit history or bug tracking
- Explicit instructions to disable antivirus software before installation
Any of these signs should prompt users to avoid the repository entirely and seek verified sources through official channels.
Related articles
Over 300 Tor Exit Nodes Hijacked to Intercept SSH Passwords and Deploy Ebury Backdoor
Attackers compromised hundreds of Tor exit nodes and repurposed them to perform man-in-the-middle attacks against SSH connections. Instead of reaching the intended server, users were redirected to attacker-controlled infrastructure where they could be tricked into accepting a forged host key and revealing their credentials. Researcher kaba identified 333 malicious exit nodes routing traffic through the same 12 interception servers after noticing an unexpected host-key warning on October 2. The campaign also attempted to install the Ebury Linux backdoor designed to steal authentication data. The Tor Project confirmed that operators' servers had their configurations altered and some middle relays were converted into exit nodes. The initial access vector remains unknown, but the activity window was limited to October 1-5. Users who connected via Tor during this period, accepted an unfamiliar key, and entered a password should treat their credentials as compromised.
LunaSpy Android Spyware Masquerades as FSB Antivirus and Bundles Right Dialer
Positive Technologies researchers discovered a malicious APK named Антивирус ФСБ.apk that installs the legitimate Right Dialer application from developer Goodwy while embedding the LunaSpy spyware. The sample uses package name com.syscore.toolsuite and requests extensive permissions including Accessibility Service to enable broad device control. Dynamic analysis in PT Sandbox revealed command-and-control communication, privilege escalation, and creation of hidden files. Static analysis showed XOR-encrypted strings and an expanded command set that includes call recording via CallService, call redirection rules in JSON format, screen tree extraction, gesture simulation, and anti-analysis commands such as RESET_REBOOT and DISABLE_PLAY_PROTECT. The malware can exfiltrate call recordings in WAV format, perform taps and swipes, and revive camera and microphone permissions through overlay notifications. Researchers published file and network indicators of compromise including multiple IP addresses used by the operators.
MegaFon Reports 34% Rise in Russian Mobile Malware Infections Driven by Android Trojans
MegaFon monitoring data shows a 34% year-over-year increase in Russian users with detected mobile malware during summer 2026, with the sharpest spike of 77% recorded in August. The growth is primarily attributed to Android trojans capable of installing apps without user consent, intercepting notifications, enabling remote access, and stealing personal data. At the same time, blocked suspicious calls dropped significantly, by 31% in June, 41% in July, and 75% in August, which the operator links to state and corporate anti-fraud measures. Scammers are adapting by hijacking messenger accounts through social engineering, malware, and even rental schemes, often combining calls with fake app installations that deploy spyware. Phishing remains active, with 30% of detected malicious resources tied to investments and crypto, 21% to social networks and messengers, and 9% to harmful APK files. Director Sergey Khrenov noted that smartphones are increasingly used as tools by the attackers themselves in these hybrid schemes.
Reflective DLL Injection: How Malware Executes DLLs Directly in Memory Without Disk Files
Reflective DLL Injection allows malicious code to load and execute a DLL entirely in memory, bypassing traditional file-based loading mechanisms on Windows. The technique uses a custom loader inside the DLL itself to handle PE format parsing, relocations, imports, TLS, and exception handling without calling LoadLibrary. Unlike standard loading, the resulting module often resides in MEM_PRIVATE regions and does not appear in conventional module lists, complicating forensic analysis. Tools such as Meterpreter and Cobalt Strike have historically employed reflective loaders, though Beacon Object Files represent a different COFF-based approach. Investigators must examine memory regions, thread start addresses, and Sysmon events 7, 8, and 10 rather than relying solely on file artifacts. The method does not bypass DEP, Arbitrary Code Guard, or access-control restrictions and leaves detectable traces when combined with behavioral indicators. Proper detection requires correlating private executable memory with process behavior and avoiding over-reliance on simplified signatures.