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
28480Commits 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 17 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

show the remote bitcoin core node warning from the terminal server settings

This commit moves an existing user warning about connecting to a remote Bitcoin Core node into a shared helper, and now also displays that same warning in the terminal (command-line) version of Sparrow. It does not change how connections a…

Refactor of existing security warning onlyNo change to network or cryptographic behaviorNo privilege boundary crossed
6ea7bca6by Craig Raw+56−433 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

wrap terminal alert lines after a line break in the text at the full width

This commit fixes a text-wrapping bug in the terminal version of Sparrow Wallet. Previously, if an alert message contained explicit line breaks (newlines), the wrapping logic counted the entire chunk after a newline as part of the current …

5316f484by Craig Raw+38−32 files
No security note in commit
Moderate 69 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

sync to the announced tip before serving a stored header when a reorg lengthens the chain, so a proof is not checked against a replaced block

This commit fixes a bug in how Sparrow Wallet verifies Bitcoin block headers during a blockchain reorganization (reorg). Previously, if a reorg made the chain longer, the wallet could serve an old, replaced block header to check a payment …

Incorrect block header served during chain reorgProof verification could be checked against replaced blockMissing sync path when announced tip extends beyond local store
40310b05by Craig Raw+39−52 files
No security note in commit
Informational 15 AI analysisMessage 82 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: Drop hard-coded magic 3

This is a tiny code cleanup in a Bitcoin Core test file. It replaces the hard-coded number 3 with the actual number of test nodes, making the test slightly easier to maintain. It does not change any real Bitcoin Core software behavior and …

1eeeee49by MarcoFalke+3−31 file
No security note in commit
Low 42 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

delete backups made before a password was added or changed from the terminal settings

This commit changes how Sparrow Wallet's terminal (command-line) version handles wallet backups when a password is added, changed, or removed. Previously, old unencrypted or differently-encrypted backups might have been kept on disk. After…

Deletion of stale wallet backups when password changesAlignment of terminal wallet behavior with desktop wallet security behaviorPrevention of recovery of wallet data from older, differently encrypted or unencrypted backups
26e6705dby Craig Raw+3−21 file
No security note in commit
Low 36 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

find, rename and delete the backups of a wallet left in a previous wallets folder when its password is added, it is renamed or it is deleted

This commit fixes a cleanup issue in the Sparrow Bitcoin wallet. Previously, if a wallet file was moved out of the default 'wallets' folder, its automatic backups could be left behind in the old folder. When the user later added a password…

Leftover wallet backup files not deleted/renamed when wallet moved out of wallets directoryPotential data residue of wallet metadata/keys in backup folder after wallet deletion or renameUI warning text updated to mention backups when backups exist outside wallets dir
8f4b70e9by Craig Raw+77−165 files
No security note in commit
Moderate 57 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

encrypt account keystores when a password is set together with a change needing a refresh, and edit an account as a child of the master wallet copy

This commit fixes a bug in Sparrow Wallet's settings form. When a user changed wallet settings that required a full refresh (like the gap limit) at the same time as adding a wallet password, the software could fail to properly encrypt the …

Incorrect encryption state propagation for child account keystores during settings refreshMissing security event emission on refresh-necessary code pathWallet copy semantics changed to keep account copies attached to master wallet copy
4acaaca2by Craig Raw+170−222 files
No security note in commit
Low 43 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

keep the open wallet encrypted while discovering accounts to add

This change adjusts how Sparrow Wallet handles wallet encryption when adding or discovering new accounts. Previously, the main open wallet was decrypted before deciding what to do next, which could leave it decrypted during a potentially l…

Reduction of plaintext key material lifetime in memoryDefense-in-depth against memory-exposure or cold-boot style attacks during long-running background operationsNo cryptographic primitive changes; change is operational/lifecycle only
0f9d99fcby Craig Raw+8−41 file
No security note in commit
Informational 22 AI analysisMessage 96 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

i18n: fit the long Tamil strings on the new UI (#3878)

This commit fixes visual layout bugs in the Cake Wallet mobile app where long Tamil translations were being drawn off-screen or clipped. It also fixes a broken unit test by adding a missing mock object. There is no security vulnerability h…

8c3365fdby Seth For Privacy+232−1446 files
No security note in commit
Informational 20 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36864: rpc: deprecate iswatchonly field of getaddressinfo

This change hides an old, always-false field called 'iswatchonly' from the getaddressinfo API response unless the user explicitly asks for deprecated features. It is a routine cleanup, not a security fix, and does not change how wallets or…

66531447by merge-script+16−34 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/high-fee-wording-v9.27.2'

This commit only updates test data and test expectations to reflect that a wording change for high Bitcoin transaction fees was released in firmware version 9.27.2 instead of 9.28.0. It does not change any device firmware code, security lo…

00f9eb22by Marko Bencun+65−1123 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 →