The problem was the phishing, not the subdomain. If your app allows users to run phishing operations, moving the content from user.foo.com to www.foo.com/user probably won't help much in parent's scenario.
If the user is going to be able to design + style the pages any way they want, having something in the URL to indicate it's still user content is important.