Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • I built Nightcrawler, an open-source autonomous penetration-testing agent that runs entirely on an Android phone.

    The project started with a question: how much of a real pentesting workflow could I run locally on relatively old mobile hardware, without relying on a cloud model or API?

    Nightcrawler runs a 1.2B-parameter model locally on the Adreno GPU of a OnePlus 8. The model chooses targets and tools, while a separate scope-enforcement proxy validates every command before execution. The system maintains per-host memory in SQLite, rotates between targets, matches detected versions against a local CVE database, executes multi-step playbooks, and generates a structured report.

    A few implementation details that may be interesting:

    Local inference runs at roughly 115 prompt tokens/sec and 13 generated tokens/sec. The small model only produces a usable command around 50% of the time, so much of the engineering is recovery logic, duplicate detection, persistent memory, and deterministic playbooks. Every command passes through a separate scope and safety layer rather than trusting the model to remain in scope. The project includes a dry-run mode, so the agent loop can be tested without executing real network commands or owning the phone hardware. I've had it running on my home network for the past 3 months uninterrupted

  • Have you ever tested this on a real corporate network?
  • Will this work on iphones as well.
  • little bit unrelated, but I watched the IG video and I thought the visual design of the app was cool af! what inspired the style?
  • I completely forgot that AI can very much also attack networks/devices in the wild. Interesting project.
  • Very cool project. Any plans to support running larger local models as mobile NPUs keep improving?
  • Fantastic project! Out of curiosity, do you foresee any optimization paths (like model quantization) that could lower the memory footprint down the road
  • What does the 50% look like when it fails? Garbage the parser throws out is easy to handle, but a well formed command aimed at the wrong host gets past the scope check, and you would only catch that reading the report afterward.
  • Judas Priest reference?
  • This looks interesting. My current phone is an Asus ROG Phone 3, which I think suffices (Snapdragon 865+ plus 12Gb RAM) but isn't rooted. Even on outdated Android 12 this phone covers everything I could possibly need as-is, and I don't intend to replace it. But, this might be the final push to upgrade ROM to something newer. I saw crDroid 16.0 still supports this ROG variant.

    Will this work with Nethunter Rootless, or ir Magisk support w/root imperative?

  • Why phone? This cuts out a lot of phones. Why not on a computer?
  • Many kids don’t have a computer
  • I used to red team professionally, and it is a lot easier to sneak an unauthorized phone into a facility than a computer.
  • The following rant is not against the owner/project - but...

    What an irony. I cant publish a attack surface mapping / pentesting tool i wrote which runs fully deterministic and really controlable due to "dual use" legal problems - but llm driven tools hit public space......

    sorry for the rant....

  • Completely understand, the legal landscape has really shifted around AI/LLM tools. I see tools drop everyday that spit in the face of DMCA/Copyright law but they skirt by mainly because they leverage AI
  • Are you referring to GitHub policies? I haven’t seen issues like that from people publishing security tools before.

    Metasploit is one example: https://github.com/rapid7/metasploit-framework

  • This is really regrettable. I think the biggest issue is that once such laws or case law are in place, it is really really impossible to repeal them, or to replace them with something more modern. So we're still applying horse laws to cars 100 years later.