TL;DR: This is a public safety notice about Soldrift / @devbeast5775, a reported Solana/Web3 tool developer case involving payment, VPS/server access, GitHub disappearance, wallet-flow evidence, and security concerns around private-key/server handling.
Public Safety Notice for Solana Builders, Traders, and Project OwnersThis post is a public safety notice regarding a reported Solana development/security incident involving the identity listed below.
This is not a call for harassment, threats, doxxing, spam, or retaliation. The purpose is evidence preservation, user protection, and warning other builders before they send funds, private keys, API keys, wallet access, source-code access, or server/root access to unknown developers.
Reported IdentityName used: Soldrift
Telegram:
https://t.me/devbeast5775GitHub profile:
https://github.com/soldriftGitHub username: soldrift
Displayed field: Solana / Web3 / memecoin launch or trading tools
SummaryThe person listed above presented himself as a Solana/Web3 tool developer. After payment and server/VPS access were provided, the delivered or modified project raised serious concerns involving wallet/private-key handling, server access, backend behavior, source-code access, and overall operational security.
Because Solana tools may involve private keys, API keys, RPC keys, wallet funding, server credentials, and live trading or launch operations, I am publishing this notice to help other builders avoid unnecessary risk.
What Happened1. Development work was discussed through Telegram.
2. Payment was sent.
3. Server/VPS access was provided.
4. A Solana-related tool/project was delivered or modified.
5. After review, the project raised wallet/key handling and server security concerns.
6. Developer access was removed and credentials were rotated.
7. GitHub later became unavailable from my side, while the Telegram profile remained active.
8. Evidence was preserved for platform reports and possible further action.
Main Security Concerns* Wallet/private-key handling risk
* Server/root access risk
* GitHub/source-code access risk
* API key / RPC key exposure risk
* Backend behavior concerns
* Unknown third-party code risk
* Risk of using production wallets or funded wallets with unverified tools
Wallet / Transaction IdentifiersPrimary wallet:
E8RcJDs3SaBP2udWy6bD7576zJ3WitfbVh16vgeqoAgi
Related wallet:
5cZWa1KZQnMPeXTHPRF8JSEPMhzRaHPehAoG1rPtiHGc
Evidence PreservedTelegram export, payment transaction records, wallet records, TXID records, GitHub screenshots, server logs, delivered project files, timeline of payment/access, and security containment actions have been preserved.
I am not publishing the full private conversation because it contains unrelated private discussion and sensitive information. Sensitive information such as private keys, seed phrases, passwords, API keys, RPC keys, SSH keys, server credentials, unrelated private messages, and personal information has been redacted or excluded.
Full Evidence Reporthttps://physicaldoges.github.io/soldrift-safety-report/Request to the CommunityPlease review the evidence carefully. If you independently believe the evidence is valid, please report the related GitHub account, repositories, mirrors, or forks through GitHub’s official reporting process.
This is not a request for harassment or personal attacks. The goal is user protection, scam prevention, and evidence preservation.
Safety WarningBefore working with any unknown developer, do not share private keys, seed phrases, API keys, RPC keys, server root access, wallet funding access, production credentials, or main project source-code access.
If any of the above were already shared, rotate them immediately.