diff --git a/src/content/cre/concepts/typescript-wasm-runtime.mdx b/src/content/cre/concepts/typescript-wasm-runtime.mdx
index 61be85dfe05..26a4c671eb0 100644
--- a/src/content/cre/concepts/typescript-wasm-runtime.mdx
+++ b/src/content/cre/concepts/typescript-wasm-runtime.mdx
@@ -34,6 +34,11 @@ Javy uses [QuickJS](https://bellard.org/quickjs), a lightweight JavaScript engin
 
 Not all Node.js built-in modules are available. For example, `node:crypto` is not supported. Before using third-party NPM packages, verify they don't rely on unsupported Node.js APIs.
 
+{/* prettier-ignore */}
+<Aside type="tip" title="Cryptography libraries">
+  If you need cryptographic functions, <a href="https://paulmillr.com/noble/" target="_blank" rel="noopener noreferrer">Noble</a> is a popular JavaScript cryptography library with minimal dependencies that works well with QuickJS. Always verify any third-party library in simulation before deploying.
+</Aside>
+
 <Aside type="note" title="Note on async/await with SDK capabilities">
   While JavaScript `Promise` and `async/await` are supported by QuickJS, **SDK capabilities do not use them**. The CRE
   TypeScript SDK uses a custom `.result()` pattern instead. See the [Core SDK
diff --git a/src/content/cre/getting-started/before-you-build-ts.mdx b/src/content/cre/getting-started/before-you-build-ts.mdx
index 031aa7a0f56..aab337683b2 100644
--- a/src/content/cre/getting-started/before-you-build-ts.mdx
+++ b/src/content/cre/getting-started/before-you-build-ts.mdx
@@ -25,6 +25,11 @@ Your TypeScript code compiles to WebAssembly and runs in a QuickJS environment,
 1. Check if it relies on Node.js built-in modules
 1. Test with `cre workflow simulate` — simulation uses the same WASM environment as production, so compatibility issues surface immediately
 
+{/* prettier-ignore */}
+<Aside type="tip" title="Cryptography libraries">
+  If you need cryptographic functions, <a href="https://paulmillr.com/noble/" target="_blank" rel="noopener noreferrer">Noble</a> is a popular JavaScript cryptography library that works well with QuickJS. Always verify any third-party library in simulation before deploying.
+</Aside>
+
 {/* prettier-ignore */}
 <Aside type="tip" title="Learn more">
   See [TypeScript Runtime Environment](/cre/concepts/typescript-wasm-runtime) for details on QuickJS compatibility and how to [verify library support](/cre/concepts/typescript-wasm-runtime#checking-library-compatibility).
diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt
index 4d8a8213be8..f7cb503ec38 100644
--- a/src/content/cre/llms-full-ts.txt
+++ b/src/content/cre/llms-full-ts.txt
@@ -6165,6 +6165,11 @@ Javy uses [QuickJS](https://bellard.org/quickjs), a lightweight JavaScript engin
 
 Not all Node.js built-in modules are available. For example, `node:crypto` is not supported. Before using third-party NPM packages, verify they don't rely on unsupported Node.js APIs.
 
+
+<Aside type="tip" title="Cryptography libraries">
+  If you need cryptographic functions, <a href="https://paulmillr.com/noble/" target="_blank" rel="noopener noreferrer">Noble</a> is a popular JavaScript cryptography library with minimal dependencies that works well with QuickJS. Always verify any third-party library in simulation before deploying.
+</Aside>
+
 <Aside type="note" title="Note on async/await with SDK capabilities">
   While JavaScript `Promise` and `async/await` are supported by QuickJS, **SDK capabilities do not use them**. The CRE
   TypeScript SDK uses a custom `.result()` pattern instead. See the [Core SDK
@@ -7671,6 +7676,11 @@ Your TypeScript code compiles to WebAssembly and runs in a QuickJS environment,
 2. Test with `cre workflow simulate` — simulation uses the same WASM environment as production, so compatibility issues surface immediately
 
 
+<Aside type="tip" title="Cryptography libraries">
+  If you need cryptographic functions, <a href="https://paulmillr.com/noble/" target="_blank" rel="noopener noreferrer">Noble</a> is a popular JavaScript cryptography library that works well with QuickJS. Always verify any third-party library in simulation before deploying.
+</Aside>
+
+
 <Aside type="tip" title="Learn more">
   See [TypeScript Runtime Environment](/cre/concepts/typescript-wasm-runtime) for details on QuickJS compatibility and how to [verify library support](/cre/concepts/typescript-wasm-runtime#checking-library-compatibility).
 </Aside>