A well-known Iranian state-sponsored hacking group called OilRig, also tracked as APT34 and Helix Kitten, has been found hiding its command-and-control (C2) server configuration inside a regular-looking image file stored on Google Drive. <\/p>\n
The threat group used a technique called LSB (Least Significant Bit) steganography to quietly embed encrypted data into a PNG image, making the attack very hard to detect through standard security tools.<\/a><\/p>\n OilRig is a cyberespionage group that has been active since at least 2016 and is widely believed to be linked to Iranian intelligence agencies. <\/p>\n The group has a long history of targeting organizations across the Middle East, the United States, Europe, and parts of Asia, with a focus on government agencies, financial institutions, energy companies, telecom providers, and chemical firms. <\/p>\n Its primary goal is to steal sensitive political, military, and geostrategic information from high-value targets.<\/a><\/p>\n Analysts at the 360 Advanced Threat Research Institute identified multiple attack samples<\/a> tied to this group during routine APT threat hunting operations. <\/p>\n These findings exposed a new and more advanced attack chain that combined phishing emails, cloud service abuse, image steganography, and in-memory execution to build a covert multi-stage campaign. <\/p>\n The group used the theme of Iran\u2019s nationwide social protests to design convincing phishing documents that pushed victims into triggering the infection without knowing.<\/a><\/p>\n The campaign started with a malicious Excel file titled \u201cFinal List_Tehran.xlsm,\u201d crafted to appear as a legitimate document tied to social unrest in Iran. <\/p>\n The file referenced January 1404 of the Iranian calendar, corresponding to late December 2025 through January 2026, suggesting the attackers designed the bait around real-world events to increase its credibility. <\/p>\n Once a victim opened the document and enabled macros, the full infection chain<\/a> silently began executing in the background.<\/a><\/p>\n The overall attack linked GitHub, Google Drive, and Telegram together into a seamless pipeline for payload delivery, configuration retrieval, and ongoing command communication. <\/p>\n By routing malicious activity through trusted and widely used platforms, OilRig made it much harder for security tools<\/a> to flag the traffic as suspicious.<\/a><\/p>\n The infection mechanism in this campaign was carefully built to avoid triggering security alerts at every step. <\/p>\n When the victim enabled macros in the Excel file, the embedded VBA code silently decoded C# source code stored in the document\u2019s CustomXMLParts section, then used the legitimate Windows compiler csc.exe to build a working malicious loader on the victim\u2019s machine, which was saved as AppVStreamingUX_Multi_User.dll.<\/a><\/p>\n The loader then connected to a GitHub repository under the account \u201cjohnpeterson1304\u201d and pulled a text file named \u201ctamiManager.txt.\u201d After decoding its Base64 content, the loader received a Google Drive link pointing to an image named \u201cMIO9.png\u201d. <\/p>\n This image appeared completely normal but secretly carried encrypted C2 configuration data embedded within its least significant pixel bits.<\/a><\/p>\n Using a custom LSB extraction algorithm followed by Base64 plus XOR decryption, the loader retrieved the full C2 setup, which contained a Telegram Bot token, a chat ID, and five module download addresses labeled m1 through m5. <\/p>\n These modules handled persistence (pr), file upload (up), file download (do), command execution (cm), and application launch (runApp), and each one was loaded directly into memory to avoid leaving files on disk that security tools could scan.<\/a><\/p>\n To maintain access after a reboot, OilRig used Windows scheduled tasks to keep the malware running persistently on the compromised machine, and the malware sent an \u201cis online\u201d heartbeat message through the Telegram Bot<\/a> API every time it activated, giving the attacker real-time confirmation that the system remained under their control.<\/a><\/p>\n Security teams should disable macro execution in Office files received from untrusted sources and set up network monitoring rules to catch unusual outbound traffic directed at GitHub or Google Drive. <\/p>\n Organizations are also strongly advised to deploy endpoint detection solutions capable of identifying in-memory DLL loading, DLL side-loading<\/a>, and process injection activity, all of which were key components of the attack technique used throughout this campaign.<\/p>\n Follow us on\u00a0Google News<\/a>,\u00a0LinkedIn<\/a>,\u00a0and\u00a0X<\/a>\u00a0to Get More Instant Updates<\/strong>,\u00a0Set CSN as a Preferred Source in\u00a0Google<\/a>.<\/strong><\/p>\n The post OilRig Hides C2 Configuration in Google Drive Image Using LSB Steganography<\/a> appeared first on Cyber Security News<\/a>.<\/p>\n<\/div>\n![\"Attack](\"https:\/\/i0.wp.com\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEhba7cngJJFc1lnLXOXs2MFYpNqgT2PIDPxXSF4YiKzxU6MkneHY2eirzQA-vVOCjBhH2xEeAi_rOWrJUZKCPhLzLwkRCjZaheofyiWOjl7XsnXHal2t62nBB4SKNACyNLgmY2POFQP8_DqPM30DwZt2F0fHheWmDtjrI-6eWg9fBjEVAHfP8jKjU9aZBA\/s16000\/Attack%2520Flow%2520%28Source%2520-%2520360%29.webp?ssl=1\")
Inside the LSB Steganography Attack Chain<\/strong><\/h2>\n
![\"OilRig](\"https:\/\/i0.wp.com\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEgGmR_yYOgK1_5Wr5M4t5hT9vzXrpOjRVoCINQt-RF3OowqxCbvw7DXP4jpXfsBkY0zwEDVUrnWuVuToNLJLIKh6jAcoKadQCy7H5heJ7IWXhUnxLmtHqXVE0TUSzUSRS7vXW35aa_ZY5iN1Sw_AasXShLmoKCQzhJTjnE8v1Jo3A8VXI3ny8pBqg4JmDQ\/s16000\/OilRig%2520Steganographic%2520PNG%2520%28Source%2520-%2520360%29.webp?ssl=1\")