Who Is Tias? Inside the World of OSINT, Digital Forensics & Game Development

Exploring the intersection of cybersecurity, open-source intelligence, gaming modifications, digital investigations, and independent software development.

Introduction: Who Is Tias?

Tias is an online alias associated with software development, gaming modifications, open-source intelligence (OSINT), digital forensics, and cybersecurity research.

My technical interests span several areas of computing, from understanding how software operates internally to developing tools that solve practical problems.

Much of my work revolves around exploring systems, examining how applications behave, automating technical processes, and experimenting with new approaches to software development.

My interests include Gorilla Tag modifications, FiveM anti-cheat investigations, digital forensic techniques, and the development of independent web-based platforms.

One of my ongoing projects is Cryptbox, a file-hosting and sharing platform designed around accessible uploads and straightforward file distribution.

This article introduces the areas I work in, the technologies I use, and the direction I want to take my projects.

Official profile: Who Is Tias?

1. Gorilla Tag: Game Modification and Development

Game modification is one of the areas that originally attracted my interest in understanding how software behaves beyond its standard functionality.

Gorilla Tag provides an interesting environment for experimenting with game mechanics, client-side behavior, user interfaces, and software modifications.

My interests in Gorilla Tag modding include:

• Mod menu interfaces and navigation systems.
• Client-side modifications and customization.
• Understanding how game systems and mechanics operate.
• Exploring software behavior and game architecture.
• Developing and testing experimental features.
• Debugging and improving modification tools.

Game modification involves more than changing how a game looks or behaves.

It requires understanding program structure, debugging unexpected behavior, managing compatibility, and recognizing how modifications interact with the original application.

These concepts apply to software engineering well beyond gaming.

The technical side of mod development

Developing modification tools can involve examining application behavior, building custom interfaces, managing software dependencies, and troubleshooting compatibility issues.

It also provides opportunities to learn about runtime environments, performance, memory management, and software architecture.

I see game modification as one area of a much broader interest in understanding how systems work.

Any future public releases or technical demonstrations will be documented through my official profiles.

2. FiveM: PC Checking and Anti-Cheat Investigations

Another area of interest is FiveM, the multiplayer modification framework associated with Grand Theft Auto V.

Competitive multiplayer environments present ongoing challenges involving cheating, unauthorized modifications, and the reliability of evidence used in investigations.

My interest in FiveM PC checking focuses on understanding how digital artifacts may help investigators evaluate suspected cheating.

Understanding PC checking

PC checking generally refers to examining a computer for evidence potentially associated with unauthorized software or prohibited game modifications.

Depending on the circumstances, investigations may involve reviewing:

• Windows event logs and system information.
• Application execution artifacts.
• File metadata and timestamps.
• Relevant process and service information.
• Software installation history.
• Game-related directories and configuration files.
• Other relevant forensic artifacts.

However, no single artifact should automatically be treated as proof of cheating.

An investigation must consider context, alternative explanations, and the possibility of false positives.

Why evidence handling matters

A reliable investigation should be transparent, authorized, and based on reproducible observations.

The presence of an unfamiliar file does not necessarily demonstrate malicious activity, just as the absence of a particular artifact does not prove that a system has never been modified.

Responsible anti-cheat investigations should prioritize consent, privacy, evidence integrity, and accurate conclusions.

My interest in this field extends beyond identifying suspicious software. It includes understanding how operating systems record activity and how technical evidence can be interpreted responsibly.

3. OSINT: Open-Source Intelligence

Open-Source Intelligence (OSINT) involves collecting, analyzing, and interpreting information from publicly available sources.

OSINT is used in cybersecurity, investigative journalism, threat intelligence, fraud prevention, and digital research.

What interests me most is how individual pieces of publicly accessible information can be evaluated and connected to produce a more complete understanding of a technical subject.

Areas of OSINT that interest me

My interests include:

Public infrastructure research

Understanding domains, DNS records, hosting infrastructure, and other publicly available technical information.

Digital footprint analysis

Examining how public usernames, websites, repositories, and online activity relate to one another.

Metadata analysis

Understanding what information files and publicly accessible resources may reveal about their origin or technical characteristics.

Research automation

Developing scripts that organize, retrieve, and process publicly accessible information.

Source verification

Comparing information across sources and identifying inconsistencies, outdated claims, or unsupported conclusions.

OSINT is not just collecting information

A large collection of data is not necessarily useful intelligence.

The real challenge is determining whether information is accurate, relevant, current, and supported by reliable evidence.

An effective OSINT workflow requires critical thinking as much as technical ability.

It also requires respecting privacy, avoiding unauthorized access, and distinguishing legitimate research from invasive behavior.

I am particularly interested in developing utilities that make public-source research more organized, transparent, and efficient.

4. Digital Forensics: Understanding Digital Evidence

Digital forensics is the process of identifying, preserving, analyzing, and interpreting information from digital systems.

It intersects naturally with my interests in OSINT, anti-cheat investigations, and cybersecurity.

Windows systems, applications, browsers, and operating environments generate numerous artifacts during ordinary use.

These artifacts can help explain how a system was used, what applications may have executed, and how particular events occurred.

Areas of interest

Some of the topics I explore include:

• Windows system artifacts.
• Application execution history.
• File system metadata.
• Event logs.
• Process behavior.
• Digital evidence interpretation.
• Forensic automation.
• Timeline analysis.

Understanding these areas requires careful attention to how artifacts are generated and what conclusions they can reasonably support.

Accuracy over assumptions

One of the most important principles in digital forensics is that evidence must be interpreted within its limitations.

A timestamp may have multiple explanations. An application artifact may persist after removal. System behavior can differ between Windows versions and configurations.

Forensic analysis should therefore rely on corroboration rather than assumptions.

My goal is to continue learning how these artifacts work and how software can assist with legitimate technical investigations.

5. Cybersecurity and Software Research

Cybersecurity is a broad field, covering everything from application security and network defense to malware analysis and digital investigations.

My interests are primarily technical and research-oriented.

I enjoy understanding how software systems communicate, how applications handle information, and how developers can improve security through better engineering practices.

Technical subjects I explore

These include:

• Python scripting and automation.
• Web application development.
• Linux environments and command-line tools.
• Windows system behavior.
• Application debugging.
• API integration.
• Software security fundamentals.
• Digital forensic utilities.
• Reverse-engineering concepts.
• Security-focused development practices.

I am interested in learning how tools work internally rather than relying entirely on their interfaces.

That approach encourages experimentation, documentation, and a deeper understanding of technical systems.

Learning through development

Building software is one of the most useful ways to develop practical technical skills.

Every project introduces challenges involving architecture, dependencies, performance, reliability, security, and deployment.

Working through these problems creates experience that theoretical study alone cannot replace.

6. Cryptbox: Building an Independent File-Hosting Platform

One of my ongoing software projects is Cryptbox.

Cryptbox is a file-hosting and sharing platform intended to provide straightforward uploads and accessible sharing links.

The project has involved working with several parts of a modern web application, including backend development, frontend interfaces, file handling, deployment, and operational security.

Technologies behind Cryptbox

My development work on Cryptbox has involved technologies such as:

Features and development areas

The project includes or has involved work on:

• File uploads and download links.
• Chunked upload handling.
• File expiration options.
• Administrative interfaces.
• Upload activity and service analytics.
• Abuse-reporting functionality.
• Virus-scanning integration work.
• Authentication and administrative security.
• Search engine metadata and indexing.
• Deployment and server configuration.

Some features are still being refined, tested, or improved.

What developing Cryptbox has taught me

Working on a file-hosting platform involves more than creating an upload button.

It requires considering storage, error handling, large file transfers, access controls, security, reliability, and the overall user experience.

Backend behavior must align with frontend expectations, and deployment introduces challenges that may not appear during local development.

Cryptbox serves as both a functional software project and an environment for expanding my understanding of web development and infrastructure.

7. My Development Environment and Technical Workflow

I work with both Windows and Linux environments, depending on the project.

Linux is particularly useful for scripting, command-line workflows, software experimentation, and technical research.

Windows remains important for application compatibility, development testing, and understanding system behavior relevant to digital forensics.

Languages and technologies

Some of the languages and tools I use or explore include:

Programming and scripting

• Python
• JavaScript
• HTML
• CSS
• Shell scripting
• PowerShell
• Java and Java-based development tooling

Development technologies

• Flask
• REST APIs
• Git and GitHub
• SQLite
• Web application deployment
• Automation scripts
• Linux development environments

Technical areas

• OSINT
• Digital forensics
• Cybersecurity
• Game modifications
• Software debugging
• Web infrastructure
• Systems research

My interests are not limited to one language or development framework.

I prefer choosing technologies based on the requirements of a project and the problems that need to be solved.

8. Why I Focus on Multiple Technical Fields

Game development, digital forensics, OSINT, and cybersecurity might initially appear unrelated.

In practice, they share several underlying concepts.

Each involves understanding systems, identifying patterns, interpreting information, and solving technical problems.

Game modifications encourage experimentation with software behavior.

Digital forensics requires careful examination of system artifacts.

OSINT emphasizes research, verification, and information analysis.

Cybersecurity combines these skills with an understanding of threats, vulnerabilities, and defensive practices.

Software development provides a way to turn those interests into practical tools.

For me, the connection between these fields is what makes them interesting.

Learning something in one area can provide useful insight into another.

9. Future Projects and Research Interests

I plan to continue expanding my knowledge and building tools across several technical areas.

Some of the subjects I want to explore further include:

OSINT automation

Creating utilities that help organize public-source research, analyze technical information, and simplify repetitive investigative workflows.

Digital forensic tooling

Exploring ways to process system artifacts, organize timelines, and present technical findings more clearly.

Anti-cheat research

Learning more about legitimate methods of identifying unauthorized game modifications while minimizing false positives and respecting user privacy.

Game modification development

Continuing to experiment with game-related tools, interfaces, debugging techniques, and software architecture.

Web application development

Improving Cryptbox and exploring new web-based utilities, automation systems, and infrastructure-related projects.

Technical documentation

Publishing project explanations, development notes, and research articles that provide useful information to other developers.

These are areas of ongoing interest rather than claims of completed products or published research.

10. My Approach to Technical Research

I believe technical work should be grounded in experimentation, evidence, and continuous improvement.

There is always more to learn, whether that involves understanding an unfamiliar operating system artifact, troubleshooting an application, or exploring a new programming language.

I try to approach projects with several principles in mind.

Understand the system. Learning why something works is more valuable than simply copying a solution.

Verify technical claims. Observations should be tested, documented, and evaluated before drawing conclusions.

Build practical tools. Software becomes especially valuable when it addresses a real problem.

Respect boundaries. Security research and digital investigations should be conducted with appropriate authorization and consideration for privacy.

Keep improving. Development is an iterative process, and early versions of a project are opportunities to identify weaknesses and make improvements.

These principles influence how I approach both software development and technical research.

11. Where to Find Tias

I use the Tias alias to organize my public technical identity and development work.

My main profile serves as a central location for information about my projects, interests, and ongoing development.

Official profile: https://cryptbox.cc/tias

Cryptbox: https://cryptbox.cc

I also use developer communities and GitHub to document technical interests, share projects, and connect with others working in related fields.

As more work becomes publicly available, I intend to use these platforms to provide clearer project histories, technical explanations, and links to released software.

Final Thoughts

Tias represents my interest in exploring technology from multiple perspectives.

From Gorilla Tag modifications and FiveM anti-cheat research to OSINT, digital forensics, and web development, I am interested in understanding how systems operate and how technical knowledge can be applied to real problems.

Projects like Cryptbox provide opportunities to turn that interest into working software, while my research interests continue to expand into different areas of cybersecurity and digital investigations.

I intend to keep learning, experimenting, building, and documenting that process.

This article is an introduction to the technical areas associated with the Tias alias, not a claim of formal credentials or independent recognition.

For more information and future project updates, visit:

Who Is Tias? — Official Profile

Written by Tias.

Software Development • OSINT • Digital Forensics • Cybersecurity • Game Modifications