Project Lexcon was a test, a dry run to something much larger...

1. Pay to Task Ratio Was Off

The compensation was disproportionately high relative to task complexity. This is a classic honeypot pattern. Attract volume then analyze how people attempt to game the system. They were stress testing their abuse detection, monitoring capabilities and compliance infrastructure.

2. Dedicated Domain with Suspicious Timing

Project Lexicon uses a unique login domain for Multimango: handshakelexicon.ai. This is NOT SOP for Handshake AI user login credentials to the Multimango platform.

Check the ICANN lookup yourself. The domain was registered November 20, 2025. That is far too recent for a production project. It was a test to collect the data needed in order to iterate and refine final project requirements before launch.

3. Full Registrant Redaction

Search handshakelexicon.ai on ICANN Lookup at lookup.icann.org. All registrant information is redacted behind Cloudflare privacy. Compare this to handshake.ai itself which shows standard registrar info.

You typically only see this level of obfuscation when a client and not Handshake owns the domain, when there is significant IP or contractual sensitivity, or when GRC (Governance, Risk, Compliance) is mission critical.

https://preview.redd.it/fnn68s36e2bg1.png?width=1080&format=png&auto=webp&s=cf0e65cd3a4305c32b2fc281ad9c66a69e7b0536

4. Two Year Registration

The domain is registered for two years. That signals a longer term contractual commitment. Not a throwaway test but a foundational test for something bigger.

5. The Project Lead is Not Random

Look him up on LinkedIn. He is a former CEO of a startup. Deep industry connections. You do not put someone like that on a disposable project.

6. Collecting Reddit Response Data

This was a socially engineered cutoff, I guarantee you that they are also collecting and measuring the flood of user response data in the r/handshakeai subreddit.

My Analysis

Handshake or their client needed real world data on worker behavior, abuse patterns, and operational resilience before scaling something much larger. Project Lexicon was that data collection exercise.

Truly, I am 100% certain this was an exceptionally brilliant feat of social engineering for the purpose of creating a project honeypot that spammers, remote/international VPN users, North Koreans, etc., would try to wiggle their way into, with the cash draw of $3.67 for a 2 to 4 minute task.

From the perspective of operational governance, I hypothesize that this was a test designed to collect this access data for the purpose of hardening their systems. That would explain why all projects are on hold until next week. They need time for final analysis and validation of their findings so every project platform-wide can be hardened.

It never made any sense to me why I was being paired with these random ass people from the developing world during these calls.

That $3.67 an hour was bait so they could identify the trends and patterns used to exploit the system for the purpose of hardening their security posture platform wide.

submitted by /u/AnonRussianHacker
[link] [comments]

Categories:

0 Comments

Leave a Reply

Avatar placeholder

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Verified by MonsterInsights