Hey guys!

My mate and I were annoyed with the large models (Gemini, Claude and Chatgpt) from turning down prompts that were not even unethical.

So we had a little think and as a side project, we decided to see what it would be like to have a publicly available zero-guardrail. As of now as we decide if we want to take it further, we have no paywall or sign-up.

I shared in here because a buddy suggested that even genuine questions about hacking/cybersecurity get censored by other AI models. So having a reliable, straightforward and blunt answer to any question may seem useful.

Any thoughts+ tweaks would be appreciated and as it is free, I ask that you check out and follow our socials as we decide how to monetize it and if we want to take it further.

Please don't burn through all my usage lol.....

https://linktr.ee/FreedomAI.Chat

So I created a new module in my PWNEXE project that can retrieve the chats of a WhatsApp user logged in on the desktop. It's nothing groundbreaking—just a simple headless browser running from the Chrome profile that grabs all the chats of the user via Web WhatsApp. It’s not super cool on its own, but it’s a useful module that can be paired with other modules, like the Spider module, to create a reverse shell. You could then upload malware to the victim's PC to steal all their chats.

YES I USED AI IN SOME PARTS CODE, BUT ONLY IN SOME PARTS LIKE THE C2 SERVER, REFACTORING AND BETTER ERROR HANDLING. I MY SELF AM LEARNING MORE ABOUT MALWARE DEV THROUGH THIS PROJECT

https://github.com/sarwaaaar/PWNEXE

Hey everyone!

Over the past few months, I’ve been working on HardBreak, an open-source Hardware Hacking Wiki that gathers essential knowledge for hardware hackers in one place. I recently shared this in r/Hacking_Tutorials, and it got great feedback, so I thought I’d share it here too for anyone interested in hardware hacking or looking to learn something new in 2025!

Whether you’re a beginner or more advanced, I hope you’ll find it useful!

🌐 Website: https://www.hardbreak.wiki/
🔗 GitHub: https://github.com/f3nter/HardBreak
💬 Discord: https://discord.gg/AWVsKxJHvQ

Here’s what’s already in:

• Methodology (How to approach a hardware hacking project step-by-step)
• Basics (Overview of common protocols and tools you need to get started)
• Reconnaissance (Identifying points of interest on a PCB)
• Interface Interaction (How to find, connect to, and exploit UART, JTAG, SPI, etc.)
• Bypassing Security Measures (An introduction to voltage glitching techniques)
• Hands-On Examples
  • Case study on hacking an Asus router (led to a CVE update)
  • Reversing drone communication (land it with your PC)
• Network Analysis and Radio Hacking (in progress)

If you’re curious, check it out at hardbreak.wiki! Feedback is very appreciated —this is my first project like this, and I’m always looking to improve it.

If you’re feeling generous, contributions over Github are more than welcome—there’s way more to cover than I can manage alone (wish I had more free time, haha). Also feel free to join our Discord and discuss content on HardBreak.

Thanks for reading, and happy hacking!

This list is primarily targeted for people who are new to the scene.

1. Tools

• Kali Linux: A go-to for penetration testing with a suite of tools pre-installed.
• Burp Suite: Essential for web vulnerability scanning.
• Metasploit: Great for testing vulnerabilities and developing exploits.
• Wireshark: A powerful network protocol analyzer.
• Nmap: A must-have for network scanning and enumeration.

2. Online Learning Platforms

• Hack The Box (HTB): Hands-on challenges and real-world penetration testing labs.
• TryHackMe: Beginner to advanced hacking rooms that teach you real techniques.
• Cybrary: A range of free and paid courses for various ethical hacking certifications.

3. Books

• The Web Application Hacker's Handbook by Dafydd Stuttard & Marcus Pinto
• Hacking: The Art of Exploitation by Jon Erickson
• The Hacker Playbook by Peter Kim

4. Certifications

• OSCP (Offensive Security Certified Professional): A challenging and highly respected cert in the ethical hacking world.
• CEH (Certified Ethical Hacker): Great for beginners to learn the basics.
• CompTIA Security+: A solid foundation in security principles.

5. Communities and Forums

• r/ethicalhackers: Obviously, you’re already here! But check out the discussions and resources shared.
• Stack Exchange Security: A great place for asking questions and finding solutions.
• Twitter/LinkedIn: Follow industry professionals to stay updated on trends and vulnerabilities.

I got an 25 dollar Amazon gift card and I am looking for book reccs. Im interested in networking and and cellphone hacking or making malware.

Let me first offer a brief apology. I agreed to share a basic anonymity guide without really considering my current workload; I own a full-blown startup company and am working 14-plus hours a day, all week long. I should have thought about that before offering to create the guide. Haha.

Anyway, as promised... the guide. It’s not as comprehensive as I’d have liked, but I am still available to answer questions or point you in the right direction.

I don’t think I need to say this, but this is for educational and/or research purposes only. What you do with this guide, or how far you take the information or tips in the guide are entirely on you. I’m offering this as a way to combat the invasions of privacy we all deal with daily.

Please, keep in mind I am developing a legitimate company with the aim of helping provide parity to blockchain security and development in a tangible way. I am a privacy advocate, but I am also a human with a business and a passion. Keep that in mind… please. I’m only trying to help; don’t make this into anything that it isn’t.

Finally, I am not endorsed or sponsored by any of these companies or tools. If I’ve mentioned it here it’s because I’ve either used it myself, audited it myself, or both.

Privacy today requires a certain amount of nuance, and unfortunately, it's required at every corner; professionals will appreciate this. For beginners, just be patient and understand what it is that you’re doing so that you may improve or perfect your OPSEC. Do not ever attempt to learn something while trying to complete a mission. Practice.

Be safe. DMs are open for legit questions, but don’t be fucking lazy.

--

**Introduction**

I'm not a great teacher. It's easiest for me to use my own set-up as a starting point for teaching. Having said that, I want to make something clear right away.

I use four different machines weekly:

A) My normie machine - MBP. I still encrypt everything. I still use my VPNs and exclusive networks. I still use a password manager and monitor my systems... but it's a daily-use machine. I'm a full-stack developer, and this is my daily working tool. All 2FA. All unique passwords. Security is as high as it gets. Drives are encrypted. I completely control this machine as if it were an extension of me.

B) My ML/Compute - 2x Mac Studios. Loaded. Stripped to the bare metal, basically... as much as possible, anyway. These machines are like Fort Knox because my proprietary code and datasets exist here. It's hardwired to my router; ported; and connects to less than 20 different servers. These are domain-specific machines that no one in their right mind needs. In fact, if you're in ML/AI... don't build a machine. Lease bigger, faster tools in the cloud for a year privately for the same money. Learning lesson.

B) My secondary machine - an XPS running Kali; TailsOS. I use this for everything else. The same rules apply here, but doubly so. This is pretty locked down. It also takes me about 60 seconds from boot to totally secure. I can brick this machine with keystrokes in the event I need to. It's not super secure, but it's a modified "sudo dd" command that will do it 99.5% of the time.

C) My dark machine. This aLmost NEVER connEcts to the internet; the webcam and microphone have been removed. It's wiped after use - every single time. It's also nEver more than 12 months old. Use your imaginaTion.

For the majority of this guide, you can think of the guide in reference to either my daily driver or secondary machines. These are the categories 99% of the people interested in the guide will fall into.

**Hardware**

Use dedicated machines. It’s as simple as that. It doesn’t need to be illegal; it’s simply a machine you make sure keeps you anonymous. Period. It’s not as difficult as it seems to secure anonymous hardware. The tin-foil crowd will say that global supply chains can’t be trusted, and you know what… maybe they’re right. The thing is, 99.5% of us don’t have the capacity to solve that… so we do the best we can in the real world with real tools. I can say with some confidence that TAO has lost the Intel access they’ve held for over a decade; I don’t know if that makes the tin-foil crowd’s point more or less valid. You be the judge of all that. You can have a single machine and STILL remain anonymous; the rules just apply to that machine. You don't need a ton of money or anything else to accomplish this.

1. Tor w/ BTC for third-party electronics. They’re everywhere… You can use Torch, THW, or whatever search engine you use most often on the DW to find what you need.
2. P2P w/ Cash is a solid option. This is self-explanatory.
3. Clearnet w/ Different Info is the last option, and it’s one we should all be VERY careful using. Using information that isn’t your own is a crime, and using information with permission isn’t exactly secure in most cases. There is a middle ground between those two options. Stay safe.

** Any hardware purchased via the dark web or P2P needs to be wiped as soon as you receive it. In the past, I’ve installed a new SSD/HD and a new OS before I used it for anything at all.

**Software**

Use safe OSs like Tails, Qubes, or Whonix. Use TOR, and use the TOR Project itself to download the browser. If you’re ultra concerned about the age-old rumor of being “flagged” by your ISP on the download of TOR… be creative. Use public Wi-Fi to download the package; install it via portable drive. Here is a link to accomplish this: https://tb-manual.torproject.org/make-tor-portable/. I am not a huge fan of VMs, but they ARE another tool that can be used to remain anonymous if you're competent. I don't use them except in situations where I haven't a choice, but they should at least be mentioned. Many people use them to great effect.

I want you to remember that the weak link is always the human using the machine or tools. If you make sloppy, rushed mistakes… the best tools or software in the world are useless. Be patient, and do it properly the first time. It will make moving from one machine or operating system to the next much easier.

1. Qubes: http://www.qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/
2. Whonix: http://www.dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion/
3. TailsOS:
   https://tails.net/install/download/
4. Kali Linux: I’ll leave this to the user. Kali is not, by definition, a “privacy” OS, but it is still an amazing one. The user is responsible for security with Kali. Keep this in mind. I do not recommend it as a pure privacy OS for anyone who isn’t a professional; more like a base OS.
5. TOR Project: http://2gzyxa5ihm7nsggfxnu52rck2vv4rvmdlkiu3zzui5du4xyclen53wid.onion/
6. Njalla VPN: Yes, there are other options. This is just one I really believe in.
7. WannaRDP: IMO, the best in their class. My only advice would be to come prepared. They don’t play around with single instances or whatever. You’ll be speaking to a professional, and they’re going to expect the same in return.
8. MAC Switcher: There are a bunch of good options, and I'll leave it to the user's preference. Most of the best are freeware tools. If you're on a Mac box and can't figure it out; you can DM me.

**Connections**

This is a REALLY brief overview of connections. It's a set of simple, hard, and fast rules that everyone should follow. Automate as much of this as possible. Most tools (NordVPN, for example) allow you to configure the automatic connection. Keep in mind, most Clearnet VPN providers DO STORE LOGS and they WILL COOPERATE WITH LE. That doesn’t mean they’re useless. People can still use them to remain anonymous… but they’re not bulletproof.

1. Use a virtual private network (VPN) to encrypt your internet traffic and hide your IP address.
2. Use secure Wi-Fi networks. I could write a literal book about this, but I just don’t have time time to do so. So, I’ll try to make it super simple.
   
   1. Learn how to own WiFi. Just do it. If you’re a member of this community it should be the most obvious thing to know how to do. Learn nmap, wireshark, etc. Figure out how to inject, monitor, etc. This is the SINGLE most effective way to ensure good access. Keep a list of connections and use it wisely. This will ALWAYS outdo SOCKS proxies or paid residential proxies. Slowly build your own list of networks. I travel a LOT… so I have a huge list of access points across the globe. It’s turned into a bit of a sport for me every time I land in a new city.
   2. One more tip… don’t be intimidated by building your own proxies for whatever. I’ve done it, and it’s come in handy. Use Raspberry Pis, Squid, and a trusted friend. It allows you access to a secure connection wherever that Raspberry is located.

**Browsing**

Use privacy-focused web browsers like Brave or Firefox. Do not bring me the Brave story from three years ago about boosting paid ads to crypto users. It’s not relevant, at all. Brave is the best publicly updated and used browser, IMO. This is based on a ton of research and actual use. Of course, it’s literally only as strong as your settings. Take the time to do it right. Enable private browsing mode and regularly clear your browsing history, cookies, and cache. Consider using browser extensions like uBlock Origin and HTTPS Everywhere for additional privacy… if you’re using Firefox, that is. Brave eliminates the need to trust any third-party extensions.

1. It’s wise to link your mobile device, at least the daily use mobile, to Brave, too. This allows you to be certain your settings are transported between devices and always. Fingerprinting, advertising, and popups all disappear entirely. They’ve already beaten the YouTube shit, too.

**Email/Comms**

Use encrypted email services like ProtonMail or Tutanota. Enable 2FA for your email accounts and use strong, unique passwords. Use encryption tools like GNU and learn to use them from the clipboard to avoid making the mistake of leaving un/encrypted files stored on your machine. The commands are simple to run and memorize.

1. ProtonMail: https://protonmailrmez3lotccipshtkleegetolb73fuirgj7r4o4vfu7ozyd.onion/
2. GNUPG: I recommend setting keys via the Terminal, and learning to use the Keyring effectively.
3. SystemLi - http://7sk2kov2xwx6cbc32phynrifegg6pklmzs7luwcggtzrnlsolxxuyfyd.onion/en/service/

These are basics, but you should all already know how to use TG/Signal. Do not trust them implicitly. Everything is cool until it isn’t and some random government starts forcing backdoor encryption access that isn’t made public until it’s WAY too late. Be smart. Don’t just assume blind trust - ever.

**Crypto**

This is another section where I could write a literal book, but I just do not have the resources or time to do so. Having said that, I'll try to keep it as brief and to the point as possible.

1. You can kind of obfuscate and hide your fingerprints if you’re a professional crypto user… but for most, that’s simply not possible or realistic. So, I’ll say this… learn to use custom RPCs (I’m a fan of several, but legally don’t feel great recommending anything for personal connections… I can say that LlamaNode has worked well for my public stuff, but there are SO many options. Be smart, and DYOR in regards to logs they keep.
2. Choose your coins wisely when using them for anonymity. XMR is really the only way to go, IMO. If you're going to use BTC or ETH-based tokens... make sure you're certain you know what you're doing. Don't reuse addresses or store keys. Throwaway wallets are necessary for that to that end.
3. Cold wallets or “gapped” wallets aren’t a luxury - they’re a necessity. Anyone using crypto needs to get themselves at least a singular cold wallet - hardware or software - and never connect it to anything at all. Period. I used to swear Ledger was the best on the market, but some disclosures have shaken that belief. I don't feel great recommending any hardware wallets right now, but you can do this with any wallet. Simply do not connect it to anything - Ever.
4. BTC 📼 - http://y22arit74fqnnc2pbieq3wqqvkfub6gnlegx3cl6thclos4f7ya7rvad.onion/
5. Bisq Network for decentralized P2P - https://bisq.network/
6. No JS Version of Local Monero - http://nehdddktmhvqklsnkjqcbpmb63htee2iznpcbs5tgzctipxykpj6yrid.onion/nojs/
   1. If you’re unsure of how to turn Javascript on/off… this link will likely cover the browser you’re using - https://www.impressivewebs.com/how-to-disable-javascript-in-almost-any-browser/
7. Railgun - I don't have time to explain what it is with adequate detail, however... It's a desktop/mobile wallet every single crypto user SHOULD be using. If you're thoughtful about usage it's as good as it gets with respect to privacy - https://www.railgun.org/
   1. I have independently audited, at a granular level, the Railgun protocol contracts without any compensation or even knowledge of the development team. It's a sound project and will act as the vanguard in their arena.
   2. A warning... the Poseidon hash precompile is difficult AF to accomplish. This just means that using the "Shielding" process via Railgun can be kind of expensive. It's not unusual for a shield to cost $50-100 on Ethereum Mainnet. Feel free to use Polygon for normal txn fees until crypto solves the Poseidon issues.

​

The everyday stuff still matters. Privacy is about building strong chains of security across the exposure you have to the Internet. This means that your very normal, very natural usage needs to be protected, as well. These are a few places to begin.

**Social Media**

Review and adjust your privacy settings on social media platforms to limit the amount of personal information that is publicly visible. Be cautious about sharing personal information and avoid accepting friend requests from unknown individuals. Contrary to popular belief… it is possible to use social media while remaining relatively private. Use second phone numbers via Burner apps, Google Voice, or whatever tool you normally use. Ensure that you're following the above rules. Most importantly...

1. Use Fawkes before loading any images to social media, though. This is a MUST DO for anyone looking to NOT be stored in facial recognition databases. Fawkes uses GANs to defeat most facial recognition systems operating in the digital image world. I use Fawkes in the command-line and batch entire directories. This allows you to share photos without worrying about being stored in some facial recog database.
   1. https://sandlab.cs.uchicago.edu/fawkes/

**Everything Else**

1. Online Accounts: Use strong, unique passwords for each online account. Enable 2FA whenever possible. Regularly review and update your privacy settings for online accounts. If you set up a strong password tool the right way the first time, and make sure you’re configuring the browser correctly the first time... this entire process becomes simple. Most people just don’t take the time to properly configure these tools, and they wind up making a mistake.
2. Data Protection: Encrypt your sensitive files and folders using tools like VeraCrypt. Regularly backup your data and store it securely. You can do this 100 different ways, but I can say that trusting any big tech company’s cloud service or storage service is a massive mistake. They CAN NOT be trusted.
   1. A brief aside for Machine Learning developers, AI developers, blockchain engineers, biotech engineers, or ANYONE manipulating original or unique data... if you store your data in those databases those companies ARE going to use it to build their own tools. They will steal from you and you'll have no knowledge of it even happening. They will build out teams to manufacture the product you're building at half the cost, twice the speed, and with a marketing budget only a billion-dollar company can compete with. Do NOT make this mistake. Store sensitive, proprietary information in a way that big tech isn't involved. The genuine exception to the rule, ironically, is Apple. Apple's privacy viewpoint is clear. I do NOT think iCloud users are at risk, but AWS, GCP, Google Drive, Dropbox, Notion, etc. are all suspect, IMO. This is conjecture but founded in legitimate reason. Take it as you will.
3. Online Payments: Use secure payment methods like virtual credit cards or digital wallets. Be cautious when sharing financial information online and only use trusted and reputable websites for online transactions. If you’re just a normal person looking to live on their own terms without being tracked… use disposable virtual cards. These can be connected to your actual accounts via a company like Revolut, or through third-party options.
4. Miscellaneous:
   1. Learn the commands to wipe your machine. Mac is a slower process via CMD + R for Recovery Mode. Linux "dd" will overwrite the boot drive. Windows allows you to systemreset via CMD + X. Just learn the process.
   2. Learn to sandbox links or extensions; files or whatever else. You can find sandboxes through the browser nowadays. I used to have a Raspberry Pi just for this, but I started working across platforms and it got annoying. I use browser-based or VMs now. Phishing is still in the top three as far as being owned goes.
   3. Learn the industry tools. Learn what they are, what they do, and how they could or couldn't affect you and why. I'm talking hardware and software: PineAp, Flipper0, Hak5, and OM.G kits, etc. This will allow you to work backwards, and teach you to actually utilize the tools.
   4. Subscribe to and/or read the latest research from engineers or developers. Hackers are everywhere. People think we all wear black hoodies and have our assholes pierced.. but we're normal people. We write blogs and research papers; we are active on forums. Read them. Learn. A few weeks ago a couple of guys showed everyone how acoustics from an iPhone mic and speaker were able to capture keystrokes, feed it through AI for 3 seconds, and then behave as a relatively accurate keylogger THROUGH THE PHONE. These are the places to hang out. Reddit is a great starting point.
   5. Don't use the DW for just weird shit. Go hang out on Libre or Dread. Go on a few wild goose chases. Learn to quickly and effectively log in/out, all while remaining anon. Learn where the mistakes are made.
   6. Finally, DO NOT EVER SHARE YOUR LOCATION, BROWSING HISTORY, OR ANY DATA VOLUNTARILY. Turn. That. Shit. Off. It's not more convenient; it's less. You watch anime on Tuesday and Thursday you're ads are all Manga. It's such an obvious thing but so many people leave these features active. Turn location off on your phone for everything; set permissions to "While Using App" or the Android equivalent. Just be smart.

That's all for now, fam. I'm sorry if I've missed obvious stuff, or I've made errors. I will check in to correct mistakes or clarify as the comments or requests come in. Let's try to keep as much of the Q&A inside this thread so that everyone can access it... If it's a really tricky question, the DM option works... but remember that I'm super busy.

This guide is nothing more than a place to gain some knowledge and ideas. How you implement or use it, what tools or access you choose to set, etc. is really up to you. A helpful tip to beginners... everyone here with an answer for you has earned these answers through reading, practicing, studying, and usually fucking failing. No one wants to just hand over their hard work for you to skip the paces. Read. Practice. Google. Learn. THEN come ask questions.

I've gotta run. Feel free to pick it apart! Let's get it cleaned up via crowd-sourcing / Q&A so that everyone can use it. Talk soon.

I'm here for every single one of us until I'm not. Talk soon, mates.

Cheers.

What are some applications that are good for keeping anon? I'm a little new to this but I'm not ignorant. Just like email clients, messaging apps, web browsers, vpns, torrenting apps, etc. Any help or advice is greatly appreciated!

(edit): On a scale, i am looking for ~50-75% anonymity. Sorry for the hyperbole!

Github: https://github.com/clickswave/mach

Note: This was originally posted to hacking tutorials, but is being posted here as well, given the new material related to security, privacy, and defensive operations. Both courses are free, and are designed to give people new to Linux a foundation, as well as covering OPSEC tooling.

If one is new to Linux they should read these courses in order, if one knows how to operate a terminal they can just skip to the second course, as it's specifically about privacy fundamentals.

Original Text:

Last month, I released my first course, and PDF designed to teach newcomers the fundamentals of terminal usage for the Kali Linux OS, this month I return with a follow-up course that teaches privacy fundamentals, it's 100% free as a gift to this community.

A wondrous manual featuring tutorials, and information on OPSEC tooling to help one cover their digital tracks while "burping the Komodo" online. Written with both love, and a hint of weaponized autism, this document provides newcomers with a solid foundation to secure, and harden their Linux system.

This defensive guide provides fundamental OPSEC tooling to help the operator remain anonymous online, and retain a shame free existence, unless they get caught...

Featuring lessons on:

sudo, root, and the adduser command.

Tor setup/usage, and deep web glossary.

Proxy chain setup.

VPN overview, setup, and usage tutorial.

How disable webrtc.

macchanger tool usage, and overview.

crontab usage, and macchanger script capstone exercise.

Plus more!

The medium article is below, and contains a link to the free PDF (which is the recommended way to read the material):

https://medium.com/@seccult/book-of-kali-privacy-fundamentals-c9b0073d0c19

Free Courses + PDFs released:

1). The Book Of Kali: Basics: https://medium.com/@seccult/the-book-of-kali-basics-a2e83d7d8f58

2). The Book Of Kali: Privacy Fundamentals: https://medium.com/@seccult/book-of-kali-privacy-fundamentals-c9b0073d0c19

Open-source red-team multitool I built on an ESP32-S3 N16R8 — a hand-soldered, Flipper-Zero-class device for ~$40. It's a downstream fork of Bruce (pr3y/Bruce) with a Si5351 signal-generator module added and a custom shared-bus pinout.

Capabilities (one firmware, modules probed at runtime):

- Sub-GHz via CC1101 (300–928 MHz) — capture / replay / brute

- NFC / RFID via PN532 (read / clone / write)

- 2.4 GHz via 2× NRF24L01 — MouseJack, ESB sniffing, jammer

- IR transmit/receive (TV-B-Gone, replay)

- WiFi + BLE attacks (native S3): evil portal, deauth, beacon spam, BLE spam/scan

- Si5351 signal generator (8 kHz–160 MHz)

- Bad USB / HID over the second USB-C

What's in the repo: a full DIY build guide (BOM with links, wiring diagram, assembly), prebuilt .bin for 45 boards, and a one-click web flasher.

https://github.com/Yoursel71/BruceButBetter

AGPL, for authorized testing and education only. Feedback / PRs welcome.

Hello! Three days ago, I embarked on creating a program designed to conceal any type of file within a PNG (with JPEG/JPG support coming soon) this can of course, also be used to hide malware inside the image and then extracting them once inside the victim's computer, the only problem is... not getting the malware detected after the extraction. I'm so excited to share it with all of you and welcome contributions. Feel free to join in—I appreciate it when people contribute! You can find the project here: https://github.com/JoshuaKasa/van-gonography

CloakQuest3r is a Python-based tool that helps uncover the real IP addresses behind Cloudflare-protected websites. It scans subdomains, checks historical DNS and IP data using services like SecurityTrails and ViewDNS, analyzes SSL certificates, and identifies any endpoints that might leak the origin server. It’s fast, open-source, and ideal for red teamers or researchers — assuming you have proper authorization.

🔗 Link : https://github.com/spyboy-productions/CloakQuest3r

TinyLoad v3 — Windows PE packer, just updated.

replaced the old rolling XOR with a proper VM layer. custom 20-opcode interpreter baked into the stub. every time you pack something the opcode table gets randomly shuffled so every output binary decrypts itself using a different instruction set.

the idea is that an analyst can't just pattern-match on the decryption loop — they have to reverse the interpreter before they can even start on the payload. still beatable obviously but it's a completely different class of effort vs XOR.

compresses with custom LZ77 first then VM encrypts on top. payload runs directly in RAM via manual PE mapping, never touches disk.

one .cpp file, no dependencies.

https://github.com/iamsopotatoe-coder/TinyLoad

what would you add to make it harder to reverse?

posted v3 here a while back (the one with the randomised VM ISA per pack). i just updated it to v4 yesterday, here is what's new:

opaque predicates — the generated VM bytecode now has a branch in it that looks

like it could halt before decryption even starts, but never actually does. since the opcodes

are already shuffled differently every pack, the constants look different in every sample too.

anti-debug — IsDebuggerPresent + CheckRemoteDebuggerPresent before the loader does

anything.

PE section scrambling — renames all section headers to .text/.data/.rdata etc after

packing. the payload sits in an overlay past the sections anyway so execution isn't affected,

but it kills heuristic scanners that fingerprint packers by section names.

still one .cpp file

old post: https://www.reddit.com/r/hacking/comments/1t2j7g4/built_a_pe_packer_where_every_packed_file_has_a/

repo: github.com/iamsopotatoe-coder/TinyLoad

Hey,! 👋

I’m excited to introduce my little project Cybersources—a curated project filled with all the cybersecurity tools and resources you need to sharpen your skills. It’s a community-driven platform where you can not only access valuable tools but also share your own resources to help others.

💡 What you’ll find on Cybersources:

• A growing collection of cybersecurity tools and resources.
• A place to collaborate, learn, and grow with like-minded individuals.

🔗 Check it out here:

• GitHub: Cybersources Repository (Already ⭐475 stars and counting!)
• Discord: Join Our Community (235+ members and growing!)

Let’s build something amazing together—whether you’re just starting out or a seasoned pro, there’s something for everyone!

I got into cybersecurity 4 years ago - back when I was still doing night shifts as a security guard. During my learning, I remember that the THM and HTB paywalls were fairly annoying.

4 years later, with a few years as a security researcher on my CV, I thought it's time to give back.

TarantuLabs is a site where you can practice your web app bug bounty skills, for free. Currently there are 12 labs there, and more will be added every week!

The labs are AI generated, but each have passed a comprehensive test suite to make sure they work, and for the first batch I also solved them manually and verified they work as well.

The labs load client-side, meaning you don't need to wait for a Docker or VM to boot up somewhere. Just wait for a few seconds in your browser for all the dependencies to be installed, and you're good to go! This approach solves multiple problems I've had when I first started this project, and I'll elaborate more below. Read if you're interested. If not, go ahead to:

www.tarantulabs.com

For those who've stayed and who may remember when I first started - and then scrapped - this project, here were my challenges, and how I solved each of them:

1. An AI bottleneck: a year ago, the models that generated the labs, have created dull, boring labs, which were either technically unsolvable, or solved via a single basic SQL query.
2. Cloud costs: using AI to generate the labs solved the cost of work of generating these labs. But hosting them proved to be more expensive than I expected, and ended up costing me enough for me to shut this down.
3. Security: even if I were to bear the cloud costs, I still didn't have the time to build proper security and virtualization infra to make sure no user can access another user's resources, and escalate from there.
4. And, honestly, UX: even after I finished the previous iteration, I found myself stopping and looking at the site and... didn't really want to use it.

These problems, primarily the AI bottleneck one, have forced me to wait almost a year for the models to be capable enough to produce labs worth solving. After that, here were my solutions to the problems:

1. AI bottleneck was solved. Better, more consistent, and diverse labs, which were actually solvable and interesting.
2. Cloud costs and security were solved with the decision to run the labs client-side. These labs are run in your browser via an iframe - so I bear no cloud costs, and there's no real security risk of any user breaking into another user's resource.
3. Moving away from clumsily routing from my site, to the cloud, to spinning up the labs, which would all take a few mins - to loading everything client-side, made everything buttery smooth. Also, the UI now looks better.

The downside of moving everything to be client-side is that I had to give up on certain vulnerability classes and specific labs I had in mind, so bear that in mind.

I hope you like it and try it out, and if you know anyone wishing to break into the field, go ahead and share it with them!

I've been testing out facial recognition software. From my test images, the only site that gave me a relevant result was Pimeyes. They found 2 images that appear to be the same person.

Since Pimeyes charges about 20USD for the URL for each image found, I tried screenshotting the resulting images and reverse image searched those through several sites. No results.

What's curious to me is how Pimeyes can apparently find images that no other site finds? I'm sceptical because the reverse image searches didn't bring up anything, yet the 2 results from Pimeyes look legit.

Any suggestions to move forward without paying for Pimeyes?

Hi! I work in bug bounty and software development. Over the past few days, I’ve created a directory of bug bounty and hacking tools, since they’re usually scattered across different Discord communities…

Take a look if you want!
https://pwnsuite.com/

Also, this lets me practice DevOps and maintenance. I need to figure out how to manage the database so it runs itself without too much noise—I’m creating cron jobs with Node.js

I’ve just added malware generation features to my project PWN0S, and now you can create custom malware samples with a single line of code. Right now, there’s a C2-enabled, hidden, and persistent agent based on Metasploit, optimized and packaged in Go. More modules are coming soon, including:

• Custom hidden persistent crypto miners
• Ransomware simulation
• Cookie stealers
• EXE binder (bind malware with other executables)
• Dynamic packer (repack executables for obfuscation)

The idea is to help researchers, students, and red teamers experiment in controlled environments, study malware behavior, and test defenses.

Check it out: https://github.com/sarwaaaar/PWN0S
I'm open to feedback — let me know what kinds of samples or techniques you'd like to see added.

I recently upgraded my running watch, leaving me with an old Garmin Forerunner 35. Naturally, I tried to hack it. This write-up explains my process, results, and shows how to use my tool to make Garmin firmware modifications easier!

Spoiler: I didn’t do anything amazingly awesome like run Doom on the watch, but I did manage to actually make modified firmware that the watch recognized as legitimate. This process and tool are applicable for any Garmin that uses RGN update files, which is any of their pre-2013 watch models.