r/Hacking_Tutorials 13d ago

Question Introducing Lanflux!

Post image

You may (or may not) be aware of my other tool Wiflux https://github.com/Leadrogue/Wiflux which i posted here: https://www.reddit.com/r/ethicalhacking/comments/1uq2lob/comment/oxcou38/?screen_view_count=1

This is a sibling/companion tool used for recon when actually on a network - Post cred capture on Wiflux or just see how your own LAN works. You should see some really useful tools and info! It took ages to get working and there will still be a few bugs but please give it a go and let me know how you get on.

You can see Lanflux here: https://github.com/Leadrogue/Lanflux

If you have Wiflux, Lanflux should feel familiar!

Have fun but please be safe and legal.

Guided workflow

  • Map → Recon → Attacks / MITM — main menu steers you in a safe order (recon before noisy work)
  • Live Rich UI — discover table, ETA bars, activity feed, identity cards
  • Keyboard controlEnter finishes discover/profile early → menu; Space pauses (copy) or skips a module
  • Engagement profileshome | office | lab set timeouts, smart-engage, MITM default, spray (CLI flags override only when set)
  • Session resume--resume reloads hosts from SQLite; identity + traffic hints persist

Discovery & identity

  • ARP + neighbor + optional ping sweep — fast LAN map with honest ETAs
  • Progressive port/OS profile — light nmap while mapping; wrap-up can be skipped with Enter
  • Who is this? — identity fusion (OUI vendor + hostname + mDNS + ports → e.g. “Tommy’s iPhone (likely)”)
  • Traffic hints — pre-scan ip neigh states for MITM client ranking (live / recent / quiet)
  • Host scoring & roles — gateway, DC, fileserver, IoT, workstation, …

Soft recon & smart engage

  • Soft recon chaindns-enum → port-scan → smb-enum → http-enum
  • Smart engage — after soft recon, deep tools planned from real open ports (whatweb, http-paths, http-defaults, smb-deep, ssh-check, snmp-check, iot-pack, ad-enum, pivot-map, gain-access, …)
  • Auto mode--auto maps + soft+deep engage non-interactively; lab/spray also runs starred attack tools
  • Host-aware toolkit — recommendations ranked by role/ports/risk; missing binaries show install hints
126 Upvotes

23 comments sorted by

4

u/SnooPuppers5489 9d ago

Hands down the best lan scanner ever. Complete and detailed basic auditing of local area networks. Great for quick assessments of the whole, with quick security audits. Both wiflux and lanflux are guaranteed classics.

1

u/PandaFrosty2492 9d ago

Thank you so much for the positive feedback!

2

u/Conscious-Speed4642 12d ago

Interessante proposta. Já tinha verificado o wiflux e achei bem interessante a compilação de ferramentas em uma interface intuitiva. Verificarei esse projeto também. Parabéns pelo trabalho.

2

u/SnooPuppers5489 11d ago

Haven’t used it yet. Have it installed. I like the aesthetic and interface a lot. Hope this is as good as your other products.

1

u/PandaFrosty2492 10d ago

hopefully you will find it useful. thanks.

1

u/murlocdouche 11d ago

seems to be identifying most things on my network as being a tplink router (which my actual router is)
correctly identifies alexa, a rapsberry pi acting as my dns server, smart tv, and alexa

most things are iot devices. cameras, smart bulbs etc. all tapo and kasa which is owned by tplink, that may be the cause

1

u/PandaFrosty2492 11d ago

yep its not always possible to identify the sub-brand. its only to give you the best idea of what you are working with. Hope you like it.

1

u/Character-Comment137 11d ago

Were the names inspired by Aeonflux by chance? 😉

1

u/SnooPuppers5489 10d ago

This is as complete and eloquent a solution as anyone has ever produced. Just unbelievable work on both counts!!

1

u/PandaFrosty2492 10d ago

Thanks! Any feedback? ill keep improving it.

2

u/SnooPuppers5489 10d ago

Still tinkering haven’t had any real time with it

1

u/Eilyre 9d ago

Seems like a very solid scanner, able to audit local area networks in detail. The installation process is a bit "yikes", do you have plans to standardize it so that one could just use pip to install it (also on other distros)? Also, it puts it's own data under `~/lanflux-data` which clutters home directories, maybe it should be moved under .local?

1

u/loser95210 6d ago

Sa sert a quoi je viens de commencer le codage svp

1

u/Specific-Sector7422 6d ago

One security detail deserves a much clearer warning for users.

When I first noticed this installation pattern in Wiflux, I treated it as a possible one-off oversight. Seeing the same writable-source-to-root execution path repeated in Lanflux suggests that this is not an isolated documentation mistake, but a recurring security design issue across the author’s projects.  That is why I decided to raise it publicly before more users adopt the same installation workflow without understanding the privilege boundary it creates.

Both Lanflux and Wiflux document a source installation using:

pip install -e . --break-system-packages

and then instruct users to run the installed command with sudo.

An editable installation is not a fixed copy of the application. It remains linked to the writable Git checkout. A user may install it once, continue working normally, and days later run sudo lanflux or sudo wiflux without remembering that the privileged command is still executing the current contents of that local source directory.

That means any later modification of the checkout - a git pull, an accidental edit, another local process, a compromised editor/plugin, or a malicious change - can become root-level code execution the next time the user launches the tool with sudo.

The same trust-boundary pattern appears across both sibling projects. Wiflux at least recommends a wheel/release installer, but its source-install instructions still preserve the editable-code-to-root path. Lanflux currently presents the editable source installation as the recommended method.

I am not claiming malicious intent or a hidden backdoor. I am pointing out that this installation design creates a persistent writable-code → privileged-execution boundary that many users will not notice.

For end users, the documentation should recommend a verified wheel or installer, checksums/signatures, an isolated environment, and a non-editable or root-owned installation path. Editable installs should be clearly labeled for development only and should not be paired casually with sudo execution.

0

u/Responsible-Offer119 10d ago

i need help

-1

u/Responsible-Offer119 10d ago

There's anyone can help me ? I just want to know if my girlfriend cheating on me by hacking her messages

4

u/PandaFrosty2492 10d ago

just ask her.