You received an OSF security notice, or you are unsure whether your research account details were involved.
Fast answer: As of November 1, 2026, OSF says passwords were not accessed and users do not need to take action because of this incident alone. Don’t change every password or replace your email address solely on that basis; act if you have separate evidence of password reuse, suspicious account activity, or another exposure. OSF’s incident notice sets those boundaries.
This is for researchers and students who use OSF for projects, registrations, or preprints, and for anyone concerned about email privacy. The key distinction is between what the incident could expose and what happened to a particular account.
Last updated: November 1, 2026. Incident details checked against the OSF notice updated October 29, 2026, and OSF’s account guidance.
Confirmed information in the OSF notice
The OSF security incident notice describes information that could be accessed. It confirms that names, OSF user IDs, email addresses, and some project, registration, and preprint metadata were within the scope of the incident. That is an incident-wide description, not proof that every person’s individual record was accessed. For your specific situation, use any direct notice you received and subsequent official OSF updates as the reference points.
| Information type | What OSF says | What that means for your decision |
|---|---|---|
| Name, OSF user ID, and email address | These could be accessed. | Treat your address and account identifier as potentially exposed; do not assume your email account itself was taken over. |
| Project, registration, and preprint metadata | Some metadata could be accessed. | Details associated with research work may carry privacy implications even when file contents are not involved. |
| Password | OSF says passwords were not accessed. | The notice alone does not provide a reason to change your password. |
| Files in private projects | OSF says they were not viewed or downloaded. | Do not describe the incident as a confirmed leak of private project file contents. |
The distinction between metadata and content matters. A project title, description, or identifier can reveal information about research activity without being the same as a document, dataset, or other project file. OSF’s notice separates these categories; users should do the same when assessing research project metadata privacy.
Did the incident involve email addresses and project files? OSF confirms that email addresses and some project-related metadata could be accessed. It also says that files in private projects were not viewed or downloaded. The confirmed scope therefore includes contact and metadata exposure, but does not establish that private project files were accessed.
That distinction does not prove that every OSF record was accessed, nor does it establish that no individual account has other risks. The official notice describes the incident’s scope; it is not a personalized audit of each user’s account.
Password-change decision
The phrase “password not accessed” is specific to the information OSF confirmed in this incident. It is not a guarantee that an account has never faced a different threat. Make the password decision based on separate evidence, not on the email-address exposure alone.
Does the OSF 2026 security incident mean you need to change your password? No—not solely because of this event, based on the notice available as of November 1, 2026. OSF says passwords were not accessed and that users do not need to take action. If the same password is used elsewhere, or there is an account alert or suspicious sign-in, handle that separate risk.
Use this decision path:
- If your OSF password is unique and there are no suspicious account signs: Keep using it. There is no incident-specific reason in the OSF notice to reset it.
- If you reused the OSF password on another service: Change it on the other service, and on OSF too if that shared password is still active. Set a different password for each account. The Federal Trade Commission’s password guidance explains why unique passwords help limit the effect of a breach elsewhere.
- If you received an unexpected sign-in alert or see account activity you cannot explain: Treat that as independent evidence. Secure the account through the official OSF account entry point, review its settings, and contact OSF support through the official help channel.
- If a password was exposed in a separate breach: Change that password wherever it was used. Do not assume the OSF incident caused the other exposure.
- If you have no direct notice and no separate warning: Don’t treat uncertainty as proof either way. Follow official OSF updates rather than changing your address or credentials on speculation.
OSF also provides guidance on profile and account settings. For accounts that support it, enable two-factor authentication. The FTC’s explanation of two-factor authentication describes it as an additional sign-in check, not a substitute for a unique password.
Does not receiving an OSF notice mean your account was unaffected? Not by itself. The public notice describes information that could be accessed, but the absence of a message does not prove whether a particular user’s record was involved. Use a personal notice or a later OSF statement to confirm individual details; don’t infer a definite yes or no from an empty inbox.
Independent notice and account checks
An incident-related message can be genuine, misleading, or unrelated to the event. Avoid making a security decision based only on the sender display name, logo, or a link inside an email. The CISA phishing and spoofing tip sheet recommends checking suspicious messages carefully rather than trusting their appearance.
Use this sequence:
- Open OSF independently. Enter the known OSF address yourself or use a saved bookmark. Find the incident notice through OSF’s official help pages instead of starting from a link in an unexpected message.
- Compare the message with the public notice. Check whether it describes the same confirmed boundaries: email addresses and some metadata could be accessed, while passwords and private-project files were not accessed as stated in the notice.
- Don’t send credentials by reply. A request to disclose your password, recovery codes, or other sign-in secrets is not a safe way to verify an incident notice.
- Check the account through the official route. Review account access and profile settings from OSF, not from a link whose destination you have not verified.
- Separate event claims from account symptoms. A password reset notice you did not request, an unfamiliar sign-in, or a separate breach alert needs its own investigation; it is not automatically explained by this incident.
- Ask OSF through its official support channel. If the message conflicts with the public notice or you need account-specific clarification, contact OSF using its official help center.
A legitimate-looking email is not individual proof that your record was accessed. Conversely, not receiving an email is not proof that it was not. Keep the public incident scope and any account-specific evidence separate.
This process helps avoid two opposite mistakes: treating a broad incident notice as proof of account takeover, and treating the stated password boundary as proof that an account can never have another issue.
Email-change limits
Replacing an address can affect where future messages arrive. It cannot erase information already included in an incident, retrieve a copy of data that was accessed, or reverse the exposure of an existing email address or project metadata.
| Possible action | Helps with | Does not do |
|---|---|---|
| Change your OSF account email | Moves future account communication to an address you control, if OSF accepts the change and you can complete its account process. | Retract an address or metadata that may already have been accessed. |
| Change a reused password | Reduces risk from that reused credential on accounts where it was active. | Resolve exposure of your email address or research metadata. |
| Use a separate address for a future low-trust signup | Keeps that signup from requiring your primary address, depending on the service and recovery requirements. | Make an existing OSF account anonymous or undo past access. |
| Review OSF account settings and contact support | Helps address account-specific questions or signs of access trouble. | Change the confirmed scope of the incident. |
Can changing your email take back information exposed in the OSF incident? No. An address change can affect future account communication, but it cannot retract an address or metadata that may already have been accessed. Change it only if there is a separate reason, such as loss of access to the old mailbox, an address you no longer control, or a planned account update that OSF supports.
For an active research account, long-term access and recovery matter more than using an address that is disposable. Before changing an OSF email, make sure you can access the replacement mailbox and follow OSF’s official account process. A temporary inbox is not a recovery plan for a project account that may need to be accessed later.
Address separation for future signups
The incident and future signup habits are separate problems. Address separation can reduce how often a low-trust website receives your primary email in the future. It does not prevent a service from exposing an address you already gave it, and it does not guarantee anonymity.
Choose an address based on how long you need the account:
- For OSF and other continuing research accounts: Use a mailbox you control over the long term. You may need it for account recovery, project notices, collaboration, or later access.
- For a low-trust site you may not use again: Consider a separate address or a temporary email option if the site’s purpose and recovery rules make that appropriate.
- For a service that requires replies or ongoing correspondence: Use an address that supports the communication and recovery you need. Don’t choose a one-off inbox if losing access could lock you out.
- For sensitive research or personal data: Check what the service requests and what its privacy terms say before registering. Address separation is only one control; it does not protect the contents you submit.
The guide to disposable and secondary email can help distinguish a short-lived address from a separate mailbox intended for continued use. For signup-specific choices, see how to reduce primary email exposure when registering. These are decisions for future registrations, not remedies for the OSF incident.
This is also why the event should not be turned into a blanket instruction to replace every address. A replacement can create recovery work without changing what was already exposed. Start with the service’s future access needs, then decide whether a separate address is suitable for that particular signup.
This week’s account review
This week’s recommended action: Check the OSF notice from an official entry point, keep your password if the only concern is this incident, and investigate only independent warning signs.
For a project manager overseeing research accounts, record the decision in the same way as any account-risk review: what OSF confirmed, what remains unknown for an individual record, and what evidence would trigger a separate response. Don’t label the matter “password compromised” when the notice says passwords were not accessed. Don’t label project files “leaked” when OSF says private project files were not viewed or downloaded.
If the only issue is possible email-address exposure, changing the address is a forward-looking choice—not incident rollback. If the password was reused, an account alert appeared, or another breach notice identifies the credential, respond to that specific evidence. Keep the OSF account on a mailbox that remains accessible for recovery and research communication.
For future one-off registrations, QuickTMP’s temporary email service can provide a separate address rather than exposing a primary mailbox to a low-trust signup. That can help keep signup-related mail away from the main inbox, but it cannot reverse the OSF incident, guarantee anonymity, or replace a lasting recovery address for an important research account.
Create first, then extend with the task
Open a temporary inbox and watch the remaining time and confirmation after each extension.