Scan to download
BTC $76,973.37 -0.78%
ETH $2,289.58 -0.92%
BNB $625.11 -0.19%
XRP $1.39 -1.48%
SOL $84.11 -1.31%
TRX $0.3231 -0.18%
DOGE $0.0998 +1.95%
ADA $0.2465 -0.10%
BCH $447.50 +0.19%
LINK $9.27 -0.47%
HYPE $40.61 -3.94%
AAVE $97.95 +2.21%
SUI $0.9307 +0.55%
XLM $0.1648 -2.22%
ZEC $336.44 -6.14%
BTC $76,973.37 -0.78%
ETH $2,289.58 -0.92%
BNB $625.11 -0.19%
XRP $1.39 -1.48%
SOL $84.11 -1.31%
TRX $0.3231 -0.18%
DOGE $0.0998 +1.95%
ADA $0.2465 -0.10%
BCH $447.50 +0.19%
LINK $9.27 -0.47%
HYPE $40.61 -3.94%
AAVE $97.95 +2.21%
SUI $0.9307 +0.55%
XLM $0.1648 -2.22%
ZEC $336.44 -6.14%

slow

Jefferies: Kelp DAO security incident may slow down Wall Street's blockchain layout

Jefferies, a Wall Street investment bank, pointed out that the approximately $293 million attack incident on Kelp DAO exposed critical infrastructure risks, which may prompt traditional financial institutions to reassess the pace of blockchain and tokenization advancement.Jefferies believes that the attackers triggered market sell-offs and liquidity strains by minting uncollateralized tokens and engaging in cross-platform lending. This incident is thought to be related to the Lazarus Group and also highlights the single point of failure issues in the verification mechanisms of cross-chain bridges. As institutions accelerate the tokenization of assets (such as funds, bonds, and deposits), the associated risks may cause some banks and asset management institutions to delay deployment and prioritize examining system security. Especially in scenarios that rely on cross-chain infrastructure, security vulnerabilities could lead to market fragmentation, undermining the practical utility of tokenized assets.Despite short-term confidence being shaken, Jefferies still emphasizes that the long-term trend remains unchanged. Under the backdrop of regulatory advancements and continuous improvements in infrastructure, applications such as stablecoins still have growth potential. However, the industry as a whole is still in the early stages of development and requires time to enhance system robustness.

Slow Fog: Pay attention to checking for malicious versions of axios and the exposure risk of global installation history for OpenClaw npm

Slow Fog has once again issued a security reminder stating to pay attention to checking for malicious versions of axios and the exposure risk of OpenClaw npm global installation history. axios@1.14.1 and axios@0.3.4 have been confirmed as malicious versions, both of which have injected the dependency plain-crypto-js@4.2.1, delivering cross-platform malicious payloads through the postinstall script.The impact of OpenClaw is assessed based on scenarios: source code builds are not affected, as the locked versions in the lock file are 1.13.5/1.13.6; however, users who installed via npm install -g openclaw@2026.3.28 face historical exposure risks due to the presence of optionalDependencies.axios@^1.7.4 in the dependency chain, which may resolve to axios@1.14.1 during the time window when the malicious version is still online. Currently, npm has reverted the resolution to axios@1.14.0, but environments that were installed during the attack window are still advised to be checked. Slow Fog has provided inspection commands and IoC paths for various platforms; if the plain-crypto-js directory is found, even if the package.json has been cleaned, it should still be regarded as high-risk execution traces. It is recommended that affected hosts immediately rotate credentials and conduct host-side inspections. Previously, Slow Fog founder Yu Xian reminded that OpenClaw version 3.28 may introduce a toxic version of axios, and users need to urgently check.
app_icon
ChainCatcher Building the Web3 world with innovations.