AU10TIX AnyDoc Authentication identifies tampered or forged documents


AU10TIX is enhancing its product suite with the launch of AnyDoc Authentication, a capability that exposes forged, tampered, or synthetic non-ID documents that may bypass traditional identity verification methods.

AnyDoc harnesses advanced AI, forensic forgery detection, and metadata analysis to empower businesses to detect document fraud, maintain regulatory compliance, and scale secure onboarding. This critical layer of protection supports a diverse range of document types, including utility bills, bank statements, tax filings, business licenses, and more.

As fraudsters shift their methods to exploit non-ID documents like utility bills, financial statements, and tax records, organizations must adopt smarter, more adaptive tools to stay ahead of the curve. AnyDoc Authentication performs over 150 AI-driven forgery tests, validates embedded metadata for consistency, and processes documents in just 5–20 seconds, delivering fraud detection at up to 99.99% accuracy with 90% fewer manual reviews.

Key features include:

  • AI-powered forgery detection: Spots manipulated text, font inconsistencies, synthetic content, and structure anomalies
  • Metadata integrity validation: Cross-checks timestamps, issuing bodies, and creation trails
  • Multi-Document versatility: Works with utility bills, tax forms, business licenses, contracts, and more
  • Format-anostic: Verifies both PDFs and image files with equal accuracy
  • Real-time classification and processing: classifies documents within three seconds and processes them in 5-20 seconds for instant decision-making.

“Effective fraud prevention demands more than identity verification; it is built on ensuring the authenticity of every supporting document,” said Yair Tal, CEO of AU10TIX. “With AnyDoc Authentication, we are redefining the standard for non-ID document authentication, enabling organizations to detect fraud at its source, before it infiltrates their systems. This is more than just a security feature; it’s a critical layer of defense that fosters trust, mitigates risk, and closes the gaps fraudsters aim to exploit.”

AnyDoc Authentication is tailored to support KYC, KYB, and AML regulatory frameworks. It cross-references extracted document data with trusted third-party sources, minimizing false positives, enhancing compliance workflows, and reducing the risk of synthetic and deepfake document attacks.

Optimized for high-risk, high-volume sectors, AnyDoc Authentication brings significant advantages across multiple industries:

  • Finance and banking: Prevent fraud in loan applications, tax filings, and financial statements.
  • Corporate compliance and KYB: Authenticate supplier contracts, business registrations, and tax records
  • Education: Validate enrollment documents, scholarships, and institutional partnerships
  • Travel & hospitality: Verify address proofs, travel documentation, and guest onboarding materials
  • Crypto and payments: Detect fraudulent merchant registrations and authenticate cross-border KYC submissions
  • Healthcare: Authenticate insurance documents, prescriptions, and provider credentials

AU10TIX’s AnyDoc Authentication is now available for businesses seeking real-time fraud detection strategies and compliance frameworks.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Researchers found one-click RCE in ASUS’s pre-installed software DriverHub

Pierluigi Paganini
May 12, 2025

Expert found two flaws in DriverHub, pre-installed on Asus motherboards, which allows remote code execution via crafted HTTP requests.

Security researcher ‘MrBruh’ discovered two vulnerabilities, tracked as CVE-2025-3462 (CVSS score of 8.4) and CVE-2025-3463 (CVSS score of 9.4), in DriverHub, a driver that is pre-installed on Asus motherboards. A remote attacker can exploit the flaws to gain arbitrary code execution.

Both flaws stem from insufficient validation, allowing misuse of DriverHub features. The company pointed out that the flaws don’t impact laptops and desktops.

DriverHub, a driver updater with no GUI, runs a background process that talks to driverhub.asus.com via RPC on localhost port 53000. Researcher MrBruh found that while it only accepts requests with an origin header set to “driverhub.asus.com,” a flawed wildcard match allowed requests from domains like “driverhub.asus.com.mrbruh.com.” An attacker can exploit this vulnerability to install malicious software.

Researcher MrBruh discovered that Asus DriverHub exposes several local RPC endpoints, including dangerous ones like UpdateApp, which downloads and installs executables with admin rights if signed by Asus. By analyzing JavaScript and decompiled code, he found that a zip file used in driver installs includes an INI setting (SilentInstallRun) that can execute arbitrary commands during silent installs. This opens a path to remote code execution (RCE).

“The files of importance here are the AsusSetup.exeAsusSetup.ini and SilentInstall.cmd. When executing AsusSetup.exe it first reads from AsusSetup.ini, which contains metadata about the driver. I took interest in a property in the file: SilentInstallRun.” reads the report published by MrBrush. “When you double-click AsusSetup.exe it launches a simple gui installer thingy. But if you run AsusSetup.exe with the -s flag (DriverHub calls it using this to do a silent install), it will execute whatever’s specified in SilentInstallRun. In this case the ini file specifies a cmd script that performs an automated headless install of the driver, but it could run anything.”

The exploit chain abuses Asus DriverHub’s update mechanism: a malicious site on a spoofed subdomain sends requests to download a benign-sounding executable and a crafted AsusSetup.ini. Then, it downloads a legitimate, signed AsusSetup.exe, which runs silently with admin rights and executes the attacker’s payload (calc.exe) as specified in the .ini file.

MrBruh discovered the flaw on April 7 and reported the vulnerabilities on April 8. Asus released security updates on May 9.

MrBruh asked Asus if they offered bug bounties. The company said they don’t offer bug bounties but would add the researcher’s name to their “hall of fame.”

“I asked ASUS if they offered bug bounties. They responded saying they do not, but they would instead put my name in their “hall of fame”. This is understandable since ASUS is just a small startup and likely does not have the capital to pay a bounty.” concludes MrBruh.

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

Pierluigi Paganini

(SecurityAffairs – hacking, ASUS)







Source link