Scan to download
BTC $69,841.07 -4.01%
ETH $1,981.28 +0.16%
BNB $683.40 -0.58%
XRP $1.26 -2.84%
SOL $79.56 -1.42%
TRX $0.3406 -2.93%
DOGE $0.0992 -0.19%
ADA $0.2238 -3.09%
BCH $285.64 -0.97%
LINK $8.83 -1.56%
HYPE $71.50 -1.17%
AAVE $77.80 -3.77%
SUI $0.8479 -3.18%
XLM $0.2280 -9.94%
ZEC $558.41 +1.51%
BTC $69,841.07 -4.01%
ETH $1,981.28 +0.16%
BNB $683.40 -0.58%
XRP $1.26 -2.84%
SOL $79.56 -1.42%
TRX $0.3406 -2.93%
DOGE $0.0992 -0.19%
ADA $0.2238 -3.09%
BCH $285.64 -0.97%
LINK $8.83 -1.56%
HYPE $71.50 -1.17%
AAVE $77.80 -3.77%
SUI $0.8479 -3.18%
XLM $0.2280 -9.94%
ZEC $558.41 +1.51%

den

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.

Coinbase reviews the May outage incident: AWS cascading failure exposes architectural risks

Coinbase released a retrospective report on the large-scale service interruption event on May 7, 2026.The outage lasted approximately 8 hours, with full recovery taking about 12 hours. During this time, trading, deposits, withdrawals, and most core services were unavailable or severely degraded. Coinbase stated that the outage was caused by multiple cooling units failing simultaneously in the cooling system of a data center in one availability zone (use1-az4) in the AWS us-east-1 region, triggering cabinet thermal protection shutdowns, which led to EC2 instances and EBS volumes going offline, affecting multiple internet services.During the recovery process, the Coinbase trading matching engine lost quorum due to the cluster architecture deployed in a single AWS data center losing most nodes. It required urgent code adjustments and the reconstruction of a new node group to restore operation, gradually restarting market trading during the recovery.Additionally, the AWS-managed Kafka (MSK) service experienced control plane failures, preventing the automatic re-election of partition leaders, further blocking quotes, fees, and some settlement and data flow systems, which expanded the overall impact.After manual partition migration in collaboration with the AWS engineering team, the system gradually returned to normal. Coinbase stated that this incident exposed its shortcomings in cross-availability zone automatic switching capabilities and disaster recovery for managed middleware. The company will upgrade its cross-region hot backup architecture, strengthen regular failure drills, and migrate the Kafka system from dual availability zones to a three availability zone deployment, while also working with AWS to advance root cause fixes and improvements.

Powell warns about the independence of the Federal Reserve

According to an article by "Federal Reserve Mouthpiece" Nick Timiraos, in a speech on Sunday evening local time, former Federal Reserve Chairman Powell stated that if any administration finds an excuse to dismiss Federal Reserve officials simply due to policy disagreements, the Federal Reserve will not be able to survive. Powell currently serves as a Federal Reserve Governor. While speaking generally about topics such as institutions and the rule of law, he did not name any specific president or express any personal grievances. However, when discussing the institutional framework designed to keep monetary policy decision-making power out of presidential control, his wording was extremely precise.Powell emphasized the legal protections aimed at preventing Federal Reserve officials from being arbitrarily dismissed and specifically pointed out that the executive branch "does not play any role in selecting or overseeing the 12 regional reserve bank presidents," who, along with the Federal Reserve Governors, vote together to determine interest rates. "If any administration finds an excuse to dismiss Federal Reserve officials simply due to policy disagreements, then future administrations will surely follow suit," Powell said.He noted that the credibility built up by the Federal Reserve over decades is an "invaluable asset," and he and his colleagues "have a responsibility to defend it."
app_icon
ChainCatcher Building the Web3 world with innovations.