We handled a recent phishing incident that targeted Dropbox

Re:We handled a recent phishing incident that targeted Dropbox by gilbertbw on Tuesday November 01, 2022 @10:07AM (#33421424)

> The code and the data around it also included a few thousand names and email addresses belonging to Dropbox employees, current and past customers, sales leads, and vendors

There isn't an explanation as to why customer, lead and vendor data is stored in GitHub? Or (less likely?) they allowed GitHub OAuth to log into other Dropbox internal services?

[ Parent | on HN ]

Re:We handled a recent phishing incident that targeted Dropbox by dannyw on Tuesday November 01, 2022 @10:36AM (#33421784)

Probably an internal prototype that incorrectly stored PII in the repo (as a CSV, .sql, etc)

[ Parent | on HN ]

Re:We handled a recent phishing incident that targeted Dropbox by aliqot on Tuesday November 01, 2022 @10:46AM (#33421909)

That's the real story here.

[ Parent | on HN ]

Re:We handled a recent phishing incident that targeted Dropbox by blowski on Tuesday November 01, 2022 @11:20AM (#33422430)

Not really. Someone’s suggested a possible reason for something that was unclear in the original article. That’s hardly a story.

[ Parent | on HN ]

Re:We handled a recent phishing incident that targeted Dropbox by aliqot on Wednesday November 02, 2022 @10:48AM (#33436707)

It's a full story.

[ Parent | on HN ]

Re:We handled a recent phishing incident that targeted Dropbox by jsty on Tuesday November 01, 2022 @11:34AM (#33422610)

My guess - issues tied to requested features from current & prospective customers, and bugs associated with specific vendors - all of which could plausibly lead to a bunch of (name, email) data points stored on GitHub

[ Parent | on HN ]