Key facts
- If macOS says cpverify will damage your computer, do not bypass it.
- Cancel the alert.
- Identify the source.
If macOS says “cpverify” will damage your computer, do not force the file to open. Move the installer or app to the Trash, confirm whether it came from an official CryptoPro package, and replace the old software with a current package from the official CryptoPro download page. The warning is more serious than the separate “Apple cannot check it for malicious software” message.
Do not bypass this exact alert: Apple says the “will damage your computer” message can appear when software contains malicious content or when its authorization has been revoked. A familiar filename alone does not prove that the file on your Mac is safe.
Quick answer: what to do with cpverify
- Cancel the alert. Do not use Open Anyway, Terminal commands, or security-setting changes to force the blocked item to run.
- Identify the source. Check whether the alert appeared while opening a CryptoPro installer, at login, in a browser, or without any action from you.
- Remove the downloaded copy. If the warning came from a new disk image, package, or archive, eject it and move the downloaded file to the Trash.
- Update or remove the old CryptoPro installation. Use the current package and instructions from CryptoPro, or ask your organization's administrator to handle a managed Mac.
- Verify normal operation. Restart the Mac, update macOS, and test only the official service that requires the cryptographic software.
If you did not intentionally install CryptoPro, cannot identify the file's origin, or continue to see the alert after removing the downloaded package, treat the item as untrusted and follow the investigation steps below.
What is cpverify on a Mac?
cpverify is a filename associated with CryptoPro software and signed-package verification. CryptoPro's current download page refers to an updated cpverify utility used when checking its signed distributions. That association explains why the name can appear during a CryptoPro CSP installation or update.
The name is not a security verdict. Any file can be renamed, an old legitimate component can have a revoked authorization, and a download can be altered or corrupted. You need to establish the file's source, the package it belongs to, and whether the vendor currently distributes that version.
Think about what happened immediately before the alert:
- If it appeared while opening an old CryptoPro installer, the package may no longer pass current macOS security checks.
- If it appeared after a macOS or security update, the new checks may have detected a component that was already present.
- If it appeared after downloading a file from a forum, mirror, message, or advertisement, delete that download and use only the vendor's official page.
- If it appeared unexpectedly at login, identify the associated application before removing system components at random.
Which macOS warning did you see?
Similar-looking macOS alerts do not mean the same thing. Match the wording before following any instructions.
| Alert wording | What it can mean | Safe response |
|---|---|---|
| “cpverify” will damage your computer | Apple's checks consider the item harmful, altered, or covered by a revoked authorization. | Do not open it. Remove the downloaded copy and replace or remove the related software through official channels. |
| Apple cannot check it for malicious software | The software was not notarized in a way macOS can verify. | Open only if you deliberately obtained the exact file from a trusted source and the developer's current instructions support it. |
| Cannot be opened because the developer cannot be verified | The developer identity is not accepted by Gatekeeper. | Return to the official source and verify the current package. Do not treat the filename as proof. |
| The app is damaged and cannot be opened | The app may be corrupted, modified, or otherwise fail macOS validation. | Delete that copy and download a fresh current version from the developer. |
Instructions that tell you to right-click and select Open are sometimes relevant to an identified, trusted, non-notarized app. They are not an appropriate response to the exact “will damage your computer” warning.
Immediate safety steps
- Take a screenshot of the complete alert and note the time it appeared.
- Cancel the dialog. Do not enter an administrator password and do not approve new privacy permissions.
- Open Finder and check Downloads for the disk image, package, or archive you just obtained. Move an untrusted download to the Trash and eject its mounted disk image.
- Open System Settings, choose General, then Software Update, and install supported macOS security updates.
- Restart the Mac. Apple's built-in XProtect protections update automatically and block known malware independently of a traditional antivirus interface.
- If the alert returns, record which app was open and which action triggered it. A reproducible trigger helps distinguish an old CryptoPro component from an unrelated file using the same name.
Do not erase certificate containers, token data, or work documents while diagnosing the warning. If the Mac is used for electronic signatures, banking, reporting, or government portals, confirm the backup and recovery process with the responsible administrator first.
Update CryptoPro from the official source
Use the official CryptoPro CSP download page. It lists current release families, operating-system packages, dates, and checksums. Access to some downloads may require a CryptoPro account. Avoid old direct package links because they can bypass the current release notes and can remain online after the recommended build changes.
| Decision | What to check | Why it matters |
|---|---|---|
| Release family | Whether your organization requires a certified release or has approved a preliminary release | The newest visible number is not automatically the correct compliance choice. |
| Mac architecture | Apple silicon, Intel, or a vendor-provided universal package | The package must support the hardware and macOS version. |
| Checksum | Compare the complete published checksum with the downloaded file when the vendor provides one | A matching checksum helps confirm that the download was not changed in transit. |
| Plug-in requirement | Whether the target portal also needs the CryptoPro browser plug-in | CSP and browser integration are related but not identical components. |
CryptoPro's documentation says the browser plug-in is included in CSP beginning with version 5.0.12600. Do not add unrelated token packages unless your token vendor or organization specifically requires them. Old advice to install every available ESMART component can create conflicts on systems that do not use that hardware.
Remove an old CryptoPro version safely
If the old installation keeps launching the blocked component, use the vendor's own removal path instead of deleting files throughout Library folders. CryptoPro's macOS documentation points to uninstall_csp.app for removal.
- Close browsers, signing applications, and any service that uses CryptoPro.
- Confirm how your certificates and private-key containers are stored. Do not remove or reformat a token, smart card, or container as part of a generic cleanup.
- Locate the official CryptoPro uninstaller supplied with the installed package or documented by your organization.
- Run the uninstaller with the required administrator approval.
- Restart the Mac before installing the approved replacement package.
- Download the replacement directly from CryptoPro, verify the release and checksum, and follow the package instructions.
If this is a work Mac, stop before removal unless you are authorized to change the cryptographic provider. Removing a working certified configuration can interrupt access to business systems even when the security alert itself needs attention.
Why the warning can appear after an update
A macOS update does not necessarily install cpverify. It can change the security data or checks used against software that was already on the Mac. Apple explains that Gatekeeper checks downloaded software for an accepted developer signature, notarization, and signs of alteration. Apple can also issue revocation information for software that should no longer be trusted.
The same timing can have other causes. A browser extension may have updated, an old login item may have launched for the first time in months, or a newly downloaded installer may have used a familiar name. That is why the trigger and source are more useful than speculation about the filename.
What not to do
- Do not disable Gatekeeper, XProtect, System Integrity Protection, or automatic security updates.
- Do not remove quarantine attributes or execute an unknown binary from Terminal.
- Do not download a repacked CryptoPro installer from a forum, file-sharing site, cloud folder, or software mirror.
- Do not follow an old direct download link solely because its version once worked.
- Do not approve Full Disk Access, Accessibility, screen recording, or administrator rights without a current vendor or organizational reason.
- Do not delete certificate containers or initialize a hardware token during troubleshooting.
These shortcuts can silence a useful warning without proving the file is safe. They can also make later diagnosis harder by removing the evidence that identifies the original package.
Verify the replacement installation
- Restart the Mac and confirm that the damage warning no longer appears at login.
- Open only the service that actually requires CryptoPro and repeat the normal sign-in or signing flow.
- Confirm that the intended certificate is visible without importing duplicate or unknown certificates.
- Check the installed CryptoPro version against the release your organization approved.
- Test the required browser integration on the official target portal. Do not use a random certificate test page.
- Keep the package version, source URL, checksum, and installation date in your support record.
A successful installer message is not the entire test. The real result is that the required signed workflow works, the security alert is gone, and no unexpected privileges or components were added.
What to do on a managed work Mac
Send your IT or security team the alert screenshot, macOS version, Mac model, CryptoPro version if known, the portal you were using, and the time the issue began. Ask which CSP release and browser combination the organization supports. A managed configuration may depend on certificate policies, smart-card drivers, mobile-device management, or a certified software build that differs from a home user's setup.
Do not work around a managed security policy. The administrator may need to replace the package centrally, remove an outdated login item, or confirm that the vendor release is approved for the organization's compliance requirements.
Troubleshooting by symptom
| Symptom | Likely next check | Action |
|---|---|---|
| Alert appears only when opening an old installer | Download date and source | Delete that copy and obtain the current approved package from CryptoPro. |
| Alert appears at every login | Related login item or background component | Use the official uninstaller or ask IT to identify the managed component. |
| CryptoPro installs but the portal cannot see certificates | Browser plug-in, certificate store, and token driver requirements | Follow the portal and organization's current compatibility instructions. |
| A new download has the same warning | Official release, checksum, and supported macOS version | Stop retrying. Contact CryptoPro or your administrator with the exact package details. |
| You never installed CryptoPro | File location, download history, and the process that triggered the alert | Treat the item as untrusted, remove the download, update macOS, and request security help if it returns. |
Frequently asked questions
Is cpverify malware?
The filename is associated with a CryptoPro verification utility, but the name alone cannot prove that a particular file is legitimate. If macOS says it will damage the computer, do not run that copy. Verify the package, source, checksum, and current vendor guidance.
Can I delete cpverify?
You can delete an untrusted downloaded installer or archive. For a component inside an installed CryptoPro product, use the official uninstaller or your organization's management process instead of deleting one binary. Partial removal can leave browser or signing workflows broken.
Why did the warning appear after a macOS update?
The update may have introduced newer security data or checks that detected an existing component. It may also be a coincidence with an app, browser extension, or login item update. Record the trigger and replace the old package through the official channel.
Should I click Open Anyway?
Not for the exact “will damage your computer” warning. Apple's controlled override is intended for software you are certain came from a trustworthy source, and it does not turn a harmful, altered, or revoked file into a safe one.
How do I reinstall CryptoPro on a Mac?
Confirm certificate and token requirements, remove the old build with CryptoPro's official uninstaller when necessary, restart, then obtain the approved macOS package from the CryptoPro download page. Verify the release, architecture, and published checksum before installation.
Does the warning mean my Mac is infected?
Not by itself. The warning means macOS blocked an item it considers unsafe or no longer authorized. Cancel the alert, remove the untrusted copy, update macOS, and investigate the trigger. Repeated unexpected alerts or other suspicious behavior justify help from an administrator or security professional.
Sources and scope
This guide was reviewed on October 14, 2026 against Apple's guidance on opening Mac apps safely and macOS malware protection, the official CryptoPro CSP download page, CryptoPro's macOS installation and removal documentation, and its browser plug-in documentation. Available releases, checksums, supported macOS versions, certified configurations, and portal requirements can change. The current vendor and organization instructions take priority.
