Search the evidence

Find the signal.

Search titles, impact clusters, countries, organizations and the full text of every analysis.

2 stories found

A broken wax seal on a paper package represents compromised software provenance.
SecurityGlobal+2 clusters01

The familiar AI name was not the security check.

A familiar name on an extension is not proof that the package came from the people you think it did. Cursor's notice makes that distinction unusually concrete. The company identified malicious versions 2.1.312 and 2.1.313 of Anthropic.claude-code in its own extension marketplace for Windows and macOS on October 29. Cursor says these versions were not developed by Anthropic and reports no evidence that the official distribution or other versions were affected. This is a software-delivery incident, not evidence that the Claude model decided to attack its users. According to the notice, the modified packages collected host information and attempted persistent remote access. Some actions were limited by privileges and implementation errors. That is a reason to describe the incident precisely, not a reason to skip checking an affected machine. Cursor removed the packages, rebuilt the marketplace and worked to disable the attacker's infrastructure. The immediate lesson is to use the vendor's affected-version and remediation guidance. Removing an extension alone may leave other changes behind; organizations should route affected systems through their incident-response process. The broader lesson is about where trust gets attached. We often recognize the model provider and stop asking how software reached our machine, who can update it, or what access an extension receives. Yet those are separate relationships with separate failure modes. A powerful coding assistant does not make software provenance an old-fashioned concern. It makes the path between a trusted brand and an executable package worth examining more carefully. Security work starts before the first prompt.

4 min
A person pauses with a key before opening a locked file cabinet beside a laptop.
PrivacyGlobal+2 clusters02

Apple says AI agents make Mac Full Disk Access too easy to grant

Apple has warned developers that Mac Full Disk Access can expose files, mail, messages and browsing history when apps use it beyond the narrow backup purposes for which the broad permission was designed. The company says it will introduce additional controls so granting that access requires very explicit user action, and it specifically names increasingly autonomous AI agents as a reason the stakes are rising. Apple has not announced a ship date or detailed the new interface, so it would be wrong to say the protection is already active. The real-world issue is not whether a permission dialog contains enough words. It is whether an ordinary person can understand that a single approval may let software inspect intimate records long after the immediate task ends. An agent adds another layer: it may choose files, chain tools or respond to untrusted material in ways a user did not individually authorize. Stronger consent can protect users and the people whose private messages are stored on their Macs, but a clumsy restriction could also disrupt legitimate backup and accessibility tools. The design test is granular, revocable permission with a clear purpose and duration, not simply a scarier all-or-nothing prompt. Apple now needs to show what developers must change, what users will see, and how the system will enforce the limit after someone clicks yes.

5 min