There is more to the story than the initial tweet and, unfortunately, as the tweet's author, I wasn't aware that article was written or published or else I could have elaborated some more in it.
It needs to be clear that Forbes was not compromised and there is no technical wrongdoing on their part in this matter. This is an advertisement network issue. Forbes has been very responsive to communications and have worked continuously to follow up on this. This incident does, indeed, show negatively on them and they were very quick to try and locate the incident to pass on to advertising networks.
Their major issue was in the requiring of users to disable ad blockers. That's where the focus should be as it opens a possible attack vector into your system.
I also posted a URL trace of the events around that time, if anyone likes to dig into those things. It's basically a reverse chronological list of every URL Chrome made:
So, unfortunately (or fortunately), there was no zero-day drive by attacking my system. But, the capability was there.