GCHQ Sebacium
GCHQ Sebacium
GCHQ Sebacium
The maximum classification allowed on GCWiki is TOP SECRET STRAP1 COMINT. Click to report
inappropriate content.
For GCWiki help contact: Support page
SEBACIUM
From GCWiki
(Redirected from File Transfer - FTP)
Jump to: navigation, search
Contents
1 Overview
2 Monitoring - DIRTY RAT
3 Information Operations - PLAGUE RAT
4 Effects - ROBO RAT
4.1 Future work
5 Tasking
6 Classification policy
6.1 Data
6.2 Operational prototypes
7 Interested Parties
8 Notes for SEBACIUM Admins
8.1 Logging
8.2 Running
8.3 Hashing and Topic Files
8.4 File Hash Monitoring
[edit] Overview
SEBACIUM is the codename for the suite of tools developed as part of ICTR-NE's active P2P exploitation
research. These tools fall into 3 categories; monitoring, information operations and effects.
DIRTY RAT currently has the capability to identify users sharing/downloading files of interest on the eMule
(Kademlia) and Bittorrent networks. On eMule it also has the ability to monitor the sharing/downloading of
files related to particular keywords. For example, we can report who (IP address and user ID) is sharing files
with "jihad" in the filename on eMule. If there is a new publication of an extremist magazine then we can
report who is sharing that unique file on the eMule and Bittorrent networks
The capability has proven highly successful and is being used extensively by JTRIG who are in the process of
fully integrating it into their systems. DIRTY RAT will soon be delivered to the Metropolitan Police and we
are in the early stages of relationships with CEOP and the FBI.
We would also like to exploit further a number of opportunities for SEBACIUM to deliver Effects e.g.
content delivery attacks, information operations, denial of service and botnet disruption. We are currently
pursuing these.
[edit] Tasking
The SEBACIUM system is tasked by keyword(s) that are used to match search/sharing requests on the
network.
Although the SEBACIUM system is deployed within JTRIG it is currently still a research prototype,
therefore please contact ICTR-NE with any requests that may provide benefit to your business area.
JTRIG
CBRN
NDIST - Effects
Make sure that log4j has been set to use UTF8 encoding in the properties file for each of the appenders. For
example:
log4j.appender.A1.encoding=UTF-8
[edit] Running
SEBACIUM should be scheduled to run once a day for 24 hours, if run for longer the machine can start to
slow down and logging will be affected. This issue is being looked into by QinetiQ and is thought to be a
memory related. Make sure you reserve enough memory for the JVM, this amount depends on how much is
available and how many hashes are on cover, the minimum is about 400MB, something like 2GB would be
preferable.
Please ensure that all topic files are given UNCLASSIFIED names and NO KEYWORDS are placed
anywhere on the SEBACIUM box.
When hashing unicode keywords please make sure that unicode has been set up properly on the box and the
input/output for all script s has been explicitly set to use UlF-8 . This should be done in DIRTY RAT and there
are also some tip s on the ICTR-NE code snip_~ts page
When hashing files, be sure that you are using the correct algorithm for eMule MD4 file hashing. This works
by hashing "'9MB chunk s of the file and then hashing the concatenated result , which is not how the normal
MD4 hashing algorithm work s. We have a tool provided by QinetiQ to do this and there are also freeware
program s available on the Internet , such as:
http://slavasoft.com/zip/fsurn.zip
When monitoring file hashes with SEBACIUM you should expect to see logs for
KADEMLIA2_PUBLISH_SOURCE_REQ , KAS_ID_LOOKUP and
KADEMLIA2_SEARCH_SOURCE_REQ . The KADEMLIA2_SEARCH_SOURCE_REQ packet indicate s
that the user is downloading the file, if this is not followed by a KADEMLIA2_PUBLISH_SOURCE_REQ
for the user then thi s may indicate that the user is not sharin g the files they download from the network.
IMPORTANT: The user hash given by the KAD_ID_LOOKUP is the KADEMLIA hash for a client ,
wherea s the user hash given by the KADEMLIA2_PUBLISH_SOURCE_REQ is the client 's eDonkey hash
which we are not currently concerned with .
POC:
Retrieved from "htt s:/
Research Protot:x~s I Amilied Research I 816 1Peer-to-12eer I P2QI Protot:x12esI
Categories : A1212lied
SEBACIUM I File Transfer
Views
• Pag~
• Discussion
• Edit
• Risto!)'.
• Delete
• Move
• Watch
• Additional Statistics
Personal tools
•
• MY-talk
• My_12references
• MY-watchlist
• MY-contributions
Navigation
• MainPa~
• Hel12Paw
• Wiki12ediaMirror
• Ask Me About ...
• Random 12ag~
• Recent chan~
• Re12orta Problem
• Contacts
• GCWeb
Search
Toolbox
• J)isclaixuers
SECRET STRAPl COMINT
The maximum classification
allowed on GCWiki is TOP SECRET STRAPl CO MINT . Click to report
ina12pmpriate
content.