NOVPUB
Chapter 60: Chapter 60: Recovering
The room was quiet, the only sound coming was from the soft whir of Jeff’s laptop. Now that he had asked all the questions he needed.
As Jessica sat nearby, clutching a pillow and watching him intently, Jeff didn’t speak.
He only glanced at the screen, his focus unwavering.
After booting EIDOLUX, he launched: razi_core --silent.
Within moments, the AI came to life behind the scenes.
RAZi, his personal digital mind, was already listening. He then proceeded with the initializing Recon.
That involved feeding the basic inputs, so he typed them in carefully.
...
Username: Jessi River
Location Guess: Leganes, Iloilo
Estimated active years: 2015–2017
Platform: SocialHub (public profile confirmed)
...
The reason for this was that before he could begin any serious recovery operation, he needed to give RAZi context, much like how a human investigator needs a case file to understand the details and background before diving into the work.
Like her username was the main identifier RAZi would use to search SocialHub.
It allowed RAZi to locate the correct profile, posts, photos, and metadata connected to Jessica’s account.
For the location, it helps RAZi filter results based on regional behavior like, IP logs, GPS-tagged photos, or timestamps that match the area.
It’s very useful for reconstructing where the account was usually accessed from.
The provided input timeframe will help RAZi focus on specific posts or login behaviors.
It narrows down recovery targets, especially when simulating old device behavior or account activity.
And of course, the platform SocialHub (public profile confirmed). It verifies that the account is publicly visible, which gives RAZi permission to begin scraping public data like posts, tags, or image metadata without triggering platform alerts.
...
razi_plugin: social_scraper.py loaded
razi_plugin: profile_matcher.py loaded
begin passive_scan(target_username)
...
razi_plugin: social_scraper.py loaded
This plugin is responsible for scraping public content from SocialHub.
The first line of code collects posts, captions, comments, and images. It extracts timestamps, locations, and device metadata like camera model, upload time, and EXIF data.
It also gathers visible interactions like friend tags, comment chains, and emoji usage.
For the second line of code, this plugin analyzes and organizes the scraped data, comparing it against the info Jeff entered.
Its job is to confirm that the public profile matches Jessica’s known activity.
It identifies key patterns, like posting hours, emoji habits, friend names, or tag locations, prioritizing the strongest identity anchors that Jeff can later use to prove ownership.
For the last line of code, this tells RAZi to start scanning the public profile, but without logging in, interacting, or sending any alerts.
The scan’s purpose is to map the profile’s public footprint, detecting activity windows and flagging anything that could be used as proof of historical access.
He didn’t log in because he was performing what’s called passive recon it’s the safest form of information gathering, ensuring no interaction or alerts are triggered during the process.
He’s only reading public data, not interacting with the platform in any way that would trigger login detection, 2FA challenges, security flags, or IP tracking linked to a user account.
After that, data began flowing across the terminal. Public posts, captions, dates and times of uploads, photo metadata, and device tags. It was all there.
"Looks like most of her posts came from her lost Oppo phone," Jeff muttered, his eyes scanning the data.
Jessica squinted at it, not understanding a thing.
...
Yaml
[POST_ID_3948]
timestamp: 2016-04-03 15:22:14
device: OPPO_A37f
os_version: Android 5.1
gps: 10.8231, 122.5485 (Iloilo)
image: IMG2048.jpg
EXIF: camera_model= Oppo; upload_time=15:22
...
"Looks like most of your posts came from that lost Oppo phone," Jeff said, his eyes never leaving the terminal.
"Mid-range model, Android 5.1. You usually uploaded stuff around 3 to 5 PM, am I correct?"
"Wait, you can see all of that?" Jessica blinked in surprise.
Jeff smiled slightly as he responded, "Well, that is because the internet never forgets."
Hearing this, she felt a little creeped out, realizing that her actions could actually be recorded.
RAZi then highlighted repeated GPS coordinates, pulling rough IP signatures from cached data across the open web.
Jeff’s fingers danced across the keyboard again, "Next part is to recreate the login environment."
He would forge the digital shadow of her old device, mirror the location, and simulate a behavioral pattern from years ago, all within EIDOLUX, invisible to the world.
And for SocialHub? It would think Jessica had come home.
Jeff’s fingers hovered briefly above the keyboard, then he initialized another submodule.
He created custom simulation inputs, each one serving a specific purpose to recreate the exact environment Jessica’s account used years ago.
...
load persona_env.py
profile: OPPO Android 5.1
location: Leganes, Iloilo
year: Approx. 2016
...
He loaded persona_env.py, activating his custom environment simulation tool.
This script told EIDOLUX to start recreating a virtual device profile, like a fake phone, but one so accurate it would fool server systems.
For the second line of code, this sets the virtual machine to mimic Jessica’s old device, the same type and operating system version that matched her past activity.
It tells SocialHub to recognize the environment as if it were her original device.
It’s just like saying. Hey, it’s me, the same phone from before.
The third line spoofs his location to match the same IP region and GPS data where her old posts came from.
Location match is a key part of SocialHub’s silent security system.
And the last line sets the environment’s behavior to match old user habits, like which emoji were trending, how the browser responded, or which version of SocialHub she used.
It makes the system think it’s operating in the past.
Lines of code scrolled past the screen as Jeff rebuilt the digital ghost of Jessica’s old phone.
All of that is part of Jeff’s digital mimicry process, and each element is critical for making SocialHub believe the login is coming from the same environment Jessica used years ago.
Then, the environment simulator responded on the screen.
...
MAC address: randomized to resemble old Oppo hardware
OS signature: Android Lollipop, mid-2010s build
Browser agent: matched from an archived snapshot of SocialHub mobile logs
Screen resolution and input delay: replicated
...
The MAC address is a unique identifier for a device’s network card.
Jeff spoofed it to look like an old Oppo phone’s hardware signature, so when SocialHub sees the request, it thinks. Ah, this phone is familiar.
For the OS signature, he simulated the device using the exact Android version, Android 5.1, that Jessica likely used.
This is important because SocialHub logs OS versions during login, and consistency equals trust.
For the browser agent, it matched an archived snapshot of SocialHub’s mobile logs.
So, every app or browser sends a user agent string when it connects, which includes the device type and app version.
He fed in an old one scraped from archive logs, making it identical to what her original app likely sent years ago.
Lastly, the screen resolution and input delay were replicated as well.
He carefully mimicked the size of her phone screen and even how fast she used to tap or type.
It’s a small detail, but some modern systems track user behavior and motion patterns for fraud detection.
...
Special thanks to ’Meiwa_Blank👑’ – the GOAT for this month, for the Golden Tickets! Love you, brotha!
Special thanks to ’Devon1234👑’ – the GOAT for this month, for the Gifts! Love you, brotha!
