It seems like the ABISM outage that was mentioned in earlier messages was referring to whatever the message desk uses to give us responses. Any code that isn't the redacted code from the 18014 message doesn't work. When we call with that code, the message desk asks for an authorization code, and then a "result". We haven't figure out what he means by result yet, but he says ""what I need to put in this box here, is 5 groups of 5 letters".
We suspect the Bursage Loop device outputs are relevant here and are in the process of figuring out which one to use.
UPDATE: We were correct in assuming that the Bursage Loop device output was relevant. Since the "authorization code" was A1BC1B, we needed to give the message desk the first line of the output for codes starting with A on the device. He then asked for a product code; we used AB101 from the earlier black otp1 message. Then he asked for a name and address, which one of our users provided. Nothing suspicious about this!
Posted: Sun Dec 23, 2012 5:48 am
Adah
We never confirmed for sure that it's an ARG, but the way the game responds to our input and makes fun of us sometimes (the "I love you" message, etc.) makes it seem that way!
Z 231045Z DEC 12
SECRET//PRJMLPL//75X5
MSGID/ORDER//
SUBJ/ORDER//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
DURING OUTAGE ORDER
SERVICE STILL AVAILABLE
ON CODE XXXXX
//
Posted: Sun Dec 23, 2012 4:58 am
Echoshock
If you guys need someone to grab a drop in Portland, Oregon ever, I'm down. Just give me the coordinates and I will grab it as quick as possible. Also, where do you learn how to find all this shit? I wanna learn how to decode like that! Where would you recommend beginning.
Also, tried calling the number. It said the call could not be completed due to a network error.
But yeah, where would I begin learning this kind of thing?
Also, did we ever confirm this as an ARG and not real?
Posted: Fri Dec 21, 2012 4:26 pm
bambusar
I noticed that agent number 18011 is missing from post with all 1800# numbers...
Firts 18011
[09:05] Adah DO YOU HAVE HAVE PROPER EQUIPMENT TO CONTINUE? MDSK 18011 COLLECTION TRUE:66 OR FALSE:72
[09:08] Adah Well, true or false is a choice. I don't want to make a decision without asking anyone first! haha
[09:08] Rumel i'd say false
[09:16] Adah success
[09:16] Adah he said "Next time your code will be 18004"
[09:18] Adah http://vocaroo.com/i/s1PLRIjgRAmM
Posted: Thu Dec 20, 2012 4:20 am
Adah
We found a TON of new black otp1 messages since my last post. I don't have the original coded messages for all of them, but they're there when I do.
18002:
Z 121800Z DEC 12
SECRET//PRJMLPL//75X5
MSGID/ABISM-NOTIFY//
SUBJ/ABISM OUTAGE//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
ABISM OUTAGE SCHEDULED
FOR MX.
STADT:230001Z DEC 12
END:232359Z DEC 12
//
Z 060345_ DEC 12
SECRET//PRJMLPL//75X5
MSGID/MX-TICKET//
SUBJ/BATT WARNING//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
TRAVEL TO FACILITY
ALPHA SIGMA, EXAMINE
BATTERY SITUATION. USE
GENERATOR CONNECTION TO
RECHARGE IF NEEDED.
REPLACE BATTERY IF NEEDED.
CONFIRM ACTIVATION CODE
99990 ON TASK COMPLETE.
Z 300022Z OCT 12
SECRET//PRJMLPL//75X5
MSGID/MX-TICKET//
SUBJ/RADIO ERROR//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
TRAVEL TO FACILITY
ALPHA SIGMA, EXAMINE
RADIO SITUATION. REPLACE
RADIO MODULE CHECK TUNING
CHECK SYSTEM VOLTAGE.
BRING REPLACEMENT PARTS
NESS. CONFIRM CODE 99990
ON TASK COMPLETE.
//
18007:
Z 011201Z DEC 12
SECRET//PRJMLPL//75X5
MSGID/STATUS//
SUBJ/REPORT//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
YES, I KNOW.
//
Z 151347Z DEC 12
SECRET//PRJMLPL//75X5
MSGID/STATUS//
SUBJ/REPORT//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
SHE PICKED UP THE DISC
100MB STANDARD HOLE
//
Z 161021Z DEC 12
SECRET//PRJMLPL//75X5
MSGID/STATUS//
SUBJ/REPORT//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
SO I ASSUME SHE IS READY?
//
18010:
Z 161053Z DEC 12
SECRET//PRJMLPL//75X5
MSGID/STATUS//
SUBJ/REPORT//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
YES, WE BELIEVE SO. AGENT
CODES ARE ROUTINELY HIT
//
18012:
Z 192046Z DEC 12
SECRET//PRJMLPL//75X5
MSGID/STATUS//
SUBJ/INQUIRY//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
DO YOU HAVE HAVE PROPER
EQUIPMENT TO CONTINUE?
MDSK 18011 COLLECTION
TRUE:XX OR FALSE:XX
//
[02:00] Xkeeper oh, no, it' sstill there, but still gives errorsiren.
[02:09] Xkeeper 419-646-0004 is weird.
[02:15] Xkeeper it's different every time, sometimes you can call it and it wont' answer for 1m30s (until you get disconnected anyway)
[02:19] Xkeeper 419...
[02:19] Xkeeper silence, really really quiet message, dial tone again, loud dtmf tone (just one), message again
[02:32] nadando says 712374 in the middle
[02:33] Xkeeper 712374 is invalid in agentsys
[03:08] nadando it says 712374 in the middle
[03:08] nadando twice
[03:10] nadando it says "please check the number and dial again" then 712374 then the error message then the number again
[03:17] nadando [b]712-374-1061[/b] has identical output to polish number
[03:17] crash_demons 7123741061 = SIDNEY
[03:14] marcusw 20:32 <nadando> also where did 1061 come from
[03:15] crash_demons 48_22_307
[04:51] nadando so +48 was just redirecting to some number in the 712374 range
[04:51] nadando or was that just a recording
[04:52] Moose-Alini im guessing its just a standard error message
[04:52] Moose-Alini but it would be evidence that this number is not actually based in poland
[04:52] Moose-Alini which i thought anyway
[04:53] Moose-Alini or could be a recording, what with the weird beeps but i dunno
The SIM card seems to have nothing of value on it other than the ID (which was already printed on the container card), so scratch that one off your list.
Posted: Tue Dec 18, 2012 8:48 pm
bambusar
List of unsolved things:
outputs from LV arduino black box,
x/xxxxxxx/xxxxxxx numbers,
operations guy
iridium card,
what the purpose of 3333x and satellite adjustment is,
and wtf 17001 is about
also agent code 13#, 9#, gibberish, message desk callbacks
also scrambleds
Posted: Mon Dec 17, 2012 4:59 am
bambusar
MAJOR BREAKTHROUGH
Both numbers OTP black file messages were decoded. They were decoded by xoring numbers with last bytes of 100MB random data chunk from Linux Ubuntu CD we found in El Passo.
Long message was also gzipped, while short message xoring yielded plain ascii.
Short 22 character message:
Code:
/ORDERS/TBD*MSG*18001
Long 338 characters message:
Code:
Z 130001Z DEC 12
SECRET//PRJMLPL//75X5
MSGID/A16041_131212_1//
SUBJ/STATUS//
/FORMAT/OBJ/00001/ASCII//
/OBJ/00001/
GOOD SEASON, LIMITED LOSSES
BUT COMPONENTS FAILED TO
REACH SVALBARD. MAY BE
EXPERIENCING COMPONENT LOSS
AT DROP SITES. SUSPECT
ROGUE AGENT OR COUNTER
OPERATION. MISSION CANNOT
CONTINUE UNLESS RECOVERED.
TWO AGENTS ASSIGNED TO
DETERMINE THREAT.
MAY NEED ASSISTANCE IN
RECOVERY.
OTP AUTH CODE 30004A
ASSIGNED UNTIL FURTHER
NOTICE. SIGNAL EMERG IF
OTP COMPROMISED OR ADDTNL
SPACE REQUIRED.//
Ymgve 1. convert numbers to bytes 2. xor result with bytes in the 100mb otp file, starting at the specified offset 3. profit
[00:30] Lurker69 Ymgve: sorry to bother but you used 100mb linux chunk and blackotp1files from today right?
[00:30] Ymgve yes
[00:30] Lurker69 but where did .gz came to play
[00:30] Ymgve it _is_ a gz file
[00:30] Ymgve if you write the xored bytes out to a file, you can open it as a gzip file
We believe that first two messages were the same as second two, since both have same lenght, and we re encoded with some mistake or cipher was to hard, so we got another set of messages that we were able to decode.
[06:57] Xkeeper4400_ Man, come on...
[06:57] Xkeeper4400_ I got operations again.
[06:57] Xkeeper4400_ kind of funny though, technical issues abound it seems
[06:57] Xkeeper4400_ [call] 2022042303 ... ...
[06:57] Xkeeper4400_ *push random keys while waiting for forward*
[06:58] Xkeeper4400_ <Operations> [in almost inaudible audio levels] operations?
[06:58] Xkeeper4400_ Hello?
[06:58] -->| lskaglsd (~voackd@2002:44a8:d0d8::44a8:d0d8) has joined #arg
[06:58] Xkeeper4400_ <Operations> [in almost inaudible audio levels] operations??
[06:58] Xkeeper4400_ then he hung up a bit later.
[06:58] Xkeeper4400_ technical difficulties
NADANDO got redirected directly to MD guy from agent numbers system, without entering any agent number.
[07:00] nadando got message desk randomly on 202 999 3335
[07:00] nadando another return with a random number
[00:44] AluisioASG ==========\\_ABISM\\_==========\\_REQ>@\\_REQ>@\\_REQ>@
[00:44] AluisioASG YEAH!
[00:44] Ymgve how
[00:45] AluisioASG DEC SIXBIT + mark parity
[00:45] AluisioASG "One popular variant was DEC SIXBIT. This is simply the ASCII character codes from 32 to 95 coded as 0 to 63 by subtracting 32; it includes the space, punctuation characters, numbers, and uppercase letters, but no control characters."
[00:46] AluisioASG 392 is mark parity; if it's not there, then there was a transmission error.
[00:46] Ymgve it's not really parity then
[00:46] Ymgve just a stop bit
[00:48] Ymgve also I think you got it wrong, I think \_ is actually some CRLF thing
[00:48] Ymgve carriage return
[00:48] AluisioASG Read them as bits (in the pastebin order); ignore the 392 column; add 32 and interpret as ASCII.
[00:50] AluisioASG right (line 1 is 0111011)
[00:57] crash_demons ==========\
[00:57] crash_demons ABISM\
[00:57] crash_demons ==========\
[00:57] crash_demons REQ>@\
[00:57] crash_demons REQ>@\
[00:57] crash_demons REQ>@
[00:58] AluisioASG So, are we supposed to answer in 17201?
[00:58] Adah How did we decode it, btw?
[00:58] Adah You don't have to tell me if it's really long and involved, haha
[00:59] crash_demons Adah, even frequencies, six character bits.
Also
[07:17] crash_demons ymgve thought maybe it was yet another prompt for information from us
This are old prompts he is referring to
Code:
[2012-12-11 18:29:39] <Lurker69> has that tones zthat zhazha dont understna been solveed
[2012-12-11 18:30:26] <Lurker69> 33334/REBOOT/33335/HALT
[2012-12-11 18:30:27] <Ymgve> it is the same tones that were at the polish number
[2012-12-11 18:30:41] <Ymgve> I'm 99% certain it means "enter another code"
There is another same or similar prompt when you are entering EMERGENCY CODE