ChatGPT’s new feature could give infostealers a map of your Mac activity
Overview
OpenAI's new Computer History feature for ChatGPT and Codex is stirring up concerns regarding user privacy and security. This feature creates a timeline of a user's activities on their Mac, summarizing app usage and website visits. While it aims to enhance user experience by recalling recent activities, it raises alarms that this detailed mapping could be exploited by malicious actors, particularly infostealers. Users could unknowingly expose sensitive information, making them vulnerable to targeted attacks. The implications of this feature stress the need for careful consideration of user data handling and privacy measures.
Key Takeaways
- Affected Systems: Mac computers using ChatGPT and Codex
- Action Required: Users should review privacy settings and consider limiting the feature's access to sensitive data.
- Timeline: Newly disclosed
Original Article Summary
OpenAI’s new Computer History feature turns recent Mac computer activity into memories ChatGPT and Codex can use, and it’s raising questions about privacy and security along the way. Computer History (Source: OpenAI) What Computer History does Computer History builds a timeline out of everyday computer use, grouping activity into summaries and noting which apps and websites contributed to each one. “Computer History replaces the earlier Chronicle research preview, but it is a rebuilt system rather … More → The post ChatGPT’s new feature could give infostealers a map of your Mac activity appeared first on Help Net Security.
Impact
Mac computers using ChatGPT and Codex
Exploitation Status
The exploitation status is currently unknown. Monitor vendor advisories and security bulletins for updates.
Timeline
Newly disclosed
Remediation
Users should review privacy settings and consider limiting the feature's access to sensitive data.
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.