In our IT guy vs ninja hacker video, a stickman IT guy walks into the data center at 2 AM and finds a ninja hacker already inside the servers. He wins the fight with four moves: a firewall shield against phishing, an MFA dodge against stolen passwords, a patch punch, and an update kick. The hacker asks how he got so strong, and the answer is the point of this post: he applies every security alert and fix as soon as it comes out.
Watch the video: https://youtu.be/J0jg_scV3js
The fight is a cartoon, but every move stands for something real that you can set up this week. Here is what each one means, and how to do it.
Why the hacker got in at 2 AM
Attacks rarely start with a ninja kicking a door down. They start quietly: a phishing email someone clicked, a reused password, or a server that missed one security update. Attackers work at night and on weekends because fewer people are watching.
That’s why the IT guy in the video doesn’t need to be faster than the hacker. He just needs to have closed the doors before the hacker arrived.
Move 1: the firewall shield (blocks phishing and unwanted traffic)
In the video, the hacker throws PHISHING shurikens and they bounce off the IT guy’s FIREWALL shield.
In real life, this is two layers working together:
- Network firewall: only the ports and services you really need are open to the internet. Admin panels, databases and remote desktop should never face the internet directly. Put them behind a VPN or allow only known IP addresses.
- Email filtering: spam and phishing filters catch most malicious emails before a user ever sees them. Turn on the protections your mail platform already includes, such as link scanning and attachment sandboxing.
Quick check: list the open ports on one of your servers today. On Linux, ss -tlnp shows every listening port. Anything you can’t explain should be closed or moved behind the firewall. For a real example of what an open port can cost you, see how to lock down an exposed Ollama server.
Move 2: the MFA dodge (a stolen password isn’t enough)
The hacker lunges with a MALWARE katana, and the IT guy side-steps with MFA.
Multi-factor authentication means a password alone doesn’t open the door. Even if a phishing page steals a user’s password, the attacker still needs the second factor.
- Turn on MFA for every admin account first, then for email, VPN and remote access.
- Prefer an authenticator app or a security key over SMS codes when you can.
- Watch for “MFA fatigue”: if a user gets sign-in prompts they didn’t start, they should deny them and tell IT.
Move 3: the patch punch (close the hole the alert warned about)
The IT guy jumps in with a PATCH punch. This is the move most teams skip, and it’s the one attackers count on.
When a security alert says a vulnerability is being exploited, the clock starts. In the N-central zero-day we covered, attackers hit servers within hours of the proof of concept going public. In the Outlook zero-day, the fix was already out, and the only question was who installed it first.
A simple patch routine:
- Subscribe to alerts for the products you run (vendor security pages plus a channel like this one).
- When an alert says “exploited in the wild”, patch that day, not at the next maintenance window.
- Test on one machine first, then roll out to the rest.
- Keep a short list of what was patched and when.
Move 4: the update kick (stay current everywhere)
The final UPDATE kick sends the hacker into the server rack. Patching fixes one known hole. Updating keeps everything current, so old holes don’t pile up.
- Operating systems, browsers, plugins and apps: turn on automatic updates where it’s safe.
- Firmware for routers, firewalls, NAS boxes and servers: check it every month.
- Software that has reached end of life gets no more security fixes, so plan to replace it.
A reminder from the WordPress world: an updated WordPress site can still be hacked if PHP itself is out of date. “Updated” has to mean the whole stack, not just the app on top.
The real secret: act on alerts fast
In the video, the hacker asks “How are you so strong?” The IT guy’s answer isn’t a tool. It’s a habit: he watches the alerts and applies every fix.
That’s why I post short security alerts as soon as a big threat breaks, with the exact steps to check and patch. You don’t have to read every security feed. You need to know which alerts matter for the systems you run, and what to do next.
Checklist: be the IT guy, not the victim
- [ ] Only needed ports are open; admin panels sit behind a VPN or an IP allow list
- [ ] Phishing and spam filtering is on for every mailbox
- [ ] MFA is on for all admin accounts, email, VPN and remote access
- [ ] You get security alerts for the products you run
- [ ] “Exploited in the wild” alerts get patched the same day
- [ ] Automatic updates are on where safe; firmware is checked monthly
- [ ] End-of-life software has a replacement plan
FAQ
Is the fight in the video real?
No. The characters and story are made up for fun, and the voices are AI-generated. The four defenses behind each move are real and worth setting up.
What is the single most important defense?
There’s no single one, but MFA on admin accounts plus fast patching of exploited vulnerabilities stops a large share of real attacks.
How fast should I patch after a security alert?
If the alert says the vulnerability is being actively exploited, patch the same day if you can. For everything else, follow your normal monthly patch cycle.
Is a firewall enough on its own?
No. A firewall limits what can reach your servers, but it can’t stop a user from typing a password into a phishing page. That’s why the IT guy also needs MFA, patches and updates.
Watch the full fight
Watch the video: https://youtu.be/J0jg_scV3js
Want the next alert before the next attack? Subscribe to Take Away Supports on YouTube for new security alerts, fixes and IT tricks, and tell me in the comments which topic you want next.
Leave a Reply