Continuous public-repository analysis

Open source.
Not open secrets.

We watch what security-critical projects change—then translate the code into clear, independent intelligence anyone can understand.

36Projects watched
28479Commits captured
22867AI analyses
57High-risk findings · 30d
Active security advisories
Critical

LNbits 1.7.0: urgent theft-risk security update

LNbits says every version before 1.7.0 is affected by the vulnerability discovered November 8 and that funds on prior versions are at risk of being stolen. Version 1.7.0 contains incident-response security fixes, but the vendor has not yet published full exploit details.

Affected: All LNbits versions before 1.7.0. The warning is no longer limited to servers using the Paywall extension. Credentials or secrets exposed before an upgrade may continue to give an attacker access afterward.

Action: Keep older instances stopped and upgrade to 1.7.0 before running LNbits. If compromise is suspected, preserve logs and prefer a fresh server. Reset all wallet keys, rotate funding-source credentials and every other stored secret, and recreate extension and application connections with new credentials. Review balances and outgoing payments.

Read source ↗
Critical

Electrum 4.8.3: malicious-server RBF theft in the wild

Electrum confirms malicious servers are exploiting a transaction-replacement attack in the wild. A server can suppress a user's newly broadcast transaction, substitute an invalid conflicting transaction paying a lookalike attacker address, and cause Electrum to display it. If the user manually fee-bumps that transaction, the wallet can sign the attacker's replacement. Electrum reports two victims and one confirmed loss of funds.

Affected: Electrum versions before 4.8.3 when connected to an untrusted or malicious Electrum server. Users who connect only to a server they trust, such as their own server, are not affected according to the vendor.

Action: Upgrade to Electrum 4.8.3 immediately, download only from electrum.org, and verify the release signatures. Until upgraded, do not fee-bump an unexpected or substituted transaction and verify every output address and amount before signing any transaction.

Read source ↗
Critical

Core Lightning v26.06.9: urgent loss-of-funds security update

Core Lightning says v26.06.9 fixes a newly reported vulnerability that can lead to loss of funds. The release also contains security fixes in channel reestablishment, splicing, HTLC shutdown handling, onion and on-chain handling, gossip range queries, runes, configuration, and several remote-crash and hardening fixes.

Affected: Every Core Lightning node running v26.06.8 or earlier is affected, according to the vendor. Technical tests for the security fixes are temporarily withheld to slow exploit development while operators upgrade.

Action: Upgrade to Core Lightning v26.06.9 immediately. Download the release from https://github.com/ElementsProject/lightning/releases/tag/v26.06.9, verify the appropriate signed SHA256 manifest and checksums for your architecture, install it, restart lightningd, and confirm the running version.

Read source ↗
The watch feed

Changes worth understanding

AI analysis is published as generated. Community notes appear after human validation.

22867 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 35 · Opaque
FW Feather WalletFeather Wallet MoneroPrivacy protocolsSoftware wallets

depends: native_qt: fix link

This commit fixes a broken download URL used when building Feather Wallet. The wallet's build system was pointing to the wrong Qt version folder (6.11 instead of 6.12), which would cause the source code download to fail. There is no securi…

b9aa7171by tobtoht+1−11 file
No security note in commit
Informational 15 AI analysisMessage 88 · Strong
MJ monero-javamonero-java Cryptographic librariesMoneroSoftware wallets

ci: pin openssl 3 and unbound on windows (#185)

This is a routine continuous-integration (CI) build fix for the Windows build pipeline. The project pinned older versions of OpenSSL and Unbound because the MSYS2 package repository upgraded to newer versions that the underlying Monero C++…

320fe570by woodser+11−21 file
No security note in commit
Informational 15 AI analysisMessage 35 · Opaque
FW Feather WalletFeather Wallet MoneroPrivacy protocolsSoftware wallets

guix: include tickers plugin

This commit changes one build script line so that the official Guix-produced Feather Wallet binaries are compiled with a 'tickers' price-tracking plugin enabled, instead of having the Reddit plugin explicitly disabled. On its own, the diff…

Build configuration change for official release pipelineEnables an external-data plugin (tickers) in distributed binariesRemoves explicit disabling of another external-data plugin (Reddit)
b13b0516by tobtoht+1−11 file
No security note in commit
Informational 3 AI analysisMessage 28 · Opaque
FW Feather WalletFeather Wallet MoneroPrivacy protocolsSoftware wallets

update monero submodule

This commit only updates the Monero submodule pointer in the Feather Wallet repository from one commit hash to another. No code changes are visible in the diff itself, and no security-related description is provided. Without knowing what c…

300b50a1by tobtoht+1−11 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
FW Feather WalletFeather Wallet MoneroPrivacy protocolsSoftware wallets

Home: remove tab

This commit removes the 'Home' tab from Feather Wallet and moves the Tickers plugin to live inside the 'Calc' tab instead. It is a user-interface cleanup change, not a security fix. There is no indication it addresses any vulnerability.

edde5b7fby tobtoht+30−24420 files
No security note in commit
Informational 18 AI analysisMessage 60 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

document building v2.5.3 to v2.5.6 with lenient dependency verification, as two pom files were later republished to maven central with additional metadata

This commit only updates documentation. It explains that when building older Sparrow Wallet releases (versions 2.5.3 through 2.5.6), two dependency files on Maven Central were later republished with extra descriptive metadata, causing a ha…

Dependency checksum mismatch in recorded verification metadataPOM-only republication of two Sparrow-published artifacts (hid4java, usb4java)Documentation instructs lenient verification for reproducible builds of older releases
6a83c9a5by Craig Raw+15−01 file
No security note in commit
Informational 19 AI analysisMessage 35 · Opaque
FW Feather WalletFeather Wallet MoneroPrivacy protocolsSoftware wallets

depends: qrencode: update link

This commit changes where Feather Wallet's build system downloads the qrencode library from. It switches the download source from the original author's website to GitHub, updates the expected file name and cryptographic hash, and adds step…

Source URL changed for dependency downloadSHA-256 hash updated for renamed archiveBuild tooling added (autoconf/automake/libtool) to support source archive without pre-generated configure
b899f206by tobtoht+8−32 files
No security note in commit
Informational 23 AI analysisMessage 35 · Opaque
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

fix litecoin renaming issue

This commit fixes a bug in the Cake Wallet Litecoin wallet where, when renaming a wallet, stored MWEB (a privacy feature for Litecoin) transaction records were being copied to a new storage box by reusing the exact same object references. …

Data migration now clones objects instead of sharing referencesPrevents potential state corruption when renaming Litecoin walletsNo explicit input validation or cryptographic change present
e45d45b1by Omar+12−11 file
No security note in commit
Informational 15 AI analysisMessage 93 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

ci: build iOS on the Mac Studio runners (canary), Xcode 27 (#3872)

This is a routine update to the project's automated iOS build pipeline. It changes which Apple computer (runner) and Xcode version are used to compile and upload the iPhone app, so the app meets Apple's upcoming App Store requirement to us…

1ab697f6by Seth For Privacy+22−21 file
No security note in commit
Informational 19 AI analysisMessage 35 · Opaque
FW Feather WalletFeather Wallet MoneroPrivacy protocolsSoftware wallets

src: remove .onion/eepsite

This commit removes Feather Wallet's .onion (Tor) and .i2p (eepsite) addresses from the user interface and from network code. It replaces those privacy-network-specific WebSocket endpoints and update URLs with ordinary clearnet HTTPS/WSS a…

Removal of hardcoded Tor/I2P service endpointsReplacement of proxy-specific WebSocket URLs with clearnet WSS URLsRemoval of proxy-aware update URL selection
63cc1ab2by tobtoht+18−363 files
No security note in commit
Informational 21 AI analysisMessage 81 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1980: examples: randomize the context in musig, erase the keypair in schnorr

This change improves two example programs in the secp256k1 cryptographic library. It adds a recommended side-channel protection step to the multi-signature example (musig.c) and ensures the single-signature example (schnorr.c) also wipes a…

Context randomization added to protect against side-channel leakageSecret key material explicitly erased from keypair object after useChanges are confined to example code, not the core library
5959bed6by merge-script+14−12 files
No security note in commit
01
Why commit watching?

Security should leave a paper trail.

A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.

Why we built this →