Captain Nemo: Come Back In Cyber World

Date Discovered: 03-Jul-2025 Records Exposed: 61,600 Timeline: Jun-2025 → Jul-2025

Another day, another leak. In this breach, Catwatchful has had its defenses cracked, exposing 61.6k sensitive records. Below we break it down for researchers, analysts, and curious hackers alike.

1. 🕵️ What Happened?

Catwatchful suffered a breach where attackers accessed sensitive user data such as usernames, email addresses, and hashed credentials. The breach traces back to a server misconfiguration, spotted in Jun-2025 and confirmed on 03-Jul-2025.

2. 🛠️ Technical Angle

• Vector: Misconfigured database instance exposed without proper authentication.
• Data: Usernames, email addresses, hashed passwords, and limited device telemetry logs.
• Logs: Attack correlated with unusual API activity spikes and repeated enumeration attempts.

3. 💥 Impact

The exposure affects registered users of the Catwatchful platform. Risks include identity theft, credential stuffing across other accounts, phishing campaigns, and exploitation of leaked device data. Security researchers warn this dataset could surface on underground forums or be weaponized in large-scale automated attacks.

4. 🔎 Researcher Notes

For OSINT & threat intel researchers, this dataset is a goldmine for: - Tracking credential reuse and weak password hashing schemes - Mapping user overlaps across services - Studying attacker enumeration patterns and targeting strategies

📌 Conclusion

The Catwatchful breach adds another chapter to 2025’s growing list of leaks. Researchers should watch how this data circulates across dark web markets, Telegram groups, and credential-stuffing attacks. Stay sharp, stay encrypted. 🕶️

Date Discovered: 13-Jul-2025 Records Exposed: 215,300 Timeline: Jun-2025 → Jul-2025

Omnicuris, a popular online medical education platform for doctors and healthcare professionals, has fallen victim to a data breach exposing over 215k records. With healthcare data being one of the most valuable assets in cybercrime markets, this incident raises red flags for both practitioners and patients indirectly connected to the platform.

1. 🕵️ What Happened?

Between June 2025 and discovery in July 2025, attackers infiltrated Omnicuris systems. The compromised dataset reportedly includes:

• 📧 Registered email addresses
• 👤 Full names & professional details of healthcare workers
• 🔑 Credentials (hashed, but strength unknown)
• 🏥 Possibly course completion records & affiliations

Early analysis points to a potential insecure server configuration or exposed database endpoint.

2. 🛠️ Technical Angle

• Vector: Suspected misconfigured database or weak API endpoint
• Data: Professional identities, credentials, contact details
• Scale: 215k healthcare accounts exposed

3. 💥 Impact

The fallout is particularly dangerous in healthcare and professional networks:

• Phishing risks targeting doctors & healthcare professionals
• Impersonation attacks (fake prescriptions, credentials fraud)
• Cross-platform credential stuffing attempts
• Potential compromise of patients via social engineering

This breach highlights the growing trend: cybercriminals increasingly target professional platforms that may lack enterprise-grade security but hold high-value data.

4. 🔎 Researcher Notes

For breach researchers and OSINT analysts, this dataset is a valuable case study in:

• Healthcare sector vulnerability patterns
• Linking professional identities to broader threat intel maps
• Studying credential exposure risks in niche professional networks

Sample Query

# Extracting healthcare domain accounts from Omnicuris leak
grep "@hospital.com" omnicuris_dump.txt | sort | uniq -c | sort -nr | head -20

📌 Conclusion

The Omnicuris breach is more than numbers — it’s a direct hit to the medical education sector. With 215k professional records exposed, the incident underscores how even specialized platforms can become lucrative targets for cybercriminals. For researchers, this is a reminder that professional data leaks can be just as impactful as consumer breaches. Stay alert, and remember: no platform is too niche to be exploited. 🕶️

Date Discovered: 15-Jul-2025 Records Exposed: 74,500 Timeline: Jun-2025 → Jul-2025

Another database hits the floor. This time it’s MaReads, a digital reading platform, leaking 74.5k sensitive records. Researchers tracking 2025’s surge of data theft have added this to the list of medium-scale breaches with potential long-tail impact.

1. 🕵️ What Happened?

Between June 2025 and its discovery in July 2025, attackers accessed MaReads’ systems, compromising user information. The leaked dataset reportedly includes:

• 📧 Email addresses
• 👤 Usernames
• 🔑 Possibly hashed or plaintext credentials

The exact intrusion vector hasn’t been disclosed, but early indicators suggest a misconfigured database or weak API security.

2. 🛠️ Technical Angle

• Vector: Likely misconfiguration / weak authentication layer
• Data: User login details, contact information
• Scale: 74.5k accounts exposed

3. 💥 Impact

While not as massive as other breaches, the MaReads leak poses risks of:

• Credential stuffing attacks on users reusing passwords
• Targeted phishing campaigns via stolen emails
• Exposure of linked accounts across other services

Researchers warn that such mid-tier breaches often fly under the radar but later fuel larger threat campaigns when aggregated.

4. 🔎 Researcher Notes

For OSINT analysts, this dataset offers:

• Patterns of password reuse across reading & subscription platforms
• Insight into regional digital service adoption
• Evidence of API or database mismanagement practices

Sample Query

# Quick scan of MaReads dump for reused Gmail accounts
grep "@gmail.com" mareads_dump.txt | sort | uniq -c | sort -nr | head -20

📌 Conclusion

The MaReads breach adds 74,500 more identities to 2025’s breach ledger. While smaller in size, the risks remain serious — from phishing to account takeovers. For researchers, this case is another reminder: weak configurations are still the easiest way in. Stay vigilant, stay encrypted. 🕶️

In May 2025, UK-based dessert restaurant chain Creams Cafe suffered a data breach impacting approximately 159,700 customers. The incident was publicly disclosed on July 23, 2025, and has since been added to breach monitoring databases such as Have I Been Pwned. The breach involved sensitive customer data, posing risks of phishing, fraud, and account compromise.

1. What Happened?

The breach exposed personal data of Creams Cafe customers, reportedly including names, email addresses, phone numbers, and account credentials. The exact attack vector has not been publicly disclosed, but breaches of this nature often result from SQL injection attacks, misconfigured databases, or compromised third-party services. No evidence has been shared indicating that payment card data was included, but affected users should assume their personal details are compromised.

• Records Exposed: 159,700 customers.

• Breach Date: May 2025.

• Disclosure: July 23, 2025.

• Data Involved: Names, emails, phone numbers, and possibly hashed or plaintext passwords.

2. Timeline of Events

• May 2025: Attackers gained unauthorized access to Creams Cafe’s customer database.

• July 23, 2025: Breach publicly disclosed and indexed by Have I Been Pwned.

3. How Should Customers Respond?

Affected customers should take immediate action to secure their online presence:

• Reset Passwords: Change your Creams Cafe account password and ensure it’s not reused on other services.

• Enable MFA: Turn on multi-factor authentication wherever possible to block unauthorized logins.

• Beware of Phishing: Be cautious of emails pretending to be from Creams Cafe or other brands, especially those asking for login or payment information.

• Check Exposure: Use Have I Been Pwned to verify whether your email address was part of this breach.

Conclusion

The Creams Cafe data breach affecting 159,700 records underscores how even hospitality and food-service businesses are vulnerable to cyberattacks. While no payment data has been confirmed as stolen, exposed personal information increases risks of phishing and identity abuse. Customers should reset passwords, enable MFA, and remain alert to suspicious messages. For businesses, this incident is another reminder of the importance of database security, patching vulnerabilities, and proactive breach monitoring.

On July 31, 2025, reports surfaced of a Pi-hole data breach impacting approximately 29,900 users. The breach occurred earlier in July 2025 and has since been confirmed by breach-monitoring platforms such as Have I Been Pwned. Pi-hole, an open-source DNS sinkhole solution popular among privacy-conscious users, suffered exposure of sensitive data that may include account details, email addresses, and authentication information.

1. What Happened?

The incident involved unauthorized access to Pi-hole user data, with nearly 30,000 accounts exposed. While the project is widely trusted in the open-source community for blocking ads and trackers, the breach raises concerns about security practices in self-hosted and open-source ecosystems. Early analysis suggests attackers may have exploited vulnerabilities in authentication systems or misconfigured services to gain access.

• Accounts Exposed: 29,900 users affected.

• Date of Breach: July 2025, disclosed on July 31, 2025.

• Risks: Potential exposure of email addresses and login credentials, enabling phishing and credential-stuffing attacks.

2. Timeline of Events

• July 2025: Unauthorized access to Pi-hole user accounts occurred.

• July 31, 2025: Breach was confirmed and indexed on public breach-monitoring platforms.

3. How Should Users Respond?

Although the scale of the breach is smaller compared to other high-profile incidents, it carries real risks for the individuals affected. Recommended actions include:

• Reset Credentials: Immediately change Pi-hole and related account passwords.

• Avoid Reuse: Ensure passwords are unique across services to minimize exposure from credential-stuffing attacks.

• Enable MFA: If available, use multi-factor authentication to secure logins.

• Stay Alert: Watch for phishing attempts that may leverage leaked data.

Conclusion

The Pi-hole breach serves as a reminder that even trusted open-source projects are not immune to compromise. With 29,900 user accounts exposed, the incident highlights the importance of strong credential hygiene and proactive monitoring. For privacy-focused users, the breach underscores the need to pair open-source tools with robust security practices.

A significant breach has surfaced under the name “Unigame”, affecting approximately 843,700 user accounts. The breach, originally dating back to December 2019, was publicly disclosed and added to breach databases such as Have I Been Pwned on August 8, 2025. Though several years old, the leaked credentials still pose a security threat, especially to users who reuse passwords across multiple platforms.

1. What Happened?

The Unigame breach involved the compromise of nearly 844,000 accounts, exposing sensitive user data. While the exact method of attack is not yet fully detailed, such breaches commonly result from weak password protection, unpatched software, or vulnerabilities in gaming or community platforms.

• Accounts Exposed: 843,700 users impacted.

• Timeframe: Breach occurred in December 2019, disclosed August 2025.

• Risk: Potential exposure of emails, usernames, and password hashes, which can be abused in credential stuffing or phishing attacks.

2. Timeline of Events

• December 2019: Original breach took place, data was compromised.

• August 8, 2025: Breach publicly disclosed and indexed for monitoring.

3. What Should Users Do?

Even though the data breach is several years old, the risks are ongoing due to widespread password reuse. Affected users should:

• Reset Passwords: Change any reused or weak passwords associated with Unigame or other accounts.

• Enable MFA: Protect accounts with multi-factor authentication wherever possible.

• Be Alert: Monitor inboxes for phishing attempts or suspicious login activity.

• Check Exposure: Verify account status on Have I Been Pwned to see if your email was included.

Conclusion

The Unigame breach, though stemming from December 2019, underscores how old data leaks can resurface years later and still endanger users. With 843,700 records exposed, the breach highlights the importance of proactive security practices: never reuse passwords, always enable MFA, and stay vigilant against phishing campaigns that exploit leaked information.

Cybersecurity researchers recently flagged a major breach under the name “Data Troll Stealer Logs”. This incident exposed an enormous 109.5 million account records, with the stolen data originating from around June 2025 and made publicly visible on August 13, 2025. The data has since been indexed by Have I Been Pwned.

1. What Is the Data Troll Breach?

The breach, attributed to Data Troll, highlights the ongoing threat of stealer logs — datasets collected from compromised machines and accounts. These logs typically contain usernames, emails, and plaintext or hashed passwords that cybercriminals later reuse in attacks like credential stuffing and phishing campaigns. With over 100 million entries exposed, the scale of this breach places countless individuals and organizations at risk.

• Scale of Exposure: 109.5 million records leaked across multiple services.

• Credential Abuse: Data is highly valuable for account takeovers.

• Wider Impact: Risks include identity theft, fraud, phishing, and corporate espionage.

2. Timeline of Events

• June 2025: Data was initially stolen and compiled into logs.

• August 13, 2025: Breach disclosed publicly and indexed by Have I Been Pwned.

3. How to Protect Yourself

If you suspect your accounts may have been affected, act quickly:

• Check Exposure: Use Have I Been Pwned to verify if your email appears in the breach.

• Change Passwords: Replace any reused or weak passwords with strong, unique ones.

• Enable MFA: Multi-factor authentication provides an extra layer of security.

• Stay Alert: Watch for suspicious login attempts, phishing emails, or unauthorized account activity.

Conclusion

The Data Troll Stealer Logs breach serves as another reminder that password reuse and weak authentication remain major vulnerabilities. With 109.5 million records leaked, users should not only update their credentials but also adopt stronger defenses such as MFA and breach monitoring. In today’s threat landscape, proactive security is the best shield against cybercriminal exploitation.

A new wave of cyberattacks has struck the financial services sector. Hackers have leaked 2.8 million sensitive records from Allianz Life, exposing personal and corporate data tied to both business partners and customers. This incident is part of a broader campaign targeting Salesforce data theft attacks worldwide.

When Did It Happen?

Allianz Life confirmed that the breach began with a social engineering attack on July 16, 2025, targeting a third-party CRM system believed to be Salesforce. The company detected the intrusion the following day, July 17, 2025, and immediately launched an investigation and containment measures. By late July, attackers began leaking stolen records on underground forums, with the total dataset reaching 2.8 million entries — representing approximately 1.1 million unique customers along with business partner data.

What Happened?

According to initial reports, attackers infiltrated Salesforce-linked environments and exfiltrated highly sensitive Allianz Life records. These records reportedly include:

• Customer information: Contact details, financial identifiers, and account-related data.

• Business partner details: Corporate agreements, client references, and operational insights.

• Internal records: Data that could be weaponized in future fraud or phishing campaigns.

Why It Matters

This breach isn’t an isolated event. Threat actors have increasingly focused on cloud-based CRMs like Salesforce, exploiting misconfigurations or stolen credentials to siphon massive datasets. The Allianz Life breach highlights three critical risks:

• Scale: With nearly 3 million records leaked, the exposure is vast.

• Trust: Financial institutions rely on customer confidence—breaches directly erode it.

• Re-use: Leaked data often resurfaces in phishing, identity theft, and BEC (Business Email Compromise) scams.

Ongoing Salesforce Data Theft Attacks

The Allianz Life incident ties into a larger pattern of attacks where hackers are exploiting Salesforce environments. Security analysts note that attackers leverage:

• Credential stuffing: Using previously stolen logins to access Salesforce accounts.

• API abuse: Pulling sensitive data at scale via misconfigured or unsecured APIs.

• Phishing lures: Creating convincing emails that impersonate Allianz and its partners.

Timeline of Events

• July 16, 2025: Hackers launch a social engineering attack against a third-party CRM system.

• July 17, 2025: Allianz Life detects the breach, begins incident response, and notifies authorities.

• Late July 2025: Stolen data begins appearing on underground forums.

• August 2025: Analysts confirm 2.8M records leaked, including ~1.1M unique customer entries.

How Customers & Partners Can Protect Themselves

If you are an Allianz Life customer or partner, here are key steps to take immediately:

• Change passwords: Update all login credentials linked to Allianz or Salesforce accounts.

• Enable MFA: Multi-factor authentication can block unauthorized logins even if credentials are stolen.

• Be alert to phishing: Expect targeted emails that exploit the breach. Verify before clicking links or sharing info.

• Monitor financial activity: Watch for suspicious transactions or identity misuse.

Industry Impact

This breach underlines a growing threat: financial and insurance companies are prime targets because of the sensitive nature of their customer data. Analysts predict increased regulatory pressure and mandatory security reviews for organizations relying heavily on third-party cloud services.

Conclusion

The Allianz Life data breach exposing 2.8M records is a stark reminder of the vulnerabilities tied to cloud-based ecosystems like Salesforce. Organizations must tighten access controls, monitor API usage, and implement stronger data governance frameworks. Meanwhile, customers and partners should remain vigilant, secure their accounts, and treat all unsolicited communications with caution.

Cybersecurity is no longer optional—it’s an expectation. As attackers adapt, so must enterprises.

What is the Assembly Tutor Project?

The Assembly Tutor project is an open-source educational tool designed to guide you through assembly language programming in a hands-on way. The project offers a series of lessons that cover everything from basic concepts like binary math and registers to advanced topics such as anti-debugging techniques and Return-Oriented Programming (ROP) chains.

With this tutor, you can learn by doing — with clear explanations, code samples, and interactive exercises that solidify your understanding. The project is structured in a way that allows learners to progress through different levels, from beginner to advanced, while also gaining practical skills to use in real-world programming scenarios.

Key Features of Assembly Tutor

1. Structured Lessons

The project is divided into various topics and levels, ensuring that you learn at a pace that works for you. The lessons are categorized into the following groups:

• Introductory Lessons: Learn the basics of assembly, from arithmetic operations to debugging your first programs.

• Intermediate Lessons: Explore function calls, memory addressing, system calls, and control flow.

• Advanced Lessons: Dive deep into advanced topics like anti-debugging techniques, ROP chains, and writing position-independent code.

• Digital World Lessons: Understand networking protocols, file compression formats, malware signatures, and DNS queries.

• Practice Problems: Apply your skills with problems focused on array indexing, system calls, shellcode analysis, and more.

2. Interactive Learning

Each lesson comes with exercises that help reinforce the concepts being taught. You'll be guided through writing and debugging real assembly programs, ensuring that the knowledge you gain is hands-on and practical.

3. Real-World Application

The project doesn’t just teach syntax; it shows you how assembly programming applies to real-world systems, such as working with memory, interacting with the operating system, and understanding how digital systems communicate.

4. Beginner-Friendly Approach

Even though assembly is a low-level language, the tutor starts with simple concepts and gradually increases the complexity, making it accessible for those who are new to the language. The lessons are designed to be understandable and provide plenty of opportunities to practice.

Getting Started with Assembly Tutor

Prerequisites

To use the Assembly Tutor project, you'll need the following:

• Python 3.x: Python is used to run the tutor script and interact with the lessons.

• NASM (Netwide Assembler): This tool is used to compile assembly code. It’s available via most package managers.

• A Unix-like environment: The tutor is designed to work best in Linux or macOS environments. For Windows users, it’s recommended to use Windows Subsystem for Linux (WSL) for a smooth experience.

Running the Tutor

Once you’ve met the prerequisites, getting started with the tutor is simple. After downloading the project, run the following command to launch the tutor:

python launcher.py

This will prompt you to select a lesson and guide you through the interactive exercises, making it easy to learn at your own pace.

Contributing to the Assembly Tutor Project

The Assembly Tutor project is open-source, and contributions are encouraged! If you're passionate about assembly programming and want to help improve the tutor, you can fork the repository, make your changes, and submit a pull request. Contributions can include new lessons, bug fixes, or enhancements to existing content.

Why Learn Assembly Language?

While high-level languages like Python, JavaScript, and Java dominate modern software development, understanding assembly language can provide several benefits:

• Deeper Understanding of Computers: Assembly language gives you insight into how the CPU, memory, and operating system interact. It helps you understand low-level operations that are abstracted away in higher-level languages.

• Optimization: Sometimes, writing in assembly allows you to optimize critical code to make it run faster or more efficiently, especially for performance-critical applications.

• Security: Knowledge of assembly is essential for areas like cybersecurity, reverse engineering, and exploit development. Understanding how programs interact with memory is key to both defending and attacking software systems.

License and Usage

The Assembly Tutor project is licensed under the MIT License, which allows you to freely use, modify, and distribute the code. To find more information about the licensing, refer to the LICENSE file in the project repository.

Conclusion

Whether you're just starting your journey into programming or you're looking to deepen your understanding of low-level systems, the Assembly Tutor project provides an engaging and hands-on way to learn assembly language. With structured lessons, interactive exercises, and real-world applications, you'll gain a solid foundation in assembly programming and improve your overall programming skills.

Check out the project on GitHub today and start learning assembly the right way!

Welcome to Learn RSA Interactively, a beginner-friendly project designed to teach the foundations of RSA encryption and decryption through interactive Python lessons. Whether you're a student, developer, or cybersecurity enthusiast, this project will walk you through the core principles of RSA with real examples and step-by-step guidance.

By the end of this journey, you’ll not only understand how RSA works but also how to implement and even break it under certain conditions!

🧠 Why Learn RSA?

RSA is one of the most widely used public-key cryptosystems. It forms the backbone of digital security—from securing your emails to protecting online transactions. But understanding RSA can be daunting unless it's broken down into digestible, practical lessons.

That’s where this project comes in: interactive, modular, and fun!

📁 Project Structure

The project is organized into Python-based lessons, each tackling a unique concept in RSA. These lessons are launched via a central launcher script, making it easy to navigate.

🗂 Directory Layout

RSA-Teaching-Project/
│
├── lessons/                   # All RSA lessons
│   ├── lesson_1_intro_to_rsa.py
│   ├── lesson_2_key_generation.py
│   ├── lesson_3_encryption_decryption.py
│   ├── lesson_4_security_of_rsa.py
│   ├── lesson_5_hacking_rsa.py
│   ├── lesson_6_euler_totient.py
│   └── lesson_7_practical_rsa.py
│
├── tools/
│   └── rsa_tool.py            # Additional tool for key management and encryption
│
├── launcher.py                # Interactive menu for selecting lessons
└── README.md                  # Documentation and project overview

 Features at a Glance

Here’s what you’ll explore:

1. 🔎 Introduction to RSA
   Understand RSA’s origins and importance in cryptography.

2. 🧮 Key Generation
   Learn how to generate public and private keys using prime numbers and modular math.

3. 🔐 Encryption & Decryption
   Discover how RSA encrypts and decrypts data with hands-on demonstrations.

4. 🛡️ Security of RSA
   Explore why RSA is secure and the mathematics that protects it.

5. 🧨 Hacking RSA
   Get a taste of how weak RSA implementations can be cracked.

6. 📐 Euler’s Totient Function
   Master one of the core functions behind RSA key generation.

7. 🛠️ Practical RSA System
   Build a real working encryption/decryption system with your own keys.

🚀 Getting Started

✅ Requirements

To run the RSA Teaching Project, make sure you have:

• Python 3.x installed

• These Python libraries:

1. pycryptodome (for cryptographic operations)

2. subprocess os(for script management)

Install dependencies with:

pip install pycryptodome

▶️ How to Run the Project

1. Clone the Repository

   git clone https://github.com/nemocyberworld/learn-rsa-interactively.git
   cd rsa-teaching-project
   

2. Launch the Menu

   python launcher.py
   

3. Choose a Lesson to Start Learning
   You’ll see a menu like this:

   Learn RSA Interactively - Launcher
   --------------------------------
   Select a lesson to run:
   1. Introduction to RSA
   2. Key Generation
   3. Encryption and Decryption
   4. Security of RSA
   5. Hacking RSA
   6. Euler's Totient Function
   7. Practical RSA Implementation
   0. Exit
   --------------------------------
   

📚 Lessons Overview

Each lesson is a self-contained Python script with color-coded output and guided commentary.

🥇 Lesson 1: Introduction to RSA

Get a high-level overview of RSA and why it's crucial in cybersecurity.

🧪 Lesson 2: Key Generation

Dive into how RSA keys are created using large prime numbers and modular arithmetic.

✉️ Lesson 3: Encryption and Decryption

Watch the math in action as you encrypt and decrypt sample messages.

🔐 Lesson 4: Security of RSA

Understand why RSA is hard to break—hint: it’s all about factoring large numbers.

💀 Lesson 5: Hacking RSA

Learn about real-world vulnerabilities and how poorly configured RSA can be exploited.

🔢 Lesson 6: Euler’s Totient Function

Discover how φ(n) is used to compute the private key during key generation.

🛠 Lesson 7: Practical RSA Implementation

Put everything together to create your own working RSA system.

🤝 Contributing

Want to make this project even better? Fork the repo, contribute lessons, fix bugs, or enhance features!

Pull requests are always welcome!

📄 License

This project is licensed under the MIT License.
See the LICENSE file for full details.

🙏 Acknowledgments

• RSA was developed by Ron Rivest, Adi Shamir, and Leonard Adleman in 1977.

• This project uses the pycryptodome library for all cryptographic functionality.

🧠 Ready to learn RSA the fun and interactive way?
Clone the repo, launch the menu, and let’s encrypt!

Mr Linux is a gamified, interactive Bash learning platform designed to make you love the terminal. Whether you're a beginner or a seasoned hacker, Mr Linux will sharpen your command-line skills through structured lessons, hands-on practice, and a challenging terminal-based game.

🔧 Built by Captain Nemo
📬 nemo14398@gmail.com
🗓️ Last Updated: 20-04-2025
🌐 Website: nemocyberworld.github.io

🧭 Project Structure

mr-linux/
├── main.sh                # Entry point for the learning interface
├── config.sh              # Global configuration
├── lessons/               # Structured topics and subtopics
│   ├── 01. Intro/
│   ├── 02. File & Directory Management/
│   ├── ...
│   └── 16. Gaming Time/   # Bash-based Mr Linux Game
└── README.md

🚀 Features

• 🧪 250+ interactive Bash lessons

• 📁 Categorized by real Linux topics

• 🎮 A gamified Linux challenge mode with 23 levels

• 🧠 Learn by doing: awk, sed, grep, permissions, networking, scripting, and more

• ✅ Tracks your learning and progress

• 💻 Written 100% in Bash – no external dependencies

🎓 Lesson Categories

🎮 Mr Linux Game

Your skills will be tested in the “Gaming Time” section — a multi-level Bash-based challenge arena.

🧩 Features:

• 23 handcrafted challenges

• Topics include permissions, searching, scripting, networking, logs, regex, and more

• Progress saved to ~/.mr_linux_save

🗂️ Example levels:

• level3_grep_mastery.sh

• level10_networking2_nc.sh

• level22_fork_bomb.sh

• level23_bash_gauntlet.sh

🛠️ Getting Started

Clone the repository

git clone https://github.com/nemcyberworld/mr-linux.git
cd mr-linux
bash main.sh

Run individual lessons manually:

cd "lessons/02. File & Directory Management/ls"
bash lesson.sh

💾 Save System

Your game progress is stored automatically in:

~/.mr_linux_save

Tracks:

• Completed levels

• Total points

To reset your progress, simply delete the file.

📬 Contact

• GitHub: @nemcyberworld

• Email: nemo14398@gmail.com

📄 License

Licensed under the MIT License. Contributions welcome!

🌟 Support Mr Linux

If you find Mr Linux useful or fun:

• ⭐ Star the repo

• 🍴 Fork and add your own lessons

• 🐛 Report issues or suggest improvements

• 📣 Share with fellow Linux learners

“The shell is my sword, and Bash is my spellbook.” — Captain Nemo 🐙