#greyhack — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #greyhack, aggregated by home.social.
-
So #greyhack finally got music.
-
I used the same tactic in #GreyHack.
Step 1. Harvest exploits.
Step 2. Feed them into exploits list files.
Step 3. Plaster the target with exploits.
Step 4. Win.https://www.theregister.com/2025/10/09/rondodox_botnet_fires_exploit_shotgun/
-
Sitting here watching Hackers (the movie) and all I can think about is what a fantastic game #GreyHack is turning out to be. It’s absolutely not talked about enough, it’s such nice take on the MMO hacker simulator genre of games.
-
Taking #GreyHack for another spin. They have officially released version 0.9 now, that means hackable smart fridges and smartphones + NPC schedules, i.e. NPCs sleep and leave things unattended so you can hack them at night.
If you haven't discovered this awesome very close to real life hacking simulator yet, it's available on Steam.
-
If you've played #GreyHack, what are your thoughts on #NiteTeam4?
Seems like there are N number of missions, a few tools with no ability to create your own with exploits and a limited "internet". Should i even bother? ATM i see GreyHack as the pinnacle of hacking simulators and everything else as just toys.
-
Fixed some of my tools in #greyhack yesterday. I see now that i have tools for everything:
Tools to disable firewalls, privesc that gets you root on anything, router tunnelling, local and remote vuln scanners, a shodan scanner that scans entire /16 networks, a sweeper that scans and steals credentials (bank, mail, accounts), a version scanner to quickly find vulnerable hosts and lots more like +40k exploits for pretty much all services.
Hell, i've even ported some Unix commands from the real world to the game like which, sort, grep, uniq etc.
I feel like i'm done, i can get in pretty much anywhere and jump around in the procedurally generated networks behind each IP address in the game.
There is a nightly build (0.9) on the way with smartphones, smart fridges etc, but it is impossible to play it right now because of the constant wipes on the test server, and there are some bugs as well that plague the production version of the game, like if you rent a server, then cancel the service, you still get billed for the system you rented which sucks.
I've found a way to create a second bank account in the game, but one shouldn't have to do stuff like that to get rid of pesky bugs that drain your bank account, something that would be EASILY fixed by the developer.
Still - this is one of the best hacking games like ever but it comes with a high learning curve and a poor tutorial, expecting casual people to read through a crapload of text.
As i wrote in a review on a gaming site: "I can't understand how people without an expensive SANS course is gonna be able to enjoy this game".
-
Got bored, hacked around in a few systems in #greyhack, found artefacts of another player, one exploit tool (poorly written), a script kiddie tool called viper and a proxy builder.
All tools showing the uploader owner and access logs were not scrubbed either.
Killed all tools, replaced them with reboot (also ssh and sudo), wiped my tools + access logs then logged out.
Giggled a bit.
-
Finally adding capabilities to my rootkit in #greyhack. I can log stuff, but when i try to send something to another host, it shows up on the screen and can't be supressed. Really annoying.
-
So, today in #greyhack, i've written backdoorable versions of:
ssh, ps, kill, sudo and passwd.
I say backdoorable, because i haven't added any payloads/features to most of them - yet.
Except for PS and KILL (which don't list certain process or refuse to kill them), i have a ready to go rootkit, installable anywhere on any computer in the game.
I'm thinking logging, subversion, blocking and other bits of fun that one can have.
-
In #greyhack, I've recently started to collect shells and credentials to servers where the cops or whoever owns the system starts tracing you immediately when you connect to the system.
Gonna start giving those credentials away to other players that annoy me...
...If you remember Stargate SG-1 when they gave away gate addresses to the Aschen... "The first address is a black hole, it gets progressively worse from then on" :D
-
An example of the power of automation:
In #Greyhack, i harvested pretty much all exploits possible in firewalls, took some time but i got a list of 915 firewall disabling exploits in the game.
This morning i built a tool that leveraged them to disable almost any firewall i found in the game. It pretty much cuts like a hot knife through butter.
I've written tools to scan hosts for remote vulnerabilities. I've written tools that leverage these remote vulnerabilities to mass scan hosts for local vulnerabilities by getting a shell and uploading vulnerability scanners.
I've also written a tool to tunnel through routers, leave no trace at all and be able to compromise any network, in some cases also players.
I'm starting to feel like an ingame version of an APT...
-
If you're looking for something different to play, give #greyhack a try. I rarely promote stuff, but this is just so awesome for the security community. It's €20 on steam, but will probably be on sale soon during XMas.
-
One cool detail about #greyhack is the generated networks behind each ip in the game. Whenever you connect, the system is generated, sometimes with one node or many more and in several subnets with different access.
The system you will try to hack is filled with servers, routers, hubs, firewalls and cameras, each device having a different set of /lib/ files with different versions and different vulnerabilities. The challenge is to get into the RIGHT computer and do whatever the mission asks for (trash the system, change records, steal password/file).
I've taken a look at the latest nightly build and there, there are also smartphones (users coming going over the day), fridges/micros and other devices as well.
-
So, i wrote a local vuln scanner in #greyhack using #greyscript. Problem is that it needs a delivery mechanism to go out on remote hosts and scan for local vulns (as scanning on my machine just results in one version of each /lib/ file, pretty much pointless).
So i wrote a remote exploiter that uses the already collected remote exploits (+35K of them) to open up a shell, check if it's root, then uploads a bunch of tools, execute them, log all vulns and send them to a collection server i set up ingame (SSH), and when done - wipe all trails including files and logs that i were even on the host at all.
Now - i got close to 40K vulns, including almost 4000 local ones that i can use for privesc whenever i get a lousy guest shell.
The code was very small, but the impact was amazing. Whatever IP i go to in the game, there is always a vulnerability i now can exploit.
-
Writing a sniffer in #greyscript is quite simple. Captures credentials and sends them off to my email account. #greyhack
-
It's interesting on how many real world tactics can be used in #greyhack.
Have already written numerous attack tools, want to write a DFIR tool but the game is so red-team focused so it's difficult, still possible to find other player artefacts on hosts (often newbies). Currently also sketching out a rootkit in my head.
One of the ways to stay unhacked is to place the right versions of /lib/ files on your puter(s) and router(s), like have very difficult requirements to exploit versions of a library file or something you don't care about, like file stealing exploits on a remote machine you control.
-
I'm going full Volt Typhoon in #Greyhack, have spent more time exploiting Routers than in actual computers lately.
Main advantage? There is no pesky admin there that can initialize a trace. Most of the shells you get are guest shells, but you can still upload attack tools and do scans/pivot to other external hosts (or further routers) or go to the internal nets behind the router.
-
Improving my capabilities in #GreyHack by doing some tool development. First one (right screen) cracks wifi passwords, from best signal strength to lowest.
The left tool is a random WiFi selector that uses the list of the program to the right to randomly (and quickly) set a new WiFi network to anything but the one you were on to hide from other players and NPC administrators trying to trace you.
-
Made my first website in #greyhack. Had to be something special.
-
So, the #greyhack nightly is very beta. Scripts crash like every second and... i'm back on vanilla build.
-
*sigh* everything is 1.0.x... tops 1.0.2 #greyhack
-
So there was a new Nightly release of #greyhack. Use the keyword "nightlybuild" on the Steam Beta to subscribe to it.
That also means that i've left the "main" gameworld and all my exploits and data is totally useless as the nightly restarted all libraries from version 1.0.0. So i pushed it all to github.
Exploits: https://github.com/ProIntegritate/GreyHackGame/blob/main/exploits_0.7_vanilla.zip
Shodan data: https://github.com/ProIntegritate/GreyHackGame/blob/main/shodan_0.7.Vanilla.zip
The data is still useful if you play without the beta so, congrats, you now have a shit-tonne of exploits (like 12k + kernel_router exploits, thousands of ssh and http exploits) and 64k + 16k worth of "shodan" data (ip, services, versions)
Have fun.
-
#Greyhack. A hacking game with a player base of like 7-13 people online, but with drama enough to fill an cybersec mastodon instance...
That game needs a block/mute function badly.
-
Found a way to remotely harvest exploits from services in the game #greyhack. Gonna add a subnet scanner to it and i can pull in craploads of exploits.
The bad thing about the game is that stuff you put on remote hosts does not run when you're not logged in to them, or offline, so creating a botnet is currently not possible, but if it were i'd be able to write one that was persistent and automatically found new exploits and spread to new hosts to stay alive.
Still, kind of useful to be able to do exploit scanning enmasse instead of pulling down 1 lib at a time and scanning that as i used to do before.
-
Some of the exploits work for a range of versions in #GreyHack, in say SSH 1.0.6, there is an exploit starting from that version that also works in 1.0.7 so it's best to research/extract the exploit from version 1.0.6.
There is a way to see what "initial" version there is for an exploit, check the player exploit store and go through the versions, there will be like a reverse shell exploit that start at 1.0.6, then 1.0.7 and on until 1.0.x where it dissappears. That is the effective version range of an exploit and all you need to do is to research the 1.0.6 version and you have capabilities for that range of SSH servers.
You can call that a cheat or not, but i call it using your head.
-
Getting some statistics for what is running in #GreyHack while scanning the 1.0.x.x block so far:
Most used services:
13349 http
6075 ssh
4850 ftp
3096 smtp
1123 sql
330 repositoryHaven't found any cameras or chat servers so far. (Yeah, you can set up your own ingame chat channels by installing chat on port 6667)
Most used SSH versions in the game:
94 ssh,1.1.7
93 ssh,1.4.2
92 ssh,1.5.4
87 ssh,1.1.1
86 ssh,1.1.9
86 ssh,1.0.7
84 ssh,1.1.6
82 ssh,1.2.0
82 ssh,1.1.2
81 ssh,1.3.7
81 ssh,1.0.0
80 ssh,1.3.6
79 ssh,1.5.6
76 ssh,1.1.8
74 ssh,1.3.1
74 ssh,1.2.9
74 ssh,1.0.6
73 ssh,1.7.9
73 ssh,1.2.3
73 ssh,1.0.3
(...)Statistically is is better to attack HTTP servers in the game than SSH, but if you wanna go after SSH, the best version to exploit is 1.1.7.
I'm a big fan of having data to up the chances of succeeding in games. Unfortunately the script i wrote crashes and the server restarts a bit now and then so i can never be sure i get some data while running, also had to rewrite the code so i could resume a scan from a given octet.
-
Well, an ingame version of Shodan is now alive and kicking in #GreyHack.
Currently scanning the "internet" in the game for known service, grabbing IP, port, service version number and actual running service on the port (you can rebind services to different ports).
-
Some initial results. Lots of SSH/HTTP, the occasional FTP or SMTP server and rarely an SQL box or a Repository server #GreyHack
-
So, while playing #greyhack, i realised that i wanted a database to search through for specific services and version names so i quickly could find what i thought about.
So i thought - Shodan! then started coding...
-
Made a small summary of OSINT tools and techniques that you can use in the game #GreyHack to find out more about the network you're up against.
https://github.com/ProIntegritate/GreyHackGame/blob/main/GreyHack_Game_OSINT.txt
-
Btw, if you play #greyhack here is the source for SSHBrute, i recently added some cases for the password like:
- First character uppercase
- Dropped first character
- Added "1" at the end of the passwordThere is a total of 6 different password combos for each password tested now and it increase the success rate a bit. Ups your chances of completing missions.
https://github.com/ProIntegritate/GreyHackGame/blob/main/sshbrute.lua
