If you’re working with Node.js <code>Buffer</code> be aware that it has a shared memory pool.
When you create 2 buffers that occupy small memory space (under 8kb), their content is placed in the same memory pool.
<pre><code class="language-javascript">// Some private key information
const privateKey = Buffer.from(&#x27;private key&#x27;);
const hackyBuffer = Buffer.from(&#x27;1&#x27;);

const typedArray = new Uint8Array(hackyBuffer.buffer)
 .filter(value =&gt; value !== 0);
const charCodes = Array.from(typedArray);

// Prints &quot;//private key1&quot;
console.log(String.fromCodePoint(...charCodes));
</code></pre>
Notice that we’re not referencing the <code>privateKey</code> buffer in any way after its declaration and are still able to get its content via the buffer that we created elsewhere in the program.

News, updates, and discussions about everything happening in and around the Node.js runtime.

Node.js developers

Node.js `Buffer` objects share a memory pool for small memory spaces (under 8kb). This can lead to unexpected data exposure, as demonstrated by creating two buffers that reveal a private key through another buffer instance. It's crucial to be aware of this behavior to avoid security risks.

Be aware of Node.js Buffer shared memory pool

this might be obvious info, but i wanted to point out that this happens in Node.js and when using <code>import { Buffer } from &quot;node:buffer&quot;;</code> in Deno, but Bun does not have this problem