Software and security
The Claude Code extension incident: what small businesses should check
Understand the malicious Claude Code packages distributed through Cursor, what was unaffected, and what to ask your developer about access and remediation.
A developer’s computer can hold the access needed to maintain your website, deploy an app or connect to business systems. That makes the tools installed on it relevant to the business owner, even when someone else handles development. The reported Claude Code extension incident is a reason to check that access carefully. The first step is to establish which package was installed and where it came from.
What happened?
The affected packages came through Cursor
Cursor’s security notice identifies malicious copies of anthropic.claude-code versions 2.1.312 and 2.1.313, distributed through its extension marketplace for macOS and Windows on 29 October 2026. The reported window was approximately 2:27 am to 1:35 pm Pacific Daylight Time. Cursor says it removed the packages and took the attacker’s server offline.
Cursor security noticeReviewed 31 October 2026
Microsoft distinguishes the unaffected distributions
The distinction between marketplaces matters. Microsoft says the malicious packages were never distributed through Microsoft’s Visual Studio Marketplace or the official Claude Code npm distribution. It also reports that Anthropic confirmed its own systems were not compromised. Calling this a general “Claude vulnerability in VS Code” would therefore misstate the evidence available on 31 October.
Microsoft Security’s investigationReviewed 31 October 2026
Why removing the extension may not be enough
The payload could run before normal activation
Phorion’s analysis describes injected code that ran when the extension module loaded, before its normal activation callback. The payload attempted to establish persistent remote access using SSH, a protocol commonly used for remote administration. Some of its changes were made outside the extension itself.
Phorion’s technical advisoryReviewed 31 October 2026
Attempted access is different from confirmed access
Successful remote access was not automatic. Microsoft says it depended on privileges and configuration, and that collected environment-variable names were not the secret values stored in them. These findings do not establish that every affected computer was remotely accessed or that every credential was stolen. They also do not establish that an exposed computer is clean.
Microsoft’s analysisReviewed 31 October 2026
Failed SSH setup could still leave changes behind
Phorion found that a flaw in the macOS setup logic could prevent SSH from being enabled while still leaving keys and persistence behind. Its updated advisory includes both affected versions. That is why a reassuring symptom, such as an extension continuing to work normally, is not a useful substitute for investigation.
Phorion’s updated findingsReviewed 31 October 2026
What could this mean for your business?
Consider an illustrative online retailer whose developer maintains the shop and its inventory integration. The business needs to know whether an affected computer could access the code repository, hosting account or integration credentials. It should not assume that customer data was exposed simply because the developer uses Cursor.
Our recommendation is to ask for a short written assessment: which devices were checked, which installation sources and versions were found, what business access those devices held, and what evidence supports the conclusion.
A response that only says “we updated Claude” leaves important questions unanswered. Equally, a headline is not enough reason to rebuild every device or rotate every business account without establishing the scope.
What can you do this week?
For potentially affected installations, use Cursor’s current notice as the starting point for a qualified IT or security review:
Use the current vendor response guidance
These steps summarise the vendors’ response guidance. Use the current advisories for platform-specific checks and have your IT provider review remediation scripts before running them.
Cursor’s response guidanceReviewed 31 October 2026
- Establish exposure. Check the marketplace source, affected versions and installation or update history against the incident window.
- Preserve evidence. Retain relevant installation records and security logs before cleanup, and investigate the published indicators.
- Contain affected devices. Isolate computers showing evidence of payload execution or backdoor installation.
- Complete remediation. Remove confirmed persistence and unauthorised access, and assess whether rebuilding is needed. Uninstalling alone may be insufficient.
- Review accessible accounts. Rotate affected credentials and revoke sessions from a trusted device, guided by the investigation.
Make developer access easier to manage
After any immediate investigation, review how development access is organised. Our suggested starting point is a simple inventory of approved extensions and their sources, named access to hosting and repositories, and a clear owner for responding to security notices.
Where practical, separate routine development from production administration and remove access that is no longer needed. Keep a record of who can revoke a deployment token or restore a service. These measures can make a future response more manageable; they do not guarantee that another incident cannot happen.
How Context Aware can help
We can help map the accounts and integrations behind your website or app, clarify who maintains them and turn findings into a practical maintenance plan. For suspected compromise, a qualified incident-response provider should lead the investigation and device cleanup.
If you are unsure who holds access to your website, we can help document the current setup and the questions to take to your developer or IT provider.
A note on the sources
Sources reviewed 31 October 2026. This article reflects Cursor’s notice, Microsoft’s investigation and Phorion’s updated advisory available at that time. The retail example is illustrative. Follow the linked notices for subsequent changes to the affected scope and remediation guidance.
Prepared by Context Aware with AI assistance and linked primary sources. Examples are illustrative. How we write our insights.