<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://nethydra.github.io/feed.xml" rel="self" type="application/atom+xml" /><link href="https://nethydra.github.io/" rel="alternate" type="text/html" /><updated>2026-05-18T06:46:15+00:00</updated><id>https://nethydra.github.io/feed.xml</id><title type="html">Your awesome title</title><subtitle>Write an awesome description for your new site here. You can edit this line in _config.yml. It will appear in your document head meta (for Google search results) and in your feed.xml site description.</subtitle><entry><title type="html">NetHydra 2026.2 Release (SONAR, MISP, WAS Support)</title><link href="https://nethydra.github.io/blog/nethydra-2026.2-release" rel="alternate" type="text/html" title="NetHydra 2026.2 Release (SONAR, MISP, WAS Support)" /><published>2026-05-18T05:05:00+00:00</published><updated>2026-05-18T05:05:00+00:00</updated><id>https://nethydra.github.io/blog/nethydra-2026.2-release</id><content type="html" xml:base="https://nethydra.github.io/blog/nethydra-2026.2-release"><![CDATA[<p>Today, NetHydra proudly announces the release of NetHydra 2026.2 — one of the biggest updates ever introduced to the NetHydra ecosystem.</p>

<p>This release delivers major improvements across the core system, performance enhancements, updated tooling, expanded compatibility, and a variety of internal changes designed to improve both flexibility and usability for security professionals.</p>

<p>Before jumping into <a href="#whats-new">What’s new</a>, let us introduce <a href="/doc/Introduction/wiki-sonar">SONAR</a>.</p>

<p>NetHydra <a href="/doc/Introduction/wiki-sonar">SONAR</a> is a dedicated enterprise-focused edition of NetHydra, built for organizations that require a more flexible security stack compared to the standard edition, NetHydra Express.</p>

<p><a href="/doc/Introduction/wiki-sonar">SONAR</a> includes additional tools and components focused on several areas of cybersecurity operations, including:</p>

<ul>
  <li>Web Application Security</li>
  <li>Threat Intelligence</li>
  <li>Defensive Security Operations</li>
  <li>Security Assessment &amp; Analysis</li>
</ul>

<p>The goal of <a href="/doc/Introduction/wiki-sonar">SONAR</a> is to provide a more adaptable platform for enterprise environments, allowing teams to customize and scale their workflows based on operational requirements.</p>

<p>In addition to the new <a href="/doc/Introduction/wiki-sonar">SONAR</a> variant, NetHydra 2026.2 also includes various improvements to tool integration, and overall platform experience.</p>

<p>This release represents another major step forward for the NetHydra project as we continue building a modern, flexible, and security-focused platform for researchers, defenders, and enterprise organization.</p>

<p><em>let’s jump to <a href="#whats-new">What’s new?</a></em></p>

<h2 id="whats-new-">What’s new —</h2>

<ul>
  <li><a href="#firefox-theme">Firefox Theme</a> - Revert compat Firefox theme</li>
  <li><a href="#system-changes">Core system improvements</a> - Added zram as default configuration</li>
  <li><a href="#new-tools">New tools</a> - 4 tools added</li>
  <li><a href="#pages-update">Page update</a> - NetHydra page update</li>
</ul>

<h2 id="firefox-theme">Firefox Theme</h2>

<p>In this update, we reverted the Firefox theme to a more compatible and classic design inspired by the 2020 Firefox appearance.</p>

<p>Special thanks to <a href="https://github.com/BGMP/firefox-revert-proton">@BGMP</a> for making this possible.</p>

<p><img src="/assets/graphics/post_graphics/nethydra-2026.02/compat-classic-firefox.png" alt="NetHydra classic firefox theme style" /></p>

<h2 id="system-changes">System Changes</h2>

<p>In this update, we decided to enable <code class="language-plaintext highlighter-rouge">zram</code> as the default configuration on NetHydra to provide a better overall system experience and improved memory management.</p>

<h2 id="new-tools">New Tools</h2>

<p>As with every NetHydra release, this update also introduces several new tools and package additions — including tools specifically added for the <a href="/doc/Introduction/wiki-sonar">SONAR</a> edition.</p>

<p>Here is a quick rundown of some of the new tools included in NetHydra 2026.2:</p>

<ul>
  <li><a href="/doc/tools/sonar-tools-misp">MISP</a> - Open source threat intelligence and information sharing platform.</li>
  <li><a href="/doc/tools/sonar-tools-burpsuite">Burp Suite</a> - Comprehensive penetration testing platform designed for web application security testing.</li>
  <li><a href="/doc/tools/sonar-tools-nuclei">Nuclei</a> - Fast and customizable vulnerability scanner based on templates.</li>
  <li><a href="/doc/tools/sonar-tools-cyberchef">CyberChef</a> - The Cyber Swiss Army Knife web app for encryption, encoding, compression and data analysis</li>
</ul>

<p>Several of these tools are included as part of the expanded <a href="/doc/Introduction/wiki-sonar">SONAR</a> toolkit to support enterprise-focused security workflows, threat analysis, and defensive operations.</p>

<h2 id="pages-update">Pages Update</h2>

<p>To provide a better experience for NetHydra visitors, we have made major improvements and visual changes across several NetHydra pages.</p>

<p>This changes includes:</p>

<ul>
  <li><a href="/">Home</a> - Redesigned homepage and landing experience.</li>
  <li><a href="/doc">Documentation Page</a> - Updated documentation layout, including improvements to the <a href="/doc/tools">Tools Pages</a>.</li>
  <li><a href="#">Blog</a> - Yes, you are reading this post using the new blog style!</li>
</ul>

<p><em>Feel better right now? :)</em></p>

<h2 id="get-nethydra-20262">Get NetHydra 2026.2</h2>

<p><strong>Fresh images?</strong>: what do you waiting for? Grab now! <a href="/get/">Get NetHydra</a></p>

<p>too lazy to get Fresh Images? Roll it now!</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>──(nethydra@NetHydra-Express)─[~]
└─── $ sudo apt update &amp;&amp; sudo apt full-upgrade -y
[...]

──(nethydra@NetHydra-Express)─[~]
└─── $ [ -f /var/run/reboot-required ] &amp;&amp; sudo reboot -f
</code></pre></div></div>

<p>You should now running NetHydra 2026.2:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>──(nethydra@NetHydra-Express)─[~]
└─── $ grep VERSION /etc/os-release
VERSION="2026.2"
VERSION_ID="2026.2"
VERSION_CODENAME="sana"

──(nethydra@NetHydra-Express)─[~]
└─── $ uname -r
6.12.86+nethydra-rt-amd64
</code></pre></div></div>

<p>Or if you’re using <a href="/doc/sonar">SONAR</a> edition:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>──(nethydra@NetHydra-Express)─[~]
└─── $ grep VERSION /etc/os-release
VERSION="2026.2"
VERSION_ID="2026.2"
VERSION_CODENAME="sana"

──(nethydra@NetHydra-Express)─[~]
└─── $ uname -r
6.12.86+sonar-amd64
</code></pre></div></div>

<p>Always, if you get any bugs in <code class="language-plaintext highlighter-rouge">NetHydra</code> please submit to <a href="https://github.com/NetHydra/NetHydra/issues">Bug tracker</a>!.</p>

<p>Want to keep up-to-date with <code class="language-plaintext highlighter-rouge">NetHydra</code>?</p>

<ul>
  <li><a href="/feed.xml">RSS feed</a></li>
  <li>Connect with us! - <a href="https://x.com/hydrapwk">X/Twitter</a>, <a href="https://infosec.exchange/@hydrapwk">Infosec.exchange</a>, <a href="https://www.instagram.com/hydrapwklinux/">Instagram</a></li>
</ul>

<p>Want to connect with <code class="language-plaintext highlighter-rouge">NetHydra</code> community? <a href="https://discord.gg/CvsukGecd">Join us</a>!</p>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[Today, NetHydra proudly announces the release of NetHydra 2026.2 — one of the biggest updates ever introduced to the NetHydra ecosystem The release including SONAR, MISP, etc.]]></summary></entry><entry><title type="html">HydraPWK - NetHydra 2026.01-sana Release (Desktop refresh, NetOpsy, Announcment)</title><link href="https://nethydra.github.io/blog/nethydra-sana-2026.1-release" rel="alternate" type="text/html" title="HydraPWK - NetHydra 2026.01-sana Release (Desktop refresh, NetOpsy, Announcment)" /><published>2026-03-03T10:36:00+00:00</published><updated>2026-03-03T10:36:00+00:00</updated><id>https://nethydra.github.io/blog/nethydra-sana-2026.1-release</id><content type="html" xml:base="https://nethydra.github.io/blog/nethydra-sana-2026.1-release"><![CDATA[<p>Today HydraPWK? No, not HydraPWK this is NetHydra! Yes! We’re rebranding HydraPWK! And now HydraPWK is NetHydra. What’s the difference between HydraPWK and NetHydra? There’s nothing “different” between HydraPWK and NetHydra, were still in the same philosophy, and <code class="language-plaintext highlighter-rouge">How-To</code>.</p>

<p>Why did we rebrand? Yes, you might think there’s a lack of consistency in our branding, but the main reason is to avoid any misunderstandings (as we announced here).</p>

<p>But don’t worry were still same!. Due to the change in project name and branding, links and more have been updated to the new address!.</p>

<p>New logo and <a href="https://github.com/NetHydra/NetHydra/tree/main/press_pack">Press pack</a></p>

<p><img src="/assets/graphics/post_graphics/nethydra-2026.01-sana/press_pack.png" alt="press pack" /></p>

<h5 id="project-link">Project link</h5>

<ul>
  <li>Official page - <a href="https://NetHydra.github.io">https://NetHydra.github.io</a></li>
  <li>GitLab - <a href="https://gitlab.com/NetHydra">https://gitlab.com/NetHydra</a></li>
  <li>GitHub - <a href="https://github.com/NetHydra">https://github.com/NetHydra</a></li>
  <li>Issues/support - <a href="https://github.com/NetHydra/NetHydra/issues">https://github.com/NetHydra/NetHydra/issues</a></li>
</ul>

<blockquote>
  <p>note: After <code class="language-plaintext highlighter-rouge">2-5</code> hours of this announcement and release, we will redirect <a href="https://hydrapwk.github.io">https://hydrapwk.github.io</a> to  <a href="https://nethydra.github.io">https://nethydra.github.io</a>.</p>
</blockquote>

<p><em>Let’s jump to, What’s new?</em></p>

<h3 id="whats-new">What’s new?</h3>
<ul>
  <li><a href="#NetOpsy">NetOpsy</a> - NetHydra DFIR Flavour.</li>
  <li><a href="#desktop-refresh">Desktop refresh</a> - New wallpaper, Menu refresh.</li>
  <li><a href="#the-wlan0-and-eth0-guy">The wlanX</a> - The legacy interface naming.</li>
  <li><a href="#discord-server">Community update</a> - Discord server NH&amp;Friends</li>
</ul>

<h3 id="netopsy">NetOpsy</h3>

<p>Say Hi to NetOpsy! What is NetOpsy? NetOpsy is another Variant of NetHydra, Which is intended for digital forensic investigation purposes.</p>

<blockquote>
  <p>NetOpsy was basically inspired by the <a href="https://caine-live.net/">Caine Project</a></p>
</blockquote>

<p>At NetOpsy we formatted the application menu to (refer to) the <code class="language-plaintext highlighter-rouge">NIST SP 800-86</code> methodology.</p>

<ul>
  <li>Collection</li>
  <li>Examination</li>
  <li>Analysis</li>
  <li>Reporting</li>
</ul>

<p>And of course, general applications for Forensic Investigations!</p>

<h3 id="desktop-refresh">Desktop refresh.</h3>

<p>New wallpaper and theme!</p>

<p><img src="/assets/graphics/post_graphics/nethydra-2026.01-sana/nethydra-desktop.png" alt="NetHydra 2026.01 Desktop" /></p>

<div style="display: flex; gap: 20px;">
	<img src="https://gitlab.com/nethydra/packages/nethydra-wallpapers/-/raw/NetHydra/2026.01/nethydra/nh-purple-circle.png" />
	<img src="https://gitlab.com/nethydra/packages/nethydra-wallpapers/-/raw/NetHydra/2026.01/nethydra/nh-blue-circle.png" />
</div>
<p><img src="https://gitlab.com/nethydra/packages/nethydra-wallpapers/-/raw/NetHydra/2026.01/nethydra/nh-gradient.png" /></p>

<h3 id="netopsy-1">NetOpsy</h3>

<p>Say Hi to NetOpsy! What is NetOpsy? NetOpsy is another Variant of NetHydra, Which is intended for digital forensic investigation purposes.</p>

<blockquote>
  <p>NetOpsy was basically inspired by the <a href="https://caine-live.net/">Caine Project</a></p>
</blockquote>

<p>At NetOpsy we formatted the application menu to (refer to) the <code class="language-plaintext highlighter-rouge">NIST SP 800-86</code> methodology.</p>

<ul>
  <li>Collection</li>
  <li>Examination</li>
  <li>Analysis</li>
  <li>Reporting</li>
</ul>

<p><img src="/assets/graphics/post_graphics/nethydra-2026.01-sana/netopsy-desktop.png" alt="NetOpsy Desktop" /></p>

<p>And of course, general applications for Forensic Investigations!</p>

<ul>
  <li>ghidra</li>
  <li>maltego</li>
  <li>wireshark</li>
  <li>autopsy</li>
  <li>binwalk</li>
  <li>guymager</li>
  <li>pdf-parser</li>
  <li>sleuthkit</li>
  <li>volatility3</li>
  <li>sherlock</li>
</ul>

<p>And Ofc! And of course if you have another app we don’t know about, LET ME KNOW!</p>

<p><a href="https://sourceforge.net/projects/hydrapwk-gnu-linux/files/Image/netopsy-dfir-2026.01-amd64.iso/download">Download NetOpsy now!</a> <a href="https://gitlab.com/nethydra/documentation/archives/-/raw/main/checksum/netopsy-2026.01/netopsy-dfir-2026.01-amd64.iso.md5">Md5sum</a></p>

<h3 id="the-wlan0-and-eth0-guy">The wlan0, and eth0 guy.</h3>

<p>Maybe you are realize the interface naming on NetHydra (formerly known as HydraPWK) is following default debian interface naming (Predictable interface naming) e.g wlp2s0, enps0xxx.</p>

<p>Which on most computers has a different name (depending on where the wireless card is installed) That’s why we have difficulty providing default configuration values in the packages we distribute (because each computer has a different interface naming).</p>

<p>Therefore, we are returning the interface names to the legacy naming method. (All configurations that use interface parameters will be set to wlan0, We will assume you are installing NetHydra as bare metal).</p>

<p><em>NetHydra is now using a legacy interface
naming, E.g wlan0, wlan1, eth0.</em></p>

<p>However, if you feel “more comfortable” with <em>predictable interface naming</em> you can check our documentation!.</p>

<h3 id="community-update-nhfriends">Community update (NH&amp;Friends)</h3>
<h4 id="discord-server">Discord server</h4>

<p>Good news! We made a new community discord server, and thank you to <a href="https://github.com/Kanax01">@Kanax01</a> for helping to set-up the discord server!. Click this link <a href="https://discord.gg/CvsukGecd">https://discord.gg/CvsukGecd</a> to <em>JOIN US</em>.</p>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[Say hello to NetHydra 2026.01 with codename sana.]]></summary></entry><entry><title type="html">SIEM On your Backpack. HydraPWK 2025.04 Viper - hydrapwk-stealth, wazuh, kernel migration</title><link href="https://nethydra.github.io/blog/hydrapwk-viper" rel="alternate" type="text/html" title="SIEM On your Backpack. HydraPWK 2025.04 Viper - hydrapwk-stealth, wazuh, kernel migration" /><published>2025-12-01T23:39:00+00:00</published><updated>2025-12-01T23:39:00+00:00</updated><id>https://nethydra.github.io/blog/hydrapwk-viper</id><content type="html" xml:base="https://nethydra.github.io/blog/hydrapwk-viper"><![CDATA[<p>Today, On hydrapwk post hydrapwk drop New release <code class="language-plaintext highlighter-rouge">HydraPWK 2025.04</code> With codename <code class="language-plaintext highlighter-rouge">Viper</code>
In this release Like usual we made with Additions and changes. What is it?</p>

<p>But before we start Let’s take a look new feature of HydraPWK (hydrapwk-stealth) you can check Image bellow for <code class="language-plaintext highlighter-rouge">hydrapwk-stealth</code> Architectures</p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-viper/hydrapwk-stealth-arhictectures.png" alt="hydrapwk-stealth-architecture" /></p>

<p><code class="language-plaintext highlighter-rouge">Note: You need to install HydraPWK on your machine before init hydrapwk-stealth</code></p>

<p>As you can see the image above is showing <code class="language-plaintext highlighter-rouge">Process</code> how You could get into <code class="language-plaintext highlighter-rouge">hydrapwk-stealth</code> and what you can <code class="language-plaintext highlighter-rouge">do or not</code> if you boot into <code class="language-plaintext highlighter-rouge">hydrapwk-stealth mode</code> And you may will asking.</p>

<blockquote>
  <p>What the goal?</p>
</blockquote>

<p>The main goal of <code class="language-plaintext highlighter-rouge">hydrapwk-stealth</code> is for reduce detection from <code class="language-plaintext highlighter-rouge">IDs (Intrusion Detection System)</code>.</p>

<p>As default the network interface when you boot into <code class="language-plaintext highlighter-rouge">hydrapwk stealth</code> the interface will use monitor mode as default (Please read. <a href="/doc/tools/hydrapwk-tools-hydrapwk-stealth">hydrapwk stealth documentation</a>).</p>

<p><code class="language-plaintext highlighter-rouge">hydrapwk-stealth</code> is temporary user, <code class="language-plaintext highlighter-rouge">home</code> directory of <code class="language-plaintext highlighter-rouge">hydrapwk-stealth</code> user is non persistence (Running on RAM) and once you reboot your data in <code class="language-plaintext highlighter-rouge">hydrapwk-stealth</code> will lost, and ofc, if the data is important you could copy your data into opt or whatever place. <code class="language-plaintext highlighter-rouge">DON'T SAVE YOUR DATA IN hydrapwk-stealth it will lost.</code></p>

<p>…And let’s jump to <code class="language-plaintext highlighter-rouge">Whats New?</code></p>

<h1 id="whats-new">What’s new?</h1>

<ul>
  <li><a href="#hydrapwk-stealth">hydrapwk stealth</a> - Stealth mode for reduce IDs Detection</li>
  <li><a href="#wazuh">Wazuh</a> - open source security platform that unifies XDR and SIEM protection for endpoints and cloud workloads.</li>
  <li><a href="#update-requirements">Update requirements</a> - system minimal requirements</li>
  <li><a href="#kernel-migration">Kernel migration</a> - Migrate HydraPWK RT(PREEMPT_RT) Kernel sources.</li>
</ul>

<h1 id="hydrapwk-stealth">HydraPWK Stealth</h1>

<p>We may don’t need to explain again about hydrapwk-stealth, we just will give you the different between boot into hydrapwk-stealth and standard hydrapwk</p>

<p><em>Boot into hydrapwk stealth</em></p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-viper/hydrapwk-stealth-desktop.png" alt="HydraPWK STEALTH" /></p>

<p><em>Boot into normal HydraPWK</em></p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-viper/hydrapwk-standard-boot.png" alt="HydraPWK boot standard" /></p>

<h1 id="wazuh">Wazuh</h1>

<p>So yeah we’ve been working 2-3 weeks to integrate wazuh for hydrapwk, and here is wazuh running natively on <code class="language-plaintext highlighter-rouge">hydrapwk</code> and it would be <code class="language-plaintext highlighter-rouge">SIEM on your backpack</code></p>

<blockquote>
  <p>Note: This is not an official binary of wazuh (the binary build by HydraPWK)</p>
</blockquote>

<p>Wazuh cannot init when you running hydrapwk on live mode you need to install hydrapwk on your machine (Please check our <a href="/doc/tools/hydrapwk-tools-wazuh">hydrapwk wazuh documentation</a>)</p>

<p>And about system requirements we are update hydrapwk minimal system requirements (Important)</p>

<p>You need <code class="language-plaintext highlighter-rouge">16GB RAM</code> and <code class="language-plaintext highlighter-rouge">128GB DISK</code> and <code class="language-plaintext highlighter-rouge">4 CORE CPU</code></p>

<p><em>HydraPWK Wazuh Login</em></p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-viper/hydrapwk-wazuh-login.png" alt="HydraPWK Wazuh Login" /></p>

<p><em>HydraPWK Wazuh Dashboard</em></p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-viper/hydrapwk-wazuh-dashboard.png" alt="HydraPWK Wazuh Dashboard" /></p>

<p><em>HydraPWK Wazuh TI MITRE</em></p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-viper/hydrapwk-wazuh-mitre.png" alt="HydraPWK Wazuh MITRE" /></p>

<p><em>HydraPWK Wazuh HIPA</em></p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-viper/hydrapwk-wazuh-hipa.png" alt="HydraPWK Wazuh Hipa" /></p>

<h1 id="update-requirements">Update requirements</h1>

<p>here is, this is our recommendation (Minimal) hardware to run hydrapwk.</p>

<table>
  <thead>
    <tr>
      <th style="text-align: center">RAM</th>
      <th style="text-align: center">DISK</th>
      <th style="text-align: center">CPU</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td style="text-align: center">16GB</td>
      <td style="text-align: center">128GB+</td>
      <td style="text-align: center">4 CORE</td>
    </tr>
  </tbody>
</table>

<p>And you may asking why? Why hydrapwk need very much <code class="language-plaintext highlighter-rouge">Resources</code>?</p>

<p>even if we’re using <code class="language-plaintext highlighter-rouge">One task one tool</code> philosophy, it is not mean <code class="language-plaintext highlighter-rouge">HydraPWK</code> Lightweight, desktop environment we’re using is minimal <code class="language-plaintext highlighter-rouge">xfce4</code> desktop and it’s just take less than 1GB on idle (We cannot claim this, but we’re sure).</p>

<p>The problem is on the tools, which the tools we’re bring is <code class="language-plaintext highlighter-rouge">Top tools</code> only industry standard tools no duplicate only <code class="language-plaintext highlighter-rouge">one task one tool</code>, so yeah we won’t to compremise with it and ofc <code class="language-plaintext highlighter-rouge">HydraPWK</code> need a big requirements, much tools in <code class="language-plaintext highlighter-rouge">HydraPWK</code> is heavy tools for <code class="language-plaintext highlighter-rouge">Industry</code></p>

<p>In essence, the tools we brought were few, but all the tools were taken from (Industry and real-world cases).</p>

<h1 id="kernel-migration">Kernel Migration</h1>

<p>So yeah, we have been import kernel source from debian, and this release we’re used it, but don’t worry the kernel is still RT(realtime) kernel (PREEMPT_RT).</p>

<p>You may asking why?</p>

<p>As you know the previous HydraPWK kernel was a vanilla kernel from linux, and it is likely to be prone to <code class="language-plaintext highlighter-rouge">BUG</code> so we imported the Debian kernel into HydraPWK to minimize <code class="language-plaintext highlighter-rouge">BUG</code>.</p>

<p>But the main important is: <em>Don’t worry HydraPWK still using RT kernel as default</em></p>

<h1 id="updating-hydrapwk">Updating hydrapwk</h1>

<blockquote>
  <p>Update hydrapwk using fresh image? Yes you can <a href="/get">Get hydrapwk image now</a></p>
</blockquote>

<p>so yeah don’t worry, if you have already hydrapwk Apes you can update you’re hydrapwk to the latest version (Viper) easily.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>hydrapwk@hydrapwk:~$ sudo apt update &amp;&amp; sudo apt full-upgrade -y # this is will pull 'HydraPWK Helper patch'
[...] # After thats you need to initialize hydrapwk viper
hydrapwk@hydrapwk:~$ sudo apt update &amp;&amp; sudo apt full-upgrade
</code></pre></div></div>

<p>And boom! now you could check your hydrapwk version</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>hydrapwk@hydrapwk:~$ grep VERSION /usr/lib/os-release
# Now the output should be `Viper`
</code></pre></div></div>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[New update HydraPWK GNU/Linux 2025.04 - HydraPWK stealth, wazuh integration, kernel migration]]></summary></entry><entry><title type="html">HydraPWK 2025.03.T1 (Apes) - colorscheme, opensearch, opensearch-dashboard</title><link href="https://nethydra.github.io/blog/hydrapwk-apes-t1" rel="alternate" type="text/html" title="HydraPWK 2025.03.T1 (Apes) - colorscheme, opensearch, opensearch-dashboard" /><published>2025-11-01T03:15:00+00:00</published><updated>2025-11-01T03:15:00+00:00</updated><id>https://nethydra.github.io/blog/hydrapwk-apes-t1</id><content type="html" xml:base="https://nethydra.github.io/blog/hydrapwk-apes-t1"><![CDATA[<p>Today, On hydrapwk post hydrapwk dropped new snapshot and changes.</p>

<p>Before we start let’s talk about this <code class="language-plaintext highlighter-rouge">Update</code> this update Why use the tail number <code class="language-plaintext highlighter-rouge">T1</code>? Yeah, because it’s a snapshot of a previous release.</p>

<p>If you remember in our <a href="/blog/hydrapwk-release-apes">major release yesterday</a> we included <code class="language-plaintext highlighter-rouge">elasticsearch</code> into the HydraPWK repo, however we had some issues regarding <code class="language-plaintext highlighter-rouge">LICENSE</code> (We have announced it in the official HydraPWK <a href="https://github.com/hydrapwk/hydrapwk/issues/16">issues</a> and channels), And we have pulled the <code class="language-plaintext highlighter-rouge">elasticsearch</code> package from hydrapwk, And instead, we included <code class="language-plaintext highlighter-rouge">OpenSearch</code> into the HydraPWK repo.</p>

<p>So basically <code class="language-plaintext highlighter-rouge">elasticsearch</code> will no longer be in HydraPWK.</p>

<p>We apologize for that, it was our (my) fault for not checking it more deeply.</p>

<p>and we want to say something, we saw some posts and reviews of hydrapwk and we really respect that and are very happy, but we also don’t want people to exaggerate about HydraPWK, we are really happy with people who want to review HydraPWK it means a lot to us, but please don’t compare HydraPWK or make something that is <code class="language-plaintext highlighter-rouge">Clickbait</code> for example, <code class="language-plaintext highlighter-rouge">HydraPWK is better than this and that</code> we don’t want that,,, we want honesty, that’s what’s best for this project … and I would be happier if there was someone who criticized this project.</p>

<h1 id="affected-packages">Affected packages.</h1>

<p>So yeah, because we replaced <code class="language-plaintext highlighter-rouge">elasticsearch</code> with <code class="language-plaintext highlighter-rouge">OpenSearch</code> and of course the tools that use that <code class="language-plaintext highlighter-rouge">Backend</code>.</p>

<p>Arkime, now arkime in hydrapwk has used <code class="language-plaintext highlighter-rouge">OpenSearch</code> as its backend as default.</p>

<p>…Let’s jump to <code class="language-plaintext highlighter-rouge">What's New?</code></p>

<blockquote>
  <p>Note: All packages with <code class="language-plaintext highlighter-rouge">&lt;packages_name&gt;_&lt;packages_version&gt;_&lt;architecture&gt;+hydrapwk</code> is build by HydraPWK</p>
</blockquote>

<h1 id="whats-new">What’s new?</h1>

<ul>
  <li>Xfce terminal colorscheme - Update colorscheme <code class="language-plaintext highlighter-rouge">hydrapwk-purplizer</code> for Xfce terminal.</li>
  <li><a href="#opensearch-as-backend">OpenSearch</a> - is an open-source, enterprise-grade search and observability suite that brings order to unstructured data at scale.</li>
  <li><a href="#opensearch-dashboards">OpenSearch dashboard</a> - data visualization tool designed to work with OpenSearch.</li>
</ul>

<p>Please check our <a href="/doc/tools">tools documentation</a> for configuration</p>
<h1 id="purplizer-colorscheme">Purplizer colorscheme</h1>

<p>In this update we updated the hydrapwk-purplizer <code class="language-plaintext highlighter-rouge">colorscheme</code> (Xfce terminal), Maybe you will notice that if there is an <code class="language-plaintext highlighter-rouge">error message</code> it will not be visible (It blends in with the terminal background), So yeah once again it was our(my) fault, so we have updated it actually we don’t need to announce this, but why not if you can announce it?.</p>

<h1 id="opensearch-as-backend">OpenSearch as backend</h1>

<p>As we(I) said before we included <code class="language-plaintext highlighter-rouge">OpenSearch</code> into the HydraPWK repository (note that it is not an official build of <code class="language-plaintext highlighter-rouge">OpenSearch</code>, In other words it is a build of HydraPWK).</p>

<h1 id="opensearch-dashboards">OpenSearch Dashboards</h1>

<p>Great news! We added <code class="language-plaintext highlighter-rouge">OpenSearch Dashboards</code> to HydraPWK, as the <code class="language-plaintext highlighter-rouge">OpenSearch</code> binary in the HydraPWK repository is not the official <code class="language-plaintext highlighter-rouge">OpenSearch</code> binary (Built by HydraPWK).</p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.03.T1/hydrapwk-opensearch-dashboard.png" alt="hydrapwk screenshoot opensearch" /></p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.03.T1/hydrapwk-dashboard-visualize.png" alt="hydrapwk screenshoot opensearch dashboard sample data" /></p>

<h1 id="updating">Updating</h1>

<p>So, you have two options for updating HydraPWK. Want to download a fresh image? Of course you <a href="/get">can!</a></p>

<p>Too lazy to download the new images? update via <code class="language-plaintext highlighter-rouge">apt</code>!</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>hydrapwk@hydrapwk:~$ sudo apt update &amp;&amp; sudo apt full-upgrade -y
[...]
</code></pre></div></div>

<p>…So yeah, just it and we’re very sorry once again about the <code class="language-plaintext highlighter-rouge">Problem</code> and Thank you for visiting this announcement…</p>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[New update HydraPWK GNU/Linux snaphost 2025.03.T1 - colorscheme, opensearch, opensearch-dashboard]]></summary></entry><entry><title type="html">HydraPWK 2025.03 (Apes) - arkime, elasticsearch, purplizer, desktop-changes, tools page</title><link href="https://nethydra.github.io/blog/hydrapwk-release-apes" rel="alternate" type="text/html" title="HydraPWK 2025.03 (Apes) - arkime, elasticsearch, purplizer, desktop-changes, tools page" /><published>2025-10-23T04:37:00+00:00</published><updated>2025-10-23T04:37:00+00:00</updated><id>https://nethydra.github.io/blog/hydrapwk-release-apes</id><content type="html" xml:base="https://nethydra.github.io/blog/hydrapwk-release-apes"><![CDATA[<p>Today in HydraPWK blog post HydraPWK released new version of HydraPWK, say hello to HydraPWK 2025.03 (Apes).</p>

<p>and the best things is, now hydrapwk is defensive too!
another word, not just focus on pentesting and hydrapwk will be <code class="language-plaintext highlighter-rouge">security auditing toolkit</code> instead <code class="language-plaintext highlighter-rouge">Pentesting toolkit</code>.</p>

<blockquote>
  <p>Don’t worry about bloatware, hydrapwk still same <code class="language-plaintext highlighter-rouge">One task one tool</code> all the tools on hydrapwk is curated tools. All the tools we choice is based on real-world case.</p>
</blockquote>

<h1 id="whats-new">What’s new?</h1>

<ul>
  <li><a href="#hydrapwk-logo-2.0">HydraPWK Logo 2.0</a> - hydrapwk updated logo (2.0)!</li>
  <li><a href="#new-tools">New tools</a> - arkime, elasticsearch</li>
  <li><a href="#polkit-rules">Polkit rules</a> - new hydrapwk Polkitd rules</li>
  <li><a href="#desktop-changes">Desktop changes</a> - HydraPWK purplizer, menu</li>
  <li><a href="#hardware-requirements">Hardware reuqirements</a> - Update recommended (Minimal hardware requirements)</li>
  <li><a href="#tools-doc">Tools documentation</a> - tools-documentation page</li>
  <li><a href="#Updating-hydrapwk">Updating hydrapwk</a> - Update hydrapwk using fresh image or APT.</li>
</ul>

<h1 id="hydrapwk-logo-20">HydraPWK Logo 2.0</h1>

<p>so! say hy! to hydrapwk logo 2.0! This is updated logo from HydraPWK 1.0
what’s the different?</p>

<p>as you can see the different between HydraPWK Logo 1.0
and new logo (2.0), we made some changes as you can see bellow, like wings, and hydrapwk body…</p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.03-apes/hydrapwk-logo-2.0.png" alt="HydraPWK Logo 2.0" /></p>

<p><a href="/doc/hydrapwk-policy-trademark">Check more details</a></p>

<h1 id="new-tools">New tools</h1>

<ul>
  <li><a href="/doc/tools/hydrapwk-tools-elasticsearch">elasticsearch</a> - Elasticsearch is a distributed search and analytics engine, scalable data store and vector database optimized for speed and relevance on production-scale workloads.</li>
  <li><a href="/doc/tools/hydrapwk-tools-arkime">Arkime</a> - scalable packet capture</li>
</ul>

<h1 id="arkime-and-elasticsearch">Arkime And elasticsearch</h1>

<p>Please read the tool documentation for <a href="/doc/tools/hydrapwk-tools-arkime">Arkime</a> and <a href="/doc/tools/hydrapwk-tools-elasticsearch">Elasticsearch/elasticsearch service</a></p>

<p>As default hydrapwk using <code class="language-plaintext highlighter-rouge">elasticsearch as backend of arkime</code>
and vice versa <code class="language-plaintext highlighter-rouge">elasticsearch</code> would be backend for several tools like <code class="language-plaintext highlighter-rouge">arkime</code> on the future.(I hope)</p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.03-apes/hydrapwk-arkime.png" alt="Arkime" /></p>

<h1 id="polkit-rules">Polkit rules</h1>

<p>Here is we made polkit rules for hydrapwk menu</p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.03-apes/hydrapwk-polkit.png" alt="HydraPWK Pkexec window" /></p>

<h1 id="desktop-changes">Desktop changes</h1>

<p>Here is! the one of the good part <code class="language-plaintext highlighter-rouge">hydrapwk-purplizer</code> and</p>

<p>like we say before hydrapwk now is not just for pentesting
 and we’ve been made new category <code class="language-plaintext highlighter-rouge">defensive</code> category! based on NIST CSF 2.0 Framework!</p>

<blockquote>
  <p>HydraPWK Menu</p>
</blockquote>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.03-apes/hydrapwk-menu-defense.png" alt="HydraPWK Menu Defense" /></p>

<blockquote>
  <p>HydraPWK Desktop</p>
</blockquote>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.03-apes/hydrapwk-desktop.png" alt="HydraPWK Menu Defense" /></p>

<h1 id="tools-doc">Tools doc</h1>

<p>so yeah we’ve been made <a href="/doc/tools">Tools documentation page</a> hydrapwk several weeks ago i guess, but yeah we still need to improvement to the Documentation…
but ofc! You could contribute.
how? The hydrapwk page is hosted by GitHub and Jekyll so you could easily edit the markdown, on the tools doc on the bottom left corner you will see <code class="language-plaintext highlighter-rouge">Edit this page</code> button, and you can click it!</p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.03-apes/hydrapwk-tools-doc.png" alt="HydraPWK tools page" /></p>

<h1 id="hardware-requirements">Hardware requirements</h1>

<p>here is, this is our recommandation (Minimal) hardware to run hydrapwk.</p>

<table>
  <thead>
    <tr>
      <th style="text-align: center">RAM</th>
      <th style="text-align: center">DISK</th>
      <th style="text-align: center">CPU</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td style="text-align: center">8-16GB</td>
      <td style="text-align: center">16GB+</td>
      <td style="text-align: center">intel i3</td>
    </tr>
  </tbody>
</table>

<h1 id="updating-hydrapwk">Updating hydrapwk</h1>

<blockquote>
  <p>Update hydrapwk using fresh image? Yes you can <a href="/get">Get hydrapwk image now</a></p>
</blockquote>

<p>so yeah don’t worry, if you have already hydrapwk yellowdog you can update you’re hydrapwk to the latest version (Apes) easily.</p>

<p>we’ve been made <code class="language-plaintext highlighter-rouge">hydrapwk-helper</code> it will automatically
change the <code class="language-plaintext highlighter-rouge">yellowdog repo to apes</code> but how?</p>

<p>its enough that’s because the <code class="language-plaintext highlighter-rouge">hydrapwk-helper</code> has part of <code class="language-plaintext highlighter-rouge">hydrapwk-utilities</code> metapackages</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>hydrapwk@hydrapwk:~$ sudo apt update &amp;&amp; sudo apt full-upgrade -y # this is will pull `hydrapwk-helper`
[...] # After thats you need to initialize hydrapwk apes
hydrapwk@hydrapwk:~$ sudo apt update &amp;&amp; sudo apt full-upgrade
</code></pre></div></div>

<p>And boom! now you could check your hydrapwk version</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>hydrapwk@hydrapwk:~$ grep VERSION /usr/lib/os-release
# Now the output should be `apes`
</code></pre></div></div>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[New release HydraPWK GNU/Linux 2025.03 (Apes) - hydrapwk purplizer, arkime, elasticsearch, tools documentation page]]></summary></entry><entry><title type="html">HydraPWK update - (GTK themes, new tools, icons update)</title><link href="https://nethydra.github.io/blog/hydrapwk-update-theme-tools-icons" rel="alternate" type="text/html" title="HydraPWK update - (GTK themes, new tools, icons update)" /><published>2025-09-19T16:30:00+00:00</published><updated>2025-09-19T16:30:00+00:00</updated><id>https://nethydra.github.io/blog/hydrapwk-update-theme-tools-icons</id><content type="html" xml:base="https://nethydra.github.io/blog/hydrapwk-update-theme-tools-icons"><![CDATA[<p>Today, HydraPWK update GTK themes, new icons and tools.</p>

<blockquote>
  <p>Once again, if you still using HydraPWK (Transition) IMAGE/ISOs <code class="language-plaintext highlighter-rouge">2025.01.6.5.*</code> please update into the latest HydraPWK IMAGE/ISOs.</p>
</blockquote>

<h1 id="whats-new">What’s new?</h1>

<ul>
  <li>new themes - <a href="#new-themes">Dark theme for HydraPWK</a></li>
  <li>new tools - <a href="#new-tools">esptool, Caringcaribou</a></li>
  <li>new icons - <a href="#new-icons">new icons for HydraPWK tools</a></li>
</ul>

<h1 id="new-tools">New tools</h1>

<ul>
  <li>esptool - <a href="https://github.com/espressif/esptool">tools for flashing and related esp from espressife</a></li>
  <li>caringcaribou - <a href="https://github.com/CaringCaribou/caringcaribou">A friendly car security exploration tool for the CAN bus</a></li>
</ul>

<h1 id="new-themes">New themes</h1>

<p><img src="/assets/graphics/post_graphics/hydrapwk-update-theme-tools-icons/hydrapwk-htop.png" alt="HydraPWK Dark GTK theme" /></p>

<p>In this update we’re adding new GTK theme (dark theme <code class="language-plaintext highlighter-rouge">fork from skeuos gtk</code>) for HydraPWK! Previously we’re only providing <code class="language-plaintext highlighter-rouge">light theme</code>.</p>

<p>Honestly this is not pure <code class="language-plaintext highlighter-rouge">dark</code> theme, this is combination <code class="language-plaintext highlighter-rouge">light</code> and <code class="language-plaintext highlighter-rouge">dark</code> colors but don’t worry, for base themes we’re using <code class="language-plaintext highlighter-rouge">dark</code> color!.</p>

<p>If you using latest HydraPWK (codename yellowdog) you can easily install this time, use APT!.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># if you using `hydrapwk-2025.02.250817233-yellowdog-T2` IMAGE/ISOs you don't need to doing this
...
hydrapwk@hydrapwk:~$ sudo apt update &amp;&amp; sudo apt full-upgrade -y # wait until the process done
...
...
hydrapwk@hydrapwk:~$ cp -r /etc/skel/.config/xfce4 ~/.config # only if you want to using dotfiles HydraPWK!
...
</code></pre></div></div>

<h1 id="new-icons">New icons</h1>

<p>And we have been creating new icons for HydraPWK tools, you can see image below!.</p>

<p><img src="/assets/graphics/post_graphics/hydrapwk-update-theme-tools-icons/hydrapwk-new-icons.png" alt="HydraPWK Icons" /></p>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[Today, HydraPWK Update new GTK theme (Hydra-Dark), new icons for HydraPWK tools, new tools.]]></summary></entry><entry><title type="html">HydraPWK new snapshot - (snapshot, metapackages, tools, drop support HydraPWK Transition)</title><link href="https://nethydra.github.io/blog/hydrapwk-new-snapshot-and-new-tools" rel="alternate" type="text/html" title="HydraPWK new snapshot - (snapshot, metapackages, tools, drop support HydraPWK Transition)" /><published>2025-09-12T22:49:00+00:00</published><updated>2025-09-12T22:49:00+00:00</updated><id>https://nethydra.github.io/blog/hydrapwk-new-snapshot-and-new-tools</id><content type="html" xml:base="https://nethydra.github.io/blog/hydrapwk-new-snapshot-and-new-tools"><![CDATA[<p>Today, in HydraPWK post new snapshot, metapackages, tools, drop support for HydraPWK Transition release.</p>

<h1 id="whats-new">What’s new?</h1>

<ul>
  <li>New tools added - <a href="#kismet">kismet</a></li>
  <li>New metapackages - <a href="#linux-image-xhydra">linux-image-xhydra metapackages</a></li>
  <li>Drop support - <a href="#drop-support">Discontinued HydraPWK (2025.01.6.5.*)support and repo</a></li>
</ul>

<h1 id="kismet">Kismet</h1>

<p>Now kismet added in HydraPWK repo!</p>

<p>What is kismet?</p>

<p>Kismet is an open source sniffer, WIDS, wardriver, and packet capture tool for Wi-Fi, Bluetooth, BTLE, wireless thermometers, airplanes, power meters, Zigbee.</p>

<h1 id="drop-packages-support">Drop packages support</h1>

<p>Here is, In the near future, this tool will no longer be included in the HydraPWK repository.</p>

<ul>
  <li>squarephish</li>
  <li>ufonet</li>
</ul>

<p>You can also, check this pages for information (status) tools in HydraPWK.</p>

<p><a href="https://hydrapwk.github.io/doc/tools-tracker">HydraPWK tools status</a></p>

<h1 id="linux-image-xhydra">Linux image xhydra</h1>

<p>We’ve been made new metapackages for HydraPWK.</p>

<p>What Is this for?</p>

<p>If you know about metapackages like <code class="language-plaintext highlighter-rouge">linux-image-amd64</code> on Debian, linux-image-xhydra Acting same (do same job) as a metapckages for kernel update, and it will make easier for us (me) for giving an update.</p>

<p>With hope, making it easier when updating, so you don’t need to manually choosing kernel version, just use <code class="language-plaintext highlighter-rouge">apt</code> for upgrading kernel for HydraPWK.</p>

<p>If you using new IMAGE/ISOs (hydrapwk-2025.02.250817233-yellowdog-T1) you could skip this step.</p>

<p>Installing linux-image-xhydra on your HydraPWK machine</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>...
sudo apt update
sudo apt install -y linux-image-xhydra
...
</code></pre></div></div>

<h1 id="drop-support">Drop support.</h1>

<p>With this we drop support (discontinued) for the release of Hydrapwk with the release of the code <code class="language-plaintext highlighter-rouge">'Transition' (2025.01.6.5.*) Debian Trixie base</code>, and we could fully working for <code class="language-plaintext highlighter-rouge">HydraPWK yellowdog release</code>!.</p>

<p>And with that’s, good bye transition!.</p>

<h1 id="support-and-resources">Support and resources</h1>

<p>GitHub issues - <a href="https://github.com/hydrapwk/hydrapwk/issues/">Have problem or critique? Open issues now!</a></p>

<p>Troubleshoot pages - <a href="https://hydrapwk.github.io/doc/troubleshot">HydraPWK Official Troubleshoot page</a></p>

<p>Reddit community - <a href="http://reddit.com/r/hydrapwk">HydraPWK Official subredit</a></p>

<p>Telegram community - <a href="https://t.me/blacktracksec">HydraPWK Official Telegram Community</a></p>

<p>Mastodon - <a href="https://infosec.exchange/@hydrapwk">infosec.exchange</a></p>

<p>Distrowatch - <a href="https://distrowatch.com/table.php?distribution=hydrapwk">HydraPWK distrowatch page</a></p>

<h1 id="latest-independent-review-about-hydrapwk">latest independent review about HydraPWK</h1>

<blockquote>
  <p>Newest review</p>
</blockquote>

<p>connectwww - <a href="https://youtu.be/adWY0YY8j4Q?si=RerYTmPIObhMOhX4">How to Install HydraPWK Linux on VirtualBox</a></p>

<p>iguru.gr - <a href="https://iguru.gr/hydrapwk-avgoustos-stress-test-cracking-reversing-forensics/">HydraPWK (Αύγουστος) Stress Test, Cracking, Reversing, Forensics</a></p>

<p>..</p>

<blockquote>
  <p>Older review</p>
</blockquote>

<p>Penguinreviewlinux.org - <a href="https://penguinreviewslinux.blogspot.com/2025/08/hydrapwk-gnulinux-20250165250806258.html?m=1">HydraPWK GNU/Linux 2025.01.6.5.250806258: Distribuția open-source pentru hacking și pentesting, cu nucleu Real-Time și unelte avansate</a></p>

<p>Desdelinux - <a href="https://blog.desdelinux.net/top-nuevas-distros-gnu-linux-2025-08/">Top nuevas Distros Linux / BSD a ser reconocidas en 2025: Parte 08</a>
<a href="https://penguinreviewslinux.blogspot.com/2025/08/hydrapwk-gnulinux-20250165250806258.html?m=1">Penguin reviews</a></p>

<p>Gladilov.org.ru - <a href="https://www.gladilov.org.ru/blog/all/new-virtual-os-22-07-2025/">Новая виртуальная ОСь — 22.07.2025</a></p>

<p>NX11Dev <a href="https://m.bilibili.com/video/BV14pbXzJE5J">HydraPWK GNU/Linux：Debian系渗透测试利器，以开源之力筑牢网络安全防线</a></p>

<p><a href="https://iguru.gr/hydrapwk-scan-stress-test-exploitation-cracking-reversing-forensics/">Iguru.gr</a></p>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[Today, in HydraPWK post new snapshot, metapackages linux-image-xhydra, Kismet, drop support for HydraPWK Transition release.]]></summary></entry><entry><title type="html">HydraPWK on Distrowatch</title><link href="https://nethydra.github.io/blog/hydrapwk-on-distrowatch-community-polkitd" rel="alternate" type="text/html" title="HydraPWK on Distrowatch" /><published>2025-09-09T14:49:00+00:00</published><updated>2025-09-09T14:49:00+00:00</updated><id>https://nethydra.github.io/blog/hydrapwk-on-distrowatch-community-polkitd</id><content type="html" xml:base="https://nethydra.github.io/blog/hydrapwk-on-distrowatch-community-polkitd"><![CDATA[<p>Today, in HydraPWK post in this time we will giving good and little bad news, and also polkitd as dependencies in our metapackages.</p>

<h1 id="hydrapwk-on-distrowatch">HydraPWK on distrowatch</h1>

<p>Even though it hasn’t been officially announced by distrowatch, looking at the <a href="https://distrowatch.com/table.php?distribution=hydrapwk">HydraPWK page on distrowatch</a>, we decided to make our own post about it.</p>

<p>Almost three years developing <a href="https://hydrapwk.github.io/doc/introduction/about-hydra">HydraPWK</a> (Formerly known as <a href="https://hydrapwk.github.io/doc/introduction/hydra-history">BlackTrack</a>) and this time has come and we’re (I’m) very excited about it, looking and developing how this project growing, until like this, maybe you just thinking this project is bad, this project is too ambitious, you’re not wrong about that’s maybe you right.</p>

<p>And the first achievement was getting into distrowatch, I mean, less than two months since we submitted this project and that was one of our best achievements, In less than two months, this small project made it onto the distrowatch page among other big projects!.</p>

<p>And we’re very thank you about it!, and with our loyal community especially Mr.pro and Fox47, I’m very thank you with you guys! Thanks once again, You’ve been with me all the way from the first time this project was created(BlackTrack) until now!(HydraPWK).</p>

<h1 id="we-got-banned-from-reddit">We got banned from reddit</h1>

<p>If you looking our previous announcement (<a href="https://hydrapwk.github.io/blog/hydrawpk-migrate">HydraPWK Migrate</a>) we’re giving announcement, if we’re making new sub community on <a href="https://reddit.com/r/hydrapwk">reddit r/hydrapwk</a> and mastodon (<a href="https://infosec.exchange/@hydrapwk">infosec.exchange</a>) but yeah sadly we got banned from reddit.</p>

<p>We have submitted an appeal to Reddit, but until now there has been no response. We hope that the Reddit platform (mods) will investigate it immediately.</p>

<h1 id="polkitd">polkitd</h1>

<p>We are currently weighing the pros and cons of adding polkitd to our IMAGE/ISO (as a dependency on our desktop metapackages).</p>

<p>We calculate the pros and cons on HydraPWK performance (polkitd will enter as autostart on the desktop) If the benefits are greater, perhaps we will consider making it part of the metapackage (dependencies hydrapwk-default-desktop).</p>

<h1 id="thanks">Thanks!</h1>

<p>And to conclude this post, we’d like to thank Debian and its community and developers! Without them, this project wouldn’t exist!.</p>

<p>Once again, thanks everyone! Don’t forget you’re free to open issues and giving critique off course.</p>

<h1 id="support-and-resources">Support and resources</h1>

<p>GitHub issues - <a href="https://github.com/hydrapwk/hydrapwk/issues/">Have problem or critique? Open issues now!</a></p>

<p>Troubleshoot pages - <a href="https://hydrapwk.github.io/doc/troubleshot">HydraPWK Official Troubleshoot page</a></p>

<p>Reddit community - <a href="http://reddit.com/r/hydrapwk">HydraPWK Official subredit</a></p>

<p>Telegram community - <a href="https://t.me/blacktracksec">HydraPWK Official Telegram Community</a></p>

<p>Mastodon - <a href="https://infosec.exchange/@hydrapwk">infosec.exchange</a></p>

<p>Distrowatch - <a href="https://distrowatch.com/table.php?distribution=hydrapwk">HydraPWK distrowatch page</a></p>

<h1 id="latest-independent-review-about-hydrapwk">latest independent review about HydraPWK</h1>

<blockquote>
  <p>Newest review</p>
</blockquote>

<p>connectwww - <a href="https://youtu.be/adWY0YY8j4Q?si=RerYTmPIObhMOhX4">How to Install HydraPWK Linux on VirtualBox</a></p>

<p>iguru.gr - <a href="https://iguru.gr/hydrapwk-avgoustos-stress-test-cracking-reversing-forensics/">HydraPWK (Αύγουστος) Stress Test, Cracking, Reversing, Forensics</a></p>

<p>..</p>

<blockquote>
  <p>Older review</p>
</blockquote>

<p>Penguinreviewlinux.org - <a href="https://penguinreviewslinux.blogspot.com/2025/08/hydrapwk-gnulinux-20250165250806258.html?m=1">HydraPWK GNU/Linux 2025.01.6.5.250806258: Distribuția open-source pentru hacking și pentesting, cu nucleu Real-Time și unelte avansate</a></p>

<p>Desdelinux - <a href="https://blog.desdelinux.net/top-nuevas-distros-gnu-linux-2025-08/">Top nuevas Distros Linux / BSD a ser reconocidas en 2025: Parte 08</a>
<a href="https://penguinreviewslinux.blogspot.com/2025/08/hydrapwk-gnulinux-20250165250806258.html?m=1">Penguin reviews</a></p>

<p>Gladilov.org.ru - <a href="https://www.gladilov.org.ru/blog/all/new-virtual-os-22-07-2025/">Новая виртуальная ОСь — 22.07.2025</a></p>

<p>NX11Dev <a href="https://m.bilibili.com/video/BV14pbXzJE5J">HydraPWK GNU/Linux：Debian系渗透测试利器，以开源之力筑牢网络安全防线</a></p>

<p><a href="https://iguru.gr/hydrapwk-scan-stress-test-exploitation-cracking-reversing-forensics/">Iguru.gr</a></p>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[HydraPWK on distrowatch, community, planning polkitd for metapackages.]]></summary></entry><entry><title type="html">Modernize your HydraPWK to deb822 style format</title><link href="https://nethydra.github.io/blog/hydrapwk-modernize" rel="alternate" type="text/html" title="Modernize your HydraPWK to deb822 style format" /><published>2025-09-06T00:13:00+00:00</published><updated>2025-09-06T00:13:00+00:00</updated><id>https://nethydra.github.io/blog/hydrapwk-modernize</id><content type="html" xml:base="https://nethydra.github.io/blog/hydrapwk-modernize"><![CDATA[<p>Today in HydraPWK post in this post will tell you how to modernize your hydrapwk <code class="language-plaintext highlighter-rouge">.list</code> (only for <a href="https://hydrapwk.github.io/blog/hydrapwk-release-yellowdog">HydraPWK yellowdog release</a>) and we just updating our ISO snapshot (<a href="https://hydrapwk.github.io/blog/hydrapwk-release-yellowdog">yellowdog</a>) if you using <code class="language-plaintext highlighter-rouge">hydrapwk-2025.02.250817233-yellowdog-deb822-amd64.iso</code> you can skip this post!</p>

<h1 id="requirements">requirements</h1>

<p>if you doesn’t have <code class="language-plaintext highlighter-rouge">wget</code> you can easily install with</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>...
hydrapwk@hydrapwk:~$ sudo apt update &amp;&amp; sudo apt install -y wget
...
</code></pre></div></div>

<h1 id="update-sources">update sources</h1>

<p>don’t worry we have been make script to update your sources!.</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>...
hydrapwk@hydrapwk:~$ wget -qO- https://gitlab.com/hydrapwk/documentation/archives/-/raw/main/checksum/misc/hydrapwk-modernize.sh | sudo bash
...
</code></pre></div></div>

<p>verify your sources</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>...
hydrapwk@hydrapwk:~$ ls /etc/apt/sources.list.d/*.sources # see output bellow

debian.sources hydrapwk.sources # make sure the output same like this
...
</code></pre></div></div>

<p>Try to update</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>...
hydrapwk@hydrapwk:~$ sudo apt update # if you getting error while run this, you're free to contact us.
...
</code></pre></div></div>

<h1 id="latest-independent-review-about-hydrapwk">latest independent review about HydraPWK</h1>

<blockquote>
  <p>Newest review</p>
</blockquote>

<p>connectwww - <a href="https://youtu.be/adWY0YY8j4Q?si=RerYTmPIObhMOhX4">How to Install HydraPWK Linux on VirtualBox</a></p>

<p>iguru.gr - <a href="https://iguru.gr/hydrapwk-avgoustos-stress-test-cracking-reversing-forensics/">HydraPWK (Αύγουστος) Stress Test, Cracking, Reversing, Forensics</a></p>

<p>..</p>

<blockquote>
  <p>Older review</p>
</blockquote>

<p>Penguinreviewlinux.org - <a href="https://penguinreviewslinux.blogspot.com/2025/08/hydrapwk-gnulinux-20250165250806258.html?m=1">HydraPWK GNU/Linux 2025.01.6.5.250806258: Distribuția open-source pentru hacking și pentesting, cu nucleu Real-Time și unelte avansate</a></p>

<p>Desdelinux - <a href="https://blog.desdelinux.net/top-nuevas-distros-gnu-linux-2025-08/">Top nuevas Distros Linux / BSD a ser reconocidas en 2025: Parte 08</a>
<a href="https://penguinreviewslinux.blogspot.com/2025/08/hydrapwk-gnulinux-20250165250806258.html?m=1">Penguin reviews</a></p>

<p>Gladilov.org.ru - <a href="https://www.gladilov.org.ru/blog/all/new-virtual-os-22-07-2025/">Новая виртуальная ОСь — 22.07.2025</a></p>

<p>NX11Dev <a href="https://m.bilibili.com/video/BV14pbXzJE5J">HydraPWK GNU/Linux：Debian系渗透测试利器，以开源之力筑牢网络安全防线</a></p>

<p><a href="https://iguru.gr/hydrapwk-scan-stress-test-exploitation-cracking-reversing-forensics/">Iguru.gr</a></p>

<p><code class="language-plaintext highlighter-rouge">(Thanks for the review!)</code></p>
<h1 id="community-support">community support</h1>

<p>GitHub issues - <a href="https://github.com/hydrapwk/hydrapwk/issues">Open issues</a></p>

<p>Troubleshoot pages - <a href="https://hydrapwk.github.io/doc/troubleshot">HydraPWK Official Troubleshoot page</a></p>

<p>Reddit community - <a href="http://reddit.com/r/hydrapwk">HydraPWK Official subredit</a></p>

<p>Telegram community - <a href="https://t.me/blacktracksec">HydraPWK Official Telegram Community</a></p>

<p>Mastodont - <a href="https://infosec.exchange/@hydrapwk">infosec.exchange</a></p>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[Modernize your HydraPWK - (Update HydraPWK yellowdog sources to deb822 format)]]></summary></entry><entry><title type="html">HydraPWK 2025.02.250817233 yellowdog release (new tools, netexec, hydrapwk-menu, Debian forky/sid base)</title><link href="https://nethydra.github.io/blog/hydrapwk-release-yellowdog" rel="alternate" type="text/html" title="HydraPWK 2025.02.250817233 yellowdog release (new tools, netexec, hydrapwk-menu, Debian forky/sid base)" /><published>2025-08-29T23:37:00+00:00</published><updated>2025-08-29T23:37:00+00:00</updated><id>https://nethydra.github.io/blog/hydrapwk-release-yellowdog</id><content type="html" xml:base="https://nethydra.github.io/blog/hydrapwk-release-yellowdog"><![CDATA[<p>Today, in HydraPWK Post HydraPWK released new version of HydraPWK (yellowdog 2025.02.250817233) like we said in previous announcement <a href="https://hydrapwk.github.io/blog/hydrawpk-migrate">here</a>
we will migrate from “Debian Trixie base” into “Debian Forky/sid” and we’ve been announcement in our community group (reddit, telegram and mastodon)
we just freeze HydraPWK version 2025.01.6.5.* so we can focus on “Debian Forky/sid base” maybe you confused about our release “semi-rolling”.</p>

<p>What’s actually “semi-rolling” means(in HydraPWK)? Actually it’s very, very different from “rolling” release, if we release new version HydraPWK with same
“branch or same base” we can still handle that’s, but if release with new branch (base) so we will cut-off or Freeze (previous release which used older base) but
don’t worry we will still give you update like fixed bug for 1-2 weeks? We can’t make sure that’s and If we feel the new base is “sufficient”,
we will migrate completely to the new base.</p>

<h1 id="whats-new">What’s new?</h1>

<ul>
  <li>menu refresh - <a href="#menu-refresh">Hybrid MITRE ATT&amp;CK Tactics</a></li>
  <li>new tools - <a href="#new-tools">netexec, modpoll, exploitdb</a></li>
  <li>kernel - <a href="#kernel-update">updating kernel to version 6.16</a></li>
  <li>can-j19399 - <a href="#kernel-update">new pre-built can-j19399 module</a></li>
  <li>separate metapackages - <a href="#separate-metapackages">Remove hydrapwk-default-tools from hydrapwk-defaults</a></li>
  <li>expanding impacket library - <a href="#impacket-library">Expanding impacket library impacket-*</a></li>
</ul>

<h1 id="menu-refresh">Menu refresh</h1>
<ul>
  <li>01-Reconnaise</li>
  <li>02-Resource development</li>
  <li>03-Initial Access</li>
  <li>04-Execution</li>
  <li>05-Persistence</li>
  <li>…</li>
  <li>Until 17-Forensic :)</li>
</ul>

<p><img src="/assets/graphics/post_graphics/hydrapwk-2025.02-yellowdog/hydrapwk-menu.png" alt="HydraPWK Applications menus MITRE ATT&amp;CK Hybird" /></p>

<p>As you can seen we’ve been “Update menu” for HydraPWK, Which this menu folllowing “Mitre ATT&amp;CK” tactics (Hybird Enterpise and Industry).</p>

<h1 id="new-tools">New tools</h1>
<p>new tools Added on This release!</p>

<ul>
  <li>netexec</li>
</ul>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>usage: netexec [-h] [--version] [-t THREADS] [--timeout TIMEOUT]
               [--jitter INTERVAL] [--verbose] [--debug] [--no-progress]
               [--log LOG] [-6] [--dns-server DNS_SERVER] [--dns-tcp]
               [--dns-timeout DNS_TIMEOUT]
               {vnc,rdp,smb,ftp,nfs,mssql,wmi,ssh,winrm,ldap} ...

     .   .
    .|   |.     _   _          _     _____
    ||   ||    | \ | |   ___  | |_  | ____| __  __   ___    ___
    \\( )//    |  \| |  / _ \ | __| |  _|   \ \/ /  / _ \  / __|
    .=[ ]=.    | |\  | |  __/ | |_  | |___   &gt;  &lt;  |  __/ | (__
  / /Ë™-Ë™\ \  |_| \_|  \___|  \__| |_____| /_/\_\  \___|  \___|
  Ë™ \   / Ë™
    Ë™   Ë™

    The network execution tool
    Maintained as an open source project by @NeffIsBack, @MJHallenbeck, @_zblurx

    For documentation and usage examples, visit: https://www.netexec.wiki/

    Version : 1.4.0+hydrapwk1
    Codename: SmoothOperator
    Commit  :

options:
  -h, --help            show this help message and exit

Generic:
  Generic options for nxc across protocols

  --version             Display nxc version
  -t, --threads THREADS
                        set how many concurrent threads to use
  --timeout TIMEOUT     max timeout in seconds of each thread
  --jitter INTERVAL     sets a random delay between each authentication

Output:
  Options to set verbosity levels and control output

  --verbose             enable verbose output
  --debug               enable debug level information
  --no-progress         do not displaying progress bar during scan
  --log LOG             export result into a custom file

DNS:
  -6                    Enable force IPv6
  --dns-server DNS_SERVER
                        Specify DNS server (default: Use hosts file &amp; System DNS)
  --dns-tcp             Use TCP instead of UDP for DNS queries
  --dns-timeout DNS_TIMEOUT
                        DNS query timeout in seconds

Available Protocols:
  {vnc,rdp,smb,ftp,nfs,mssql,wmi,ssh,winrm,ldap}
    vnc                 own stuff using VNC
    rdp                 own stuff using RDP
    smb                 own stuff using SMB
    ftp                 own stuff using FTP
    nfs                 own stuff using NFS
    mssql               own stuff using MSSQL
    wmi                 own stuff using WMI
    ssh                 own stuff using SSH
    winrm               own stuff using WINRM
    ldap                own stuff using LDAP

</code></pre></div></div>
<ul>
  <li>exploitdb(searchsploit)</li>
  <li>modpoll</li>
</ul>

<h1 id="impacket-library">Impacket library</h1>

<p>So, yeah for make easier we’re decide to expand some impacket library, so you don’t need to enter /usr/share/doc/python3-impacket/examples/ directory</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>/usr/bin/impacket-atexec	/usr/bin/impacket-registry-read
/usr/bin/impacket-changepasswd	/usr/bin/impacket-regsecrets
/usr/bin/impacket-dcomexec	/usr/bin/impacket-rpcdump
/usr/bin/impacket-exchange	/usr/bin/impacket-rpcmap
/usr/bin/impacket-samrdump      /usr/bin/impacket-mimikatz
/usr/bin/impacket-mqtt_check	/usr/bin/impacket-smbclient
/usr/bin/impacket-mssqlclient	/usr/bin/impacket-smbexec
/usr/bin/impacket-netview	/usr/bin/impacket-smbserver
/usr/bin/impacket-ping		/usr/bin/impacket-sniff
/usr/bin/impacket-ping6		/usr/bin/impacket-sniffer
/usr/bin/impacket-psexec	/usr/bin/impacket-ticketConverter
/usr/bin/impacket-rdp_check	/usr/bin/impacket-ticketer
/usr/bin/impacket-reg		/usr/bin/impacket-wmiexec
/usr/bin/impacket-secretsdump
</code></pre></div></div>

<h1 id="kernel-update">Kernel Update</h1>

<p>So we have update HydraPWK kernel to latest stable Linux kernel 6.16 and Enabling “can-j1939” modules</p>

<h1 id="seperate-metapackages">Seperate metapackages</h1>

<p>As you know in our HydraPWK version 2025.01.6.5.* we combine packages hydrapwk-default-tools inside hydrapwk-defaults as dependencies.</p>

<p>and we relize it’s not a good things, so we decide to remove hydrapwk-default-tools from hydrapwk-defaults (as dependencies), and not including in ISO/IMAGE
that’s because as you know, if you delete, just one tools, your environment will broke, were very sorry about thats.</p>

<p>don’t worry you’re free now to remove tools.</p>

<h1 id="upgrading">Upgrading</h1>

<p>So like we said before, this release we’re using Debian Forky/sid as base, so you need to download <code class="language-plaintext highlighter-rouge">beta iso for updating</code>, but don’t worry if you doesn’t want to update to ‘This release (beta) with codename yellowdog’ you can still using stable base, but ofc it’s will got freeze, but don’t worry we will maintenance the repo for stable base for maybe 1 week</p>]]></content><author><name>Joe</name></author><summary type="html"><![CDATA[Release beta HydraPWK yellowdog 2025.02.250817233 - (netexec, exploitdb, modpoll, 6.16 kernel, Debian Forky/sid base)]]></summary></entry></feed>