How CipherDrive Handles Malware and Dangerous Files

CipherDrive™ is not intended to be used to store, distribute, conceal, or operate malware, ransomware, phishing infrastructure, or other malicious files.

Malware checks can happen before encryption

Where applicable, the Risk Assessment Engine may evaluate a file before client-side encryption and generate technical signals such as:

cryptographic hashes;
file signatures;
malware indicators;
known-content matches;
risk scores;
other safety metadata.

These signals can be compared against trusted malware, anti-abuse, or security systems.

What happens if malware is detected?

Depending on the severity and confidence of the signal, Ackaia may:

block the upload;
prevent storage;
disable a Public Link;
restrict sharing;
preserve relevant technical records;
restrict or suspend the account;
terminate accounts involved in serious or repeated abuse;
cooperate with lawful security or legal processes where appropriate.

What if malware is reported after the file is stored?

Ackaia may act on information available after storage, including:

Public Link reports;
object and transfer metadata;
risk signals generated during applicable processing;
security reports;
claimant evidence;
account activity;
law-enforcement or legal notices.

Ackaia can disable distribution or restrict an account without necessarily decrypting the underlying stored file.

Does Ackaia scan every encrypted file after upload?

The published zero-knowledge architecture does not rely on Ackaia decrypting all stored files for server-side malware scanning.

Safety controls instead operate at disclosed pre-encryption boundaries and through available metadata, link activity, reports, technical indicators, and enforcement systems.

Why doesn't Ackaia publish malware-detection thresholds?

Detailed detection thresholds, private signatures, bypass conditions, and internal evasion logic are security-sensitive.

Publishing them could make the platform easier to abuse and weaken protection for users and infrastructure.

What if a legitimate file is mistakenly flagged?

False positives are possible in any automated detection system.

If the product provides an appeal or review path, use it and provide the relevant error message, object reference, time, and non-secret context explaining why you believe the detection is incorrect.

Do not repeatedly modify or repackage a blocked file to test ways around the detection system.

Downloaded files can still be dangerous

Zero-knowledge encryption does not make a malicious file safe to open.

If you receive a suspicious CipherDrive share:

do not run unknown executables;
do not disable security software to open the file;
verify the sender through a trusted channel;
use appropriate endpoint-security tools;
report clearly malicious Public Links to Ackaia.

Encryption protects confidentiality; it does not certify that a file is harmless.