Apify confirms customer data viewed in November intrusion
Users who link GitHub to Apify must reconnect their accounts after tokens were revoked, and some stored data was viewed by the intruder.
Users who link GitHub to Apify must reconnect their accounts after tokens were revoked, and some stored data was viewed by the intruder.
Developers relying on Apify should check their integrations and re-enroll two-factor authentication while the investigation continues.
The safety of each workflow now depends largely on how its author configures write access and custom jobs.
Owners of installed modchips can no longer update or reflash their firmware, and future modders lose access to the code.
Users who clone repositories with submodules are exposed until they install Git 2.56.1 or a patched 2.50 to 2.55 release.
Withdrawing the code without repairing the underlying faults could leave the problems in place for anyone who already holds a copy.
Thousands of credentials have surfaced because a local settings file, meant to stay private, sometimes gets committed to public projects.
Pull requests become a running record that agents update on each push, with merges blocked until review findings are closed.
Pinned commits now run even when tags or branches move, but the lockfile does not vouch that those commits are safe.
Session cookies stolen by infostealer malware will no longer work from another machine on Chrome for macOS and Windows, once the staged rollout reaches a user.
The trust placed in signed OpenAI and Anthropic executables is what lets the Yoba campaign's malware slip past some security tools.
Attackers rotate the repositories quickly and clean up after infection, so checking the owner before any download matters more than usual.
Agent-opened pull requests now make up over 40% of activity, and GitHub has rebuilt parts of its backend to keep up.
Organisations running private repositories or GitHub Enterprise Server are not covered by GitHub's workflow hold, so they must check their own exposure.
Anyone who installed LiteLLM 1.107.0 from PyPI, Docker Hub or GHCR in the affected window may need to treat their credentials as exposed.
Operators running big self-hosted runner pools get tunable rate limits, concurrency and shutdown timing, plus lighter load on the Kubernetes API.
The hosting service will close after attackers reached its systems with leaked credentials and exposed data tied to 321,810 accounts.
The company has re-enabled release immutability after blocking the altered packages and tells affected users to clean systems and rotate secrets.
Developers can carry one Copilot task into the editor without starting over, keeping the same context as they review and change code.
GitHub is testing a physical shortcut layer for Copilot so developers can trigger common actions without leaving their workflow.
Maintainers can now get star trends in one request, while detailed user lists are limited to repo admins and collaborators.
GitHub made progress on moving production traffic and tightening failure handling, but recent incidents and a missed migration target show the work is not done.
The faster system lets generic secret detection run in push protection, so likely secrets can be caught before code is accepted.
The rewrite makes Copilot faster to embed in host apps and keeps an out-of-process option for setups that still need it.
The self-hosted runner tool is now generally available at no extra cost, but teams upgrading from the preview must take runners offline first.
The malware operation has resumed at scale, making it harder for GitHub takedowns to remove every copy at once.
GitHub is trying to catch more exposed credentials earlier as AI agents and push volume keep rising.
The benchmark is meant to make offline comparisons between code reviewers more useful for production decisions.
The findings show that secret leaks can stay exposed for years even where GitHub’s Push Protection reduces some new exposure.
The service gives agent builders a managed runtime and controlled tool access instead of making them assemble that layer themselves.
Open source taskflows built on GitHub’s AI agent have already exposed dozens of Android flaws in real apps.
New Git release tightens merge safety and boosts performance on large repos while shrinking storage footprints.
The campaign extends from tenant-wide resource wipes to direct hits on AI datasets and vector stores.
Teams that invoked the affected actions may need to check whether workflow-accessible credentials were exposed.
Kelley defends prioritizing human mentorship over AI code and says moving to Codeberg restored reliable CI for Zig.
Users and the agent can update a shared workspace as work progresses, then keep it for a project or personal reuse.
The campaign bypasses npm v12’s install-time checks and has already landed in projects via millions of downloads.