Urgent.News

What's breaking now, across thousands of outlets.

Editions

Tech

The homoglyph trick against similarity checking is documented - as not working

Drop a Cyrillic о into the middle of a word and a string matcher stops seeing the word, while the page looks identical. It is the kind of thing you would write in ten lines and it is exactly the kind of thing a tool might do to your file without telling you. The vendor documentation says it swaps those characters back out before scanning, and raises a flag on the way past. I went looking because…

A recent discovery reveals a flaw in similarity checking software that exploits the use of homoglyphs, or characters that appear similar to their Latin counterparts. By inserting a Cyrillic "о" into a word, a string matcher fails to recognize the alteration, yet visually, the document appears unchanged. This technique, documented by vendors but demonstrated to be ineffective, raises concerns about the reliability of such tools.

The vendor's documentation assures that lookalike characters are automatically converted back before scanning, thus allowing the similarity check to proceed. However, the flags generated by the software do not signify wrongdoing but merely require human review. The flags cover a range of issues, including hidden text, invisible quotation marks, white text on white backgrounds, and replaced characters.

The replacement technique aims to disrupt similarity matching by inserting characters from other alphabets that resemble Latin letters. However, Turnitin's algorithms detect and correct for these substitutions, raising flags but not hindering the matching process. The technique fails to achieve its intended effect, resulting in a documented instance of a bypass that does not work as intended.

While most authors are unlikely to use this method, it highlights the importance of thoroughly examining submitted files for hidden characters or alterations before relying on similarity checking tools.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Spring JPA Fundamentals for Tailored Software Solution...

If you've spent any real time building Java backends, you've probably felt the moment where your database layer starts eating your codebase alive. Spring JPA exists to stop that from happening.

  • Spring JPA simplifies Java backend database layer
  • Core components: Entity classes, Repositories, EntityManager, Transactions
  • Transactions use @Transactional for automatic rollback

The Commit Timestamps Told the Real Story

I didn't notice our team was burning out. The commit history did. It started as an idle observation — I was scrolling through a repo's activity graph looking for something unrelated, and noticed a…

  • Commit timestamps revealed burnout pattern in remote team
  • Late-night commits unnoticed due to remote work dynamics
  • Early monitoring tools needed to detect burnout proactively

Running a Monitoring SaaS on Cloudflare Workers + Supabase for Almost Nothing

Originally published on the Merlonix blog . Merlonix monitors uptime, SSL/TLS, DNS, email authentication, blacklists, Certificate Transparency, Core Web Vitals, and MCP servers for agencies.

  • System runs on eight Cloudflare Workers and Supabase Postgres database with row-level security.
  • Monitoring cadence enforced only for paying customers, using revenue-gated SLA throttle.

More from Friday 21 August →