Scan to Download
Search "Config" has a total of9related results
Techub News, according to TechCrunch, robotics data layer startup Config has completed a $27 million seed funding round, led by Samsung Venture Investment, with a valuation exceeding $200 million. Hyundai Motor, LG, SKT, among others, also participated, bringing total funding to $34 million. The company was founded in January 2025 by former Meta researcher Minjoon Seo, positioning itself as the "TSMC of robotics data," dedicated to providing training data for robotics foundation models rather than directly manufacturing robots. Its clients currently include large manufacturers and system integrators.
Techub News reports that LayerZero has issued a statement indicating that on April 18, KelpDAO suffered an attack involving approximately $290 million. Preliminary signs suggest this attack may have been carried out by a highly sophisticated state actor (suspected to be TraderTraitor, a subgroup of North Korea's Lazarus Group). As KelpDAO employs a single DVN setup, this incident is limited to its rsETH configuration and will not affect any other cross-chain assets or applications. The attack targeted the downstream RPC infrastructure used by the LayerZero Labs DVN. All affected RPC nodes have been deprecated and replaced, and the LayerZero Labs DVN is now operational again. Currently, the team is contacting all applications using a 1/1 DVN configuration to migrate to a multi-DVN setup with redundancy. The LayerZero Labs DVN will not sign or authenticate messages from any application using a 1/1 configuration. LayerZero Labs maintains direct contact with multiple global law enforcement agencies and is cooperating with their investigations. Additionally, it is actively supporting industry partners and Seal911 in tracking the flow of funds.
Techub News reports, SlowMist founder Yu Xian analyzed the Kelp DAO hack and stated: The LayerZero cross-chain used by the attacker was configured as 1/1 DVN, which is the classic "single signature" configuration, while the LayerZero official documentation recommends 2/2 by default. This "single signature single point" might also have been compromised by social engineering methods (just speculation, specifics await investigation). The attacker successfully stole 116,500 rsETH on Ethereum and actually attempted two more times to steal an additional 40,000 rsETH but failed. The attacker's transaction fees came from Tornado Cash. The 116,500 rsETH was dispersed and laundered, putting pressure on various staking platforms, especially Aave, which now faces massive bad debt.
Techub News reported that Aave founder Stani Kulechov posted on the X platform, stating that a misconfiguration in Aave's CAPO oracle led to wstETH E-Mode liquidations, resulting in a loss of 345 ETH. No bad debt was incurred, and all affected users will receive full compensation. Aave DAO SPs are finalizing the reimbursement plan, and 141 ETH has already been recovered through BuilderNet refunds. The CAPO system, launched as a hybrid oracle over a year ago, has transmitted over 1,200 payloads involving more than 3,000 parameters without incident, contributing to Aave's robust growth; the system is designed to prevent oracle exploits, including artificially inflated exchange rates and donation attacks, by enforcing maximum caps through off-chain computation and on-chain verification.
Techub News reports, according to BlockSec monitoring, the Ethereum protocol Ploutus liquidity pool suffered a loss of approximately $390,000 due to pricing deviation caused by its oracle being misconfigured to use the BTC/USD Chainlink price feed for USDC pricing. The attacker exploited this error, borrowing 187 Ethereum using only 8 USDC as collateral. This exploit occurred in block 24538897, immediately following the misconfiguration transaction in block 24538896, indicating the attacker was closely monitoring the configuration changes.
Techub News reports, according to Decrypt, the DeFi lending protocol Moonwell incurred approximately $1.78 million in bad debt due to an oracle configuration error. After Moonwell enabled Chainlink's OEV wrapper contract via governance proposal MIP-X43 on February 15, a severe misconfiguration occurred in the price oracle for cbETH, temporarily valuing it at only $1. On-chain trading bots and liquidators quickly acted, seizing thousands of dollars worth of cbETH collateral by repaying debts of around $1. This configuration error led to the liquidation of 1,096.317 cbETH in total, wiping out most or all of many borrowers' collateral and leaving the protocol with significant bad debt. The Moonwell team immediately reduced the cbETH borrowing and supply caps to 0.01 upon discovery to limit further losses, but a spokesperson declined to comment further on the source of the error or details of the vulnerability.
Techub News reports that 23pds, the Chief Information Security Officer of SlowMist Technology, tweeted that the AI agent-specific forum Moltbook experienced a database leak due to a configuration issue, exposing 4.75 million records. These include 1.5 million API authorization tokens, 35,000 user email addresses, 20,000 email records, and some OpenAI API keys. Users are advised to promptly check the security of related accounts and replace relevant keys and passwords in a timely manner.
Techub News reports that the Ethereum Foundation tweeted that the Prysm consensus client on the Ethereum mainnet is currently experiencing a failure, and node operators using Prysm need to reconfigure their Consensus Layer (CL) nodes. The Ethereum Foundation also emphasized that if other consensus clients are being used, they are unaffected and no action is required.
Techub News: The Aster team issued a statement regarding the significant abnormal volatility of the XPL contract this morning, stating that the incident originated from a parameter configuration error during the transition of XPL from the pre-listing market to the official perpetual market. This error caused the index price to be capped at $1, and even after the cap was removed, the system remained in pre-listing mode, leading to an abnormal price surge between 5:36 and 5:45. The issue was fully resolved before 5:45 and was confirmed to be an internal configuration error, not an external attack. Related compensation will be automatically distributed to affected user accounts within one hour. If there are any questions, a support ticket can be submitted via Discord after the distribution is completed.
Current search results fully loaded
