georgeom.net

What is georgeom.net?

georgeom.net is the personal blog of George Omnet, a computer science and cybersecurity enthusiast who works as a principal software engineer. The site is mainly a working notebook: it documents his bug bounty findings and CTF (capture-the-flag) write-ups as a record of his own progress over time.

Who it is for

• Aspiring bug bounty hunters who want to see how someone scopes a target, tests it and reports a finding.
• CTF players looking for walkthroughs of challenge categories they are stuck on.
• Cybersecurity students and interview candidates who want concrete examples of applied security work rather than theory.

What you will actually find

• Write-ups of bug bounty submissions, typically explaining the vulnerability class, how it was discovered and what the impact was.
• CTF challenge solutions, usually tied to a specific competition or event.
• A projects page, plus links to his Twitter, GitHub, email and LinkedIn if you want to follow the work elsewhere.
• Occasional personal context — the homepage notes what he has recently watched and read, which gives the blog a low-key, personal tone rather than a corporate one.

How to use it

Start with the write-ups that match your current interest. If you are learning web exploitation, read a bug bounty post and try to reproduce the reasoning on a legal practice target before reading the next one. If you compete in CTFs, use the write-ups as a reference after attempting the challenge yourself; the value is in comparing your approach with his, not in copying the answer.

Trade-off to keep in mind

This is a personal blog, not a structured course or a maintained knowledge base. Coverage depends on what George has worked on recently, so you may find deep material on one topic and nothing on another. Treat it as one practitioner's field notes and pair it with other resources such as PortSwigger Web Security Academy for structured practice, OWASP for reference material, or Hack The Box and TryHackMe for hands-on labs.

A useful next step: open the blog index, pick one bug bounty write-up, and note the three steps the author took before finding the issue — that pattern is usually more transferable than the specific payload.

How can I learn from the CTF write-ups on this blog?

The write-ups are the main event here: the author describes the blog as mostly bug bounty and CTF write-ups used to document his own work over time. That framing tells you how to read them. These are working notes from someone solving challenges, not a structured course, so the value comes from following the reasoning rather than copying the final payload.

A practical way to work through them

Pick a challenge type you already have some footing in, then read with the solution covered.

1. Read the challenge description and stop. Write down what you would try first, and what the obvious dead ends are.
2. Skim the write-up's headings or tool names to see which direction the author took, then try to reproduce the first step yourself before reading further.
3. When you get stuck, read one section, close the tab, and continue on your own.
4. Afterwards, note the one technique you did not know and re-solve the challenge from scratch a week later.

That last step matters more than the reading. Recognition feels like learning but fades quickly; re-solving is what makes a technique stick.

What to extract from each write-up

• Reconnaissance habits. What did the author check before touching the interesting part? Bug bounty and CTF work both reward boring, systematic enumeration.
• Tool choice and arguments. Note which tool was used for which job, and why a simpler one would not have worked.
• The pivot. Most challenges hinge on one moment where the approach changes. Find it and ask what clue triggered it.
• Failure paths. A good write-up mentions what did not work. Those dead ends are often more instructive than the winning path.

Where this blog fits

Use it as a supplement, not a starting point. If you are new to CTFs, work through beginner-oriented platforms first so the terminology is familiar, then come here for realistic, competition-flavoured problem solving. If you already compete or hunt bugs, the write-ups are a way to see another person's methodology and compare it against your own.

For structured practice alongside the reading, picoCTF suits beginners, Hack The Box and TryHackMe offer guided and unguided machines, and CTFtime lists upcoming competitions and archives past ones if you want events to test yourself against.

A concrete first session

Take one write-up on a topic you know least about. Before reading, spend 20 minutes on the challenge yourself if it is still available, or on a similar one. Then read the write-up and write a short note in your own words covering the vulnerability class, the tooling, and the step you missed. Keep those notes; after ten write-ups you will have a personal reference that reflects your actual gaps rather than a generic checklist.

What bug bounty strategies and findings are shared here?

The site shares bug bounty work as first-person write-ups rather than as a strategy guide. George Omnet documents his own findings and methods, so you get concrete examples of how a vulnerability was spotted, confirmed and reported, not a generic playbook.

What you'll find

• Bug bounty write-ups: narrative accounts of individual findings, usually walking through recon, the vulnerable behavior and the impact.
• CTF write-ups: competition challenges solved step by step, useful for practicing exploitation and tooling in a lower-stakes setting.
• Independent research: security topics explored outside of bounty programs or competitions.

How to use it

Read a write-up for the reasoning, not just the payload. The transferable part is usually how the author decided where to look — which endpoint, parameter or trust boundary seemed worth testing — and how they turned a suspicious behavior into a demonstrable impact. If you're preparing for your first bounty reports, note how findings are framed for a triage team: clear reproduction steps, realistic severity, and a stated business consequence.

Where to go next

Start with the write-ups closest to the technology you already work with, since the recon instincts transfer better than the specific bug class. Pair this with broader community references: HackerOne for program and report-writing guidance, Bugcrowd for vulnerability taxonomy, and OWASP for the underlying weakness categories that most bounty findings map onto.

One caveat: a personal blog reflects one researcher's targets and time period. Treat each write-up as an example of a method, and check whether the technique still applies before reusing it — vendors patch, and what worked on one program may be explicitly out of scope on another.

What independent cybersecurity research is featured on this site?

georgeom.net is a personal cybersecurity blog by George Omnet, focused on documenting hands-on security work rather than publishing formal academic research. Its featured content falls into three broad areas:

• CTF write-ups – walkthroughs of capture-the-flag challenges, showing the steps taken to solve them.
• Bug bounty write-ups – accounts of finding and reporting vulnerabilities in real products and programs.
• Independent research – the author's own security investigations, published alongside the write-ups.

The site describes itself as a place to "document my work over time," so the value is in the process: how a problem was approached, what tools or techniques were used, and what the outcome was. The author is a computer science and cybersecurity enthusiast working as a principal software engineer, which suggests the write-ups lean practical rather than theoretical.

Who it suits: readers preparing for CTFs, bug bounty hunters looking for methodology, and developers who want to see how real vulnerabilities are discovered. Trade-off: because it is a personal documentation blog, coverage depends on what the author has worked on recently, not a structured research program.

Next step: browse the CTF and bug bounty write-up sections first if you want technique, or the independent research posts if you want broader findings. For additional perspectives on similar work, see HackerOne and PortSwigger.

What projects has George Omnet worked on?

The blog itself does not list a portfolio of projects. Its "Projects" link is present in the navigation, but the page evidence shows no project names, descriptions or repositories, so the concrete answer is: no specific projects are documented on the homepage.

What the homepage does establish is the author's working context and the kind of work the blog documents:

• Role: principal software engineer at Photon Insights, alongside a stated interest in computer science and cybersecurity.
• Recurring written work: bug bounty and CTF write-ups, framed as a way to document his work over time.
• Other channels: Twitter, GitHub, Email and LinkedIn are linked from the page for following activity outside the blog.

How to find actual projects

If you want project-level detail, the useful next step is the blog's Projects section, which should hold any named tools or repositories. Failing that, his GitHub profile is the more likely place for code, since write-ups tend to describe findings rather than ship software. Someone evaluating his work for a security role would get more signal from a few CTF write-ups showing method — reconnaissance, exploitation, reporting — than from a project list alone.

As general advice, when a personal site separates "Blog" and "Projects", treat the blog as evidence of thinking and the projects page as evidence of building; neither substitutes for the other.

How can I contact George Omnet or follow his work?

You can follow George Omnet's work through the social and contact links published on his blog, georgeom.net. The site's own header lists Twitter, GitHub, Email, and LinkedIn as the ways to reach him, and it describes the blog as covering bug bounty and CTF write-ups that document his work over time.

Best options depending on your goal

• Following new posts: The blog itself is the main channel, since write-ups are posted there rather than only on social media.
• Professional or work-related contact: LinkedIn is the appropriate route, and the site notes he works as a principal software engineer at Photon Insights.
• Code and technical artifacts: GitHub is where you would expect related repositories or tooling from his projects to appear.
• Direct questions: Email, if you have a specific, well-scoped query rather than a general request.
• Short updates and discussion: Twitter, which suits quick reactions to a write-up.

A practical next step

If you want to reference a specific piece of his work, read the relevant write-up on georgeom.net first and then use the matching contact link from the site header. For example, a question about a CTF technique fits a GitHub issue or email; a collaboration or hiring enquiry fits LinkedIn.

One caveat worth keeping in mind: social profiles and email addresses change over time, so treat the links currently listed on his own site as the authoritative set rather than any address you find quoted elsewhere.