GHSA-4rmq-mc2c-r495: Babylon Incorrect FP inactive accounting in costaking creates “phantom stake” that earns rewards after BTC unbond
Summary A state consistency bug in x/costaking can leave a BTC delegator with non-zero ActiveSatoshis (Phatom Stake) even after they have fully unbonded their BTC delegation, if their Finality Provider (FP) drops out of the active set in the exact same babylon block height.
Published Dec 9, 2025
Affected packages
github.com/babylonlabs-io/babylon/v4
- Ecosystem
- Go
- Affected
- < 4.2.0
- Fixed in
- 4.2.0
- Check
go list -m github.com/babylonlabs-io/babylon/v4
github.com/babylonlabs-io/babylon/v3
- Ecosystem
- Go
- Affected
- <= 3.0.0-snapshot.250805a
- Fixed in
- No patched version yet
- Check
go list -m github.com/babylonlabs-io/babylon/v3
github.com/babylonlabs-io/babylon/v2
- Ecosystem
- Go
- Affected
- <= 2.3.2
- Fixed in
- No patched version yet
- Check
go list -m github.com/babylonlabs-io/babylon/v2
github.com/babylonlabs-io/babylon
- Ecosystem
- Go
- Affected
- <= 1.1.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/babylonlabs-io/babylon
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A state consistency bug in x/costaking can leave a BTC delegator with non-zero ActiveSatoshis (Phatom Stake) even after they have fully unbonded their BTC delegation, if their Finality Provider (FP) drops out of the active set in the exact same babylon block height. This creates a “phantom stake”: the delegator’s BTC capital is withdrawn, the FP is inactive, but costaking continues to treat the delegation as active BTC stake allowing ongoing rewards accrual without backing BTC.
Impact
An address can keep earning costaking rewards with zero BTC staked.
Reported by @BottyBott.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-m6wq-66p2-c8pc
Babylon Nil BlockHash in BLS vote extensions triggers panics in consensus handlers
high8.7No fixDec 8, 2025GHSA-2fcv-qww3-9v6h
Babylon's malformed vote extensions are not rejected
high7.0Nov 24, 2025GHSA-xq4h-wqm2-668w
Babylon's BIP322 signature implementation is not fully compliant to the spec
medium6.9Nov 24, 2025GHSA-rj53-j6jw-7f7g
Babylon vulnerable to chain halt when a message modifies the validator set at the epoch boundary
high8.9Jul 8, 2025GHSA-56j4-446m-qrf6
Babylon vulnerable to chain half when transaction has fees different than `ubbn`
high8.7No fixJun 30, 2025GHSA-7mm3-vfg8-7rg6
Babylon Finality Provider `MsgCommitPubRandList` replay attack
high8.9May 15, 2025
