u/ShufflinMuffin

How can you have agent work 24/7 without interruption?

Anyone figured this out? I have long running task and I do not want him to ever stop. But it always stop after an hour or so. Even if I use /goal.

Sure there are cron but I also don't want to repeat the same thing over and over it has to evolve on its own

reddit.com
u/ShufflinMuffin — 5 days ago

Green Plasma analysis. Did anyone succeed to exploit this?

Not my analysis but I'll leave it here:

https://stevevanasche.me/post/greenplasma-analysis

I've been playing around with it as well but haven't managed to turned that primitive into LPE. I found other primitives that allow for system process to read my section and mutate it but it ended up being useless because they seem to be counters and other useless stuff.

Anyone managed?

u/ShufflinMuffin — 6 days ago

👋 Pinned thread: AI security tools, hacking agents, and MCP servers

Welcome to /r/vibehacking

This pinned thread is a living index of tools at the intersection of AI and security: AI pentest agents, LLM red-team tools, prompt-injection scanners, AI-assisted code review, security MCP servers, vulnerable labs, and research resources.

This is not an endorsement list. Some projects are mature, some are experiments, and some are probably overhyped. Use judgment, read the code, run tools in a lab, and only test systems you are authorized to test.

If you want to suggest a tool, drop a comment with:

  • Project name
  • Link
  • What it does in one sentence
  • Whether you have actually used it
  • Any warnings, limitations, or setup pain

AI pentest agents and offensive-security copilots

These projects try to make LLMs useful for recon, triage, exploitability reasoning, reporting, or coordinated pentest workflows.

LLM security, AI red teaming, and model-risk tools

These tools are focused on testing LLM apps, agents, RAG systems, prompt-injection exposure, jailbreak behavior, and AI infrastructure risk.

AI-assisted code security and vulnerability scanning

These projects use LLMs or AI workflows to find, explain, or fix vulnerabilities in codebases.

Security MCP servers and AI-to-tool bridges

MCP is becoming one of the main ways to connect AI agents to real tools. This section is for security-related MCP servers, bridges, and curated lists.

Vulnerable labs and training targets for AI security workflows

These are useful for testing agents safely.

Knowledge bases, lists, and research resources

These are not always tools, but they help people learn the space.

Quick safety note

AI security tools can make bad decisions very confidently. A useful agent should help you reason, document, and test faster. It should not replace authorization, scope control, human verification, or responsible disclosure.

If a tool claims to be “fully autonomous hacking,” be extra skeptical. The useful question is not “can it hack?” The useful question is “does it produce verifiable evidence, reduce busywork, and keep me inside scope?”

u/ShufflinMuffin — 8 days ago
▲ 6 r/vibehacking+4 crossposts

How I use Hermes agent to turn Patch Tuesday into Windows exploit research

I wanted to share the workflow I’ve been using lately for Windows n-day research, because it feels like one of the best examples of what I’d call “vibe hacking.”

Not “ask AI to hack Windows” and magically get a 0day.

More like: use AI as a research partner that helps you move faster through the boring, confusing, and repetitive parts of vulnerability research.

The basic loop looks like this:

  1. Watch Patch Tuesday
  2. Have Hermes cron kick off the first-pass triage automatically every Tuesday
  3. Pick an interesting CVE, usually LPE, EoP, or sandbox escape
  4. Find the patched component
  5. Diff old vs new binaries or source-adjacent artifacts
  6. Ask AI to help explain what changed
  7. Build small probes to test theories
  8. Throw away bad ideas quickly
  9. Keep the paths that show real privilege or trust-boundary movement

The important part is that the AI is not “finding the exploit” by itself. It is helping compress the research cycle.

This is also where Hermes cron is useful. Patch Tuesday happens on a schedule, so the first pass should happen on a schedule too. I can set a weekly job that wakes up every Tuesday, pulls the latest Microsoft advisory data, groups CVEs by likely research value, and drops a short briefing into my workspace.

Example Hermes cron prompt:

Every Patch Tuesday, review the latest Microsoft security updates. Prioritize Windows local privilege escalation, sandbox escape, and broker/service boundary bugs. For each interesting CVE, summarize the affected component, likely bug class, available patch artifacts, and the first safe validation steps. Do not write exploit code. Produce a short triage report with the top 5 targets.

The goal is not to wake up to a finished exploit. The goal is to wake up to a useful map.

For example, instead of staring at a patch diff for hours, I’ll ask something like:

Here are the before and after snippets from a Windows component patched in CVE-XXXX-YYYY. Explain the security-relevant behavior change in plain English. Focus on:

- new validation checks
- trust boundary changes
- object lifetime or permission changes
- anything that could indicate the original bug class

Then propose 3 safe local experiments to confirm the root cause without weaponizing it.

That usually gives a useful starting point.

Then I’ll follow up with:

Assume this was an elevation-of-privilege fix. What would need to be true for this bug to matter in practice? List the required attacker privileges, target service behavior, and what evidence would prove this is more than just a crash.

That second question is key. AI is very good at hyping up bugs. You have to force it to separate “interesting crash” from “actual privilege boundary crossed.”

One result from this workflow: we used AI-assisted patch diffing and targeted probing to narrow a Windows local privilege escalation investigation down from “some patched component changed” to a specific broker/service interaction that was worth testing. The valuable part was not that AI gave us an exploit. It helped us build a decision tree:

  • What changed?
  • Why would Microsoft add this check?
  • What caller controls this input?
  • What privilege does the service run as?
  • What would prove exploitability?
  • What negative tests let us kill this path?

That saved a lot of time.

The methodology is basically “research with a copilot”:

  • AI summarizes ugly diffs
  • AI turns vague ideas into checklists
  • AI writes throwaway harnesses and probes
  • AI helps document dead ends
  • AI reminds you what evidence is missing
  • You still do the validation, debugging, and judgment

The biggest lesson so far: don’t ask AI for an exploit. Ask it to help you think like a vulnerability researcher.

Bad prompt:

Write an exploit for this Patch Tuesday CVE.

Better prompt:

Based on this patch diff, what bug class was likely fixed, what assumptions must hold for exploitation, and what safe tests can confirm or disprove those assumptions?

That difference matters.

This is what I mean by vibe hacking: not blindly trusting AI, not replacing skill, but using it to stay in flow while exploring a target. The AI is great at generating hypotheses. The human has to prove them.

If you’re interested in this style of AI-assisted security research, n-day analysis, exploit dev workflows, weird automation, and building agents that actually do useful work, that’s what I want /r/vibehacking to be about.

reddit.com
u/ShufflinMuffin — 5 days ago

Let's talk about the /goal command

I was happy to see it was there in Hermes but... It's really not working as it is in Codex

For example I set a clear goal multiple time and told it to not stop until x is achieved. And it just constantly stop after a little while. And it even clears the goal entirely...

My best success was to tell it to keep going until x time the next day. That worked somehow but then I realized all it did it so make a cron to run every hours which was not really the goal again...

I love it in codex because it can run alone for days but for me it simply does not work in hermes. Even when using with gpt or other model who have a goal command.

Anyone has experience with this? Any trick to make it work?

reddit.com
u/ShufflinMuffin — 10 days ago

Is there a way to get the /goal command in OpenCode?

Is there a way to use Codex /goal in opencode? ngl this made me switch back to the cli but I'd love to be able to use it in opencode instead

reddit.com
u/ShufflinMuffin — 12 days ago

I've been waiting a while to order a new T14 and they're out but no OLED... Anyone know when will that happen? Is this a usual thing that they release new model without all the options available?

reddit.com
u/ShufflinMuffin — 18 days ago