Well, there is a configuration that leaves you very vulnerable to an attack vector.
Researchers were claiming to have reached near 100% confidence that a double spend can be performed.
- http://eprint.iacr.org/2012/248.pdf
Of course, they didn't follow the recommended actions ... configure your client to accept no incoming connections and for outgoing to explicitly connect to a well-connected node (or a node operated by a trustworthy party).
Here are the various double spending attacks:
- https://en.bitcoin.it/wiki/Double-spending#Race_attack
Blockchain.info likely only has outgoing connections but that doesn't mean that is the best method for a merchant to use for notifications as the attacker might receive a connection from Blockchain and through that connection relay simultaneously to Blockchain.info and to the various mining pools simultaneously. You want to ensure with certainty that your node does not have a direct connection to or from the attacker.