github

Slow Fog released a threat intelligence report stating that they recently received user feedback about a GitHub repository named sol-live, which disguises itself as a Solidity interview practice project. However, it hides commands in the .vscode/settings.json file to download and execute remote scripts, which may trigger malicious payloads when users start the project with custom terminal configurations.Slow Fog's analysis shows that the related malicious payloads can collect browser login databases, wallet extension storage, and macOS Keychain files. They also have the capability to scan and upload local files, execute remote commands, provide interactive Shell access, and monitor the clipboard. In macOS and Linux environments, the malicious terminal configuration must be actively initiated by the user to execute; the attack chain on Windows has not been confirmed due to issues with quote handling.

NetEase UU Remote has publicly released a third-party app integration protocol on GitHub, allowing developers to add a remote control entry to their iOS and Android applications. For example, to add a "Connect to Work Computer" button for an AI programming assistant, when users click it for the first time, they will be redirected to UU Remote to select and bind their Windows or Mac. After that, they can directly initiate remote control with another click, without having to repeatedly search for the device.Remote control supports full screen and picture-in-picture modes, allowing users to operate their computers through a floating window while using other apps on their phones. After leaving home, users can check if Claude Code or Codex on their home Mac has completed tasks, and they can directly invoke remote control from third-party applications. Developers can obtain connection results in windowed mode to determine if the device is offline or if the connection has failed.What has been opened is a cross-app invocation protocol, not the source code of the remote control engine, nor an interface for AI to automatically operate computers. Third-party applications still need to call the installed UU Remote client, and the actual remote control is completed by NetEase. Currently, the controlled devices only support Windows and macOS, and the mobile side must use UU Remote version 4.42.0 or later.

The free and open-source tool REA (Reverse Engineer Anything) saw its star count on GitHub rise from less than 10,000 on October 6 to over 100,000 by October 12, with more than 30,000 added in a single day on October 11. This tool integrates AI programming assistants like Claude Code and OpenAI Codex with professional reverse engineering suites like Ghidra, bridging the model context protocol MCP launched by Anthropic. Since its creation in April of this year, REA had long gone unnoticed; its readme file states that the tool does not claim to restore original source code or automatically clone applications, nor does it come with a decompiler.REA has been used for various reverse engineering attempts on software and games: players have made Spider-Man swing through Gotham City in "Batman: Arkham City," someone stuffed about 1,600 items from "Minecraft" into "Elden Ring" to battle Boss Malenia, and mod authors have brought firearms and menus from "Escape from Tarkov" into "The Elder Scrolls V: Skyrim." Old console exclusives are also breaking free from their platforms; in September, enthusiasts used open-source AI models and recompilation tools to bring "Fable 2," which had never been released on PC, to Windows, with AI completing the startup in about an hour, followed by a long manual fix; another developer has made "GTA 5" run natively and smoothly on iOS.

Market news shows that OpenAI and GitHub have won the copyright lawsuit regarding AI programming tools.

The Slow Fog security team recently disclosed the discovery of a malicious GitHub repository impersonating the "Qwen 3.8 27B local quantitative model." The repository claims that the model file should exceed 16GB, while the actual downloaded content is only about 487KB, containing disguised files, a LuaJIT interpreter, and obfuscated Lua scripts. Slow Fog emphasizes that the official Qwen project has not been compromised.Slow Fog's analysis indicates that after the malicious program runs, it will collect host information, capture the screen, and send it to the attacker's C2 server; when the hard-coded server fails, it will also read backup C2 addresses from contracts on the Polygon chain, allowing the attacker to rotate infrastructure through on-chain transactions.Subsequent payloads can steal browser login information, cookies, history, email, WinSCP, Steam credentials, as well as files and extension data related to cryptocurrency wallets. Slow Fog also found that at least 23 GitHub repositories and 29 similar compressed packages used the same Lua delivery chain.

The GitHub official status page shows that the platform is currently experiencing service disruptions, with multiple core functionalities experiencing decreased availability.According to the latest announcement, the error rate for GitHub's web interface and API requests reached about 20%, while the error rate for repository archive downloads and raw repository content downloads was around 50%. Additionally, SAML and OIDC authentication, SCIM, and Team Sync functionalities are also affected.Currently affected services include: decreased performance of Pull Requests; decreased performance of Issues; decreased performance of Actions; decreased performance of Webhooks; anomalies in API Requests; decreased availability of GitHub Copilot.GitHub stated that the team is continuously investigating the root cause of this incident and will provide further updates once more information is available.As of now, GitHub has not disclosed the specific cause of the outage, nor has it indicated whether it involves a security incident. This service disruption may affect developers and enterprise users who rely on GitHub for code hosting, continuous integration and deployment, and AI-assisted development.

According to an announcement from Qubic's official X account (@Qubic), a security incident occurred in the Qubic GitHub organization on July 13, where a compromised account accessed the code repository and extracted sensitive information. The official team has intervened to address the situation.The official team recommends that the following users take immediate action: Network Guardians should immediately rotate their seeds; Web wallet users who unlocked their wallets between 03:00 and 10:00 UTC on that day should migrate to a new identity; if unsure of the last unlock time, migration is also advised; developers should pause pulling or deploying code from the Qubic code repository until the official audit is confirmed to be completed.The official team stated that complete details and subsequent updates will be released on the official Discord channel, reminding users not to trust information from unofficial channels, and warning that no one should request user seeds for any reason. A post-incident report will be published after the situation is resolved.

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.