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 10 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/rust): reduce coverage map size

This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…

No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
9bf2fc3aby M1nd3r+1−11 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

btc: fix high-fee wording cutoff in vectors

This commit only updates test data and test expectations for the BitBox02 firmware. It changes which firmware versions are expected to show an old versus new high-fee warning message, because the real firmware already started showing the n…

dc5702d0by benma's agent+65−1123 files
No security note in commit
Moderate 50 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

treat a proxy's reply that it could not reach the server as a server failure, so it no longer turns off the proxy

This change fixes a bug where Sparrow Wallet would disable its Tor/proxy connection whenever the proxy reported it couldn't reach the destination server. Previously, the app misread 'the destination is unreachable' as 'the proxy itself is …

Proxy bypass risk: misclassification of destination errors as proxy failures could cause the wallet to disable Tor/proxy and connect directly, degrading privacyNetwork-level privacy fix: preserves intended proxy routing when the proxy is operational but the remote server is notNo cryptographic, authentication, or input-validation changes
ebe83462by Craig Raw+5−11 file
No security note in commit
Moderate 64 AI analysisMessage 55 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

hold rates, version and currency requests and refuse auth47 and lnurl-auth logins while internal tor is starting

This commit fixes a privacy and security issue in Sparrow Wallet where certain network requests and authentication actions could run before the built-in Tor proxy was ready. Without the fix, those requests could bypass Tor and expose the u…

Requests that should transit Tor could be sent over a direct connection during Tor startupAuth47 and LNURL-auth authentication could be performed without Tor, deanonymizing the userExchange-rate, version, and currency requests could leak real IP address and wallet usage timing
71cd1c74by Craig Raw+25−32 files
No security note in commit
Low 48 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

create the server transport only when connecting, so a call made after disconnecting cannot leave one for the next connection

This commit fixes a logic bug in how Sparrow Wallet connects to Bitcoin Electrum servers. Previously, background tasks that ran after a disconnect could accidentally create a new server connection on their own, using stale or mismatched se…

Lifecycle bypass: background code paths could instantiate a network transport outside the intended connection sequenceState mismatch risk: a transport created post-disconnect would use settings captured at creation time, not at the moment the user initiated the connectionDefense in depth: change converts a silent auto-create into an explicit exception, preventing unintended reuse
7b6e8443by Craig Raw+13−41 file
No security note in commit
Low 44 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

reach an onion host written with a trailing dot over tor, and remove the dot from saved server urls

This commit fixes a handling quirk for Tor 'onion' web addresses when they are written with a trailing dot (for example, 'example.onion.'). Previously, Sparrow did not recognize these dotted onion addresses as Tor destinations, so it might…

Tor/onion address canonicalization bypasstrailing-dot FQDN not recognized as onion hostproxy requirement check bypassed for dotted onion hosts
70f2f51fby Craig Raw+34−44 files
No security note in commit
Low 35 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

use the default port for a proxy given without one in http requests, bwt, tor identity changes and tor status checks

This commit fixes a bug where Sparrow Wallet would use an invalid port number when a user configured a Tor/proxy server address without explicitly specifying a port. Previously, the code called getPort(), which could return -1 or an undefi…

Use of default port fallback for network proxy configurationPotential prior behavior of connecting to invalid/undefined port when proxy string lacked portTor control port derived from proxy port (proxy port + 1), making correct proxy port handling security-relevant for identity rotation
921c43beby Craig Raw+9−75 files
No security note in commit
Informational 18 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

accept a proxy port given with the host, and keep the saved proxy when the host is invalid, in the desktop and terminal settings

This commit fixes a small user-experience bug in Sparrow Wallet's proxy settings. Previously, if a user typed a proxy address that included a port (like '127.0.0.1:9050') into the host field, the app rejected it as invalid and could also w…

Input validation logic changed for proxy host/port fieldsBehavioral fix prevents accidental clearing of saved proxy configuration on invalid host inputNo cryptographic, authentication, or network-layer changes observed
63e19930by Craig Raw+43−12 files
No security note in commit
Low 28 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

stop a connection waiting to retry while the server settings are open, and reconnect on closing

This commit fixes a small timing bug in Sparrow Wallet's server settings screen. Previously, if the wallet was trying to reconnect to a server in the background while the user opened the server settings, the reconnect could read the half-e…

TOCTOU-like race between background connection retry and user editing server settingsPotential use of partially modified server configuration by a connection attemptFix is preventive rather than reactive to a reported exploit
6404bb46by Craig Raw+4−01 file
No security note in commit
Moderate 61 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

check whether a server host is an ip literal as inetaddress reads one

This commit tightens how Sparrow Wallet decides whether a server address is a raw IP address (like 192.168.1.1) versus a hostname (like example.com). It replaces a more forgiving Google utility with Java's stricter InetAddress.ofLiteral ch…

Replaces permissive IP parsing with strict InetAddress.ofLiteral validationAvoids local DNS resolution of ambiguous host strings when a proxy is configuredPrevents zone-ID IPv6 literals and full-width Unicode digit strings from being accepted as IP literals
02f8a0c5by Craig Raw+155−53 files
No security note in commit
Low 42 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

compare a re-announced chain tip by block when deciding whether to retry or refuse it

This commit fixes a logic bug in how Sparrow Wallet decides whether to retry or reject a newly announced blockchain tip from an Electrum server. Previously, the code compared tip objects using Java's == operator, which checks whether two v…

Logic bug: reference equality used where value equality (same block) was intendedPotential denial of wallet sync: repeated same-block announcements could bypass retry/refuse logicNo input validation changes; fix is localized to identity-vs-value comparison
40724fa8by Craig Raw+39−33 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 →