IPCRIME | THE UNDERGROUND FILES | NOVEMBER 16, 2026
An old partner key can outlive the project it was created for. Recent published incident reports from Barracuda and Cursor provide two separate examples of how third-party data and credentials can lead to wider compromise. There is no verified public evidence that the same attacker carried out both incidents, even though their operational patterns have similarities.
Case one: Barracuda’s unrevoked key
Barracuda says it issued a cloud access key to an external vendor for an AI-related project and failed to deactivate it when the work ended. After the vendor’s development environment was compromised, an attacker used the key in early November. Barracuda’s timeline describes a roughly 44-hour intrusion touching about ten cloud accounts. Subsequent access included source-code and automation-related credentials. Barracuda’s analysis says the activity matched the ARTEX AI testing framework; that is the vendor’s technical assessment.
Case two: Cursor’s shared-trace exposure
Cursor says a separate exposed key associated with Fireworks AI let an attacker copy data from a shared bucket. Some historical coding-agent traces outside Privacy Mode held unredacted credentials. The attacker reached additional services and the cache used to distribute certain Claude Code extension builds. The chain demonstrates that even a read-only data store can become an entry point if the data it holds contains secrets.
Common mechanics, different incident facts
Neither company publicly reported that a user simply chose a weak password. In both stories, the material issue was what a supplier could reach and which credentials or shared records remained accessible. The timing, data involved, persistence and customer impact differed. A meaningful comparative investigation should preserve those distinctions rather than invent a single coordinated campaign.
The unglamorous controls that would matter
Close vendor access when a contract or project ends. Use expiring credentials, narrowly scoped roles and named internal owners for each key. Test whether external vendors can access stored logs or AI traces that may inadvertently include secrets. Audit CI systems and repositories for long-lived credentials. Review how quickly revocation actually prevents access across cloud platforms and integrations.
What remains unanswered
Barracuda and Cursor are still responsible for their own incident communication and remediation. Published reports do not let independent readers reconstruct every attacker action or prove exactly which customer records were accessed. Future updates should be attributed to additional vendor findings rather than guessed from similarities.
Sources and documentation
IPCRIME’s independent documentation-based analysis, not a claim of private forensic access or hands-on penetration-testing validation. Dates and uncertain facts are attributed above.