BTC $62,609.60 -0.24%
ETH $1,783.43 +0.35%
BNB $569.14 +0.16%
XRP $1.06 -0.63%
SOL $75.15 -1.68%
TRX $0.3248 -1.61%
DOGE $0.0722 +0.05%
ADA $0.1590 -0.68%
BCH $235.86 -0.23%
LINK $7.94 +0.06%
HYPE $63.73 -2.25%
AAVE $95.67 +1.28%
SUI $0.7321 +0.07%
XLM $0.1790 -2.03%
ZEC $507.46 -1.87%
BTC $62,609.60 -0.24%
ETH $1,783.43 +0.35%
BNB $569.14 +0.16%
XRP $1.06 -0.63%
SOL $75.15 -1.68%
TRX $0.3248 -1.61%
DOGE $0.0722 +0.05%
ADA $0.1590 -0.68%
BCH $235.86 -0.23%
LINK $7.94 +0.06%
HYPE $63.73 -2.25%
AAVE $95.67 +1.28%
SUI $0.7321 +0.07%
XLM $0.1790 -2.03%
ZEC $507.46 -1.87%

slow

All
Article
Flash

Vitalik: Maintain an open attitude towards slowing down or pausing AI, and agree to initiate a pause if extreme situations arise

Vitalik posted on the X platform, stating that AI 2040 and its critics have incompatible worldviews regarding the speed and significance of AI progress. AI 2040 believes that unless strong measures are taken to completely prevent it, some form of superintelligence will emerge in various scenarios by 2040; critics argue that AI 2040 underestimates human coordination capabilities and threatens freedom, but do not view ASI itself as a risk of power concentration.He believes that if he were convinced that the current form of AI is just an ordinary technology, he would be closer to the critics' camp; if he were convinced that superintelligence would inevitably arrive by 2030, he would be closer to the AI 2040 camp. At the same time, due to significant uncertainty, he remains open to the idea of slowing down or pausing, and feels uncomfortable with the stance proposed by some large AI companies and intellectuals that "open source is detrimental, and the ideal outcome is to maintain global control dominance."Vitalik stated that an important reason he supports the d/acc platform is that directions such as formal verification, cryptography, secure and open hardware, pandemic resilience, defensive biotechnology, food and basic resource security, public cognitive systems, and non-concentrated power physical security are worth promoting under both worldviews. He also mentioned that the 2040 plan has increasingly supported open source and incorporated the idea of "mutual assured destruction of computational power," which is an improvement compared to allowing a few participants to selectively deprive their identified subjects of rights.There is no way to avoid trade-offs regarding whether to slow down or pause, and Vitalik believes that trigger conditions can be preset, allowing for a more open attitude towards slowing down or pausing when sufficient conditions are met within a specific timeframe.He also stated that if he were Elon Musk or Zuck, he would significantly transform Twitter into a platform that helps identify and facilitate such large win-win agreements, encouraging more people to participate in discussions, but he thinks this might also be naive. Currently, he does not see any non-naive ASI transition response plans, so he tends to show some tolerance towards those who are trying.
2026-07-11

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.
app_icon
ChainCatcher Building the Web3 world with innovations.