Category: Adversary Intelligence
Industry: BFSI
Motivation:Financial
Region: India
Source*:
B - Usually Reliable
2 - Possibly true
Executive Summary
This is an ongoing report and we will keep on updating as we have more information
This advisory highlights recent attacks on Indian banks, focusing on two primary attack vectors: geopolitical tensions and credential stealers/social media account takeovers.
In the last year we have observed that hacktivist groups have the following techniques that they generally use:
- DDOS attacks - They use free tools and scripts sourced from github to attack their targets
- Breached Credentials - Hacktvist groups have realized that freely available credentials give them much more visibility. We have observed that groups have utilized customer credentials as well to garner attention
- .git/.svn/.env - Some threat actors have started scanning for these aforementioned endpoints to get environment variables or code repository which has been shipped to prod environment by mistake
Geopolitical Attacks
The ongoing Israel-Palestine conflict has fueled the activities of hacktivist groups, who have targeted Indian banks due to perceived political stances. The attacks have primarily focused on Distributed Denial of Service (DDoS) attacks aiming to disrupt online banking services and websites.
Timeline of Attacks on Indian Banks/Insurance firms:
- February 21: Lulsezsec Indonesia claims to start targeting Indian banks.
- June 6: A hacktivist group claims to have compromised a major Indian bank, however, the claim was later debunked as the target was an unrelated service.
- June 7: The RADNET group claims a DDoS attack against a indian Bank
- June 11: Multiple banks suffer DDoS attacks from the same RADNET hacktivist group.
- June 21: Rippersec targets claims to target an Indian bank with a DDoS attack.
- June 22: “Infamous” targeted an Indian headquartered Insurance firm and dumped PII data of ~150k customers
- June 23: An Indian Wallet application/subscription management service was breached by a TA called “billy100” ~110k customer PII details were dumped
- June 23: Sulawesi Indonesia carries out a DDoS attack against another Indian Bank.
Screenshot of hacktivist groups targeting indian banks
Please Note - Hacktivist groups are notorious for making claims to create chaos, at the time of writing this report most of these claims have been debunked and there was no spike noticed by the said banks/targeted banks. This happens because of the attention that they get in the pursuit of making these lofty claims.
Recommendations :
- DDoS Mitigation: Invest in DDoS protection services and implement effective mitigation strategies to minimize the impact of attacks. This includes:
- Cloud-based DDoS protection: Utilize cloud-based solutions to distribute traffic and absorb attacks.
- Traffic filtering: Implement firewalls and other security measures to filter malicious traffic and prevent it from reaching critical servers.
- Rate limiting: Set limits on the number of requests allowed from individual IP addresses or specific locations to prevent excessive traffic.
- Network optimization: Optimize network infrastructure for performance and resilience, ensuring quick recovery from DDoS attacks.
Credential Stealers and Social Media Takeovers
In recent weeks, there has been a rise in attacks where hackers hijack social media accounts of major Indian banks, primarily Twitter, and use them to promote cryptocurrency scams. Hackers employ various techniques to acquire these accounts, including:
- Credential stealers: Malicious software that steals usernames, passwords, and other sensitive data.
- Underground forums: Online marketplaces where stolen account credentials are bought and sold.
Once control is gained, the compromised accounts spread links to fraudulent crypto websites and "crypto drainers," malicious tools designed to steal cryptocurrencies from unsuspecting users. The scams often leverage the popularity of Elon Musk and other prominent figures to gain trust.
Recomendations for Banks:
- Enhanced security: Implement robust security measures to protect online banking platforms and social media accounts from DDoS attacks and credential theft. This includes multi-factor authentication (MFA), strong password policies, and regular security audits.
- Social media security: Implement strong authentication protocols and monitor social media accounts for suspicious activity. Consider using social media management tools to prevent unauthorized access.
- Public awareness: Educate customers about the risks of cryptocurrency scams and how to identify fake websites and malicious links.
Recommendations For Users:
- Be cautious: Be vigilant about suspicious links and unsolicited messages, especially on social media.
- Verify information: Always verify information before clicking on any links, especially when it comes to financial transactions or cryptocurrency investments.
- Protect your accounts: Use strong, unique passwords for all online accounts and enable MFA where available.
Enhanced Cybersecurity Measures for Strengthening Organizational Defenses
- Conduct comprehensive scans for viruses and malware on all information systems within the ecosystem, and ensure they are updated with the latest patches after appropriate testing.
- Establish necessary defenses against DDoS attacks, including investing in cloud-based DDoS protection services and implementing traffic filtering measures.
- Implement stringent access control measures to restrict and monitor access to critical systems.
- Maintain continuous monitoring of network activities and server logs to quickly identify and address suspicious and malicious activities within the organization's network.
- Disable vulnerable services like Remote Desktop Protocol (RDP) and Server Message Block (SMB) by default on all critical systems. Remote access to networks hosting critical payment infrastructure should also be disabled by default, with restricted access granted on a need-to-know basis and appropriate monitoring. Remote logon activities should be restricted and closely monitored for potential unauthorized access whenever allowed.
References