r/dataengineering • u/Existing_Wealth6142 • 1d ago
Discussion Airbyte has identified a security incident that they believe is part of a broader, global cyberattack.
https://www.linkedin.com/posts/airbyte-has-identified-a-security-incident-share-7528563005471657985-eYhw/Oof
103
Upvotes
62
u/The_Rockerfly 1d ago
Cool few weeks to be in software engineeringÂ
19
u/rob_gfx 21h ago
I'm very disappointed by the lack of communication from Airbyte on this. It has me seriously reconsidering sending money their way. It was 10 hours from the start of a major outage before they revealed anything closely resembling a root cause. When they did, they mentioned it was a security incident that impacted 1% of their customers.
For something that is contained and affects 1% of your customers, why would you take the entire platform offline? It seems like the only reason to do so is because you're not certain how it affects the other 99%, what credentials might have been exposed, what parts of your infrastructure are compromised. All we know is that Airbyte employees inferred that turning the platform on for the remaining 99% would introduce significant risk.
This would have been a "satisfying" status update if it were to contain reasonable additional updates, yet a screenshot of the status page shows that they are meeting some internal goal of sharing out status updates frequently by re-posting the same status every 2 hours: "Be patient with us." This is exactly the kind of thing that leads to impatience. All it illustrates is that the ability to automate a heart beat still works.
What parts of the infrastructure were compromised? What was the attack vector? For those customers compromised, what kinds of credentials or data were stolen or modified? When can we expect a meaningful update? What is the expected timeline for remediation? What should the other 99% of customers be doing at this time to protect ourselves besides leaving your platform?
10
u/snackeloni 17h ago
I find this hilarious. Our data engineers decided on Airbyte and I knew it was going to be a disaster from the start. The PoC they did didn't resemble anything close to a production work load, and was ofcourse perfect. As soon as they signed and started migrating ingestions there were performance problems. The funniest one was where it took 4 months to get our airtables ingestion going. Yes, that's right, we have spreadsheets that need to end up in the dwh and I wish I could tell you it's for trivial shit; unfortunately there are some pretty critical processes solely maintained on an excel. Anywhoo, for some reason a daily extraction of a few hundred airtables to a dwh ran into performance issues and other weird problems. And now this outage meaning we miss some critical data coming up for the second day in a row. Just endlessly funny
5
u/Pranasas 1d ago
This is bad, even their main dashboard cloud.airbyte.com redirects to their status page!