Three codes could be found hidden in the Missed Connection post on the Investigate Ingress blog.

[1] luc28mnoxmkt732ni

[2] xvezefedddfdnacgenzhfgfgxed

[3] m3m3b79cnx8k

Code #1

Observations

The passcode format is right there, go through your usual cipher routine.

Spoiler

Atbash and ROT didn’t give anything, next step is morse.

.-.. ..- -.-. ..--- ---.. -- -. --- -..- -- -.- - --... ...-- ..--- -. ..

You’ll need to reverse and swap the morse code to get the right passcode

-- -. ...-- ..--- ---.. . .-. .. .--. ... -. .. --... ...-- -.-. .-- --.-

Convert morse to text

MN328ERIPSNI73CWQ

Reverse

QWC37INSPIRE823NM

Code #2

Observations

All letters, no particular range.

[hint]Nop not morse this time, more like numbers[/hint]

Spoiler

My first instinct was to see if morse would give a pattern but nothing came out. Let’s try converting letters to numbers (a=0)

23 21 4 25 4 5 4 3 3 3 5 3 13 0 2 6 4 13 25 7 5 6 5 6 23 4 3

Now let’s pair them up.

23 21 42 54 54 33 35 31 30 26 41 32 57 56 56 23 43

A few 5 in there could mean Ascii numbers but the rest is not in the right range, should be in the 6, 7 & 8 range. Notice how they are in the 2, 3 & 4 range? Let’s atbash those numbers (1=9 and 0=0)

87 89 68 56 56 77 75 79 70 84 69 78 53 54 54 87 67

Convert decimal to Ascii

WYD88MKOFTEN566WC

Code #3

Observations

All the right ingredients, that same old cipher again.

Spoiler

Make a 4×3 grid

`m`	`3`	`m`	`3`
`b`	`7`	`9`	`c`
`n`	`x`	`8`	`k`

Read down from the upper left M

mbn37xm983ck

Invalid ? Reverse the second row

`m`	`3`	`m`	`3`
`c`	`9`	`7`	`b`
`n`	`x`	`8`	`k`

Read down from the upper left M

mcn39xm783bk

Code #1

Observations

Code #2

Observations

Code #3

Observations

Share this:

Related