github

Tin tức từ ChainCatcher, đội ngũ bảo mật SlowMist gần đây đã tiết lộ phát hiện một kho GitHub độc hại giả mạo "Qwen 3.8 27B mô hình định lượng cục bộ". Kho này tuyên bố rằng tệp mô hình phải vượt quá 16GB, trong khi nội dung tải về thực tế chỉ khoảng 487KB, chứa các tệp ngụy trang, trình thông dịch LuaJIT và các kịch bản Lua đã bị làm rối. SlowMist nhấn mạnh rằng dự án chính thức của Qwen không bị xâm nhập.Phân tích của SlowMist chỉ ra rằng, sau khi chương trình độc hại này chạy, nó sẽ thu thập thông tin máy chủ, chụp màn hình và gửi đến máy chủ C2 của kẻ tấn công; khi máy chủ mã hóa không còn hoạt động, nó sẽ đọc địa chỉ C2 dự phòng từ hợp đồng trên chuỗi Polygon, kẻ tấn công có thể xoay vòng cơ sở hạ tầng thông qua giao dịch trên chuỗi.Tải trọng tiếp theo có thể đánh cắp thông tin đăng nhập trình duyệt, Cookie, lịch sử, email, chứng chỉ WinSCP, Steam, cũng như các tệp và dữ liệu mở rộng liên quan đến ví tiền điện tử. SlowMist cũng phát hiện ra rằng, ít nhất 23 kho GitHub và 29 gói nén tương tự đã sử dụng cùng một chuỗi phát Lua.

Thông báo từ ChainCatcher, trang trạng thái chính thức của GitHub cho thấy, hiện tại nền tảng của họ đang trải qua sự cố dịch vụ, nhiều chức năng cốt lõi gặp phải sự giảm sút về khả năng sử dụng.Theo thông báo mới nhất, tỷ lệ lỗi trên trang web GitHub và yêu cầu API đã từng đạt khoảng 20%, tỷ lệ lỗi khi tải xuống kho lưu trữ và nội dung kho lưu trữ gốc khoảng 50%. Ngoài ra, xác thực danh tính SAML và OIDC, SCIM cũng như chức năng đồng bộ nhóm cũng bị ảnh hưởng.Hiện tại, các dịch vụ bị ảnh hưởng bao gồm: hiệu suất của Pull Requests giảm; hiệu suất của Issues giảm; hiệu suất của Actions giảm; hiệu suất của Webhooks giảm; yêu cầu API gặp sự cố; GitHub Copilot giảm khả năng sử dụng.GitHub cho biết, đội ngũ đang tiếp tục điều tra nguyên nhân gốc rễ của sự kiện này và sẽ cập nhật trạng thái thêm khi có thêm thông tin.Tính đến thời điểm hiện tại, GitHub vẫn chưa công bố nguyên nhân cụ thể của sự cố này, cũng như không cho biết liệu có liên quan đến sự cố an ninh hay không. Sự cố dịch vụ này có thể ảnh hưởng đến các nhà phát triển và người dùng doanh nghiệp phụ thuộc vào GitHub để lưu trữ mã, triển khai tích hợp liên tục và phát triển hỗ trợ AI.

ChainCatcher thông báo, theo thông cáo từ tài khoản X chính thức của Qubic (@Qubic), tổ chức GitHub của Qubic đã xảy ra sự cố bảo mật vào ngày 13 tháng 7, một tài khoản bị xâm nhập đã truy cập vào kho mã và lấy thông tin nhạy cảm, chính thức đã can thiệp xử lý.Chính thức khuyến nghị các người dùng sau đây ngay lập tức hành động: Người bảo vệ mạng (Network Guardian) nên ngay lập tức thay đổi seed; Người dùng ví Web nếu đã mở khóa ví trong khoảng thời gian từ 03:00 đến 10:00 UTC hôm đó, hãy chuyển sang danh tính mới; nếu không chắc chắn về thời gian mở khóa lần cuối, cũng khuyến nghị chuyển đổi; Các nhà phát triển nên tạm ngừng kéo hoặc triển khai mã từ kho mã Qubic cho đến khi chính thức xác nhận hoàn thành kiểm toán.Chính thức cho biết, chi tiết đầy đủ và cập nhật tiếp theo sẽ được công bố trên kênh Discord chính thức, nhắc nhở người dùng không nên tin tưởng thông tin từ các kênh không chính thức, và cảnh báo bất kỳ ai không được yêu cầu seed của người dùng vì bất kỳ lý do gì. Báo cáo xử lý sự cố sẽ được công bố sau khi hoàn tất xử lý.

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.

According to GoPlus monitoring, the hacker group TeamPCP claims to have obtained the source code from about 4,000 private repositories within GitHub and is selling it for $50,000 on underground forums, offering sample verification. If no one buys it, this batch of data may be publicly released for free later.Previously, GitHub officials confirmed that they are investigating the issue of "unauthorized access to internal repositories," suspecting that malicious VS Code/AI Coding plugins were installed on GitHub employee devices.

According to the threat intelligence released by Slow Fog, several high-frequency npm packages including AntV and Echarts-for-react, as well as the Python SDK durabletask, have recently been targeted by the Mini Shai-Hulud "mini sandworm" supply chain attack. The npm account atool was compromised, and the attacker automatically published 637 malicious versions within 22 minutes, affecting 317 packages. The attacker continuously uploaded durabletask versions 1.4.1, 1.4.2, and 1.4.3 within 35 minutes, bypassing normal release controls and impersonating an official Microsoft release.The large-scale leak of GitHub tokens and the ransomware attack on Grafana Labs are likely related to this supply chain attack. Affected components include high-frequency components such as AntV and Echarts-for-react in the npm ecosystem, as well as Python packages durabletask 1.4.1, 1.4.2, and 1.4.3. Attackers can steal cloud and local credentials, gain unauthorized access to internal repositories and sensitive cloud infrastructure, move laterally to developer machines and CI/CD pipelines, sell and exploit leaked GitHub tokens, and implement ransom and data leak threats.Slow Fog recommends immediately rotating all exposed credentials, replacing affected packages, isolating potentially infected systems, and implementing strict dependency review policies. Previously, it was reported that the "mini sandworm" worm had recently completed widespread infection in open-source code repositories, and developers should be vigilant in checking for issues.

GitHub has updated the details of the investigation into the unauthorized access incident of its internal repositories: GitHub detected and contained an incident yesterday involving an employee's device being compromised, which involved a maliciously implanted VS Code extension. GitHub removed the malicious extension, isolated the affected terminals, and immediately initiated an incident response. Current assessments show that only GitHub's internal repositories experienced data exfiltration, and the approximately 3,800 repositories claimed by the attackers are roughly consistent with the investigation results. GitHub has prioritized rotating critical credentials, is analyzing logs, verifying credential rotations, and monitoring subsequent activities, with a complete report to be released after the investigation is concluded.Additionally, Slow Mist's Chief Information Security Officer 23pds commented on this incident, stating: "By analyzing leaks from cybercrime forums, hackers may have used Anthropic's Mythos security AI to precisely breach GitHub's defenses and steal information from about 4,000 core internal repositories: including the source code for Copilot, the algorithms for CodeQL, the Actions runtime, and the entire billing system. Further analysis of this code could lead to subsequent attacks, having a profound security impact on the integration of the open-source community."

In response to the unauthorized access event of the internal code repository disclosed by GitHub, Zhao Changpeng reminded, "If the code contains an API Key, even if it is in a private repository, it should be reviewed and replaced immediately."

GitHub has officially stated that it is investigating an unauthorized access incident involving its internal code repository. GitHub claims that there is currently no evidence to suggest that customer data stored in enterprise, organization, or code repositories outside the GitHub platform has been affected, but the company is continuously monitoring its infrastructure to prevent further abnormal activities.GitHub stated that if it is later confirmed that user data or services are affected, it will notify customers through existing incident response and notification channels.

The open-source data visualization tool Grafana stated on platform X that it recently discovered an unauthorized attacker had obtained a token that could access the Grafana Labs GitHub environment and used it to download the code repository.An investigation confirmed that this incident did not involve customer data or personal information leakage, and no impact on customer systems or business operations was found. After the incident, forensic analysis was immediately initiated, and it is believed that the source of the credential leak has been identified. Additional security measures have also been deployed to strengthen environmental protection.Furthermore, Grafana disclosed that the attacker attempted to demand a ransom to prevent the code repository from being made public, but the company ultimately decided to refuse to pay the ransom and will release more information about the incident review after the investigation is completed.

Tencent's PR Director Zhang Jun stated today that on March 30, the WeChat Work CLI open-source project was launched on the GitHub community, opening up seven core product capabilities including messaging, scheduling, documents, smart forms, meetings, to-do lists, and contacts, supporting mainstream AIAgents (such as ClaudeCode, Codex, WorkBuddy, QClaw, etc.) for invocation.Developers can leverage these capabilities to enable AIAgents to understand and utilize WeChat Work's features in a more natural way, quickly developing AI applications that are more aligned with everyday office scenarios.

According to market news, the security platform OX Security has disclosed that the developers of the AI agent project OpenClaw are becoming targets of cryptocurrency phishing activities.Attackers create fake GitHub accounts, initiate topics in repositories controlled by them, and @ dozens of developers, claiming they have won a $5000 CLAW token reward, leading them to a clone website that is almost identical to openclaw.ai. This phishing site includes a "Connect Wallet" button, aimed at stealing the assets of connected wallets. Malicious code is hidden in deeply obfuscated JavaScript files, featuring a "nuke" function that clears browser local storage data to hinder forensic analysis, and encodes information such as wallet addresses and transaction values to send back to the C2 server. Researchers identified a suspected cryptocurrency wallet address used to receive stolen funds. The related accounts were created last week and deleted within hours, with no confirmed victims at this time. OpenClaw has become a target for scammers due to its high visibility, and its Discord community has previously encountered a large amount of cryptocurrency spam. Earlier reports indicated that OpenClaw's founder warned to be cautious of cryptocurrency scam emails sent in the name of OpenClaw.

OpenClaw founder Peter Steinberger criticized the GitHub security vulnerability reporting process for multiple issues. He pointed out that currently, vulnerability reports are only accessible to administrators, making it difficult for teams to effectively distribute and collaborate on handling them.In addition, GitHub's API functionality for vulnerability reporting is insufficient, as it cannot read or post comments through automated agents, which limits the automation capabilities of the security response process. Peter Steinberger also specifically noted that the current vulnerability reports are filled with a large amount of low-quality AI-generated content, requiring hours to sift through, further increasing the burden of security handling work.

Pump.fun announces the launch of the GitHub creator fee sharing feature. Users can now allocate creator fees to any GitHub account through the Pump.fun mobile app. More social features are coming soon.

ClawdBot (now renamed Moltbot) founder Peter Steinberger posted on social media that the issue of his GitHub account being hijacked has been resolved, and this issue only affected personal accounts, not organizational accounts. He specifically reminded users to be wary of about 20 impersonating X scam accounts.

According to a report by The Paper, it has recently been reported that Tencent has officially sent a complaint letter to GitHub (the world's largest code hosting and collaboration platform), requesting the removal of a batch of open-source projects that "allow users to export or analyze their WeChat chat records." Among them, some project leaders who are more concerned have publicly stated that, under legal pressure, the projects have been forced to cease maintenance.In response, Tencent stated that some open-source projects that read WeChat chat records have cracked the local database keys through reverse engineering of the WeChat client, bypassing the encryption measures of the WeChat client, which threatens the data privacy and client security of users and third parties, and can easily be exploited by black and gray industries.