Skip to content

Latest commit

 

History

History
283 lines (249 loc) · 12 KB

observer_unit_20.md

File metadata and controls

283 lines (249 loc) · 12 KB

observer_unit_20:0fcf50356

user

< - info ->

< - end of info ->

notes

no notes found

dir

  • sequince_data_0029.txt
  • intercepted_data_0087.txt
  • intercepted_data_0088.txt
  • intercepted_data_0089.txt
  • intercepted_data_0090.txt
  • intercepted_data_0091.txt
  • intercepted_data_0092.txt
  • intercepted_data_0093.txt

file sequince_data_0029.txt

63527461d2d7f5e457e511def810
e02fed826b0d63527461d2d7f5e457e51
1def810e02fed826b0d63527461d2d7f5e457e511
def810e02fed826b0d63527461d2d7f5e4
57e511def810e02fed826b0d63527461d2d7f5e4
57e511def810e02fed826b0d63527461d2d7f5e457e511def8
10e02fed826b0d63527461d2d7f5e45
7e511def810e02fed826b0d63527461d2d7f5e457e51
1def810e02fed826b0d63527461d2d7f5e457e511def810e0
2fed826b0d63527461d2d
7f5e457e511def810e02fed826b0d
63527461d2d7f5e457e511def810e02fed826b0d
63527461d2d7f5e457e511def810e02fe
d826b0d63527461d2d7f5e457
e511def810e02fed826b0d63527461d2d7f5e457e511def810e02fed826b0d

file intercepted_data_0087.txt

[08.09.11] N5RHGZLSOZUW4ZZAORQXEZ3FOQQGE6JAMNQXELBAORQWS3DJNZTSAIBA
[11.03.38] J5KDAMJOEBKGQYLUEBRTK4RANFZSA43UNFWGYIDGN5WGY33
[--.09.15]
[11.03.49] XNFXGOIDVOMXAUT2UGAZC4ICZN52SA5DINFXGWIDJOTRIBGLTH
[08.10.16] ORQXEZ3FOQQGS4ZANVXXM2LOM4WCA53FEBQXEZJAMNWG643F
[11.10.56] NYQG6ZTGEEFCAIBA
[11.05.38] 4XC4CSPKQYDCLRAIZ2WG23JNZTSA33COZUW6ZLTNR4SCICXMX
[11.09.22] GGYLSEBRGI5BAMRXW5YUATF2CA4TV
[08.11.21] NNSWK4BAMRUXG5DBNZRWKLBAMRXW4J3UEBTWK5BAMNQXKZ3IOQQCAIBA
[11.08.41] THEZLBNMQG6NLUFQQGU5LTOQQGI4TJOZSSA5DIMUQ
[--.00.14]
[11.06.42] QQG65LUEBQWE33VOQQHI2DFEBWTM43TNFXGOIDEN5RXGIDTN5
[08.12.35] OVXGIZLSON2G633EFQQGQ2LHNB3WC6JAN
[11.06.33] RIBGLSMUQGEZLJNZTSA5BQNFWGKZBBEBKGQZLZEBTG65LOM
[11.07.19] WWK2DPO4QQUT2UGAZC4ICBNRZGSZ3IOQWCAZDPN3RIBGLUEB
[08.14.38] Z2W2YTFOIQEKUSSJ5JCYICFKJJE6URANBUWO2BAONYGKZLE

When the lines are reordered by the timestamps at the start, we can decode parts with Base32: N5RHGZLSOZUW4ZZAORQXEZ3FOQQGE6JAMNQXELBAORQWS3DJNZTSAIBAORQXEZ3FOQQGS4ZANVXXM2LOM4WCA53FEBQXEZJAMNWG643FNNSWK4BAMRUXG5DBNZRWKLBAMRXW4J3UEBTWK5BAMNQXKZ3IOQQCAIBAOVXGIZLSON2G633EFQQGQ2LHNB3WC6JANZ2W2YTFOIQEKUSSJ5JCYICFKJJE6URANBUWO2BAONYGKZLEJ5KDAMJOEBKGQYLUEBRTK4RANFZSA43UNFWGYIDGN5WGY33XNFXGOIDVOMXAUT2UGAZC4ICZN52SA5DINFXGWIDJOTRIBGLTH4XC4CSPKQYDCLRAIZ2WG23JNZTSA33COZUW6ZLTNR4SCICXMXRIBGLSMUQGEZLJNZTSA5BQNFWGKZBBEBKGQZLZEBTG65LOMQQG65LUEBQWE33VOQQHI2DFEBWTM43TNFXGOIDEN5RXGIDTN5WWK2DPO4QQUT2UGAZC4ICBNRZGSZ3IOQWCAZDPN3RIBGLUEBTHEZLBNMQG6NLUFQQGU5LTOQQGI4TJOZSSA5DIMUQGGYLSEBRGI5BAMRXW5YUATF2CA4TVNYQG6ZTGEEFCAIBA

observing target by car, tailing   target is moving, we are closekeep distance, don't get caught    understood, highway number ERROR, ERROR high speed
OT01. That c5r is still following us.
OT02. You think it's?..
OT01. Fucking obvioesly! We're being t0iled! They found out about the m6ssing docs somehow!
OT02. Alright, don't freak o5t, just drive the car bdt don't run off!

the misplaced letters are like this:
5→a (c5r)
e→u (obvioesly)
0→a (t0iled)
6→i (m6ssing)
5→u (o5t)
d→u (bdt)
5e065d

file intercepted_data_0088.txt

[15:02:37] Encrypted data: NU9UMDEuIFdlIApoYXZ
[15:02:38] Encrypted data: lIAp0byBsb3NlIApkdGhlbS
[15:02:39] Encrypted data: EgVGhleeKAmXJlIAowZ
[15:02:48] Encrypted data: 29ubmEgCmtpbGwgdXMh
[15:02:49] Encrypted data: Ck9UMDIuIE5vLCB3ZS
[15:02:59] Encrypted data: Bkb27igJl0LiAKNEl04oC
[15:03:03] Encrypted data: ZcyBiZXN0IHdlIGxldCB0
[15:03:27] Encrypted data: aGVtIHN0b3AgdXMuIApXZS
[15:04:24] Encrypted data: Bkb27igJl0IGhhdmUgYW55
[15:04:34] Encrypted data: dGhpbmcgCjJvbiB1c
[15:04:41] Encrypted data: ywgcmVtZW1iZXI/IA
[15:05:06] Encrypted data: pUaGUgZG9jcyBhcmUg
[15:05:11] Encrypted data: CjZpbiBhIHNhZmUgCnBsYWNl
[15:05:17] Encrypted data: LiBUaGV5IAp3b27igJl0IGZpbmQg
[15:05:23] Encrypted data: CjNhbnl0aGluZy4gCi8vIGhvdyBuYWl2
[15:05:31] Encrypted data: ZSBpcyB0aGF0PyAK

The first 11 lines upto the / form this text when decoded with base64: (and encoding set to UTF-8)

5OT01. We 
have 
to lose 
dthem! They’re 
0gonna 
kill us!
OT02. No, we don’t. 
4It’s best we let them stop us. 
We don’t have anything 
2on us, remember  

After the slash the text goes like this:

The docs are 
6in a safe 
place. They 
won’t find 
3anything. 
// how naive is that? 

The weird inserted numbers and letters form this: 5d04263

file intercepted_data_0089.txt

//
< Corrupt data > T1QwMS4gU3VzcGljaW9uIGlz < /Corrupt data >
< Corrupt data > IGVub3VnaCB/3mb3IgdGhlb < /Corrupt data >
< Corrupt data > SEgVGhleeKAmWxsIGNsYXAg < /Corrupt data >
< Corrupt data > dXMgYW5kIGJ1cnkgdXMgb/4GlrZ < /Corrupt data >
< Corrupt data > SB0aG9zZSBib2RpZXMgZ < /Corrupt data >
< Corrupt data > nJvbSB0aGUgZXhwZXJpbWVudHM < /Corrupt data >
< Corrupt data > hCk9UMDIuIFllYWggYW5kIGhvd < /Corrupt data >
< Corrupt data > yB3aWxsIHRo/6ZXkgZXhwbGFpbiB0 < /Corrupt data >
< Corrupt data > aGF0IHdlIGRpc2FwcGVhcmVkIG9 < /Corrupt data >
< Corrupt data > uIGEgc2ljayBsZWF2ZT8gV2UgaGF2ZSB < /Corrupt data >
< Corrupt data > mYW1pbGllcywgdGhleeKAmWx/dsIGJlIG < /Corrupt data >
< Corrupt data > xvb2tpbmcgZm9yIHVzLgog < /Corrupt data >

If we take a single character after each slash, we get 346d. Then we can take all the remaining text and decode it with Base64 to get

OT01. Suspicion is enough for them! They’ll clap us and bury us like those bodies from the experiments!
OT02. Yeah and how will they explain that we disappeared on a sick leave? We have families, they’ll be looking for us.

file intercepted_data_0090.txt

T1QwMS4gTXkgd2lmZSB3b3VsZCBsb3ZlIHRvIHRha2UgYSBjb3VwbGUgbWlsbCBhbm
QgZm9yZ2V0IGFib3V0IG1lLiBBbnl3YXksIGl0J3MgVGVycmFHcm91cCwgdGhleSdsbC
Bjb3ZlciB0aGUgdHJhY2tzIGFuZCB0aGF0J3MgaXQhIC8vIGRydW0gcm9sbOKApiBoZ-7
eKAmXMgcmlnaHQuCk9UMDIuIENhbG0gdGhlIGZ1Y2sgZG93biBhbHJlYWR5ISBBbm-e
QgbGV0IG9mZiB0aGUgZ2FzLiBEb27igJl0IGxldCB0aGVtIGtub3cgd2Ugbm90aWNlZC-a
B0aGVtIHRhaWxpbmcgdXMuIFdlIGFyZSBqdXN0IGdvaW5nIG9uIGEgdmFjYXRpb24sI-2
HRoYXTigJlzIGl0LiAvLyBzb21lb25lIHJlYWxseSB3YW50ZWQgdGhlbSB0byBub3RpY2UK

If we remove the charactes after the dashes, we can decode the whole text with Base64:

OT01. My wife would love to take a couple mill and forget about me. Anyway, it's TerraGroup, they'll cover the tracks and that's it! // drum roll… he’s right.
OT02. Calm the fuck down already! And let off the gas. Don’t let them know we noticed them tailing us. We are just going on a vacation, that’s it. // someone really wanted them to notice

The removed characters are 7ea2.

file intercepted_data_0091.txt

rot
T1QwMS4gT2theSwg
OUY+Mj/igKYgU2h
pdCwgdGhleeKA
mXJlIGNhdGMw
QzZEIHVwISBU
aGV54oCZcm
UgQEZDZX
JpbmcgdXM
hCk9UMDIu
IEZ1Y2tpbm
cgZHJpdmU
hIFRoZXnigJl
yZSA0NkQwa
W5nIHRvIHB1c
2ggdXMgb2ZmIQ
otIC0gLSB0aXJlcy
BzY3JlZWNoaW5nI
C0gLSAtIEY/OkUKLS
AtIC0gcmVjb3JkaW5n
IGVuZCAtIC0gLSAwX1
9gCmNiMjhjYTIyNWE4CiAg
4792

All lines (except the first and the last) connected together can be decoded from Base64:

OT01. Okay, 9F>2?… Shit, they’re catc0C6D up! They’re @FCering us!
OT02. Fucking drive! They’re 46D0ing to push us off!
- - - tires screeching - - - F?:E
- - - recording end - - - 0__`
cb28ca225a8

If we take the weird characters and run them through ROT47 (as hinted by the first and the last lines of the file) we get a name of another account:

9F>2?0C6D@FC46D0F?:E0__`
->
human_resources_unit_001

We can take all the excess characters from the previous files

  • 00875e065d
  • 00885d04263
  • 0089346d
  • 00907ea2
  • 0091cb28ca225a8

Which forms the string 5e065d5d04263346d7ea2cb28ca225a8, which is a password for human_resources_unit_001.

file intercepted_data_0092.txt

OUY+Mj8wQzZEQEZDNDZEMEY/OkUwY19f

Decoded with Base64 and then ROT47 gives human_resources_unit_400

file intercepted_data_0093.txt

[16.12.20** 18:12 UTC] System idle, no input. Code: GJ3TQY
[16.12.20** 18:15 UTC] LOGIN ATTEMPT! Result: FAILED Reason: WRONG PASSWORD
[16.12.20** 18:16 UTC] LOGIN ATTEMPT! Result: Success. Code: 22M53X
[16.12.20** 18:18 UTC] TGmessanger.exe run, build 20.112.AOKWJ , secured channel established. Code: RSVQR
[16.12.20** 18:19 UTC] ObserverFrame.exe run, build 14.12.00. secured channel established. Code: CWHFY
[16.12.20** 18:20 UTC] Services protected, protection protocol one HGSTP , protection protocol two LE4GS5
[16.12.20** 18:22 UTC] Data stream exchange started. Data ray code: LZJRBH
[16.12.20** 18:23 UTC] Data stream exchange started. Data ray code: U5DKG
[16.12.20** 18:24 UTC] Data stream recieving. Data size: 2.34 gb. Data ray code: JYXIRS
[16.12.20** 18:25 UTC] Browser.exe started. Connection established. Code: VJZFG
[16.12.20** 18:26 UTC] Browser.exe data access request. Access denied. Code: 4UTIIUY
[16.12.20** 18:28 UTC] Browser.exe data access request. Access granted.
[16.12.20** 18:30 UTC] Browser.exe data streaming. Data stream: aHR0cHM6
[16.12.20** 18:31 UTC] Browser.exe data streaming. Data stream: Ly9jbGNr
[16.12.20** 18:32 UTC] Browser.exe data streaming. Data stream: LnJ1L1ZtcjNn
[16.12.20** 18:33 UTC] Services protected, protection protocol one W6RST , protection protocol two PBCHE
[16.12.20** 18:34 UTC] Services protected, protection protocol one R2YIRC , protection protocol two TC4TZM
[16.12.20** 18:35 UTC] Error! Missing data! Erorr code: FBFAUTJ. Data stream: IFEGWNS
[16.12.20** 18:36 UTC] Services protected, protection protocol one OGY4HGQ , protection protocol two KRMV3
[16.12.20** 18:37 UTC] Error! Missing data! Erorr code: VOZLOKRJ. Data stream: Q====

The datastream connected together results in aHR0cHM6Ly9jbGNrLnJ1L1ZtcjNn, which can be decoded from Base64 to https://clck.ru/Vmr3g
This link redirects to https://www.youtube.com/watch?v=dQw4w9WgXcQ&ab_channel=RickAstley, which is Rick Astley - Never Gonna Give You Up (Official Music Video) - the Rickroll

All the weird codes written in capitals connect to GJ3TQY22M53XAOKWJRSVQRCWHFYHGSTPLE4GS5LZJRBHU5DKGJYXIRSVJZFG4UTIIUYW6RSTPBCHER2YIRCTC4TZMFBFAUTJIFEGWNSOGY4HGQKRMV3VOZLOKRJQ====
, which can be decoded first with Base32 and then 5 times with Base58 to observer_unit_12



The full story from this user:

(slightly modified to make sense in English - fixed typos and replaces weird numbers. So don't take this for future deciphering)

observing target by car, tailing ... target is moving, we are closekeep distance, don't get caught ... understood, highway number ERROR, ERROR high speed

OT01. That car is still following us.
OT02. You think it's?..
OT01. Fucking obviously! We're being tailed! They found out about the missing docs somehow!
OT02. Alright, don't freak out, just drive the car but don't run off!

OT01. We have to lose them! They’re gonna kill us!
OT02. No, we don’t. It’s best we let them stop us. We don’t have anything on us, remember? The docs are in a safe place. They won’t find anything. // how naive is that?

OT01. Suspicion is enough for them! They’ll clap us and bury us like those bodies from the experiments! OT02. Yeah and how will they explain that we disappeared on a sick leave? We have families, they’ll be looking for us.

OT01. My wife would love to take a couple mill and forget about me. Anyway, it's TerraGroup, they'll cover the tracks and that's it! // drum roll… he’s right.
OT02. Calm the fuck down already! And let off the gas. Don’t let them know we noticed them tailing us. We are just going on a vacation, that’s it. // someone really wanted them to notice

OT01. Okay, … Shit, they’re catching up! They’re nearing us!
OT02. Fucking drive! They’re going to push us off!
- - - tires screeching - - -
- - - recording end - - -