Skip to main content

Maltego launches version 4.1.15 - New tabular export formats and bug fixes!

We are excited to announce that we have released an update from 4.1.14 to 4.1.15 for Maltego !

You will be able to update your client by either clicking on Check for Updates” under the Tools section of the Maltego application menu, or by monitoring the bottom-right corner for an update prompt.  

The current version of Maltego is visible in the title bar: 
Version 4.1.15 brings with it a rework of the graph export features in the form of updated CSV and Excel file structures, as well as graph export to XML in the yEd and Gephi GraphML formats (more on this below and also on our documentation  

We have also worked on fixing bugs that have been reported by you such as deadlocks when reaching 10,000 entities in CE or Classic. This ensures smooth use of Maltego without roadblocks in between your important investigation. 

Overall, the update entails the following changes and bug fixes:


Export Graph to Table 
During your investigations, you might want to export graphs to a tabular format for use in other software, or to incorporate in a report. The new export options give you a bit more flexibility in how the graph data is represented in these tables. 

Let’s create a simple graph to export: 
As before, the Graph Export Wizard allows you to choose whether you want to export the whole graph or just a selection. Depending on what data you choose to include in the export, you might end up generating duplicate rows. 

Remove these duplicates automatically by checking the Remove duplicate rows option. 
When choosing the export details, there are two main options:  
  • Export a table containing the Source and Target Entities value only or
  • Export a table with All Property Values 
When you want to export all the property values, you can choose that they are Grouped by Entity type with blank lines separating them, or as an Entity property flat map. 

When you export the properties, you also get a list of the links in the graph, and there is an option to export that to a Separate Link File instead. 

Exporting Source and Target Entities value only

For the above example graph, exporting only the source and target entities will produce the following result: 
Exporting All Property Values, Grouped by Entity type 

Exporting the entities with their properties, grouped by type, produces the table below. 

The export also includes a list of the links, using the ‘EntityID’ reference to link two entities. These can be in a separate file or at the bottom of the list of entities as in this example: 

Data is grouped into two header rows and multiple property value rows. 
  • The first row (1) includes the entity type and display values of the properties
  • The second row (2) contains the property name
  • The remaining rows (3) include the property values
Exporting All Property Values as a flat map

Exporting the entities and their properties as a flat table produces a file like the one below. Notice that there is only one header-row, and that properties are only populated where relevant in an entity. As an example, only the Website entity has a value for the ‘ports’ property. 

Export Graph as XML 

There are three GraphML formats to which you can export:  
  • one used by Maltego,   
  • one by yEd and
  • another by Gephi.
Please take note: 
Unfortunately, the GraphML format is not standardised, with different applications using the format in a different way. There is no agreed way to store metadata within the XML file, and not even whether the y-axis runs from the top to the bottom, or the other way around. Therefore, more export formats with the same extension must be supported. 

The Save dialog presents the two new export formats along with the existing Maltego GraphML XML format. There is also a checkbox to select whether you want to export only the selected entities. 

Let’s import the GraphML exports into applications that support these formats. 

This is what the graph looks like in yEd: 
And after a bit of tweaking on how it is rendered, this is what the same graph looks like in Gephi: 

We would like to thank you all for your feedback and unwavering support. We are happy to incorporate it in our updates and will continue to do so in the future.

Have feature requests? Write to us at