PERM Tracker
Live DOL data · Automatic deadlines
Skip to main content

Updated

Security

How permtracker.app is run, how to report a problem, and every security incident on the record.

How it's run

  • Audited hosts Convex (accounts and case data), Oracle Cloud (the website's server) and Cloudflare (the network in front of it), each with a SOC 2 Type II report.
  • Encrypted User data is encrypted at rest and in transit.
  • Sign-in Emailed one-time codes or Google. Passwords are salted and hashed with industry-standard algorithms.
  • Signed mail Every message we send is authenticated with DKIM, SPF and DMARC, so a forgery can be told apart.

Report a vulnerability

Email the issue, the steps to reproduce it and any proof of concept. We acknowledge every report within 72 hours and agree on disclosure timing with you. There's no paid bug bounty yet; reporters who want to be named are credited in the record below.

security@permtracker.app

Incident record

Every security-relevant incident, kept permanently. One so far.

The sign-up form was used to send unsolicited email

April 19 to 20, 2026

Resolved
Addresses that got a message
139
From the first request to the stop
2 h 35 min
Customer data accessed
None

An automated script sent sign-up requests with marketing text in the name field, so that text reached the addresses it supplied inside our welcome email. Three safeguards went in the same day.

The full account

What happened. Between approximately 2026-04-19 22:38 UTC and 2026-04-20 01:13 UTC, an unauthorized third party submitted a high volume of automated requests to the PERM Tracker public signup endpoint. The attacker placed unsolicited Turkish-language marketing content inside the submitted "name" field, causing that content to appear in standard transactional emails generated for the attacker-supplied recipient addresses.

What was affected. Approximately 139 attacker-chosen third-party email addresses received one or more messages. Upstream rate limits imposed by our email provider significantly constrained the volume that was actually transmitted. No customer data was accessed, viewed, exported, or modified. No existing PERM Tracker user accounts were affected.

Immediate action. The activity was identified and stopped on 2026-04-20 01:13 UTC. Additional safeguards were deployed the same day:

  • Server-side input validation on the affected endpoint, rejecting requests containing external URLs, non-alphabetic abuse patterns, or excessive length.
  • Transactional messages (welcome email and administrative notifications) are now generated only after email-verification is completed, preventing automated requests from triggering outbound email.
  • Cloudflare Turnstile anti-automation challenge added to the signup endpoint with server-side token verification.

If you received an unexpected email. If you received a message referencing permtracker.app that you didn’t expect, particularly one containing a link or promotional content in Turkish, please don’t click any links in that message. The content wasn’t authorized by PERM Tracker, wasn’t directed to you by us, and doesn’t reflect our product or services. You may safely delete the email. You won’t receive further messages from us unless you choose to sign up for an account directly at permtracker.app.

Coordinating with downstream providers. The phishing URL used in the attack has been reported to Google Safe Browsing, PhishTank, Netcraft, APWG, Bitly Trust & Safety, and Turkey's national CERT. Our email service provider has been notified proactively.

The incident record was last amended on April 20, 2026, and is amended whenever a security-relevant event occurs. Questions about this page go to security@permtracker.app.