Trust & Safety

Report Abuse & Harmful Links

We take quishing, phishing, scam links, and malicious exploits with utmost seriousness. Here is how to notify our security team for immediate action.

1. Prohibited Malicious Activities

JRCodeNest strictly prohibits the use of our studio and viewer platform for:

  • Phishing & Quishing: Impersonating banking portals, Microsoft 365, Google, Apple ID, parking meter payment terminals, or municipal utility payment gateways.
  • Malware Distribution: Distributing malicious APKs, malware droppers, ransomware, or executable browser payloads.
  • Fraudulent Schemes: Crypto investment scams, advance-fee fraud, counterfeit prize notifications, or deceptive marketing scams.
  • Unlawful & Hateful Content: Defamation, non-consensual imagery, harassment, or unlawful threats.

2. How to Report an Abusive Code

To file an abuse report, send an email directly to our dedicated abuse response desk:

Dedicated Abuse Contact Email:

devcraft.official@proton.me

Reports are triaged by our security engineering desk.

Required Information to Include:

  1. The Suspect URL: Provide the full destination URL or the viewer page link (e.g., https://jr-codenest-view.pages.dev/#...).
  2. Payload Hash (if known): If you decoded the payload, include the SHA-256 cryptographic hash of the raw string.
  3. Nature of Abuse: Briefly describe whether the link constitutes phishing, malware distribution, or a fraudulent impersonation.
  4. Physical Location (if applicable): If the QR code was discovered on public infrastructure (parking meters, restaurant tables, transit kiosks), specify the location so local authorities can be alerted.

3. Our Rapid Cryptographic Takedown Mechanism

Because JRCodeNest viewer links are decentralized and client-rendered, we maintain a cryptographic SHA-256 blocklist:

  • When a reported payload or domain is confirmed malicious, its SHA-256 hash is added to our client-side blocklist (src/config/blocklist.json).
  • When any user visits a viewer page matching that hash, the browser’s Web Crypto engine immediately detects the match and prevents the page from rendering, displaying: “This page was disabled due to reported abuse or security violations.”
  • The viewer client enforces a strict Content Security Policy (default-src 'none'; script-src 'self'; ...) that prevents external network calls and script injection.

4. Legal Law Enforcement Inquiries

We cooperate with law enforcement authorities investigating cybercrime, quishing campaigns, and fraud. Because we do not log personal IP addresses or store user accounts, our technical assistance is limited to cryptographic verification and payload blocklisting.