Incident Score: Analysis & Impact (CLI1777436623)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of ClickUp's Breach and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts ClickUp Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the ClickUp breach identified under incident ID CLI1777436623.
The analysis begins with a detailed overview of ClickUp's information like the linkedin page: https://www.linkedin.com/company/clickup-app, the number of followers: 0, the industry type: Software Development and the number of employees: 1539 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 835 and after the incident was 809 with a difference of -26 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on ClickUp and their customers.
On 27 April 2026, ClickUp disclosed Data Exposure issues under the banner "ClickUp Exposes 893 Customer Emails and API Token Due to Feature Flag Misconfiguration".
On April 27, 2026, security researcher disclosure forced ClickUp to address a months-long misconfiguration in its feature flag system, exposing 893 customer email addresses and a live API token.
The disruption is felt across the environment, affecting Feature flag system (Split.io), and exposing 893 customer email addresses and 1 live API token, with nearly 893 email addresses, 1 API token records at risk.
In response, moved swiftly to contain the threat with measures like Invalidation of exposed API token, removal of email addresses from flag configurations, and began remediation that includes Automated tooling to detect PII/credentials in flag configurations, secrets scanning in deployment pipeline, replacement of email addresses with internal identifiers, and stakeholders are being briefed through Direct notification to affected customers.
The case underscores how Resolved, teams are taking away lessons such as Failure to account for public accessibility of feature flag targeting rules when using PII in configurations. Peer review processes did not catch the accumulation of sensitive data, and recommending next steps like Implement automated tooling to detect PII/credentials in flag configurations, add secrets scanning to deployment pipelines, replace PII with internal identifiers, and supplement peer review with system-level checks, with advisories going out to stakeholders covering Affected customers were notified directly.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with moderate confidence (60%), with evidence including public accessibility via the platform’s client-side SDK, and split.io’s public *splitChanges* endpoint and Compromise Software Dependencies and Development Tools: Misconfiguration (T1584.006) with moderate to high confidence (80%), with evidence including feature flag misconfiguration (Split.io-based system), and treated flag targeting rules as internal tooling. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials in Files (T1552.006) with high confidence (90%), with evidence including one live API token found in a rate-limiting flag, and aPI token remained in configuration until invalidated. Under the Collection tactic, the analysis identified Data from Information Repositories (T1213) with moderate to high confidence (80%), with evidence including 893 customer email addresses embedded in flag targeting rules, and pII in flag configurations was unintended. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with lower confidence (30%), supported by evidence indicating no evidence of malicious access beyond the researcher’s investigation and Transfer Data to Cloud Account (T1537) with lower confidence (40%), supported by evidence indicating public *splitChanges* endpoint queryable via client-side SDK. Under the Defense Evasion tactic, the analysis identified Impair Defenses: Disable or Modify Tools (T1562.001) with moderate confidence (50%), supported by evidence indicating peer review process did not catch accumulation of sensitive data. Under the Impact tactic, the analysis identified Endpoint Denial of Service: Application or System Exploitation (T1499.004) with lower confidence (40%), supported by evidence indicating rate-limiting flag contained a live API token. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- ClickUp Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/clickup-app/incident/CLI1777436623
- ClickUp CyberSecurity Rating page: https://www.rankiteo.com/company/clickup-app
- ClickUp Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/cli1777436623-clickup-breach-april-2026/
- ClickUp CyberSecurity Score History: https://www.rankiteo.com/company/clickup-app/history
- ClickUp CyberSecurity Incident Source: https://thecyberexpress.com/clickup-feature-flag-misgonfiguration-leak/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf