Say you and me were amongst DigitalOcean’s customers. Our contact information would be likely stored somewhere at DigitalOcean, and again at Mailchimp in order to carry out DigitalOcean’s email marketing campaigns or such.
Now if you and me have 2FA on our email account won’t manage to contribute anything towards our data being leaked from Mailchimp, nor receiving potential phishing emails. What does make it more difficult is for hackers to access DigitalOcean’s account on Mailchimp, were 2FA to be set by DigitalOcean on their Mailchimp account.
… Nevertheless … if we are talking about some hacker that managed to obtain access to a Mailchimp’s employee’s account, as seems to be the case, we may presume that the employee’s account could have privilages to access data for Mailchimp’s corporate accounts (i.e. DigitalOcean), with disregard to them (DigitalOcean) having 2FA on or off on their account. Afterall, support tends to need to look into customer’s data and configuration, and it would seem weird that they were impeded because of a customer 2FA setting. This is my speculation, but seemingly reasonable.
What could have helped is for employee accounts themselves to have 2FA access to the Mailchimp’s overall system, and to be required to connect through a VPN from a fixed set of firewall approved IPs (perhaps with 2FA on the VPN login itself).