Cloud database giant Snowflake is investigating targeted identity-based attacks against some of its customers. These sophisticated attacks aim to exploit user credentials to gain unauthorized access to sensitive data stored in Snowflake’s cloud services.
Summary:
- Nature of Attacks: Targeted identity-based attacks focusing on customer credentials.
- Platform: Snowflake cloud database services.
- Potential Impact: Unauthorized data access, potential data breaches, data exploitation.
- Current Status: Under investigation by Snowflake.
Scenarios:
- Increased User Activity Preceding Suspicion of Campaign:
- An observable increase in user activity might have been detected initially.
- This increase led to the suspicion that a targeted campaign could be underway.
- Implication: The campaign might have triggered users to proactively secure their accounts, leading to increased activity.
- Panic from Campaign Leading to Increased User Activity:
- The initial suspicion or detection of a campaign caused panic among users.
- As a result, users increased their activity to secure their accounts and data.
- Implication: The panic and awareness from the suspected campaign caused a surge in security-related user activities.
Joint Statement on Investigation:
On May 31st, 2024, Snowflake issued a joint statement with CrowdStrike and Mandiant stating that they are investigating a targeted campaign against Snowflake users with single-factor authentication.
There is no evidence to suggest vulnerabilities in Snowflake’s product or any data exfiltration caused by compromised credentials of a current or former Snowflake employee.
If you are a Snowflake customer, it’s important to read the company’s guidance on preventing unauthorized access and ensure your environment is properly configured and sufficiently monitored.
What does this mean for my organization? Given the importance of data stored in Snowflake databases and warehouses, compromised credentials can lead to significant data breaches.
Once an attacker has control of an identity in cloud-hosted applications, there is no perimeter. It’s essential to ensure that if an identity is compromised, there are additional lines of defense between the bad actor and your sensitive data.
Mitigation Steps:
- Enable Multi-Factor Authentication (MFA): Ensure all user accounts utilize MFA for added security.
- Regularly Rotate API and OAuth Keys: Keep credentials secure by rotating them frequently.
- Monitor Account Activities: Keep a close watch on account activities for any suspicious behavior.
- Security Audits: Conduct frequent security audits to identify potential vulnerabilities.
- Awareness and Training: Educate users about the risks and best practices for maintaining account security.
Snowflake has published a security bulletin with Indicators of Compromise (IoCs), investigative queries, and advice on securing accounts. According to the bulletin, customers should review their account activity, implement stricter security protocols, and follow recommended practices for API key management.
Identified Malicious IP Addresses:
104.223.91.28 | 198.54.135.99 | 184.147.100.29 | 146.70.117.210 | 198.54.130.153 | 169.150.203.22 |
185.156.46.163 | 146.70.171.99 | 206.217.206.108 | 45.86.221.146 | 193.32.126.233 | 87.249.134.11 |
66.115.189.247 | 104.129.24.124 | 146.70.171.112 | 198.54.135.67 | 146.70.124.216 | 45.134.142.200 |
206.217.205.49 | 146.70.117.56 | 169.150.201.25 | 66.63.167.147 | 194.230.144.126 | 146.70.165.227 |
154.47.30.137 | 154.47.30.150 | 96.44.191.140 | 146.70.166.176 | 198.44.136.56 | 176.123.6.193 |
192.252.212.60 | 173.44.63.112 | 37.19.210.34 | 37.19.210.21 | 185.213.155.241 | 198.44.136.82 |
93.115.0.49 | 204.152.216.105 | 198.44.129.82 | 185.248.85.59 | 198.54.131.152 | 102.165.16.161 |
185.156.46.144 | 45.134.140.144 | 198.54.135.35 | 176.123.3.132 | 185.248.85.14 | 169.150.223.208 |
162.33.177.32 | 194.230.145.67 | 5.47.87.202 | 194.230.160.5 | 194.230.147.127 | 176.220.186.152 |
194.230.160.237 | 194.230.158.178 | 194.230.145.76 | 45.155.91.99 | 194.230.158.107 | 194.230.148.99 |
194.230.144.50 | 185.204.1.178 | 79.127.217.44 | 104.129.24.115 | 146.70.119.24 | 138.199.34.144 |
185.248.85.14 |
Additionally, connections from clients identifying as ‘rapeflake’ or ‘DBeaver_DBeaverUltimate’ running on Windows Server 2022 should be scrutinized, as they are known to be associated with data exfiltration.
Recommendations:
- Enforce MFA and SSO: Identify and isolate Snowflake users without MFA enabled, including users with elevated permissions.
- Identify Sensitive Data Exposure: Understand what actions users and groups can perform on critical data and where it is potentially overexposed.
- Audit Sensitive Data Access Activity: Audit trail to search for risky actions such as users dropping tables or performing queries to exfiltrate data.
- Check Network Access Policies: Create a policy to alert you whenever a Snowflake resource doesn’t have a network access policy set to limit who can connect to your Snowflake instance.
- Enable User Behavior Analysis: Use advanced, behavior-based threat detection on Snowflake logs.