Historically, codes were found on the Niantic Investigation Board. Unfortunately, on October 1 2013, Henry Richard Loeb posted this message to the board:
This Investigation Board contains the evidence of a conspiracy so vast it cannot be contained by this dimension.
We are under attack. We are at the brink of being shaped into a new species. We are wrapped in symbiotic harmony with another intelligence, somewhere, that enhances our minds when we visit The Portals.
Any or All of these statements may be true.
To those who discover this website, dive deeper. The Investigations List will lead you to the truth.
Once your eyes are open, join us at +NianticProject where the investigation continues, growing in strength and scale each passing day.
Be warned. The safety of ignorance, once shed, can never be found again.
On YouTube, the Ingress account will have weekly Ingress Report and Obsessed videos. There hasn’t been any codes discovered in Season 2 of Obsessed but Season 1 had videos embedded in the videos and in the comments.
Frame in Obsessed Episode 1 with passcode highlighted in yellow.
A comment left in Obsessed Episode 3
In the Ingress Report, codes can sometimes be embedded in the video, in the description, in the annotations, or in the keywords. There are also videos that relate to the storyline that are posted to the Ingress YouTube channel.
On Twitter, codes will be tweeted shortly before or after the “main” Niantic Project post.
On Facebook, codes will sometimes be posted within a link’s summary.
Good afternoon, Agents and Investigators! My name is Mustafa Said and welcome back, as always, to This Week in Niantic History.
So let’s begin with what was revealed on September 8th, 2013:
Shortly after Cassandra, Carrie Campbell was confirmed dead in Chicago. Shortly afterwards, H. Richard Loeb compiled a massive memorial of those who honored her. How it ties into the story-Carrie’s death struck a huge blow to the research of the Shaper Glyphs.
On September 9th, 2013, the first of three videos was released:
In it, Hank Johnson and Devra Bogdanovich, who met up in NYC during the Cassandra Anomaly, had something to discuss….
On September 10th, 2013, the second Hank and Devra video was released:
And on September 11th, 2013, the final video was released:
How they all tie into the story: Devra makes some startling revelations about her involvement with Visur and of the Shapers.
And finally, on September 12th, 2013, the twenty-fifth installment of the Ingress Report was released:
In this episode, Susanna Moyer talks about the disappearance of Oliver Lynton-Wolfe and Klue after Cassandra and the new Agent Achievement System coming to the Ingress Scanner.
Tune into DeCode Ingress next week to find out what happened next in Niantic History!
Welcome back to our 10th teardown. This version is currently on its 1% rollout via the Google Play Store. Some of you are lucky enough to have this version now, while others will be receiving it soon. However, the official description states “bug-fixes”, while we know there is a lot more under the hood. So lets take a look.
In APK since 1.55.0
Mission layouts continue to be fleshed out / slightly changed. From a purely technical standpoint, the amount of server to client code changes are little to none. All the final tweaks seem to be related to language abstraction, layout development and Field Trip.
A possible mission requirement is “View Field Trip card“. This has been a vague reference since the Field Trip classes were blank. Now they are fleshed out and we know exactly how they work. After visiting a portal (not sure if isolated to just missions), you will have an option to view the Field Trip card associated with that portal (assuming one exists). An internal web browser will open up and load that Field Trip card.
For those who don’t know. Field Trip is basically the portals of Ingress with more history and background. Take for example this Field Trip card and respective portal.
Field Trip card
Ingress portal view for that Field Trip card
A few new fields snuck into the Mission detail view called “authorNickname” and “authorTeam“. It appears the majority of Missions will be agent created with the carefully thought out and interesting ones being placed on the top of your regional mission list via good ratings. The agent name / team will be visible on the list to show who created each mission.
At the end of the day, you can’t expect Niantic to make missions for all ~25,000 regional zones, so its good to have agent created content to populate mission lists.
Missions – A Recap
Since it has been 6 versions since Missions were discovered. I thought I would do a quick overview of what we know now.
Missions will be a new tab much like “Training” in which you can launch and complete a set amount of way points for a specific mission. Missions may require you to do any of the following
Hack a Portal
Capture a Portal
Create a Link
Create a Field
Install a Mod
Take a Photo
View Field Trip card
Enter Passphrase (via clues)
You will be able to view
Number of agents who completed a mission
Percent who liked it
Average time to complete mission
After completing the mission you will be
granted a badge (not medal) for that mission to show completion
allowed to rate the mission if you liked it or not
You might have a Mission that works like this (state park based)
Visit this _________ State Park
Hack ______ Portal
View the Field Trip card for __________ Portal
Enter the Passphrase via the hints from _____________ Portal
First seen on the intel map, handshake and 1.59.1 apk. We were given clues that certain portals could stand out from the rest via the below images.
Renamed images via the original Ornaments
In addition to images above, model (.obj) files have been added for these ornaments. This ensures that these ornaments will be available to see via your scanner. On our next set of anomalies (after Helios), we will probably have an easier way to identify cluster and volatile portals.
APNS – Apple Push Notification Service?
We saw a group of new strings in this version.
<string name="APNS_ATTACK_FULL">Your portal %1$s is under attack by %2$s.</string>
<string name="APNS_ATTACK_NO_ATTACKER">Your portal %s is under attack.</string>
<string name="APNS_ATTACK_ATTACKER_ONLY">One of your portals is under attack by %s.</string>
<string name="APNS_ATTACK_GENERIC">One of your portals is under attack.</string>
<string name="APNS_NEUTRALIZED_FULL">Your portal %1$s neutralized by %2$s.</string>
<string name="APNS_NEUTRALIZED_NO_ATTACKER">Your portal %s neutralized.</string>
<string name="APNS_NEUTRALIZED_ATTACKER_ONLY">One of your portals neutralized by %s.</string>
<string name="APNS_NEUTRALIZED_GENERIC">One of your portals neutralized.</string>
<string name="APNS_MULTIPLE_ATTACK_NOTIFICATION">%1$s is attacking your portals %2$s.</string>
<string name="APNS_MULTIPLE_NEUTRALIZED_NOTIFICATION">%1$s neutralized your portals %2$s.</string>
The only strange part is that these strings were found in the strings.xml of the Android version of Ingress. I can understand some development overlap in the libGDX portion of the application (since libGDX is multi-platform) but string resources are different between Android and iOS. So maybe we labeled APNS incorrectly or are misunderstanding this feature.
Either way, it seems to have generic messages along with handling one attacker vs multiple. Maybe to stop the overwhelming spam of notifications when at an anomaly.
What are these handshake things (knobs) ?
It’s how different version of scanners communicate with one server. Features are enabled/disabled depending on your scanner version. This allows us to see future changes coming, since they are already packed in the APK. Features that stay in knobs can be disabled / enabled at whim with a server update. So for example, removing a knob does not mean its gone from Ingress. It just means it no longer needs a configuration boolean so it’s here to stay. This is how missions are in the APK for everyone but only accessible by some.
Build September 2
Leaked September 9
The two main features we are following are currently Missions and Ornaments. Both of these features are very close, if not already finished in their development cycle. So it sparks the question what will Niantic bring next? We will see what goodies are brought in 1.61.0. Until then, enjoy 1.60.0.
Good afternoon, Agents and Investigators! My name is Mustafa Said and welcome back, as always, to This Week in Niantic History!
So let’s begin with what was revealed on September 1st, 2013:
One year ago today a document surfaced on the Niantic Project Investigator Board.
It was another comic book page made by Tycho, showing us another glimpse into the events of Epiphany Night and the escape of Roland Jarvis and Devra Bogdanovich…
How it ties into the story: More info of the Epiphany Night escape were revealed.
On September 2nd, 2013, a video was released:
It was a small conversation between H. Richard Loeb and Carrie Campbell. I’ll leave the contents of the video for you to decide….
How it ties into the story: This may have been the last time anyone saw Carrie alive. After Cassandra, she vanished into thin air….
On September 3rd, 2013, a document surfaced on the Niantic Project Investigator Board:
In this conversation between J. Phillips and Ken Owen, much is learned about the secrets of who was targeting Susanna Moyer during Cassandra and the fate of the Ingress Beta…
How it ties into the story: Secrets are revealed and the mystery of who was after Moyer deepens.
On September 4th, 2013, another document surfaced on the Investigator Board:
In this Tycho Poster, we see…well, we see a person who resembles Oliver Lynton-Wolfe and a statue. We can assume that the thing in the statue is Roland Jarvis pre-13MAGNUS. You can make the phrases out yourself. But what does this mean?
How it ties into the story: Okay. SO remember this little video I reviewed last week? Here it is:
This video was taken before the events in the poster happened. We can then assume that Oliver Lynton-Wolfe went to Jarvis after the video was done and what happened in the poster-some kind of attack on Wolfe-occurred. From there, Lynton-Wolfe became dedicated to defeating Jarvis, even trying to fight back and destroy him. The result of that…I’ll cover it someday but if you were following the events of last Oct to December, you already know.
And finally, on September 5th, 2013, the twenty-fourth installment of the Ingress Report was released:
In this installment…well, you’ll have to see it yourself. All I’ll say is that it’s no regular report.
Cassandra is over. But what comes next?
Tune into DeCode Ingress, as always, next week to see what happened next in Niantic History!
Tip: compare the position of numbers to where they are in the passcode format, if they share a characteristic (in this case, they all begin with 5 and nothing else does), it’s very likely substitution is the method to use.
We’ll need to figure out the keyword to figure out how to reverse engineer how the pairs correlate to letters and numbers used in the passcode
Keyword regex pattern
We are assuming each pair of characters match up to a particular letter so the 61 in the 3rd position matches the 61 in the 6th position.
Our assumption is that the only pairs that match are the 3rd and 6th character, so ezekiel is not a candidate.
chapeau and forward remain, looking at their ASCII values:
Looking at the 3rd and 5th letter of the keyword carefully:
It looks like the B has shifted only 1 position with everything else staying the same, n and o are next to each other in the alphabet. pandora seems to be the likely candidate for the keyword.
p is next to o in the alphabet and r is close to p, let’s examine their transcribed relationship:
The B was at the end of the line for o and shifted to the beginning for p. The R stayed in the same position but the Y moved one position to the right. Likewise, the B for r is two positions away from the B for p.
The two remaining characters are a and d:
There aren’t any B’s here but there are only 2 colours in these lines compared to the 3 for n, o, p, and r.
Yellow and Blue make Green. Red and Blue make Magneta. That’s where the missing B’s went.
Noting the positions of R, Y, and B in pandora:
01234567 R Y B
BR____Y_ p 1 6 0
_M__Y___ a 1 4 1
_R___YB_ n 1 5 6
_R__G___ d 1 4 4
_R___Y_B o 1 5 7
_RB___Y_ r 1 6 2
_M__Y___ a 1 4 1
RYB matches the octal representation of the word pandora: (160 141 156 144 157 162 141):
Completing the prefix and suffix:
Prefix: R Y B
R_____YB 0 6 7
_R_B__Y_ 1 6 3
_RB___Y_ 1 6 2
_R_BY___ 1 4 3
R____BY_ 0 6 5
067 163 162 143 065
Suffix: R Y B
_R___BY_ 1 6 5
R____BY_ 0 6 5
M______Y 0 7 0
R__B__Y_ 0 6 3
_M____Y_ 1 6 1
165 065 070 063 161
We have shown that regular expressions can be used to help us look for keywords in codes. From there, it will help us get a better understanding of the steps needed to convert the code into a passcode.
Regular Expressions aren’t only useful for passcode solves. They are used in the real world for searching and replacing text in a document. Here’s a link to a XKCD comic that explores one such “real world” scenario.
We’ll be going back to our regular decoding walkthroughs but we’ll take a quick look at which social media accounts to follow to be sure you won’t miss a code.