"Know the attack, defend with how it works." Launching the Mamoru Hacker archive

##1. What this site is for: from video to text and lab records

I’m a working white hat hacker. My day job is vulnerability assessment and incident response, and on YouTube I explain how to defend against cyber attacks.

Video works well for showing the big picture of an attack and its defense. Running time and platform rules, though, leave out detailed command usage, full raw logs, and the deeper technical background.

This site organizes the technical details and lab data that the videos could not cover, and keeps them as a working knowledge base you can come back to.

##2. Content area 1: how security tools work, and how to test them safely

I explain open source security tools and assessment frameworks published on GitHub and similar sites, from a practical point of view.

Each review goes beyond translating the usage instructions and makes three things clear.

• Mechanism and impact: what traffic and processing the tool runs behind the scenes, and how far it reaches into a system.
• Red team and blue team views: how attackers use it (for example, in penetration tests), and how it looks to defenders watching logs and alerts.
• Building a safe isolated lab: how to reproduce the behavior with Docker or virtual machines on your own computer, without touching real systems.

I also cover tools that can be turned into attack tools. You cannot design an effective defense without knowing how the attack works. Every such review follows the law and ethics, and includes guidelines for trying the tool only on systems you are permitted to test or in your own isolated lab.

##3. Content area 2: primary-source analysis of vulnerabilities and incidents

I take apart newly published critical vulnerabilities (CVEs) and the techniques used in security incidents in Japan and abroad.

• Primary sources first: I do not judge from news articles or social media posts. I read vendor security advisories, CVE records, and official technical reports before I write.
• Reproduced on real machines: when I reproduce a case in my isolated lab, the post states the test date, environment, and versions at the top, and explains it with real server logs and evidence of the behavior.

##4. Writing and testing policy

Everything Mamoru Hacker publishes follows three principles.

1. No FUD: I avoid exaggeration that only spreads fear. I break down the conditions an attack needs and show how large the real risk is.
2. Start from how it works: instead of surface warnings like “don’t do this,” I show why something happens and which setting stops the chain.
3. Full sources: I keep guesses separate from facts and always list the primary sources at the end of each post.

##5. Platforms and what each one is for

I use several platforms for different purposes. You can reach them all from the links in the footer.

• YouTube (videos and Shorts): lab demos on real machines and visual explanations of how things work
• This site: detailed tool reviews, technical lab logs for vulnerabilities, and the tool database
• note: checklists and summaries tied to the videos, for general readers and practitioners
• X and Threads: daily incident news, short takes on threat intelligence, and stories from the lab
• Instagram: an archive of short videos (reels) on phone security and scam techniques