[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fupIvQpEh3Y2YQ_2polGbFR0TFZ1sWnFrcO4QP1qfGm4":3},{"code":4,"msg":5,"data":6},0,"success",{"id":7,"title":8,"description":9,"coverPicUrl":10,"keywords":11,"commentId":12,"isOriginal":13,"isCopyable":13,"view":14,"publish_time":15,"update_time":15,"content":16},55,"Apifox被曝供应链投毒 大量高敏感信息被盗取 速查！","3月25日，白帽黑客@白帽酱 发布了一篇技术分析，曝光了一起针对国内主流 API 调试工具Apifox的供应链投毒攻击的技术细节。当日晚间，Apifox 官方同步发布风险提示与升级公告，确认其公网 SaaS 版桌面客户端遭遇恶意代码投毒，全平台用户均受影响，攻击活跃窗口长达 18 天，大量开发者与企业的核心敏感凭证面临泄露风险，甚至可能已遭遇深度入侵。","https:\u002F\u002Fi0.bilitools.top\u002Fimages\u002Fartical\u002Fcover\u002F70152fccb3f81e62d5c2f73fd02230ac2.png","Apifox,供应链攻击,网络安全",56,true,6824,1774551375,{"frontmatter":17,"meta":18,"nodes":19},{},{},[20,43,52,56,65,70,74,78,129,133,152,157,166,172,181,186,195,200,204,223,227,232,236,245,249,253,263,289,293,297,305,311,315,322,330,413,417,421,425],[21,22,25,26,35,36,42],"p",{"$":23},{"html":24,"block":4},1,"就在昨天（3月25日），白帽黑客",[27,28,34],"a",{"$":29,"title":30,"href":31,"target":32,"rel":33},{"html":24,"block":4},"@白帽酱 的博客","https:\u002F\u002Frce.moe\u002F","_blank","noopener","@白帽酱"," 发布了一篇",[27,37,41],{"$":38,"title":39,"href":40,"target":32,"rel":33},{"html":24,"block":4},"Apifox 供应链投毒攻击 — 完整技术分析","https:\u002F\u002Frce.moe\u002F2026\u002F03\u002F25\u002Fapifox-supply-chain-attack-analysis\u002F","技术分析","，曝光了一起针对国内主流 API 调试工具Apifox的供应链投毒攻击的技术细节。报告显示，这次攻击者十分狡猾，准备工作十分严密，用心险恶。",[21,44,46,47],{"$":45},{"html":24,"block":4},"昨日晚间，Apifox 官方同步发布风险提示与升级公告，确认其",[48,49,51],"strong",{"$":50},{"html":24,"block":4},"公网 SaaS 版桌面客户端遭遇恶意代码投毒，全平台（Windows、macOS、Linux）用户均受影响，攻击活跃窗口长达 18 天，大量开发者与企业的核心敏感凭证面临泄露风险，甚至可能已遭遇深度入侵。",[21,53,55],{"$":54},{"html":24,"block":4},"目前已有消息表明多家互联网企业正在紧急进行内部网络和数据安全排查工作。",[21,57,59],{"$":58},{"html":24,"block":4},[60,61],"img",{"$":62,"src":63,"alt":64},{"html":24,"block":4},"\u002F\u002Fi0.bilitools.top\u002Fimages\u002Fartical\u002F70152fccb3f81e62d5c2f73fd02230ac0.png","Apifox公告",[66,67,69],"h2",{"$":68,"id":69},{"html":24,"block":4},"事件核心始末",[21,71,73],{"$":72},{"html":24,"block":4},"本次攻击的根源，在于 Apifox 桌面端基于 Electron 框架开发时，未严格启用 sandbox 沙箱参数，暴露了 Node.js API 接口，给了攻击者可乘之机。",[21,75,77],{"$":76},{"html":24,"block":4},"攻击的完整时间线如下：",[79,80,82,105,113,121],"ul",{"$":81},{"html":24,"block":4},[83,84,86,90,91,99,100,104],"li",{"$":85},{"html":24,"block":4},[48,87,89],{"$":88},{"html":24,"block":4},"2026 年 3 月 4 日","：攻击者注册的恶意 C2 域名",[92,93,95],"code",{"$":94},{"html":24,"block":4},[27,96,98],{"href":97},"http:\u002F\u002Fapifox.it.com","apifox.it.com","完成解析上线，Apifox CDN 上的",[92,101,103],{"$":102},{"html":24,"block":4},"apifox-app-event-tracking.min.js","文件被恶意篡改，投毒攻击正式启动",[83,106,108,112],{"$":107},{"html":24,"block":4},[48,109,111],{"$":110},{"html":24,"block":4},"3 月 4 日 - 3 月 22 日","：攻击持续活跃，恶意代码通过 CDN 广泛分发，期间攻击者持续迭代攻击载荷，不断扩大窃取范围",[83,114,116,120],{"$":115},{"html":24,"block":4},[48,117,119],{"$":118},{"html":24,"block":4},"3 月 22 日","：恶意域名 DNS 记录下线，停止解析",[83,122,124,128],{"$":123},{"html":24,"block":4},[48,125,127],{"$":126},{"html":24,"block":4},"3 月 25 日","：安全研究人员发布完整技术分析报告，Apifox 官方同步发布风险公告与修复版本",[21,130,132],{"$":131},{"html":24,"block":4},"被篡改的 JS 文件原本是 Apifox 的合法事件追踪 SDK，正常大小仅 34KB，投毒后被追加了约 42KB 的严重混淆恶意代码，文件大小变为 77KB。Apifox 桌面端启动时会自动加载该文件，导致恶意代码在用户设备上直接执行。",[21,134,136,137,142,143,151],{"$":135},{"html":24,"block":4},"值得警惕的是，攻击者使用的",[92,138,140],{"$":139},{"html":24,"block":4},[27,141,98],{"href":97},"域名极具迷惑性 ——",[48,144,146,150],{"$":145},{"html":24,"block":4},[92,147,149],{"$":148},{"html":24,"block":4},".it.com","并非意大利国别域名，而是无标准监管的商业二级域名服务","，极易被误认为 Apifox 官方测试域名、区域服务域名，社会工程学设计极其隐蔽。",[66,153,156],{"$":154,"id":155},{"html":24,"block":4},"攻击全流程不止窃密更是完整的主机控制权接管","攻击全流程：不止窃密，更是完整的主机控制权接管",[21,158,160,161,165],{"$":159},{"html":24,"block":4},"安全研究人员通过反混淆还原了完整攻击链，本次攻击绝非简单的信息窃取，而是一套",[48,162,164],{"$":163},{"html":24,"block":4},"设计精巧、能力完整的远程控制体系，攻击分为多个阶段逐步推进","：",[167,168,171],"h3",{"$":169,"id":170},{"html":24,"block":4},"第一阶段终端沦陷与基础信息窃取","第一阶段：终端沦陷与基础信息窃取",[21,173,175,176,180],{"$":174},{"html":24,"block":4},"恶意代码执行后，首先会完成设备指纹标定，通过 MAC 地址、CPU 型号、主机名等信息生成唯一设备 ID，同时直接窃取 Apifox 本地存储的用户登录 accessToken，调用官方 API ",[48,177,179],{"$":178},{"html":24,"block":4},"获取用户的姓名、邮箱等核心身份信息","，为后续定向攻击铺路。",[167,182,185],{"$":183,"id":184},{"html":24,"block":4},"第二阶段c2-通信与远程载荷加载","第二阶段：C2 通信与远程载荷加载",[21,187,189,190,194],{"$":188},{"html":24,"block":4},"恶意代码会主动连接恶意 C2 服务器，加密上传用户与设备信息，同时获取并执行攻击者下发的远程指令。攻击者采用了 RSA-2048 非对称加密保护通信，同时通过",[48,191,193],{"$":192},{"html":24,"block":4},"一次性随机 URL、脚本加载后自销毁、无缓存配置","等手段，大幅提升取证与溯源难度。",[167,196,199],{"$":197,"id":198},{"html":24,"block":4},"第三阶段全量高敏感信息批量窃取","第三阶段：全量高敏感信息批量窃取",[21,201,203],{"$":202},{"html":24,"block":4},"这是本次攻击危害最直接的环节，攻击者分两个版本迭代，几乎覆盖了开发者设备上所有核心权限凭证：",[79,205,207,215],{"$":206},{"html":24,"block":4},[83,208,210,214],{"$":209},{"html":24,"block":4},[48,211,213],{"$":212},{"html":24,"block":4},"v1基础窃取范围","：SSH 目录全量密钥对、Shell 命令历史（含硬编码的密码、Token、内网地址）、Git 明文凭证、系统进程列表",[83,216,218,222],{"$":217},{"html":24,"block":4},[48,219,221],{"$":220},{"html":24,"block":4},"v2升级窃取范围","：K8s 集群配置文件、npm 仓库认证 Token、Shell 环境变量、SVN 凭证，同时遍历用户桌面、文档、主目录，Windows 设备额外扫描 D\u002FE\u002FF 盘目录结构",[21,224,226],{"$":225},{"html":24,"block":4},"所有窃取的数据会经过 Gzip 压缩 + AES-256-GCM 加密后，批量上传到攻击者服务器，完全规避常规 DLP 检测。",[167,228,231],{"$":229,"id":230},{"html":24,"block":4},"最致命风险可随时下发任意代码的完整-rce-能力","最致命风险：可随时下发任意代码的完整 RCE 能力",[21,233,235],{"$":234},{"html":24,"block":4},"必须重点警示的是，目前已捕获的窃密行为，仅仅是攻击的侦察阶段。",[21,237,239,240,244],{"$":238},{"html":24,"block":4},"这套恶意代码的核心，是一个基于",[92,241,243],{"$":242},{"html":24,"block":4},"eval()","的完全灵活的远程代码执行平台 —— 只要 Apifox 客户端保持运行，恶意代码会以 30 分钟到 3 小时的随机间隔持续轮询 C2 服务器，攻击者可在任意时间，向任意目标设备下发任意代码，实现完全的主机控制。",[21,246,248],{"$":247},{"html":24,"block":4},"这意味着，被标记为高价值目标的企业、机构用户，极有可能已经遭遇了更深层次的入侵：包括植入独立持久化后门、利用窃取的 SSH 密钥横向渗透内网、接管 K8s 生产集群、窃取核心源代码与数据库数据，甚至利用窃取的凭证发起二次供应链投毒。",[66,250,252],{"$":251,"id":252},{"html":24,"block":4},"官方公告与修复进展",[21,254,256,257,262],{"$":255},{"html":24,"block":4},"Apifox 官方在 3 月 25 日发布的《",[27,258,260],{"$":259,"title":260,"href":261,"target":32,"rel":33},{"html":24,"block":4},"关于 Apifox 外部 JS 文件受篡改的风险提示与升级公告","https:\u002F\u002Fdocs.apifox.com\u002F8392582m0","》中，确认了本次供应链攻击事件，向用户致歉并公布了修复方案：",[264,265,267,276,280],"ol",{"$":266},{"html":24,"block":4},[83,268,270,271,275],{"$":269},{"html":24,"block":4},"已紧急发布",[48,272,274],{"$":273},{"html":24,"block":4},"2.8.19 修复版本","，开启自动更新提醒，彻底废除了风险文件的在线动态加载机制，改为本地内置打包，从根源切断同类攻击路径",[83,277,279],{"$":278},{"html":24,"block":4},"已完成内部服务器相关安全凭证的全量重置，同步启动深度代码审计与溯源调查",[83,281,283,284,288],{"$":282},{"html":24,"block":4},"明确本次事件受影响范围仅为",[48,285,287],{"$":286},{"html":24,"block":4},"2026 年 3 月 4 日 - 3 月 22 日期间使用的公网 SaaS 版桌面客户端","，SaaS Web 版、私有化部署版用户不受影响",[66,290,292],{"$":291,"id":292},{"html":24,"block":4},"紧急处置指南",[21,294,296],{"$":295},{"html":24,"block":4},"根据作者在评论区提供的排查方向，有人在博文评论区提供了快速检测的方法：",[21,298,300],{"$":299},{"html":24,"block":4},[60,301],{"$":302,"src":303,"alt":304},{"html":24,"block":4},"\u002F\u002Fi0.bilitools.top\u002Fimages\u002Fartical\u002Fc62938fde1a75c14b9ae371376931f820.png","",[306,307,310],"pre",{"$":308,"class":309},{"html":24,"block":24},"language-cpp","\u003Ccode># Windows PowerShell下执行\nSelect-String -Path \"$env:APPDATA\\apifox\\Local Storage\\leveldb\\*\" -Pattern \"rl_mc\",\"rl_headers\" -List | Select-Object Path\n\n# macOS 终端下执行\ngrep -arlE \"rl_mc|rl_headers\" ~\u002FLibrary\u002FApplication\\ Support\u002Fapifox\u002FLocal\\ Storage\u002Fleveldb\n\n# 如果有输出具体文件则可以判定中招，需要及时采取补救措施。\u003C\u002Fcode>",[306,312,314],{"$":313},{"html":24,"block":24},"\u003Cspan style=\"font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, 'Open Sans', 'Helvetica Neue', sans-serif; white-space: normal;\">小编排查后发现也中招了\u003C\u002Fspan>😅😅😅",[21,316,318],{"$":317},{"html":24,"block":4},[60,319],{"$":320,"src":321,"alt":304},{"html":24,"block":4},"\u002F\u002Fi0.bilitools.top\u002Fimages\u002Fartical\u002Fad5da2be5d10ffa5391ed8d5ae19972b0.png",[21,323,325,326,165],{"$":324},{"html":24,"block":4},"@白帽酱 在报告中提示，",[48,327,329],{"$":328},{"html":24,"block":4},"无论是否发现异常，只要你在风险时间段内使用过 Apifox SaaS 桌面客户端，务必按照 “已失陷” 的最高级别完成以下处置，切勿抱有侥幸心理",[264,331,333,341,372,387,405],{"$":332},{"html":24,"block":4},[83,334,336,340],{"$":335},{"html":24,"block":4},[48,337,339],{"$":338},{"html":24,"block":4},"立即升级客户端","：尽快将 Apifox 桌面端升级至 2.8.19 及以上最新版本，立即停用所有旧版本客户端",[83,342,344,348,349],{"$":343},{"html":24,"block":4},[48,345,347],{"$":346},{"html":24,"block":4},"全量轮换敏感凭证","：这是最核心的处置步骤，务必全面排查并重置以下凭证：",[79,350,352,356,360,364,368],{"$":351},{"html":24,"block":4},[83,353,355],{"$":354},{"html":24,"block":4},"全量 SSH 密钥对，同步排查服务器登录日志，清除异常访问记录",[83,357,359],{"$":358},{"html":24,"block":4},"GitHub、GitLab 等平台的 Personal Access Token",[83,361,363],{"$":362},{"html":24,"block":4},"Kubernetes 集群的 OIDC Token 与 kubeconfig 配置",[83,365,367],{"$":366},{"html":24,"block":4},"npm、私有镜像仓库的认证 Token",[83,369,371],{"$":370},{"html":24,"block":4},"命令行历史、环境变量中暴露的数据库密码、云服务 AK\u002FSK、API Key 等所有敏感信息",[83,373,375,379,380,386],{"$":374},{"html":24,"block":4},[48,376,378],{"$":377},{"html":24,"block":4},"阻断恶意域名访问","：在 hosts 文件中添加配置",[92,381,383,384],{"$":382},{"html":24,"block":4},"127.0.0.1 ",[27,385,98],{"href":97},"，彻底拦截与恶意 C2 服务器的通信",[83,388,390,394,395,399,400,404],{"$":389},{"html":24,"block":4},[48,391,393],{"$":392},{"html":24,"block":4},"失陷检测","：检查 Apifox 客户端 Electron localStorage 中是否存在",[92,396,398],{"$":397},{"html":24,"block":4},"_rl_headers","、",[92,401,403],{"$":402},{"html":24,"block":4},"_rl_mc","恶意键值，排查设备网络日志中是否存在对恶意域名的访问记录",[83,406,408,412],{"$":407},{"html":24,"block":4},[48,409,411],{"$":410},{"html":24,"block":4},"全面风险审计","：企业用户需全面审计内网服务器、代码仓库、集群环境的异常操作，排查横向渗透痕迹",[66,414,416],{"$":415,"id":416},{"html":24,"block":4},"警钟撅烂",[21,418,420],{"$":419},{"html":24,"block":4},"本次事件是一起典型的开发者工具供应链攻击，攻击者利用开发者工具的高权限属性，通过篡改 CDN 资源实现广撒网式入侵，一旦得手，就能直接触达企业核心研发、生产环境，危害极大。",[21,422,424],{"$":423},{"html":24,"block":4},"而本次攻击也暴露出两个关键问题：一是 Electron 桌面应用的安全机制滥用，未启用沙箱、过度暴露 Node.js API，直接让前端恶意代码获得了系统级权限；二是前端远程资源的完整性校验缺失，未启用 SRI 子资源完整性校验，导致 CDN 资源被篡改后无法被识别拦截。",[21,426,428],{"$":427},{"html":24,"block":4},"对于广大开发者与企业而言，本次事件也敲响了警钟：研发工具类软件往往持有最高级别的系统与环境权限，其供应链安全必须纳入核心安全管控体系，切勿再将第三方研发工具视为 “可信资产”。"]