
Great partnership, @ValkyriSecurity is a great team!
✓Security built from the ground up - infrastructure, on-chain, and every layer in between. DM us to get started!

Great partnership, @ValkyriSecurity is a great team!

As we get closer to launch, we're partnering with @ValkyriSecurity to make ongoing security reviews a standard practice in how we maintain and secure our infrastructure. Glad to have their team on board.

Valkyri Security 🤝 @utexocom We're excited to announce our long-term security partnership with Utexo, the team bringing USDT back home to Bitcoin. This goes beyond a one-time audit. We're working together on an ongoing basis to strengthen security across Utexo's fullstack infrastructure spanning across smart contracts, TEE, Web2 etc. Security is a continuous commitment, and we're looking forward to building a more secure Bitcoin ecosystem together 🫡

🎉 GIVEAWAY ALERT: We have one extra @EFDevcon ticket to sponsor! Need a ticket? Tell us why in the comments within 24 hours. We’d love to see you at Devcon! 🚀

🚨 MAJOR SECURITY ALERT: bitcoinjs patches multiple high security issues in their packages We hit some of the most critical infrastructure in Bitcoin is dependent on bitcoinjs packages—bitcoinjs-lib, bip39, tiny-secp256k1 were affected are ato multiple high security issues affecting major wallets, protocols, bitcoin infra and sdks : > bitcoinjs-lib: CVE-2026-107846, GHSA-8247-5gp7-95qh, GHSA-4mfv-5394-26c7, GHSA-88jr-9qj4-ccm4, GHSA-h52v-8xwg-7j95 (patch versions: 7.0.5, 6.1.10, 5.2.3) > bip39: CVE-2026-107847, GHSA-39w3-8jr6-f676 (latest patch version: 3.1.12) > tiny-secp256k1: CVE-2026-107853, GHSA-85g9-f6v5-wqq7, GHSA-rm9w-7fv8-3rhx (latest patch version: 2.2.5) All of the above packages have ~500k downloads/week. Also, multiple other CVEs/disclosures took place over more libs of bitcoinjs by other researchers like the ARSB and Bitcoin Red Team: > bitcoinjs-lib: GHSA-4vm8-79jj-j6w4 (patch versions: v7.0.5, 6.1.10, 5.2.3) > bip38: GHSA-mj7w-64jg-8f98 > bip32-utils: GHSA-wvw7-chj5-hr2g(patch version: 0.11.2) > merkle-lib: GHSA-g353-54jg-j6gg (patch version: 2.0.11) > bolt11: CVE-2026-107855 (patch version: 1.4.2) There are a total of 15 findings (14 highs, 1 medium) and cover areas including transaction and block parsing, PSBT fee calculations, proof verification, mnemonic handling and elliptic-curve operations. Their impact depends on the affected version and how an application uses the library. Each advisory explains those conditions and the required remediation. It was greating coordinating with @junderwood4649, @landabaso.

🚨ANNOUNCEMENT: We've merged teams with @CustodiaLab. We have joined forces. The real work started long before the announcement. Expect deeper research, more 0-day hunting, and exploit research across Web2 and Web3 With @kvazar_ai working around the clock, we're building toward one goal: "PATCH THE WORLD" The hunt never stops. Always on duty to catch the critical.🫡

🚨 MAJOR SECURITY ALERT On October 20, details of two critical remote code execution (RCE) vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619, leaked online before their coordinated disclosure and before patches were released. Expect the fix to be released today. It is scheduled for Wednesday, 21 October 2026 at 14:00 UTC. Kindly update it ASAP. php.net/archive/2026.php#202…

Full details: blog.valkyrisec.com/liquid-n…

🚨 Liquid Network ~4,000 BTC Incident: Technical Post-Mortem @real_a_kalout breaks down the cache bug behind the incident, the exploitation path, and the security assumptions that failed. Full technical analysis 👇


🚨JUST IN : Thanks for 4k followers, fam🎉 It's time, we should celeberate. And the only way we know is by "hacking" your code, legally and responsibly. We’re opening up "3 FREE SECURITY SCANS" with @kvazar_ai for builders shipping serious protocols. We’re opening the submissions for codebase across: - Smart Contracts - Solana Programs - Bitcoin Infrastructure - TEE - DLT - Web2 We’re not looking for random repos. Bring us something serious - strong idea, real product, and mostly importantly a codebase you’re actively shipping. We’ll select 3 projects that we find the most interesting and put them through Kvazar. Over the past few months, Kvazar has been finding bugs across some pretty solid stacks. Now we want to turn that firepower toward projects in this community. You get the full security report, passed through our triage. No pitch, no paywall. Just free security research for builders who are actually shipping for celebration. DM me personally or @kvazar_ai or reach us at: 📩security@kvazar.xyz

🚨 JUST IN: Kvazar discovered security issues in one of Bitcoin’s most important wallet firmware. Kvazar contributed security research to Blockstream Jade, with reported issues fixed in Jade firmware 1.0.41. We’re continuing to work with @Blockstream across multiple projects

The reason you know about the critical issue in Core Lightning:

It's almost more than an year since we posted our research/guide on "How to Hack a Web3 Wallet (Legally): A Full-Stack Pentesting Guide" It's still relevant, worth a check. Read more: blog.valkyrisec.com/how-to-h…

Valkyri Security 🤝 @dualguardaudits You know you have earned the honour when a security company trusts another security company with its own security. Honoured to be auditing DualGuard — a security contest and bug bounty platform. Security securing security.

One of the biggest mistakes smart contract engineers make when building off-chain systems: ATOMICITY, assuming the EVM's failure model still applies. While reviewing a Polymarket-based Telegram bot, I uncovered a flaw that enabled dual redemption because of exactly this mistake 🧵: