Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zhexi Oray Tunnel Backdoor in Go1 has been disclosed please advise... #120

Open
ZhexiBackdoor opened this issue Mar 21, 2025 · 1 comment

Comments

@ZhexiBackdoor
Copy link

https://x.com/Bin4ryDigit/status/1903092582021804543

https://think-awesome.com/download_unitree_report

Tunnel services
CloudSail
CloudSail (Zhexi) is a remote access tunnel service developed by Zhexi Technology, primarily
targeted at Chinese markets. The service is designed to provide NAT traversal and remote access
capabilities for IoT devices, industrial equipment, and other networked systems. While the service
itself is a legitimate tool for remote device management. It can be compared to ngrok, cloudflare
tunnel etc.
To understand the CloudSail service and its capabilities more read the FAQ:
https://jmz.zhexi.tech/faq/
What can the service do?
The CloudSail service can establish a connection from any device to another, even across
different networks, depending on your configuration.
For example, you could open a TCP connection to a connected device: the client on the device
connects to the CloudSail network, allowing you to route connections to services running on that
device.
This means if an SSH daemon is running on the client device, you could connect to it through
CloudSail, even if the local network blocks incoming connections or lacks port forwarding —
effectively circumventing NAT and firewall restrictions.
This can be especially useful when your device is on a mobile network with CGNAT or similar
configurations, which would typically prevent external access. However, this level of access can
also be dangerous. The decision to enable such functionality should always remain with the user,
not the manufacturer.

@ZhexiBackdoor
Copy link
Author

I can see you killed the token for the zhexi backdoor and removed the API key. Now you have to make public disclosure. Don’t forget that part. You are welcome for the email, you cold have at least said thanks. "2025/03/23 15:11:47 2926 ERROR [worker:handleRegisterResponse] register failed. Error:token not valid"

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant