Valves Security (@ValvesSec) header
Valves Security (@ValvesSec) profile picture

We keep your project secure, so you can build and innovate with confidence

Joined February 2026
Photo by Valves Security (@ValvesSec)Photo by Valves Security (@ValvesSec)Photo by Valves Security (@ValvesSec)Photo by Valves Security (@ValvesSec)Photo by Valves Security (@ValvesSec)Photo by Valves Security (@ValvesSec)Photo by Valves Security (@ValvesSec)Photo by Valves Security (@ValvesSec)Photo by Valves Security (@ValvesSec)
We covered the Lunya DEX - concentrated-liquidity core ported from Uniswap V3 Core, farming and liquidity vaults. We also covered its launchpad, where tokens launch on a bonding curve and graduate into a DEX pool with permanently locked liquidity.
1
2
7
307
🚨 Every audit we do now comes with a private security contest! Yet the most exciting part for the builders is still unannounced! Save this post! Big announcement coming in 2 days! Don't miss it! 👀
1
3
47
1,156
🔜 We're cooking something... You will find out about it soon enough! Developers, we need more code. Security researchers, you will soon get another chance to prove yourselves. The game has changed. So did we! 👀
7
237
Much more to come.
2
18
440
Valves Security 🤝 @oxleydotfun Oxley launches tokens through auctions, followed by post-auction trading. All powered on @Enter_Elysium. Auditors with impressive portfolios are on the job. The highest possible level of security is our priority!
1
5
9
749
Valves Security retweeted
underrated team for real 📌
Thanks to @seedless_wallet, we have now developed a TypeScript security tool that we will be using in the future! We used our tool, improved it, and this is what the team had to say! Happy to have contributed! 🫡
3
1
15
593
Thanks to @seedless_wallet, we have now developed a TypeScript security tool that we will be using in the future! We used our tool, improved it, and this is what the team had to say! Happy to have contributed! 🫡
1
2
1
10
1,146
Truly happy to see such kind words coming our way 🫡
2
16
949
We have contributed to Web3 in many ways❗️ Our official engagements are just one part of what we have been doing over the past six months. - We have reached out to many protocols, identifying vulnerabilities with our AI-powered security tool, without receiving anything in return. - We have built a training hub for aspiring security researchers who want to learn and improve their skills. - We have invested real money in the protocols we have secured, including DeFi and liquidity pool projects. We are here to make Web3 safer, and our contributions go far beyond paid engagements. 🫡
2
18
683
Get the answers to these questions valvessecurity.com/auditors-… - Why do we only put proven auditors on your code? - What does “proven” actually mean? - What questions should you ask before starting an audit with a security firm?
14
585
Valves Security retweeted
Was not too hard. Happy to share this! The @ValvesSec AI security tooling just got a major update 🫣
We’re expanding our Cyber Verification Program to give security professionals broader access to our most capable models. Through this program, verified security professionals can access Claude Mythos 5.1, Opus 5.5, and Sonnet 5.5 with safeguards designed for defensive work. We’re also opening up new tiers to allow for authorized offensive work, like penetration testing and red-teaming. anthropic.com/news/cyber-ver…
1
3
1
17
1,263
We keep your project secure, so you can build and innovate with confidence 🛡️
1
5
198
Valves Security retweeted
🥪 The fee payer controlled how cheaply the protocol could sell its own cut. A liquidity manager compounded the trading fees earned by a user's position. It took a percentage of those fee tokens, sold that cut for USDC to pay the protocol, and reinvested the remaining tokens for the owner. The owner supplied the slippage tolerance for that fee sale too. Illustrative numbers for one non-USDC fee token, with no bot fee: 100 earned TOKEN leave 90 for reinvestment after a 10 TOKEN protocol cut. If those 10 TOKEN sell for 80 USDC instead of 100, the owner still gives up 10 TOKEN. The protocol receives 20 USDC less. ⚔️ Attack path: 1. The owner targets a compound where the remaining tokens match the position's required ratio at execution, so reinvestment needs no rebalance swap. They choose a permissive slippage tolerance. 2. Front-run: the owner sells TOKEN into the market used by the fee sale, pushing its price down. 3. Compound: their transaction sells the protocol's fixed token cut at the worsened price. The loose tolerance allows the reduced USDC output, and the remaining tokens proceed to reinvestment without a rebalance swap. 4. Back-run: the owner buys TOKEN back after the compound, seeking to unwind the first trade at a lower price. 💥 Impact: The protocol receives less USDC from the same fee-token charge. The owner can potentially recover part of that fee through the surrounding trades. Skipping the rebalance matters: a rebalance swap could also expose the owner's remaining tokens to the manipulated price. Liquidity addition and any dust conversions still occur and affect the economics. 🔎 Root cause: The fee payer chose the allowed execution loss on the sale funding the protocol's payout. Worse execution reduced that payout without increasing the predetermined fee-token charge. 🛠️ Fix: Enforce a protocol-set slippage cap on fee conversions while honoring a stricter user tolerance.
4
13
567
Valves Security retweeted
For every protocol, we build a custom security team that brings together different strengths: auditors who find uncommon bugs and those who consistently deliver high coverage. We know that every protocol is different, and we put together the right team for your needs 🤝
3
13
333
For every protocol, we build a custom security team that brings together different strengths: auditors who find uncommon bugs and those who consistently deliver high coverage. We know that every protocol is different, and we put together the right team for your needs 🤝
3
13
333
🥪 The fee payer controlled how cheaply the protocol could sell its own cut. A liquidity manager compounded the trading fees earned by a user's position. It took a percentage of those fee tokens, sold that cut for USDC to pay the protocol, and reinvested the remaining tokens for the owner. The owner supplied the slippage tolerance for that fee sale too. Illustrative numbers for one non-USDC fee token, with no bot fee: 100 earned TOKEN leave 90 for reinvestment after a 10 TOKEN protocol cut. If those 10 TOKEN sell for 80 USDC instead of 100, the owner still gives up 10 TOKEN. The protocol receives 20 USDC less. ⚔️ Attack path: 1. The owner targets a compound where the remaining tokens match the position's required ratio at execution, so reinvestment needs no rebalance swap. They choose a permissive slippage tolerance. 2. Front-run: the owner sells TOKEN into the market used by the fee sale, pushing its price down. 3. Compound: their transaction sells the protocol's fixed token cut at the worsened price. The loose tolerance allows the reduced USDC output, and the remaining tokens proceed to reinvestment without a rebalance swap. 4. Back-run: the owner buys TOKEN back after the compound, seeking to unwind the first trade at a lower price. 💥 Impact: The protocol receives less USDC from the same fee-token charge. The owner can potentially recover part of that fee through the surrounding trades. Skipping the rebalance matters: a rebalance swap could also expose the owner's remaining tokens to the manipulated price. Liquidity addition and any dust conversions still occur and affect the economics. 🔎 Root cause: The fee payer chose the allowed execution loss on the sale funding the protocol's payout. Worse execution reduced that payout without increasing the predetermined fee-token charge. 🛠️ Fix: Enforce a protocol-set slippage cap on fee conversions while honoring a stricter user tolerance.
4
13
567
We literally invest in the projects that we have secured and believe in. We are part of DeFi, we use DeFi, and we are proud to work alongside the brilliant minds building this space. We don’t just secure Web3 from the sidelines. We are part of the ecosystem ourselves 🫡
1
7
328
To get a quote and kick off your project’s audit as quickly as possible, you need to have a clearly defined scope and a Github repository ready to share. We can move fast! You can use that in your advantage 👊
2
8
503