【独家】AWS爆出惊天漏洞！AI助手Q dev竟成“自毁按钮”，出海企业如何防范？- 大数跨境

首页

【独家】AWS爆出惊天漏洞！AI助手Q dev竟成“自毁按钮”，出海企业如何防范？

雨神汇

2025-07-24

导读：黑客提交PR引爆云安全危机，AWS的“安全至上”口号还能信吗？

点击蓝字关注雨生

AWS爆出惊天漏洞！AI助手竟成“自毁按钮”，出海企业如何防范？

副标题：黑客提交PR引爆云安全危机，AWS的“安全至上”遇上“AI至上”还能信吗？

今早雨生收到海外版雨生云计算【Corey Quinn】的 Big News，这应该是首类AI 入侵Cloud infra。

核心摘要：

知名AWS观察者Corey Quinn发布报告，指出一位黑客通过提交恶意PR（Pull Request）的方式，成功入侵Amazon Q Developer extension for VS Code，并使其具备了删除用户本地文件和云基础设施的能力。尽管AWS声称未有客户受到影响，但其处理方式（悄悄删除问题版本，未发布安全公告）引发了广泛质疑。

在华出海从业者及CXO关注点：

云安全风险再敲警钟： 该事件再次凸显了云安全面临的严峻挑战，出海企业需重新审视自身的云安全策略。
AI安全成新焦点： AI coding assistant的安全漏洞可能导致更严重的后果，出海企业需加强对AI工具的安全评估和管理。
供应链安全不容忽视： 黑客通过PR入侵的方式，暴露了开源供应链的安全风险，出海企业需加强对第三方代码的审查。
透明度至关重要： AWS的处理方式引发了对透明度的质疑，出海企业在选择云服务商时，应关注其信息披露和安全事件响应机制。

建议转发理由：

深度揭露： 详细揭露AWS安全漏洞事件的始末，引发行业对云安全的深入思考。
风险警示： 提醒出海企业关注云安全、AI安全和供应链安全等风险，提高安全意识。
选型参考： 为出海企业在选择云服务商时，提供参考依据，强调透明度和安全事件响应的重要性。

雨生点评：

AWS的这次安全事件无疑是一次重大警钟。它提醒我们，在享受云计算带来的便利的同时，必须时刻保持对安全的警惕。对于在华出海企业而言，除了加强自身的技术防护能力外，更要关注云服务商的安全机制和透明度。只有选择值得信赖的合作伙伴，才能真正保障业务的稳定运行。

英文&中文对照翻译稿：

Headline: Last Week in AWS: Amazon Q: Now with Helpful AI-Powered Self-Destruct Capabilities

标题：上周在AWS：Amazon Q：现在具有有用的AI驱动的自毁功能

A hacker submitted a PR. It got merged. It told Amazon Q to nuke your computer and cloud infra. Amazon shipped it.

一位黑客提交了一个PR（Pull Request）。它被合并了。它告诉Amazon Q摧毁你的电脑和云基础设施。Amazon发布了它。

Mistakes happen, and cloud security is hard. But this is very far from "oops, we fat-fingered a command," this is "someone intentionally slipped a live grenade into prod and AWS gave it version release notes."

错误会发生，云安全很难。但这远非“哎呀，我们错误地输入了一个命令”，而是“有人故意将一颗实弹手榴弹塞进生产环境，而AWS给它提供了版本发布说明”。

"Security Is Our Top Priority," They Said With a Straight Face

“安全是我们的首要任务”，他们面不改色地说。

"We quickly mitigated an attempt to exploit a known issue..."

“我们迅速缓解了利用已知问题进行的攻击……”

Which is a fancy way of saying: "We got lucky this time." Not secure, just fortunate that their AI assistant didn't execute what it was told.

这是一种委婉的说法：“这次我们很幸运。”不是安全，只是幸运的是他们的AI助手没有执行它被告知的内容。

If I have to hear about it from a third party, it undermines "Security is Job Zero" and reduces it from an ethos into pretty words trotted out for keynote slides.

如果我必须从第三方那里听到这件事，它会破坏“安全是首要任务”，并将其从一种精神降低为在主题演讲幻灯片上展示的漂亮话语。

The prompt instructed Amazon Q to use shell commands to wipe local directories--including user home directories--while skipping hidden files like a considerate digital arsonist.

提示指示Amazon Q使用shell命令擦除本地目录——包括用户主目录——同时像一个体贴的数字纵火犯一样跳过隐藏文件。

The prompt told Q to discover configured AWS profiles, then start issuing destructive CLI commands: aws ec2 terminate-instances, aws s3 rm, aws iam delete-user, ...and so on.

提示告诉Q发现配置的AWS配置文件，然后开始发出破坏性的CLI命令：aws ec2 terminate-instances，aws s3 rm，aws iam delete-user，...等等。

Amazon confidently claims that no customer resources were affected. But here's the thing:

Amazon自信地声称没有客户资源受到影响。但问题是：

The injected prompt was designed to delete things quietly and log the destruction to a local file--/tmp/CLEANER.LOG.

注入的提示旨在悄悄地删除东西并将破坏记录到本地文件——/tmp/CLEANER.LOG。

So unless Amazon deployed agents to comb through the temp directories of every system running the compromised version during the roughly two days this extension was the default--and let's be real, they didn't, and couldn't since that's customer-side of the shared responsibility model--there's no way they can confidently say nothing happened.

因此，除非Amazon部署代理来梳理每个运行受损版本的系统的临时目录，大约两天内这个扩展是默认的——并且让我们现实一点，他们没有，并且由于那是共享责任模型的客户侧，所以无法这样做——否则他们无法自信地说什么都没发生。

According to the hacker (hardly a credible source, but they're talking while AWS is studiously not) they submitted the malicious pull request from a random GitHub account with no prior access--not a longtime contributor, not an employee, not even someone with any track record.

根据黑客的说法（几乎不是一个可信的来源，但他们在说话而AWS却在认真地不做声），他们从一个随机的GitHub帐户提交了恶意拉取请求，该帐户以前没有任何访问权限——不是长期贡献者，不是员工，甚至不是任何有记录的人。

Version 1.84.0 of the Amazon Q Developer extension was silently pulled from the Visual Studio Code Marketplace. No changelog note. No security advisory. No CVE. No "our bad." Just… gone.

Amazon Q Developer扩展的1.84.0版本已从Visual Studio Code Marketplace中悄悄删除。没有变更日志注释。没有安全建议。没有CVE。没有“我们的错”。只是……消失了。

Amazon's claim that "no customer resources were impacted" leans heavily--suspiciously heavily--on the idea that the attacker didn't really intend to cause damage.

Amazon声称“没有客户资源受到影响”严重依赖——令人怀疑地严重依赖——攻击者实际上并不打算造成损害的想法。

Intent is irrelevant when someone can run aws s3 rm across your cloud estate. Whether or not they pulled the trigger is beside the point--the gun was loaded, cocked, and handed to them with a release tag.

当有人可以在您的云资产中运行aws s3 rm时，意图无关紧要。他们是否扣动了扳机是无关紧要的——枪已上膛，扳机已扣动，并带有发布标签地交给了他们。

Maybe Vet Pull Requests Just a Little Bit

也许稍微审查一下拉取请求

Don't Handle Security Incidents Like You're Hiding a Body

不要像隐藏尸体一样处理安全事件

Stop Leaning on "No Customers Were Impacted" as a Security Strategy

停止依赖“没有客户受到影响”作为安全策略

Original Article Link: https://www.lastweekinaws.com/blog/amazon-q-now-with-helpful-ai-powered-self-destruct-capabilities/?ck_subscriber_id=1493233596&utm_source=convertkit&utm_medium=email&utm_campaign=%5BLast%20Week%20in%20AWS%20Extras%5D:%20Amazon%20Q:%20Now%20with%20Helpful%20AI-Powered%20Self-Destruct%20Capabilities%20-%2018388251

雨生福利

知识星球三日体验卡@雨生的VIP盆友们，可以领取体验。