Scan to download
BTC $60,611.75 -0.26%
ETH $1,553.03 -2.58%
BNB $573.50 -1.43%
XRP $1.09 -0.68%
SOL $62.16 -4.56%
TRX $0.3207 -0.70%
DOGE $0.0817 -1.03%
ADA $0.1579 -1.14%
BCH $218.84 +0.44%
LINK $7.38 -0.03%
HYPE $58.28 -4.28%
AAVE $60.88 -1.57%
SUI $0.7141 +1.56%
XLM $0.2019 +7.15%
ZEC $342.26 +1.90%
BTC $60,611.75 -0.26%
ETH $1,553.03 -2.58%
BNB $573.50 -1.43%
XRP $1.09 -0.68%
SOL $62.16 -4.56%
TRX $0.3207 -0.70%
DOGE $0.0817 -1.03%
ADA $0.1579 -1.14%
BCH $218.84 +0.44%
LINK $7.38 -0.03%
HYPE $58.28 -4.28%
AAVE $60.88 -1.57%
SUI $0.7141 +1.56%
XLM $0.2019 +7.15%
ZEC $342.26 +1.90%

tac

Slow Fog: Red Hat cloud service npm package suffers from active supply chain attacks, with stolen credentials found in over 300 GitHub repositories

SlowMist has issued a security alert, detecting an active npm supply chain attack targeting @redhat-cloud-services related packages. Currently, over 31 packages have been confirmed affected, with a weekly download volume of approximately 116,000 times, and stolen credentials exist in more than 300 GitHub repositories. This attack method is highly similar to the previous "Shai-Hulud" npm attack, including credential theft, creation of malicious repositories, and automated secret leakage. New suspicious repositories continue to emerge, indicating that the attack is still ongoing, and developers are still being continuously infected.Potential harms include: theft of GitHub/npm tokens, leakage of AWS/GCP/Azure cloud credentials, collection of SSH keys and Kubernetes secrets, leakage of local environment and wallet data, creation of malicious repositories and persistence operations, and even potentially destructive actions after tokens are revoked. It is recommended to immediately remove or downgrade affected @redhat-cloud-services package versions, conduct a comprehensive audit of CI/CD workflows and dependency installations, rotate all GitHub, npm, cloud service, SSH, and wallet-related keys, retain logs, and rebuild exposed developer machines or Runners from clean images while maintaining a high level of vigilance.

Aave releases post-attack investigation on Kelp rsETH bridge

Regarding the attack on the Kelp rsETH LayerZero V2 bridge that occurred on April 18, Aave released a post-incident investigation on the X platform, emphasizing that the exposure was primarily due to third-party bridge infrastructure rather than the protocol itself. The attacker executed an RPC poisoning attack targeting a single validator of LayerZero, forging a cross-chain message. This led to the release of 116,500 rsETH on the Ethereum side without actual destruction on Unichain. The attacker subsequently deposited the stolen rsETH into Aave V3 (Ethereum Core and Arbitrum), borrowing approximately 82,650 WETH and 821 wstETH.The Aave Protocol Guardian and Risk Steward immediately implemented protective measures for the rsETH and WETH reserves. Currently, the WETH and rsETH markets in the affected V3 deployments are operating normally. The rsETH held by the attacker on Arbitrum has been destroyed, the LayerZero OFT adapter has been fully recharged in five batches, rsETH support has been fully restored, and Kelp has reopened the withdrawal, bridging, and claims functions for rsETH. The WETH LTV in the affected markets has been reset to pre-attack values, and Aave V3 is fully operational across all markets except for rsETH.The Arbitrum DAO has voted to authorize the transfer of frozen ETH to Aave LLC, and it is currently awaiting on-chain execution. The court is still reviewing the substantive content of the injunction, and Aave LLC will continue to comply with the injunction during the court's deliberation. Ongoing projects include: the Aave risk framework from Llama Risk, the bridging assessment framework, the release of evaluation reports for currently live assets, on-chain execution of Arbitrum DAO votes, and the court's review of the injunction.
app_icon
ChainCatcher Building the Web3 world with innovations.