|
Researchers have uncovered a threat group launching surveillance campaigns that target victims’ personal device data, browser credentials, and Telegram messaging application files. One notable tool in the group’s arsenal is an Android malware that collects all two-factor authentication (2FA) security codes sent to devices, sniffs out Telegram credentials, and launches Google account phishing attacks. Researchers found the threat group, dubbed Rampant Kitten, has targeted Iranian entities with surveillance campaigns for at least six years. It specifically targets Iranian minorities and anti-regime organizations, including the Association of Families of Camp Ashraf and Liberty Residents (AFALR); and the Azerbaijan National Resistance Organization. The threat group has relied on a wide array of tools for carrying out their attacks, including four Windows info-stealer variants used for pilfering Telegram and KeePass account information; phishing pages that impersonate Telegram to steal passwords; and the aforementioned Android backdoor that extracts 2FA codes from SMS messages and records the phone’s voice surroundings. “Following the tracks of this attack revealed a large-scale operation that has largely managed to remain under the radar for at least six years,” said researchers with Check Point Research, in a Friday analysis. “According to the evidence we gathered, the threat actors, who appear to be operating from Iran, take advantage of multiple attack vectors to spy on their victims, attacking victims’ personal computers and mobile devices.” The Attacks Researchers first discovered Rampant Kitten’s campaign through a document, the title of which translates to “The Regime Fears the Spread of the Revolutionary Cannons.docx.” It’s unclear how this document is spread (via spear-phishing or otherwise), but it purports to describe the ongoing struggle between the Iranian regime and the Revolutionary Cannons, an anti-regime, Mujahedin-e Khalq movement. The document when opened loads a document template from a remote server (afalr-sharepoint[.]com), which impersonates a website for a non-profit that aids Iranian dissidents. It then downloads malicious macro code, which executes a batch script to download and execute a next-stage payload. This payload then checks if the popular Telegram messenger service is installed on the victims’ system. If so, it extracts three executables from its resources. These executables include an information stealer, which lifts Telegram files from the victim’s computer, steals information from the KeePass password-management application, uploads any file it can find which ends with a set of pre-defined extensions, and logs clipboard data and takes desktop screenshots. Researchers were able to track multiple variants of this payload dating back to 2014. These include the TelB (used in June and July 2020) and TelAndExt variants (May 2019 to February 2020), which focus on Telegram; a Python info stealer (February 2018 to January 2020) that is focused on stealing data from Telegram, Chrome, Firefox and Edge; and a HookInjEx variant (December 2014 to May 2020), an info stealer that targets browsers, device audio, keylogging and clipboard data. During their investigation, researchers also uncovered a malicious Android application tied to the same threat actors. The application was purporting to be a service to help Persian speakers in Sweden get their driver’s license. Instead, once victims download the application, the backdoor steals their SMS messages and bypasses 2FA by forwarding all SMS messages containing 2FA codes to an attacker-controlled phone number. “One of the unique functionalities in this malicious application is forwarding any SMS starting with the prefix G- (The prefix of Google two-factor authentication codes) to a phone number that it receives from the C2 server,” said researchers. “Furthermore, all incoming SMS messages from Telegram, and other social network apps, are also automatically sent to the attackers’ phone number.” Of note, the application also launches a phishing attack targeting victims’ Google account (Gmail) credentials. The user is presented with a legitimate Google login page, inside Android’s WebView. In reality, attackers have used Android’s JavascriptInterface to steal typed-in credentials, as well as a timer that periodically retrieves the information from the username and password input fields. We have more of this posted on OUR FORUM. A newly discovered technique by a researcher shows how Google's App Engine domains can be abused to deliver phishing and malware while remaining undetected by leading enterprise security products. Google App Engine is a cloud-based service platform for developing and hosting web apps on Google's servers. While reports of phishing campaigns leveraging enterprise cloud domains are nothing new, what makes Google App Engine infrastructure risky in how the subdomains get generated and paths are routed. Typically scammers use cloud services to create a malicious app that gets assigned a subdomain. They then host phishing pages there. Or they may use the app as a command-and-control (C2) server to deliver malware payload. But the URL structures are usually generated in a manner that makes them easy to monitor and block using enterprise security products, should there be a need. Therefore, a cybersecurity professional could block traffic to and from this particular app by simply blocking requests to and from this subdomain. This wouldn't prevent communication with the rest of the Microsoft Azure apps that use other subdomains. It gets a bit more complicated, however, in the case of Google App Engine. Security researcher Marcel Afrahim demonstrated an intended design of Google App Engine's subdomain generator, which can be abused to use the app infrastructure for malicious purposes, all while remaining undetected. A subdomain, in this case, does not only represent an app, it represents an app's version, the service name, project ID, and region ID fields. But the most important point to note here is, if any of those fields are incorrect, Google App Engine won't show a 404 Not Found page, but instead show the app's "default" page (a concept referred to as soft routing). "Requests are received by any version that is configured for traffic in the targeted service. If the service that you are targeting does not exist, the request gets Soft Routed," states Afrahim, adding: "If a request matches the PROJECT_ID.REGION_ID.r.appspot.com portion of the hostname, but includes a service, version, or instance name that does not exist, then the request is routed to the default service, which is essentially your default hostname of the app." Essentially, this means there are a lot of permutations of subdomains to get to the attacker's malicious app. As long as every subdomain has a valid "project_ID" field, invalid variations of other fields can be used at the attacker's discretion to generate a long list of subdomains, which all lead to the same app. The fact that a single malicious app is now represented by multiple permutations of its subdomains makes it hard for sysadmins and security professionals to block malicious activity. But further, to a technologically unsavvy user, all of these subdomains would appear to be a "secure site." After all, the appspot.com domain and all its subdomains come with the seal of "Google Trust Services" in their SSL certificates. Even further, most enterprise security solutions such as Symantec WebPulse web filter automatically allow traffic to trusted category sites. And Google's appspot.com domain, due to its reputation and legitimate corporate use cases, earns an "Office/Business Applications" tag, skipping the scrutiny of web proxies. This complete article is posted on OUR FORUM with much more information.
Intel's slow trickle of information on its Tiger Lake processors recently turned into a veritable flood as the company shared information about its first salvo of 10nm SuperFin chips, but one detail was missing: Any official disclosures of chips with more than four cores. That changed in a decidedly low-key way, as a blog post from Intel fellow Boyd Phelps on Medium reveals that the company will introduce eight-core models soon, saying: "We also added a 3MB non-inclusive last-level-cache (LLC) per core slice. A single core workload has access to 12MB of LLC in the 4-core die or up to 24MB in the 8-core die configuration (more detail on 8-core products at a later date)." Intel claims that it's four-core Tiger Lake models, by virtue of their 10nm SuperFin Process, Willow Cove Cores, and Iris XE graphics can already beat AMD's eight-core Renoir chips in some performance benchmarks. If Intel's performance projections for its quad-core models are accurate, the eight-core Tiger Lake models could prove to be exceedingly competitive against AMD's existing Ryzen Mobile 'Renoir' lineup, possibly even wresting away the lead in threaded applications. We've yet to see independent third-party verification of the quad-core Tiger Lake chips in reviews, but AMD's upcoming Zen 3 "Cezanne" APUs are now extremely important as AMD looks to keep its performance advantage in the laptop market despite the looming eight-core Tiger Lake models. The current dual- and quad-core Tiger Lake chips address only the 7 to 28W segment, while larger eight-core Tiger Lake-H processors would obviously tackle the upper echelons of the performance market, possibly stretching up to 45W models (~65W peak) for H-series Core i9 and i7 models. We won't go into Tiger Lake's full technical details, we have all of those resources in one place here, but Intel's plans for eight-core Tiger Lake models aren't entirely surprising. Intel's current 10th-gen lineup includes 10nm Ice Lake processors that address the iGPU gaming market with up to four cores, while the 14nm Comet Lake processors slot in for high-performance productivity workloads. However, Intel told us during its Tiger Lake briefings that all of its future laptop chips will come with the 10nm SuperFin (or better) process, meaning the company won't have a split product stack for its 11th-gen lineup. Much of Intel's previous limitations on its Ice Lake models stemmed from the low clock frequencies and poor yields, both of which conspired to limit performance and core counts - Intel's best 10nm efforts thus far have resulted in quad-core chips for laptops. Intel's new 10nm SuperFin process has corrected the clock speed issues, we see up to a 700 MHz increase to base and boost frequencies, and the emergence of eight core models imply that defect rates are lower, and thus yields are up, allowing Intel to punch out 10nm laptop chips with up to eight cores. Intel has no plans to bring Tiger Lake to its lineup of desktop chips, but we have already seen the first new Tiger Lake NUCs emerge from ASRock. Naturally, eight-core Tiger Lake models will also work their way into the NUC lineups. Given their pairing with the Xe graphics engine, they could prove to pack a decent performance punch for compact desktop PCs. Stay abreast on this and other news from Intel by visiting OUR FORUM. |
Latest Articles
|


