Security experts working on recently discovered worm, Flame, have confirmed that developers responsible for the malware worked with Stuxnet authors in the early stages of each threat's development.
"What we have found is very strong evidence that Stuxnet/Duqu and Flame cyber-weapons are connected," Kaspersky said.
It seems that there is evidence to suggest that the malware creators cooperated with each other "at least once” during the time that the cyber-attack software was developed. This is evident due to the source code that has obviously been shared between Duqu, Stuxnet and Flame.
"The list includes the names of mutually exclusive objects, the algorithm used to decrypt strings, and the similar approaches to file naming," Kaspersky said.
Whilst Iran were quick to point the finger at Israel in the wake of the discovery of Flame, this has not been proven and a recent NYT investigation has suggested that the US is most likely to be responsible for Stuxnet, possibly in cooperation with Israel and under the orders of President Obama.
However, the UN has dismissed the claim of alleged US involvement as nothing more than speculation. It's not thought that the same development team worked on all three threats, but rather that separate teams of malware authors shared information which has made it clear that parts of the same code, not seen elsewhere, was written by the same team.
The UN has since come forward and urged countries to find a resolution to this kind of issue to avoid the threat of "global cyberwar”.
"There is a risk of cyberwar - but it's not necessary. That's what we're trying to do: prevent. We're saying the best way to win a war is to avoid it in the first place," the UN's Dr Hamadoun Toure told the BBC.
"As the UN, of course we are interested in making sure there is a peaceful resolution, and a peaceful approach to this.”
"Our role is first to co-ordinate international efforts - not only sharing knowledge, but also training people, especially from developing countries because we want to avoid one country being a weak link in the whole process.