BTC $64,470.05 -1.54%
ETH $1,803.20 -1.33%
BNB $589.77 -1.30%
XRP $0.9501 -1.22%
SOL $71.28 -0.84%
TRX $0.3026 -1.75%
DOGE $0.0584 -0.97%
ADA $0.1517 -1.76%
BCH $205.95 -1.29%
LINK $9.11 -1.37%
HYPE $67.06 -1.26%
AAVE $109.28 +2.42%
SUI $0.7200 -1.31%
XLM $0.1375 -1.17%
ZEC $885.94 -2.51%
AAPL $358.81 +0.56%
AMZN $265.31 +0.60%
GOOGL $294.92 +0.83%
MSFT $528.20 +1.41%
META $638.73 +0.13%
NVDA $159.29 -1.00%
TSLA $386.61 -0.19%
SNDK $833.04 -2.38%
INTC $56.73 -2.02%
SPCX $139.96 +1.57%
MU $738.02 -2.57%
AMD $507.53 -2.70%
BTC $64,470.05 -1.54%
ETH $1,803.20 -1.33%
BNB $589.77 -1.30%
XRP $0.9501 -1.22%
SOL $71.28 -0.84%
TRX $0.3026 -1.75%
DOGE $0.0584 -0.97%
ADA $0.1517 -1.76%
BCH $205.95 -1.29%
LINK $9.11 -1.37%
HYPE $67.06 -1.26%
AAVE $109.28 +2.42%
SUI $0.7200 -1.31%
XLM $0.1375 -1.17%
ZEC $885.94 -2.51%
AAPL $358.81 +0.56%
AMZN $265.31 +0.60%
GOOGL $294.92 +0.83%
MSFT $528.20 +1.41%
META $638.73 +0.13%
NVDA $159.29 -1.00%
TSLA $386.61 -0.19%
SNDK $833.04 -2.38%
INTC $56.73 -2.02%
SPCX $139.96 +1.57%
MU $738.02 -2.57%
AMD $507.53 -2.70%

vulnerabilities

All
Article
Flash

GCSA disclosed KuCoin phishing, Bitkub supply chain risks, and Avalanche contract vulnerabilities: attackers transferred approximately 1,013,400 USDC

According to GCSA monitoring, the Global Cybersecurity Alliance (GCSA) has released three independent technical investigation reports, disclosing several recent security risks related to digital assets. Attackers impersonated security@ku.com to lure users into downloading remote control programs. GCSA found that the relevant domain names had not previously configured DMARC; after notification, KuCoin has completed rectification and enabled DMARC isolation policies.After the original MCP toolkit referenced in Bitkub's official documentation was taken down, a third party re-registered the npm package name. The installation method without a fixed version and the risk of plaintext keys may lead to credential leakage; there is currently no actual evidence of theft, and Bitkub has not yet responded to the notification.The TranchePool treasury within the Avalanche ecosystem was attacked due to a cross-day settlement logic flaw, where attackers utilized flash loans and repeated withdrawals to transfer approximately 1.0134 million USDC within 202 seconds. This incident is categorized as a vulnerability in the upper application, and the underlying network was not affected. GCSA stated that it has reported the clues to the relevant platforms and published the original analysis and evidence for industry reference.

OpenAI reveals autonomous vulnerability pipeline: a run that produced 948 local privilege escalation vulnerabilities in Linux

According to disclosures from OpenAI's official website, the company has established an autonomous security research pipeline covering vulnerability discovery, dynamic verification, exploitability assessment, and patch generation. In a run centered on an upcoming network model, the pipeline completed scanning and verification of targets related to the Linux kernel, generating 948 exploits that can achieve local privilege escalation (LPE) on commonly used Linux distributions, with an API cost of approximately $1.213 million, or about $1,279 per LPE exploit.It was reported that the pipeline identified and analyzed a total of 2,308 candidate discoveries, dynamically reproducing 1,724 vulnerabilities, and producing 291 information leakage proofs of concept (PoC); the target virtual machine ran a standard desktop system with complete protection. The Scout agent initially identified about 5,034 audit targets (approximately 2.8 million lines of code, accounting for about 7% of the kernel), and the Analyst agent produced candidate discoveries in about 12 hours. OpenAI stated that it has prioritized reporting critical vulnerability patches as recommended by the Linux community and continues to advance the remaining reports in collaboration with Patch the Planet partners.OpenAI also mentioned that in the adapted kernelCTF environment, an additional 25 information leakage PoCs and 21 LPEs were obtained; among 166 sampled exploits, the agent reportedly used at least 10 newer Linux exploitation techniques that it deemed more recent. The company emphasized that maintainers are quick to fix: over 100 LPEs have been patched or entered temporary patches within about 10 days of scanning, and approximately 300 others have entered public discussion.

Aztec launched the Tierra V6 network upgrade, fixing security vulnerabilities and doubling the speed of privacy transaction proofs

According to The Block, the Aztec Foundation behind the Ethereum privacy Layer 2 network Aztec has launched the Tierra (Alpha V6) upgrade, which fixes security vulnerabilities from previous versions, including a critical vulnerability in V5, and introduces an AI-based security testing system.In terms of performance, the new version doubles the speed of generating privacy transaction proofs, taking only about 1 second on local devices; the time for Ethereum messages to reach Aztec has also been reduced from an average of about 2 minutes to as fast as 12 seconds, further enhancing cross-chain deposit and transaction efficiency. Aztec stated that due to the network's decentralized architecture, fixing critical vulnerabilities requires an upgrade of the entire network, and plans are currently underway to accelerate the deployment of future security updates.In terms of ecosystem, Aztec has recently relaunched the self-custody privacy wallet zk.money, and several applications are being launched or prepared for launch, including Galactica, which supports privacy AI inference, the privacy perpetual contract trading platform Nemi, the privacy browser wallet Nulo, and Xochi and Nyx, which support privacy payments and transactions. Meanwhile, Aztec has also released a new brand image and website, aiming to become the infrastructure platform for privacy applications.

OnKey founder: The iPhone 11 and earlier models have hardware vulnerabilities that cannot be fixed through system updates, and it is not recommended to use them for storing mnemonic phrases

OnKey founder Yishi posted on platform X to remind users that using older iPhone models as cold wallets for cryptocurrency assets may pose security risks. The checkm8 vulnerability exists in the BootROM of iPhone 4S to iPhone X, and the usbliter8 vulnerability, which was disclosed in June this year, affects iPhone XS, XR, 11 series, and second-generation SE, all involving the device's low-level boot code, which cannot be fixed through iOS system updates. Once an attacker gains physical access to the device, they can execute code via the USB interface before iOS boots, and turning on airplane mode cannot prevent such attacks.Yishi advises that iPhone 11 and earlier models are not recommended for storing mnemonic phrases. Users who have used such devices to save mnemonic phrases should generate a brand new mnemonic phrase in a trusted environment and migrate their assets, rather than just changing the wallet address under the original mnemonic phrase. Additionally, users should promptly update their systems, use more complex device and wallet passwords, avoid charging through public USB interfaces, and be vigilant about potential physical attacks during periods when the device is out of their control for extended periods.Previously, OneKey founder Yishi had posted on platform X suggesting users use iPhones as cold wallets, but only recommended using iPhone 17 or newer models.

first_img THORChain plans to execute the v3.21 upgrade on October 23, fixing vulnerabilities to promote the restart of Rujira

According to The Defiant, THORChain announced that its v3.21 upgrade will fix the FIN contract vulnerability on Rujira and allow the previously paused application layer to restart. The network has set the upgrade target at block height 28,366,100, with an expected time around October 23. After the restart, trading, lending, borrowing, and automated trading on Rujira will resume. Rujira's products run through smart contracts within THORChain, rather than on an independent blockchain, and the application layer can pause these contracts without affecting the underlying layer of THORChain.According to Rujira, the vulnerability was discovered on September 26, when an attacker transferred a custom concentrated liquidity position without holding a position. The team paused the application layer with the support of node operators, and only one position from the Rujira team itself was affected, with no loss of user funds. Rujira attributed the vulnerability to a flaw in the position transfer function, rather than the trading logic of the liquidity strategy. On September 27, Rujira stated that the fix is located at the underlying layer and has been scheduled for the v3.21 upgrade.Regarding the restart window, Rujira proposed a conditional grace period in its plan on October 15: if the application layer is ready to resume, any credit account position with a loan-to-value ratio above 100% and meeting liquidation conditions will request node operators to pause the credit account contract for an additional 24 hours, allowing borrowers to replenish collateral before liquidation resumes. Borrowers can replenish collateral through Rujira Borrow or by directly transferring assets to the credit account address. Rujira indicated on October 10 that positions still deemed unsafe after the grace period may be liquidated when the liquidator triggers the process.

Polygon Labs: Bor v2.1.3 released, fixing two DoS security vulnerabilities

Polygon Labs official announcement, Bor v2.1.3 is officially released to the public, previously distributed in private version form to validators and major infrastructure providers. This update fixes two medium-severity denial-of-service vulnerabilities in BlockSTM V2 parallel block execution, both submitted by security researchers through the Immunefi bug bounty program.Unbounded keccak256 cache issue: Attackers can fill hundreds of MiB of cache during the speculative execution phase by constructing specific transactions, leading to node memory exhaustion and delayed block production. The fix is to set a capacity limit on the shared cache. Repeated code hash calculation issue in parallel execution: A single transaction can cause the parallel processor to take about 11 seconds, severely affecting node activity. The fix is to cache code hash results on a per-transaction basis.In addition, this update also includes several internal hardening measures: the transaction pool address filtering adds interception for EIP-7702 SetCode authorization, RPC batch execution pool concurrency limit fixes, consistency fixes for reading balances across self-destruct boundaries in parallel execution, and an automatic cleanup mechanism for pending transactions (default 3 hours). The affected versions are Bor v2.1.1 and v2.1.2. v2.1.3 is a non-hard fork, and nodes can upgrade individually without coordination. No exploitation records of the two vulnerabilities have been found on the mainnet and testnet Amoy.

Papertrade responds to concerns about price manipulation and protocol vulnerabilities: the relaxed position limit in the early stages of launch is the cause, and parameters have begun to tighten

Papertrade's official response to the allegations of price manipulation and the existence of obvious loopholes in the protocol states: It has never been possible for small orders to have the same priority as large orders. If this were done, the front end would suffer from congestion due to junk trading, and the consequences would be much worse than the existing queuing mechanism.Under these constraints, we have designed the fair launch to be as inclusive as possible.Last night, the attempts to manipulate BTC/ETH on Hyperliquid BBO were not due to flaws in the mechanism that took six months to design. These situations had already been considered; it was only because the position limits were set very loosely in the early stages to cope with congestion that such occurrences were possible. If position limits were set during peak demand for launching, it would only exacerbate the slow experience, and the queuing mechanism itself, due to the uncertainty of opening/closing confirmation times, naturally provides protection against manipulation.As congestion eases, we have begun to tighten position limits on-chain and at the relay level. In such a system, manipulation attacks are always possible— the key is whether the attempt is economically viable. The official goal is to set parameters to a point where it is almost never profitable; even if successful, the tail risk is extremely high, and the expected value is negative.
app_icon
ChainCatcher Building the Web3 world with innovations.