TL;DR
Pendle splits a yield-bearing asset into PT (principal token) A Pendle token that redeems for one unit of the underlying on its maturity date. Bought at a discount, it locks in a fixed yield if held to that date. (principal, redeems at par at maturity) and YT (the yield stream). The September report downgraded Pendle to caution because the contract that actually holds the kHYPE behind our PT is an upgradeable proxy that three signatures can re-code with no delay, and one key can pause. This refresh re-read every part of that path on chain after the showcase rolled from PT-kHYPE-24SEP2026 into PT-kHYPE-25MAR2027.
The roll did not change the custody path. The new market 0x697dd29e...1c60 and its PT 0x9ccac956...57a8 are immutable and ownerless, and both point at the same SY, 0x57fc55df...eb9e. That SY still runs implementation 0x4f30a9d4...0210, unchanged since 19 September, under the same ProxyAdmin. The ProxyAdmin is still owned by the same 3-of-5 HyperEVM Safe with no modules, no guard and no Timelock A built-in delay between an admin approving a change and the change taking effect, so users can withdraw first if they disagree..
Two things did change. The SY now holds 68,007.23 kHYPE, down from 393,262.46, because the September market matured and holders redeemed. That is about $5.5M of principal instead of $37.5M. And on 23 October the Safe granted GUARDIAN to two more codeless addresses on both Ethereum and HyperEVM, so three separate single keys can now pause instead of one. Neither address has ever sent a transaction. Pendle TVL Total value locked: the dollar value of everything deposited in a protocol or pool. It shows size, not safety. fell 21% to $1.004B over the same seven weeks. No exploit, pause or governance incident was found. The verdict stays caution.
Checklist
Audits & contracts. Nothing moved here. Pendle's public Audit A security firm's review of a protocol's code. It lowers the odds of a bug but does not rule one out, so check what was in scope. tree still holds 23 PDFs in seven folders. The main codebase folder covers Spearbit-2024, ChainSecurity-2024, Dedaub, Ackee, Dingbats, WatchPug, 0xleastwood and CMichel. The other six folders are sPendle, marketV6, marketV7, LpPtoracle, LinearDiscountOracle and PtLooping. The only commit touching the folder since September is a 22 September release that modified the existing PtLooping report. No folder covers SY adapters. The September report quoted ChainSecurity's 2024 core audit saying the derived SY implementations were out of scope. That quote was not re-read this run, but nothing in the tree has replaced it. The core is well audited. The contract holding the money has no separate public audit.
Admin control. The red carries over, and the evidence is fresher. On HyperEVM the SY's EIP-1967 admin slot still points at ProxyAdmin 0xa28c08f1...5e64, whose owner() is the Safe 0x7877AdFa...75Ac. That Safe is version 1.4.1 with threshold 3 and the same five signers as in September, zero modules and an empty guard; its nonce is 24 (21 in September). The SY's own owner() is still the governance proxy 0x2aD631F7...f31e. Its implementation, 0x53c26f76...3ab9, is unchanged on both chains and has no schedule, queue or delay function in its ABI. On Ethereum the governance Safe 0x8119EC16...6ee1 is also unchanged: 3 of 5, same owners, no modules, no guard, nonce 813 against 809.
The instant-upgrade path is not theoretical. On 22 September the Ethereum Safe used its ProxyAdmin, at the same address as the HyperEVM one, to call upgrade on SY Strata Senior nOPAL (0xefc86eda...) and point it at a new implementation. It upgraded a second proxy (0xf82ef408...) in the same block. On 6 October, and again on 23 October, it called upgradeTo on Pendle's swap-helper proxy 0xd4f48096... on both chains. All of these look like routine maintenance. All of them executed with three signatures and no notice period. None touched the kHYPE SY. The three HyperEVM Safe transactions since 19 September contain no call to the ProxyAdmin.
The GUARDIAN finding got wider. In September one codeless address, 0xeEa6f790...761F, held GUARDIAN, and it still does on both chains. The 23 October batch, executed on Ethereum and HyperEVM, also called grantRole(GUARDIAN, ...) for 0xefd36b57...f6db and 0xb74e6bf4...9cbf. Direct hasRole calls return true for both addresses on both chains. eth_getCode returns nothing for either, and both have a nonce of zero. Each of the three can call pause(address[]) alone. The same batch made the dev Multisig A wallet that needs several keyholders to sign, such as 5 of 9. Safer than one key, but only as safe as the people who hold the keys. 0xE6F0489E... a selector admin for seven selectors and added scoped access for other callers on other targets. On 27 October a HyperEVM-only batch made 0xeEa6f790 a selector admin for one more selector, 0xb6492d04, which we did not resolve. The charitable reading is that the team gave its incident responders more hands. Even so, three single keys, not one multisig, can now freeze the contract this position exits through.
Oracle. Unchanged. Pendle prices PT and LP (liquidity provider) Depositing two tokens into a trading pool to earn its swap fees. If their prices drift apart, you end up holding more of the one that fell. through its own TWAP Oracle The price feed a protocol trusts to value collateral. A wrong or manipulated price can cause unfair liquidations or let bad loans through., pyYtLpOracle at 0x5542be50...DAc2. Its 2,999 bytes of code were re-confirmed on HyperEVM this run. No external price feed sits in the core path. Redemption at maturity does not read the oracle.
Liquidity & exit. Rewritten for the new market. PT-kHYPE-25MAR2027 shows $2.55M of Liquidity How much you can sell or withdraw right now without moving the price or waiting. Thin liquidity means a slow or costly exit. and $4.18M of total market TVL, against $6.25M of liquidity in the September market. A fresh sell quote sized to the whole position, about $4,500, returns 55.92 SY at about 0.025% Slippage and price impact How much worse than the quoted price a large trade fills, because it eats into the order book. Our exit costs measure it in bp against the mid price. and $0.90 in swap fees. The trade is 0.2% of the pool, and the quote flags it safe. The catch: Pendle's API printed under $2 of 24-hour trading volume for this market at the 18:00 UTC snapshot. Depth exists, flow does not. Maturity is 25 March 2027, 139 days out. As in September, the exit token is the SY, not kHYPE. Both a sale and a redemption at maturity still pass through the upgradeable contract above.
Yield: real vs emission. The market prints 1.77% implied against 1.89% underlying kHYPE yield, so the fixed leg is currently a little below floating. The fixed return is the discount to par, about 0.66% now, paid for by Kinetiq staking yield, not by PENDLE Emissions and points Emissions are new tokens a protocol issues to pay rewards; they count in the reward yield. Points may turn into tokens later and are never counted in a rate.. pendleApy adds 0.19 points to LPs' 2.12% aggregate yield; a PT holder does not collect it or depend on it. In the showcase this leg hedges a HYPE short, so its job is to hold value, not to earn.
Holder concentration. Re-measured through Ethplorer on Ethereum. The deprecated vePENDLE contract still holds 63,388,491 PENDLE, 22.52% of supply. sPENDLE dropped from 35,269,860 to 30,446,148 and now holds 10.81%. 0xf977814e...acec, long published as a Binance hot wallet but not verified as such here, rose from 18.8M to 22.0M, 7.81%. The governance Safe is unchanged at 19,751,622, 7.02%. The two unidentified contracts from September hold 5.73% and 5.23%. The unlabelled EOA that held 4.01% in September is no longer in the top twelve. The top twelve hold about 68.6% in total, down from 72%. None of this touches PT principal.
Track record. Still clean at the protocol level. DeFiLlama's hacks list now has 1,340 entries, the latest dated 5 November 2026, and none names Pendle, Boros or Kinetiq. The only adjacent entry is still Penpie: 3 September 2024, $27M, reentrancy, filed under magpie-ecosystem. Penpie is a separate protocol built on Pendle. Pendle paused its own contracts in response and reported about $105M safeguarded. An X search and a web search covering 19 September to 6 November found no exploit, pause, emergency action or governance announcement. Two older items surfaced and belong on the record. In July 2024 Pendle's domain was hijacked, and the team shut the attack down within about 40 minutes. In an undated 2025 episode, a compromised user wallet minted and dumped PT and YT; Pendle said it was not a protocol breach. The SY reads paused() = false today.
Worst case
Three of five signers, compromised or coerced, call upgrade on the HyperEVM ProxyAdmin and point the kHYPE SY at hostile code. The 68,007 kHYPE in that contract, about $5.5M, becomes whatever the new code says it is. The PT and the market stay immutable, and that does not help, because what they are immutably owed is SY. With no timelock, there is no window to exit first. No insurance fund backs this. The September events on Ethereum show the Safe performs exactly this operation on other SYs as routine.
The more likely bad day is softer, and it now has three triggers instead of one. Any of three GUARDIAN keys can pause the SY. Our PT-kHYPE would become unsellable while the HYPE short on Pacifica keeps repricing, leaving the hedge open for as long as the pause lasts. A long pause around 25 March would also delay redemption.
Underneath both sits Kinetiq. The SY only holds kHYPE, so a failure in kHYPE itself passes straight through to the PT whatever Pendle does. Permissionless market creation, the path Penpie's attacker used, also still exists. It cannot reach an existing market, but a repeat would likely trigger another protocol-wide pause.
Bottom line
Caution, unchanged. Nothing Pendle did in seven weeks broke anything, and the core is still immutable and well audited. But every specific reason for the September downgrade still holds on chain. The SY under our position can be upgraded by three signatures with no delay and paused by a single key, and there are now three such keys instead of one. Pendle's own Ethereum Safe upgraded another SY with no delay on 22 September, which shows the power is used in normal operation.
For the showcase the exposure is modest: about $4,500 in PT, an exit that costs a few Basis point (bp) One hundredth of a percent: 1 bp = 0.01%, so 25 bp is 0.25%. The exit costs on the funding page are in bp. today, and 139 days to maturity. Both our position and the pool behind it are smaller than in September. The verdict rests on the attack surface, not the size. Any one of three changes would move this back to solid: a timelock in front of the ProxyAdmin, a renounced proxy admin on the SY, or GUARDIAN moved from single keys to a multisig. None of those happened this period.
Data appendix
- TVL: $1,004,353,989 (DeFiLlama parent
pendle, 2026-11-06) =pendle-v2$996,739,240 plusboros$7,614,748. Down 21.4% from the $1,276,986,822 recorded on 2026-09-19 (DeFiLlama's daily series now prints $1,269,733,342 for that date). At 7.5% of the $13,390,777,660 ATH of 2025-09-19. By chain: Ethereum $766.5M, Monad $150.2M, Arbitrum $43.7M, X Layer $21.7M, Hyperliquid L1 $9.97M, BSC $7.1M, Base $2.5M, Plasma $1.9M, Sonic $0.47M, Robinhood Chain $0.18M. Since 2026-09-19: Hyperliquid L1 down 76% from about $42.3M, Arbitrum down 72% from about $155M, Plasma down 97% from $65.2M, X Layer down 69%, Monad down 27%, Ethereum up 7%. Source: api.llama.fi/tvl/pendle, /tvl/pendle-v2, /tvl/boros, /protocol/pendle. - Audits: 23 PDFs in seven folders, same as 2026-09-19. Main codebase: Spearbit-2024, ChainSecurity-2024, Dedaub, Ackee, Dingbats, WatchPug, 0xleastwood, CMichel. Other folders: WatchPug (sPendle, LpPtoracle, LinearDiscountOracle, PtLooping), WatchPug and HickupHH3 (marketV6, marketV7). Latest commit touching
audits/is 2026-09-22 (v6.11.0), which modifiedPtLooping/WatchPug.pdfonly. No SY-adapter folder. ChainSecurity scope language carried from the 2026-09-19 read, not re-read. Source: GitHub API, pendle-finance/pendle-core-v2-public. - Bug bounty: not verified in this review.
- Custody path (HyperEVM, on chain 2026-11-06): market
0x697dd29eed8e926205a08400a60d1578154c1a60,readTokens()= SY0x57fc55dff8ceca86ee94a6bf255af2f0ed90eb9e, PT0x9ccac9566fba516a5df00a23e81801b1f1cb57a8, YT0xd78bdbaa4cbd60bc9311faea101fd96caa889448;expiry()= 1805932800 (2027-03-25 00:00 UTC). PT and market both return zero at the EIP-1967 implementation and admin slots and revert onowner(). PTSY()= the same SY as the matured September market. SY implementation slot0x4f30a9d41b80ecc5b94306ab4364951ae3170210(unchanged; 13,952 bytes on HyperEVM, a different contract from vePENDLE at the same address on Ethereum), admin slot0xa28c08f165116587d4f3e708743b4dee155c5e64(unchanged),owner()= governance proxy0x2ad631f7...f31e,paused()= false,exchangeRate()= 1.02769. ProxyAdminowner()= HyperEVM Safe0x7877AdFaDEd756f3248a0EBfe8Ac2E2eF87b75Ac. - Custody balances (on chain 2026-11-06):
kHYPE.balanceOf(SY)= 68,007.2301 andSY.totalSupply()= 68,007.2301, identical, against 393,262.4575 on 2026-09-19. About $5.48M at CoinGecko's $80.57 kHYPE. Of the SY: new YT holds 26,091.01, new market 25,998.87, matured September YT 596.63, matured September market 1.01. PT-25MAR2027 total supply 26,792.48. - Admin (Ethereum, on chain 2026-11-06): Safe
0x8119EC16F0573B7dAc7C0CB94EB504FB32456ee1,VERSION()1.4.1, threshold 3, owners0x231fc5b0...,0x7bd45693...,0x9ce6de7e...,0x38ab4a7d...,0xf5173647..., no modules, guard slot zero, nonce 813. Governance proxy implementation0x53c26f7645500fea9a856bfa09e820dacf643ab9,hasRole(DEFAULT_ADMIN_ROLE, Safe)= true. Ethereum ProxyAdmin0xa28c08f1...owner()= this Safe. - Admin (HyperEVM, on chain 2026-11-06): Safe
0x7877AdFa...75Ac, 1.4.1, threshold 3, the same five owners, no modules, empty guard, nonce 24. Same governance proxy implementation,hasRole(DEFAULT_ADMIN_ROLE, Safe)= true. - Guardian (both chains, on chain 2026-11-06):
hasRole(GUARDIAN, ...)true for0xeEa6f790F18563e91b18Df00b89d9F79B2E6761F(no code; nonce 2,473 on Ethereum, 231 on HyperEVM),0xefd36b57d7fc077088d04c3c712fb8958fe7f6db(no code, nonce 0) and0xb74e6bf4baf65e0a1fff6102acc78f416ce99cbf(no code, nonce 0). False for both Safes and the dev multisig0xE6F0489E.... The two new holders were granted bygrantRoleinside the 2026-10-23 batch on each chain. - Safe activity since 2026-09-19, decoded from Etherscan: Ethereum, 2026-09-22: ProxyAdmin
upgrade(0xf82ef408..., 0x578f916a...); batch with ProxyAdminupgradeof SY Strata Senior nOPAL0xefc86eda...to0x547c907c...plus a governance-proxyaggregatecall to it. Both chains, 2026-10-06:upgradeToon swap helper0xd4f48096...(ABI:swap,SwapSingle). Both chains, 2026-10-23:upgradeToon the same helper,setSelectorToFacetson Router0x888888888889758F76e7103c6CbF23ABbF58F946, two GUARDIAN grants,modifySelectorAdminfor the dev multisig over seven selectors, severalmodifyScopedAccessgrants (one extra on HyperEVM only). HyperEVM, 2026-10-27:modifySelectorAdmin(0xeEa6f790, [0xb6492d04], [true])and twomodifyScopedAccessgrants on that selector to target0xe5125dfe..., which had no code at read time. HyperEVM Safe transactions since 2026-09-19: exactly these three (2026-10-06, 2026-10-23, 2026-10-27), none calling the ProxyAdmin. Selector names computed locally by keccak. Selector0xb6492d04unresolved. - Oracle:
pyYtLpOracle0x5542be50420E88dd7D5B4a3D488FA6ED82F6DAc2, 2,999 bytes on HyperEVM. - Owned position: 57.8766 PT-kHYPE-25MAR2027, rolled 2026-09-24. Market snapshot 2026-11-06 18:00 UTC: liquidity $2,549,348, total TVL $4,177,691, 24h volume $1.98, implied 1.770%, underlying 1.889%, PT discount 0.662%,
pendleApy0.186%, aggregated 2.119%, max boosted 2.399%, accounting-asset price $78.33. Full-exit quote ($4,500, sell PT): 55.92 SY out, price impact 0.025%, swap fee $0.90, 0.2% of pool, safe to execute. Position value about $4,500. Source: api-v2.pendle.finance market data, pendle-mcp liquidity_depth. - PENDLE token: $1.68, market cap about $291M, FDV $472.2M, circulating 173,932,675 of 281,527,448 total, down 23.5% over 30 days and 35.6% over one year. Source: CoinGecko, 2026-11-06.
- Holder concentration: vePENDLE
0x4f30a9d4...63,388,491 (22.52%); sPENDLE0x99999999...414430,446,148 (10.81%);0xf977814e...acec22,000,000 (7.81%, Binance label unverified); governance Safe 19,751,622 (7.02%);0x399be606...16,120,440 (5.73%);0xa3a7b6f8...14,721,370 (5.23%); then 2.75%, 1.63%, 1.52%, 1.24%, 1.22%, 1.15%. Top twelve 68.63%. vePENDLE and governance Safe balances and total supply cross-checked with directbalanceOfandtotalSupplycalls. Source: Ethplorer top holders, Ethereum RPC. - Recent news scan (2026-09-19 to 2026-11-06): A Grok X search found no Pendle, Boros or Kinetiq security incident, pause, emergency action, multisig or timelock change, or sPENDLE/vePENDLE tokenomics change. A web search for October 2026 found no exploit or pause. It did surface two older items: the July 2024 domain hijack (Coinspeaker, citing Pendle's post of 12 July 2024) and a 2025 compromised-wallet PT/YT dump that Pendle said was not a protocol breach (CoinSpot, Bloomingbit; exact date not verified in this review).
- Incident record: DeFiLlama hacks list, 1,340 entries, latest 2026-11-05, no entry for Pendle, Boros or Kinetiq. Adjacent: Penpie, 2024-09-03, $27,000,000, Reentrancy, parent
magpie-ecosystem.
Maintained monthly. Methodology: DeFi Research Instruction v2.