In high school I port-scanned the entire district network internally and sent direct prints to district HQ printers complaining about their lack of segmentation.
@SwiftOnSecurity 15 years ago as an apprentice i scanned the entire company network and triggered a warning on every computer because they installed a hidden VNC server on every machine. 300+ machines. That was fun.
@SwiftOnSecurity I did the same but instead of a complaint about network segmentation it was a picture of a man eating marmite with the caption "marmite man will eat your first born child".

@SwiftOnSecurity I was a weird kid.

(I'm still a weird adult.)

@SwiftOnSecurity I ended up finding the district datacenter and a whole pile of Very Vulnerable Servers. that was a fun time
@SwiftOnSecurity we made all the LCD displays say things like INSERT COIN or PK LOAD COOKIE
@SwiftOnSecurity I set up an email forwarding loop between myself and a few friends which brought the internal email network down for a whole week
@SwiftOnSecurity in College I used Sub7 to scan the entire network and pop-up warnings on people's computers. A Suite-mate discovered the raw text password file on our Unix pinemail server and crack the passwords.
@SwiftOnSecurity in my first corporate job I downloaded Linux (really! Not sure what distro) and was chastised for saturating the T1 for a big chunk of overnight.
@SwiftOnSecurity
I just printed out a wingdings smiley face at some huge font size to them all. Those were the days

@SwiftOnSecurity My high school after-school job my senior year was coding at the school district's computer office. This was back in the days when "the network" was 300-baud modems.

I still recall accidentally erasing the existence of a junior high school one day. (Yes, we did daily backups.)

@SwiftOnSecurity still miss the fun days of abusing β€˜net send’ in the computer lab.
@SwiftOnSecurity In my high school, the "network" was six Commodore PETs sharing a printer.

@SwiftOnSecurity In college, I would set the computer lab printer LCD status screens to say: "Please insert 25 cents" and "Warning: Low Oil"... because they were not password protected and were on the flat network.

(Not as many were thinking about this threat model in 1999 however.)

@SwiftOnSecurity in our SunOS computer room (around 200 stations) the default print job was sent with priority 1, a colleague figured out that you could send jobs with priority 0 without additional rights, so selfish me used it to get my documents printed first. I didn’t think about the angry glares of the people lining up to get their documents. Got a bit more ethical in my experiments afterwards.
@SwiftOnSecurity All I did was sniff the principal's email password and ask why it was being sent in clear text.
@SwiftOnSecurity This reminds me of an ancient situation where Google had indexed some copier web UI as it did not have a robots.txt. The model had a handy feature for printing a test page with an option to do so [x] continuously. This probably meant "until out of paper" – that was hard to tell from the other side of the Internet.
@SwiftOnSecurity when I was in high school. staff network drives were not password protected.
And class grades were in Microsoft access πŸ˜‘
And I was the one given detention for telling the #sysadmin 😭

@SwiftOnSecurity In middle school, while working a summer job, I hacked into the payroll system and gave my self a $10/hr raise. I marched into the company president's* office to show him how insecure the computer was (Early 80's PDP clone, I think. Don't recall the exact model)

The President was pleased by my efforts but the company Controller was *NOT* happy.

* Company president = dad. Lesson: Have backing of management before performing white hat hacking