<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Javascript on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/javascript/</link><description>Recent content in Javascript on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 07 May 2026 14:42:24 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/javascript/index.xml" rel="self" type="application/rss+xml"/><item><title>vm2 Node.js Sandbox Escape 12 Critical Vulnerabilities Two Without a Patch</title><link>https://hackingpassion.com/vm2-sandbox-escape/</link><pubDate>Thu, 07 May 2026 14:42:24 +0200</pubDate><guid>https://hackingpassion.com/vm2-sandbox-escape/</guid><description>&lt;p>Twelve critical vulnerabilities were just published for &lt;strong>vm2&lt;/strong>, a Node.js security library that sits inside millions of applications. Three of them score a perfect 10 out of 10. The creator shut the project down in 2023 because it was too broken to fix, restarted it anyway in October 2025, and here we are.&lt;/p>
&lt;p>The library is called &lt;strong>vm2&lt;/strong>. When a platform lets users run their own code, that code needs somewhere to run where it cannot touch anything it should not touch. Not the files on the server, not the ability to run system commands, not connections to other services. That sealed-off space where code runs but cannot escape is called a &lt;strong>sandbox&lt;/strong>. &lt;strong>vm2&lt;/strong> was the tool &lt;strong>Node.js&lt;/strong> developers used to build one.&lt;/p></description></item><item><title>Axios npm Supply Chain Attack: How a Fake Meeting Compromised 100 Million Downloads</title><link>https://hackingpassion.com/axios-npm-supply-chain-attack/</link><pubDate>Sat, 04 Apr 2026 13:50:24 +0200</pubDate><guid>https://hackingpassion.com/axios-npm-supply-chain-attack/</guid><description>&lt;p>Axios, the JavaScript library with over &lt;strong>100 million weekly downloads&lt;/strong>, was compromised on March 31st. For roughly three hours, every fresh install of those two versions silently dropped a &lt;strong>remote access trojan&lt;/strong> on the machine that ran it. Windows, macOS, and Linux, all targeted. The installation completed normally, nothing flagged the change, and the backdoor was already running by the time the command finished. 😏&lt;/p>
&lt;p>Axios is a JavaScript HTTP client that developers use to send web requests from their applications. It ships inside frontend frameworks, backend services, mobile apps, and &lt;strong>CI/CD pipelines&lt;/strong>, and if a company runs Node.js anywhere in their stack, Axios is almost certainly somewhere in that dependency tree. That is what made this attack so significant.&lt;/p></description></item><item><title>Linux Inside a PDF</title><link>https://hackingpassion.com/linux-inside-pdf/</link><pubDate>Mon, 26 Jan 2026 10:30:00 +0100</pubDate><guid>https://hackingpassion.com/linux-inside-pdf/</guid><description>&lt;p>Linux running inside a PDF. An actual working operating system with a terminal where you can type commands. Open a PDF in Chrome. Wait 30 seconds. You now have a working Linux terminal. No installation, no software, just a 6MB file that boots an entire operating system.&lt;/p>
&lt;p>A high school student named Allen built this, the same kid who previously crammed Doom into a PDF. Before that he made tools to bypass school software restrictions and exploits to boot Linux on locked-down Chromebooks.&lt;/p></description></item></channel></rss>