company logo

Product

Our Product

We are Reshaping the way Developers find and fix vulnerabilities before they get exploited.

Solutions

By Industry

BFSI

Healthcare

Education

IT & Telecom

Government

By Role

CISO/CTO

DevOps Engineer

Resources

Resource Library

Get actionable insight straight from our threat Intel lab to keep you informed about the ever-changing Threat landscape.

Subscribe to Our Weekly Threat Digest

Company

Contact Us

Have queries, feedback or prospects? Get in touch and we shall be with you shortly.

loading..
loading..
loading..
Loading...

Discord

API

CDN

loading..
loading..
loading..

Discord CDN & API abuses triggered a new wave of malware exposure

Discord CDN and API abuses caused a spike in malware incidents. RATs and credential-stealing malware found in Discords servers...

24-Jul-2021
3 min read

Related Articles

loading..

Supply Chain Attack

CDN

Polyfill.io relaunches on a new domain after being accused of delivering malicio...

Polyfill.io, a widely used JavaScript CDN service, has been at the center of a significant cybersecurity dispute. Following the discovery of malicious code being delivered to over 100,000 websites, the service has been relaunched on a new domain. This [Threatfeed](https://www.secureblink.com/cyber-security-news) analyzes the underlying nuances of this supply chain attack. #### Background & Initial Discovery Polyfill.io was designed to [help](https://github.com/polyfillpolyfill/polyfill-service) developers add modern JavaScript functionality to older browsers. However, in February 2024, a Chinese entity named 'Funnull' acquired the polyfill.io domain and inserted malicious code into the scripts delivered by its CDN. This malicious code primarily targeted mobile devices, redirecting users to undesirable sites. Researchers from Sansec [identified](https://sansec.io/research/polyfill-supply-chain-attack) the attack, noting that the compromised scripts affected more than 100,000 websites. The malicious code injected by polyfill.io's CDN was designed to hijack mobile devices visiting websites embedding the CDN's scripts. #### Analysis of the Malicious Code The inserted malicious code was sophisticated and strategically designed to evade detection. It redirected users to sports betting sites using a typosquatted domain name (google-anaiytics[.]com), an intentional misspelling of Google Analytics. This kind of attack highlights the potential risks of supply chain vulnerabilities, where third-party code can compromise entire networks. Here is an instance of how such malicious code might look: ![MaliCode1.jpg](https://sb-cms.s3.ap-south-1.amazonaws.com/Mali_Code1_44df6760eb.jpg) This script deceptively loads from a malicious domain, mimicking a legitimate service to avoid immediate suspicion. #### Response and Mitigation Measures Following the [exposure](https://twitter.com/Polyfill_Global/status/1805707089672815039), the polyfill.io domain was shut down by its registrar, Namecheap. The service owners swiftly relaunched it on a new domain, polyfill.com, and asserted there were "no supply chain risks." They claimed all services were cached in Cloudflare, ensuring static content delivery without third-party interference. Despite these assurances, security experts remain skeptical. Cloudflare, a prominent cloud security company, noted unauthorized use of its name and logo by polyfill.io, further eroding trust in the service. Cloudflare's CEO, Matthew Prince, highlighted the scale of the impact, revealing that tens of millions of websites had used polyfill.io, underscoring the seriousness of the breach. #### Technical Deep Dive: Supply Chain Risks Supply chain attacks like the one involving polyfill.io underscore the critical need for robust security practices. When third-party services are integrated into web applications, they become potential vectors for attacks. This incident demonstrates several key vulnerabilities: 1. **Third-Party Code Injection**: The compromised polyfill.io CDN served as an entry point for malicious code. Developers must thoroughly vet third-party services and ensure they are secure. 2. **Domain Trust and Verification**: The use of typosquatted domains (e.g., google-anaiytics[.]com) highlights the importance of domain verification. Implementing strict domain whitelisting can mitigate such risks. 3. **Content Caching and Delivery**: While caching content in services like Cloudflare can reduce risk, it is not foolproof. Continuous monitoring and verification of cached content are essential. #### Recommendations for Developers To safeguard against similar supply chain attacks, developers should consider the following practices: 1. **Self-Hosting Critical Libraries**: Instead of relying on third-party CDNs, host critical libraries on your servers. This ensures direct control over the content delivered to users. 2. **Implementing Subresource Integrity (SRI)**: SRI allows browsers to verify that resources fetched from a CDN have not been tampered with. This can prevent malicious modifications to scripts. ![MaliCode2.jpg](https://sb-cms.s3.ap-south-1.amazonaws.com/Mali_Code2_b60b6b11c2.jpg) 3. **Regular Security Audits**: Conducting periodic security audits of third-party services and dependencies can identify potential vulnerabilities before they are exploited. #### Role of Media and Public Perception Polyfill.io's response to the allegations, particularly their claims of being "maliciously defamed," underscores the challenges companies face in managing public perception during a security crisis. The service's owners have actively defended their integrity, emphasizing the use of Cloudflare caching to mitigate risks. However, trust once lost is difficult to regain, especially when authoritative entities like Cloudflare contradict the company's claims. #### Legal Implications The legal ramifications of such a breach are significant. Companies affected by the malicious code injected through polyfill.io's CDN could potentially seek legal recourse. Additionally, ethical considerations come into play, as the responsibility to protect user data and ensure secure services is paramount. The incident highlights the ethical duty of service providers to maintain the highest standards of security and transparency. #### Future Outlook and Industry Impact This incident is likely to influence future industry practices regarding the use of third-party CDNs. Developers and organizations might shift towards more secure, self-hosted solutions or rely on reputable, audited CDNs with stringent security measures. The focus on supply chain security will intensify, driving innovation in tools and practices designed to detect and prevent such attacks. #### Comparative Analysis Comparing the Polyfill.io incident with other notable supply chain attacks, such as the SolarWinds breach, provides valuable insights into common tactics and mitigation strategies. Both cases involved the compromise of trusted third-party services, highlighting the need for comprehensive security frameworks that encompass all aspects of the supply chain.

loading..   29-Jun-2024
loading..   5 min read
loading..

MoveIt

Authentication Bypass

Discover the latest critical vulnerabilities in MOVEit Transfer. Learn about CVE...

Threat actors are actively engaged to exploit a critical authentication bypass vulnerability in Progress MOVEit Transfer, shortly after the flaw was made public by the vendor. MOVEit Transfer is a managed file transfer (MFT) solution utilized in enterprise settings to securely transfer files using protocols such as SFTP, SCP, and HTTP. These vulnerabilities, notably [CVE-2024-5806](https://community.progress.com/s/article/MOVEit-Transfer-Product-Security-Alert-Bulletin-June-2024-CVE-2024-5806) and [CVE-2024-5805](https://community.progress.com/s/article/MOVEit-Transfer-Product-Security-Alert-Bulletin-June-2024-CVE-2024-5805), have severe implications for data security across various industries. This [Threatfeed](https://www.secureblink.com/cyber-security-news) delves into the technical nuances of these vulnerabilities, providing an in-depth understanding of their impact, exploitation mechanisms, and mitigation strategies. #### Overview of MOVEit Transfer Vulnerabilities ##### CVE-2024-5806: Authentication Bypass Vulnerability Initially rated with a CVSS score of 7.4, CVE-2024-5806 has been re-evaluated to 9.1, elevating its severity from High to Critical. This vulnerability affects MOVEit Transfer versions from 2023.0.0 before [2023.0.11](https://docs.progress.com/bundle/moveit-transfer-release-notes-2023/page/Whats-New-in-MOVEit-Transfer-2023.html), 2023.1.0 before [2023.1.6](https://docs.progress.com/bundle/moveit-transfer-release-notes-2023_1/page/Whats-New-in-MOVEit-Transfer-2023.1.html), and 2024.0.0 before [2024.0.2](https://docs.progress.com/bundle/moveit-transfer-release-notes-2024/page/Whats-New-in-MOVEit-Transfer-2024.html). The flaw arises from improper error handling in the IPWorks SSH library, allowing attackers to manipulate SSH key data for authentication bypass. ##### CVE-2024-5805: Critical Vulnerability in MOVEit Gateway CVE-2024-5805, with a CVSS score of 9.1, is a critical vulnerability affecting MOVEit Gateway version 2024.0.0. This vulnerability permits attackers to exploit forced authentication scenarios, enabling them to capture Net-NTLMv2 hashes by connecting to malicious SMB servers. ### Detailed Analysis #### Newly Identified Vulnerabilities **CVE-2024-5806 (CVSS 9.1 - Critical)** - **Affected Product:** MOVEit Transfer - **Description:** Authentication Bypass - **Affected Versions:** From 2023.0.0 to 2023.0.11, from 2023.1.0 to 2023.1.6, from 2024.0.0 to 2024.0.2. **CVE-2024-5805 (CVSS 9.1 - Critical)** - **Affected Product:** MOVEit Gateway - **Description:** Authentication Bypass - **Affected Version:** 2024.0.0 #### Background and Impact MOVEit Transfer is a managed file transfer (MFT) solution widely used for secure file transfers within and between organizations. The product has a history of critical vulnerabilities, with the [Clop ransomware](https://www.secureblink.com/threat-research/clop-ransomware) exploiting these vulnerabilities in 2023 to steal data from numerous organizations. [MOVEit](https://www.secureblink.com/cyber-security-news/cl0p-ransomware-s-torrent-data-leak-disclosing-mov-eit-s-massive-breach) Gateway is designed to enable safer deployments by acting as a proxy service. ![moveit-dash.webp](https://sb-cms.s3.ap-south-1.amazonaws.com/moveit_dash_186174fbc3.webp) ***Instances of MoveIt Transfer*** The recently identified vulnerabilities have significant implications: - As of June 25, 2024, 2,700 instances of MOVEit Transfer were observed online, predominantly in the US, UK, Germany, the Netherlands, and Canada. - The exposure level has remained consistent with previous observations from 2023, highlighting persistent security risks. ### Technical Analysis of CVE-2024-5806 The authentication bypass vulnerability in MOVEit Transfer stems from issues within the IPWorks SSH library. When error handling fails, attackers can manipulate SSH key data to impersonate legitimate users. This flaw enables unauthorized access to sensitive data and systems. ##### Exploitation Mechanics 1. **SSH Key Manipulation**: Attackers craft malicious SSH key data to bypass authentication checks. The server fails to properly validate the key, granting unauthorized access. 2. **Impersonation Attack**: By exploiting the manipulated SSH key, attackers can impersonate any user on the server, gaining access to restricted areas and sensitive information. ```python # Example Code Snippet def validate_ssh_key(key): try: # Error-prone validation process if not validate(key): raise InvalidKeyException("Invalid SSH Key") except InvalidKeyException as e: log.error("Key validation failed: {}".format(e)) return False return True ``` In the above code snippet, the `validate_ssh_key` function demonstrates improper handling of SSH key validation, which can be exploited for authentication bypass. ### Technical Analysis of CVE-2024-5805 The critical vulnerability in MOVEit Gateway involves forced authentication scenarios where the server connects to a malicious SMB server. This interaction exposes a Net-NTLMv2 hash, which can be used for further exploitation. ##### Exploitation Mechanics 1. **Forced Authentication**: Attackers trick the server into authenticating against a malicious SMB server, capturing the Net-NTLMv2 hash. 2. **Hash Exploitation**: The captured hash can be leveraged to impersonate the server or conduct pass-the-hash attacks, compromising the entire system. ```python # Example Code Snippet def connect_to_smb(server, credentials): try: # Attempt connection to SMB server smb_connection = SMBConnection(server, credentials) smb_connection.authenticate() except SMBException as e: log.error("SMB connection failed: {}".format(e)) return False return True ``` In this code snippet, the `connect_to_smb` function illustrates how forced authentication to a malicious server can expose sensitive credentials. ### Technical Dissection by watchTowr Labs Researchers from [watchTowr Labs](https://labs.watchtowr.com/auth-bypass-in-un-limited-scenarios-progress-moveit-transfer-cve-2024-5806/) provided an in-depth technical analysis of the authentication bypass vulnerabilities: - **Vulnerability Origin:** Unlike a straightforward SQL injection, this vulnerability arises from the interaction between MOVEit and the IPWorks SSH library, compounded by issues in error handling. - **Observed Behavior:** During authentication using SSH key pair authentication, the server throws an exception due to illegal characters in the path, indicating mishandled input. ### Exploit Scenarios #### Forced Authentication Attack An attacker can exploit this vulnerability by: 1. Supplying a UNC path to a malicious SMB server. 2. The target server attempts to connect, falling back to the less secure Net-NTLMv2 protocol, which can then be exploited to capture authentication hashes. ### Mitigation and Recommendations To mitigate these vulnerabilities, Progress Software recommends several immediate actions: 1. **Patch Deployment**: Apply the latest patches for MOVEit Transfer and MOVEit Gateway to mitigate known vulnerabilities. 2. **Restrict RDP Access**: Block inbound RDP access to MOVEit Transfer to prevent unauthorized remote access. 3. **Limit Outbound Connections**: Restrict outbound connections to trusted servers only, reducing the risk of forced authentication attacks. Additionally, users should apply patches as soon as they are available and monitor network traffic for any unusual activity indicating attempted exploitation. ### Exposure Analysis As of June 25, 2024, approximately 2,700 instances of MOVEit Transfer are online, predominantly in the United States. The majority of these instances are hosted on Microsoft or Amazon autonomous systems, underscoring the widespread usage and potential risk of exploitation. ### Conclusion The vulnerabilities in MOVEit Transfer and MOVEit Gateway present significant risks to data security. CVE-2024-5806 and CVE-2024-5805 exemplify how flaws in authentication mechanisms can be exploited to gain unauthorized access and compromise sensitive systems. By understanding the technical details and implementing recommended mitigations, organizations can protect themselves against these critical threats. The identification of these new vulnerabilities in MOVEit Transfer and Gateway underscores the importance of robust cybersecurity measures. Organizations using these products should prioritize applying the recommended mitigations and closely monitor their systems for signs of compromise. For further details and continuous updates, refer to Progress Software's advisory and security bulletins. Through meticulous evaluation and proactive measures, the integrity and security of critical systems can be maintained.

loading..   28-Jun-2024
loading..   7 min read
loading..

AWS

Coinstats

Cryptotheft

CoinStats breach exposes 1,590 crypto wallets via alleged social engineering att...

On June 22, 2024, CoinStats, a popular cryptocurrency portfolio management app, faced a significant security breach compromising 1,590 crypto wallets. This incident not only disrupted services temporarily but also raised serious questions about the security measures of cryptocurrency platforms. The following [Threatfeed](https://www.secureblink.com/cyber-security-news) analysis will meticulously dissect the critical nuances of this cryptocurrency breach of this year, its technical aspects, and the broader implications --- #### Incident Overview **CoinStats Breach** The breach initially surfaced on June 22, leading to the temporary suspension of CoinStats services. The [attack](https://x.com/CoinStats/status/1804633869372559788) was limited to 1.3% of all wallets, resulting in a loss of approximately $2 million. A detailed investigation revealed that the attack was orchestrated by compromising an employee's computer through social engineering, which led to the infiltration of their AWS infrastructure. CoinStats shared a list of [impacted wallets](https://docs.google.com/spreadsheets/d/1Lwxpy2T6W7aptjBJUio0Z01zihsqknXn6KPhzawQLVI/edit?gid=1914313472#gid=1914313472), but some [users reported](http://x.com/ArturJaro/status/1804803184872820899) thefts from wallets not on the list. Thus, the breach's scope might be larger than verified. **Technical Details of the Breach** The attack exploited social engineering tactics to install malicious software on an employee's computer. This allegedly allowed the attacker to obtain unauthorized access to the AWS environment where CoinStats' wallet data was stored. Despite prompt action to limit the breach, the attacker managed to access a significant number of wallets . ![4676c939-a8fa-4f1c-84b6-2e3888c0f346.png](https://sb-cms.s3.ap-south-1.amazonaws.com/4676c939_a8fa_4f1c_84b6_2e3888c0f346_cc4767d05a.png) ***CoinStats Post Attack' Status*** **Response and Mitigation** CoinStats' response involved immediate shutdown and isolation of affected systems. They published a list of compromised wallets and urged users to transfer their funds to secure external wallets. The company is conducting a thorough post-mortem analysis to refine its security measures and prevent future breaches . --- #### Social Engineering: A Critical Weakness **Understanding Social Engineering** Social engineering involves manipulating individuals into performing actions or divulging confidential information. This tactic exploits human psychology rather than technical vulnerabilities, making it a potent weapon for attackers . **Case Study: CoinStats Incident** In the CoinStats breach, the attacker used social engineering to trick an employee into downloading malware according to what was understood on June 26, [Narek Gevorgyan](https://x.com/narek_gevorgyan/status/1805873896836440411), CEO of CoinStats, via there findings of an [internal investigation](https://www.reddit.com/r/CoinStats/comments/1doubje/an_update_from_coinstats_ceo/): _“Our AWS infrastructure was hacked, with strong evidence suggesting it was done through one of our employees who was socially engineered into downloading malicious software onto his work computer.”_ This malware then facilitated unauthorized access to the company's AWS infrastructure. The specifics of the malware used remain unclear, but its impact underscores the effectiveness of social engineering in bypassing technical defenses . Gevorgyan’s message refrained from promising refunds for all victims, instead indicating that the company will outline a detailed action plan following a comprehensive post-mortem analysis. _"I empathize with those who lost money; I understand their hardship. CoinStats will support the victims of the hack, and we’ve been exploring various options internally."_ Some community members have reported even more substantial losses. For example, Blurr.eth’s wallet allegedly lost 3,657 Maker tokens, valued at approximately $8.7 million. --- #### Broader Implications for Cryptocurrency Platforms **Increasing Trend of Security Breaches** The CoinStats incident is not isolated. Other platforms, such as CoinGecko, have also faced security breaches recently. CoinGecko's breach on June 5 involved a compromised employee account on a third-party email management platform, leading to the exposure of user data . **Impact on User Trust and Platform Security** These incidents erode user trust and highlight the need for robust security practices. Users are now more cautious, emphasizing the need for platforms to adopt stringent security protocols, including multi-factor authentication and regular security audits . **Role of Employee Training and Awareness** Educating employees about social engineering tactics is crucial. Regular training sessions and simulated phishing attacks can help build a security-conscious workforce, reducing the risk of similar breaches in the future . --- #### Technical Analysis of the CoinStats Breach **AWS Infrastructure Vulnerabilities** The breach highlighted vulnerabilities in CoinStats' AWS setup. While AWS provides robust security features, improper configuration and inadequate monitoring can lead to significant risks. In this case, the compromised employee credentials allowed the attacker to navigate the AWS environment undetected initially . **Malware and Exploitation Tactics** The malware used in the CoinStats breach was likely designed to evade detection and exfiltrate data stealthily. Analyzing the malware's code and behavior can provide insights into its mechanisms and help develop countermeasures. For instance, using endpoint detection and response (EDR) tools could have potentially identified the unusual activity early . **Mitigation Strategies** Post-breach, CoinStats needs to implement several mitigation strategies: - **Enhanced Access Controls:** Implementing stricter access controls and limiting permissions can reduce the impact of compromised credentials. - **Regular Security Audits:** Conducting frequent audits of infrastructure and codebases helps identify and rectify vulnerabilities. - **Incident Response Plan:** Developing a comprehensive incident response plan ensures swift and coordinated action during future breaches . ---

loading..   28-Jun-2024
loading..   5 min read