example IP leads to public IP space github profile is two random words main.py very generic repo name furry CVE- XXXX- XXXX- POC.py calc.exe Detected language: Chinese (simplified) exploit.rb "I found this at a garage sale" ko-fi link terminal screenshot NIST is late to the game uploaded 5 months before anybody noticed screenshot in the form of a code block "I found this at a thrift store" Slightly wrong code (skid repellent) "IT forgot to ask for this back" exploit-db doesn't credit the writer "full writeup here" leads to a dead link grainy youtube explainer blog post that reads like a lifestyle blog anime pfp "I found this in a dumpster" example IP leads to public IP space github profile is two random words main.py very generic repo name furry CVE- XXXX- XXXX- POC.py calc.exe Detected language: Chinese (simplified) exploit.rb "I found this at a garage sale" ko-fi link terminal screenshot NIST is late to the game uploaded 5 months before anybody noticed screenshot in the form of a code block "I found this at a thrift store" Slightly wrong code (skid repellent) "IT forgot to ask for this back" exploit-db doesn't credit the writer "full writeup here" leads to a dead link grainy youtube explainer blog post that reads like a lifestyle blog anime pfp "I found this in a dumpster"
(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
example IP leads to public IP space
github profile is two random words
main.py
very generic repo name
furry
CVE-XXXX-XXXX-POC.py
calc.exe
Detected language: Chinese (simplified)
exploit.rb
"I found this at a garage sale"
ko-fi link
terminal screenshot
NIST is late to the game
uploaded 5 months before anybody noticed
screenshot in the form of a code block
"I found this at a thrift store"
Slightly wrong code (skid repellent)
"IT forgot to ask for this back"
exploit-db doesn't credit the writer
"full writeup here" leads to a dead link
grainy youtube explainer
blog post that reads like a lifestyle blog
anime pfp
"I found this in a dumpster"