Research any topic before you write.
Find related topics. | Discover entities. | See connections. | Build a topical map.
Duqu is a collection of computer malware discovered on 1 September 2011, thought by Kaspersky Labs to be related to the Stuxnet worm and to have been created by Unit 8200. The Laboratory of Cryptography and System Security (CrySyS Lab) of the Budapest University of Technology and Economics in Hungary discovered the threat, analysed the malware, and wrote…
History, Technology & Measurement
Explore the main themes, entities and connections around Duqu. Start with the topic map, then use the sections below for research and deeper semantic analysis.
Start with a few of the strongest sections from the source topic. These are research directions, not a list of keywords you must use.
High-confidence facts extracted from structured source data. Use them as anchors for further research.
Browse the full topic structure. Each item opens a new analysis centered on that subject.
Deeper signals for content research, entity SEO and topical coverage. The plain-language headings explain what each technical view is useful for.
See the strongest relationship patterns around the current topic before diving into the raw triples.
Use these terms to understand the vocabulary surrounding the topic, not as a checklist for keyword stuffing.
stuxnet malware related control used information microsoft symantec crysys 2011 system files command servers zero-day digital attack stars virus systems
| Subject | Predicate | Object | Confidence | Src |
|---|---|---|---|---|
| Duqu | is a | collection of computer malware discovered on 1 September 2011 | 0.90 | text |
| Duqu | is a | process of only using Duqu for unknown goals | 0.90 | text |
| keystrokes | instance of | Executables developed after Stuxnet using the Stuxnet source code that have been discovered.The executables are designed to capture information | 0.80 | text |
| system information.Current analysis shows no code related to industrial control systems | instance of | Executables developed after Stuxnet using the Stuxnet source code that have been discovered.The executables are designed to capture information | 0.80 | text |
| exploits | instance of | Executables developed after Stuxnet using the Stuxnet source code that have been discovered.The executables are designed to capture information | 0.80 | text |
| or self-replication.The executables have been found in a limited number of organizations | instance of | Executables developed after Stuxnet using the Stuxnet source code that have been discovered.The executables are designed to capture information | 0.80 | text |
| including those involved in the manufacturing of industrial control systems.The exfiltrated data may be used to enable a future Stuxnet-like attack | instance of | Executables developed after Stuxnet using the Stuxnet source code that have been discovered.The executables are designed to capture information | 0.80 | text |
| or might already have been used as the basis for the Stuxnet attack | instance of | Executables developed after Stuxnet using the Stuxnet source code that have been discovered.The executables are designed to capture information | 0.80 | text |
| Duqu | related to Command and control servers | Some | 0.60 | section |
| Duqu | related to Command and control servers | It | 0.60 | section |
| Duqu | related to Command and control servers | CentOS | 0.60 | section |
| Duqu | related to Command and control servers | Servers | 0.60 | section |
These clusters group vocabulary that occurs around closely connected concepts in the source material.
Bridges can reveal useful research angles that are easy to miss in a flat list of related terms.