Live Mission: Operation Jadelion

Possible live mission has begun and agents are getting calls.

Please follow Live Events Etiquette

Discuss all findings here, IRC or in TeamSpeak

Mail from dispatch on 22:22 GMT+1
MISSION FOR: ALL ACTIVE AGENTS
MISSION No: 300029 [Operation JADELION]
AREA OF OPERATIONS: WORLDWIDE

--
1. Action required:
Decode emergency message, report contents and origin to Dispatch for analysis.

2. Background:
On 12/11/15, our SIGINT team intercepted an encoded message on a frequency used by European authorities only in times of medical emergencies. The message has been transcribed and is available in the archive [Call number A91BA9]

Our technical team is in the process of analysing the encoding of the message, as it does not fit the standards used by authorities.

3. Recommendation:
(a) Decode the message, determine the contents and origin.
(b) Notify Dispatch [[email protected]] of your findings and stand by for updates via Twitter and the situation room.

Google Docs form for mission critical info

Please note! This is an live event. No need for using Spoiler tags in live missions. You can go all in with the intel

Email #2 from Dispatch

MISSION FOR: ALL ACTIVE AGENTS
MISSION No: 300029 [Operation JADELION]
AREA OF OPERATIONS: WORLDWIDE

--
Update on JADELION:
A meeting has been set up between the Vanburg Institute scientist, Gregory Letzky [Subject H2D7L1], and Agent Dylanamite at 18:00 UTC today. Our agent is set to receive information regarding Test Subject Omega [Target D5FA65], which recently escaped a Vanburg lab. Once this information is received, we will need to work quickly to ID and locate the target, and set up a point of interception.

The meeting will be recording by our agent, and can be viewed at https://www.periscope.tv/dylanamite beginning at 18:00 UTC.

 

I received a call. Archive number a91ba9
http://archive.blackwatchmen.com/search/a91ba9
Still looking into this now.

 

Just got the call. Will research it when I get home.

Phonecall for anyone interested: https://clyp.it/vm0xz3iu

 

google document with code segemtents to edit: https://docs.google.com/document/d/1fvvKXEMyqXqOdH2o3JhS259YIEgUKpRs-35E2VBMmVw/edit?usp=sharing
pastebin of linebreak seperated code segments: http://pastebin.com/4zCkH6fw

 

I also just received a call, but am at work so cannot work on decoding until sometime this evening.

Same archive number as LN3000.

 

Assuming xx-xxx is a codon, its not a direct codon to letter conversion cipher, because the only duplicate is 04-841 at it ocurrs exactly twice, every other segment is unique

 

I'm certain this has been observed, but the first two digits of each code segment are a number between 01 and 20. Every number in the 01-20 range is represented at least once except for 03. The distribution varies widely. The most common prefixes are:

01 (11)
17 (9)
02 (8)
04 (7)
12 (7)
05 (6)
18 (6)
20 (6)

... with 08 and 15 appearing just once each, and 03, again, being absent entirely. This seems broadly consistent with a letter frequency distribution (in English? in another language?)

The last three digits of each code segment range from 000 to 984.

 

Received the call. I thought it might be a language of sort as the first two number before the dash numeric value goes to 20, but 03 isn't there after i filtered and broke down everything to see if there was a pattern, but as Aetheros indicate "04-841" repeats twice, but it being there must have some uniqueness to it.

The numbers before the dash must represent something that links the numbers after the dash in some fashion.

 

IF YOU COME TO A CONCLUSION PLEASE VERIFY YOUR ANSWER BY PUTTING AN EXPLANATION OF HOW YOU GOT TO THAT POINT, AS BRIEF OR LONG AS YOU WISH, ON ANY ACCESSIBLE MEDIA OF YOUR CHOICE THAT WE'RE USING -- FORUM, IRC, IN THE DOC ITSELF, ETC. OTHERWISE WE'RE DELETING/DISREGARDING IT.

THIS IS SO WE CAN RECREATE THE RESULTS AND AVOID RED HERRINGS AND WILD GOOSE CHASES. THANK.

 

Less of the red caps please, makes it sound like you are shouting orders.

 

>implying I'm not

 

Hope not, I shot the last person who shouted orders at me

 

Just to debunk Hex and Hieroglyph profferings:

 

I got this call while I was at work. Looking into it, but i have no clue what I am looking at.

I feel like it has something to do with the emergency frequency itself, but I am having a hard time pinpointing it.

Will look into this more when possible.

 

Daedalus preempting all of the jokes.

 

Agent Santiak,

Understood. We just received a new report from our SIGINT team and it appears that the emergency channel was used in the past for medical alerts concerning disease spread. We still have no updates regarding the nature of the message encoding.

Division 66

 

ALERT LAB C REPORTS EMERGENCY SUBJECT OMEGA HAS ESCAPED AND ENTERED LANGNEY SEWER OMEGA MUST BE NEUTRALIZED

 

Oh cool you guys cracked it

 

Just to follow up: The message was decoded by translating the first 2 digits to its alphabet equivalent, then finding the ICD-10 medical code (sans periods), and use the first letter of the diagnosis to string together the sentence.
http://www.hipaaspace.com/Medical_Billing/Coding/ICD-10/Diagnosis/p242