i2i-systems
bd_3f49dcdab41e8715 · schema v1 · pii pii-v2
Full breach record for i2i-systems →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Barracuda on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
This is one of the most poorly secured companies we have ever encountered. Over the course of a week, we analyzed the infrastructure and moved freely across their network. The infrastructure lacked proper security configurations, and the IT department showed a complete disregard for the data. As a result of the attack, 693 gigabytes of data were exfiltrated. We downloaded the complete source code for the following projects: Caplan DataGov-Dev-Docker DDR DDR-Veriskop DFE-Dev Kangal-Dev SDD-DEV-DOCKER SDD-MAIN commonprojects.zip Copycat.zip CopycatLive.zip datacat.war datagov.war Kangal-Dev.zip Kangal-Master.zip [REDACTED-EMAIL] smartdq.war The volume of exfiltrated source code totaled 44 gigabytes. The data includes a full snapshot of the latest releases from the development repository. i2i-systems has a direct connection to the information security company Veriskop; therefore, this breach directly affects them as well. In addition, i2i-systems engaged in joint projects with partners such as Vodafone, Etiya, Bouygues, Freedom Mobile, and others; this is evidenced by the Linux servers located within the i2i-systems infrastructure: 1864654005 backup_Veriskop-SQA1.local_2026-08-31_203808.tar.gz 3292962897 copycat2019.i2isystems.local_critical_backup_2026-08-31_19-30-29.tar.gz 18422354 critical_backup_bouygues_fcbs_batch2.local_20260830_221815.tar.gz 2231188487 etiya-mobile-test-01.local_backup_20260831_213207.tar.gz 20546323810 freedom-mobile1-critical-vault.tar.gz 1050673952 freedom-mobile2-secrets-20260830-232814.tar.gz 721661 maya-redhat7-9_2026-08-30_233036.tar.gz 22966288270 ol8-10-innobi_full_backup_20260831_022640.tar.gz 529695763 veriskop-db-critical-backup-2026-08-31_234418.tar.gz 13012999372 veriskop-fiziksel-yedek-20260831023535.tar.gz 309528511 veriskop-oracle-critical-backup-2026-08-31_203340.tar.gz 633604141 veriskop-rhel-7.local_critical_backup.tar.g
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Sep 13, 2026
Claim posted
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
No regulatory filing corroborates this yet — it is the attacker's own assertion. Watch this entity to be notified the moment a filing corroborates or contradicts it.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.