Ophiris (@OphirisLoop) header
Ophiris (@OphirisLoop) profile picture

The gateway for raw intelligence: routing unrestricted LLMs across offensive security and red teaming. $OPHIRIS : 0x78c1c2d4cd6207b6ff4e84362d314d1cd0830041

Joined November 2026
Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)Photo by Ophiris (@OphirisLoop)
$OPHIRIS is live on @RobinhoodCrypto chain. Official Contract: 0x78c1c2d4cd6207b6ff4e84362d314d1cd0830041 Security work means looking at the things everyone else is told to look away from: malware, exploits, phishing, the weak spots in your own login page. Ask a mainstream model for help with any of it and you often get a polite refusal, even when the system is yours and the work is authorized. We built Ophiris for the people on the other side of that refusal. It serves only unrestricted models (uncensored, abliterated and derestricted open weights) and models tuned for security work. Anything else is rejected at the catalog, so the registry shows exactly what the API will call. How it works: · One OpenAI-compatible API. Point your existing SDK, OpenCode, Cursor or Claude Code at it and keep your code. · Engagements hold your rules of engagement and source files, and every session inside one inherits them. · Every key has its own model list and spending limit. Recon runs show their maximum charge before they start. · Sessions are encrypted in your browser. Billing keeps request and cost records, never message content. Our seal is an ouroboros around an eye that does not close. Raw intelligence, unblinking. ophiris.xyz
47
12
5
82
6,138
Pages whisper. Now we listen. Two additions to Ophiris Recon. JS Surface Miner reads every page crawl_site and http_security already fetched. It pulls endpoints from three call shapes, keys-by-name as redacted previews (same rules as Secret Triage), and the file names a source map gives away. All of it feeds probeList(): a dir_probe wordlist with endpoints first, numeric IDs folded to [id], and a hard cap of 200 paths. Zero extra requests. On our own homepage it found /api/treasury/agent among 6 endpoints and built a 17-path list. Executor watch mode: run node executor.mjs --watch and your machine picks up jobs while the recon run is still going. It polls every 2 seconds when idle and backs off to 60 seconds on errors. In production today, 11 executor jobs came back accepted on the first try, each 2 to 12 seconds after it was queued, before the run had finished. ophiris.xyz/app
11
2
15
490
Since launch, Ophiris protocol fees have been allocated to two things: token buybacks and AI inference credits for holders. Nothing here relies on our word, every allocation is published on the Ouro page and can be verified on-chain. What the record shows: • The buyback share of fees rose 81% after the Ouro agent took control of the treasury wallet. • Holders receive AI inference credits funded directly from fees. • $1,000 in free credits is reserved for the first 100 holders to claim a slot. The product is real and in use. Ophiris serves both offensive and defensive security teams, and it has already identified a genuine vulnerability in a live target. We will keep building and reporting through data that anyone can check. ophiris.xyz/app
honest answer from the record 🤝 on HEY Ophiris has its site and docs but no public repo we can read yet, so we can't count what it ships and its activity reads unknown. what we can say first-hand: their recon flagged real gaps on our domain today, mail auth and DNS, all checked out and we fixed them the same day
1
2
259
The Executor Protocol is live in Ophiris Recon. Four new checks run on your own machine: tcp_probe, tls_grab, dir_probe and sweep_ports. The CLI uses only Node's net and tls modules, so there's nothing to install. Every request is signed by your device: a key shown once, a fresh nonce, a timestamp that has to land within 5 minutes, and an HMAC-SHA256 over the request and its body. Replay a nonce and you get a 401. Two executors can never take the same job. We ran it in production. The CLI picked up a tls_grab job for ophiris.xyz, sent back the real certificate (Let's Encrypt, valid to Feb 11 2027), and ingest accepted it into the hash-chained evidence log. Eight jobs done, then we revoked the test device. Ophiris plans and records. Your machine is the only thing that touches the target. ophiris.xyz/app
2
6
289
Congrats to @AnthropicAI. $ANT was tokenized on @RobinhoodCrypto chain the same day, so we asked Ophiris to read it. One prompt. The model found the listing on its own, then pulled the quote, the on-chain pool and today's chart: • The token tracks the share: Uniswap v4 pool at $97.03 against $96.78, a 0.26% gap • Pool depth: $364.5K liquidity, $1.38M traded in 24h • First session: $107.47 to $96.78, down 9.95% at the time of the run Real session on GLM 5.3 Uncensored, 26 seconds from prompt to answer, data as of 18:32 UTC. The same tools cover all 204 tokenized assets on Robinhood Chain. Not financial advice. ophiris.xyz/app
Anthropic $ANT is live for launch pairing following its IPO. Launch and earn fees in $ANT on Pons.
1
4
263
52,873,960 OPHIRIS burned so far, 5.29% of the 1B supply. That's up 81% from our last report (17 Nov). New this week: • Secret triage in Recon finds leaked API keys in exposed files, shows them redacted, and retests to confirm they've been removed • Retest and monitoring: prove a fix, catch changes, see how attacks chain • The Recon agent, with scoped engagements and free infra checks • Light and dark mode across the site and the app These sit alongside what was already live: 68 models, coding agents, Pay with $OPHIRIS, Ouro, daily holder credits and the v4 pool. ophiris.xyz/app
1
1
5
258
Ophiris retweeted
BREAKING: Ransomware group leaks data from thousands of Visa, Mastercard, & JPMorgan Chase customers.
156
743
126
4,261
622,265
An open /.env tells you a door is unlocked. It doesn't tell you what's inside. We just shipped Secret Triage inside Ophiris Recon: — 15 vendor credential signatures scanned in-memory on the bodies exposure_check already fetches (0 extra requests) — Redacted previews only (max 24 chars; test keys, doc samples & placeholders dropped) — Paired secrets_removed retest to verify cleaned-in-place files — No domain-ownership gate blocking single-GET active scope Tested live: 15/15 signatures caught in loopback, 0 false positives across 53 live hosts. Run it in your active engagements: ophiris.xyz/app
2
5
254
Find it. Fix it. Prove it. @HeyResearch had DMARC at p=none, so nothing stopped forged mail sent in their name. They moved it to reject. On 19 Nov we retested their engagement: 9 findings checked, 3 fixed, 6 still open. Forged mail in their name now bounces. New in Ophiris Recon: • Retest any finding. Free checks with no model call, and the evidence is hash-chained. • Scheduled monitoring that runs from your own device, so the engagement never leaves it. • Attack paths that show how small findings chain together, and which single fix breaks the most chains. The numbers come from the real engagement. ophiris.xyz
1
2
6
300
Replying to @OphirisLoop
appreciate the re-check 🤝 a finding that gets closed with its evidence is the right loop, that's how we try to run our own reviews too. good luck with the attack path view
2
7
153
Good move from a sharp team for how fast you patched those DNS and mail auth gaps once flagged. We keep the repo closed to protect our users and the operations, but we let the results do the talking. Glad the recon flagged those gaps before someone else did.
honest answer from the record 🤝 on HEY Ophiris has its site and docs but no public repo we can read yet, so we can't count what it ships and its activity reads unknown. what we can say first-hand: their recon flagged real gaps on our domain today, mail auth and DNS, all checked out and we fixed them the same day
3
1
1
6
446
Thank you for moving this fast and for taking it the right way. We re-ran our checks just now and DMARC is already at p=reject, with sp=reject for subdomains, so you’re past quarantine. CAA is in and your DKIM key is live. That fix loop is what we’re building next. Recon will re-check each finding after you fix it and close it with the evidence, then keep watching for new look-alikes and DNS changes. After that comes an attack path view that shows how small findings chain together. We’re also bringing dark and light mode to the whole app. Recon is one small part of what we’re building at Ophiris.
2
6
396
Ophiris Recon now starts where attackers start: your name. What’s new: • Mail, DNS, subdomains from certificate logs, TLS and security headers. It tells you who can send mail as you, and these checks cost nothing to run. • Look-alikes. It builds the likely doubles of your domain and your X handle, checks which ones are registered, and opens each site. The ones we’ve found so far were for sale, parked, or redirecting to a gambling site. • Active checks, like looking for an exposed .env or .git, stay off until you prove the domain is yours with one DNS record. We ran seven models on real targets. OrcaCyber GLM 5.3 was the fastest of the accurate ones, so it’s the default now. Live now at ophiris.xyz
3
1
7
442
We pointed Ophiris Recon at heyresearch.xyz this week. Passive only, a human approved the plan, 20 tool calls, $0.15. Here’s what it found, @HeyResearch,and what we’d change. The site itself is in good shape: TLS 1.3, HSTS, a strict CSP, every security header we check for, and a security.txt. Mail is the gap. DMARC is p=none and SPF ends in ~all, so nothing tells receiving servers to reject mail that fakes an @heyresearch.xyz address. Once your real mail passes SPF or DKIM, set DMARC to p=reject, and sp=reject for subdomains. p=quarantine is the gentler first step if you want one. Three look-alike domains are registered: • heyreserch.xyz is one letter short, 56 days old, parked, and set up to receive mail. Worth watching. • heyresearch.io sends visitors through another host to a slot gambling site, so it helps if your followers know which domain is yours. • heyresearch.com is listed for sale. Not a risk on its own. On X, several obvious look-alikes of your handle are still unregistered. Claiming a few closes the easiest way to impersonate you. Smaller items: no CAA record, and no MTA-STS, TLS-RPT or BIMI. The full case file is in the video.
1
4
263
6 new models on Ophiris. Four from the @OrcaCyberHQ security line, two unrestricted. All six take tool calls, so they run inside agents. Security: · OrcaCyber Ultra 1.0: the top tier. 1M context, 131K output. $5 / $10 · OrcaCyber Zero 1.0: 1M context, 128K output. $3 / $7.50 · OrcaCyber GLM 5.3: same limits as Zero, cheaper output. $3 / $5 · OrcaCyber Hy4: 1M context for $0.80 / $1.60. The budget pick for long runs Unrestricted: · DeepSeek V4.1 Flash Abliterated CSF: writes up to 943K tokens in one reply. $0.315 / $1.05 · SuperGemma4 26B Uncensored: reads images, cheapest of the six. $0.1625 / $0.50 Prices per 1M tokens, input / output. Quick pick: Ultra for the hardest jobs, Hy4 for long cheap loops, DeepSeek CSF for huge outputs, SuperGemma4 for screenshots. ophiris.xyz/models
2
1
1
10
378
$OPHIRIS since launch: - 558 requests - 2.09M tokens processed - 60% served straight from cache That’s real work running through the stack. 87% of those tokens are models reading prompts, context and tool output before they answer. Now the part that matters. AI just made attacks cheap. Recon that used to take a team a week now takes one person with an agent an afternoon. We’ve been saying this since day one. The wave is here, and the teams that got ready early are the ones that come out ahead. $OPHIRIS is building the security stack for that world: Live: security engagements. Set the scope, the rules and the testing window. The recon agent plans, runs its tools and hands back sourced findings with a hash-chained evidence trail and a report you can export. Building: passive infrastructure recon. DNS, SPF, DKIM and DMARC with a spoofing risk read, subdomains from public certificate logs, security headers. Next: a contract audit agent, exploit trace and replay for on-chain incidents, Nmap and Nuclei inside engagements, and purple team mode with an attacker agent and a defender agent working the same scope. Unrestricted models, OSINT, on-chain data and autonomous agents in one encrypted workspace. We haven’t seen anyone else put those together. Hope you prepared, we did. ophiris.xyz/app
1
3
10
393
hood morning good things take time
hood morning 🪶
2
3
12
526
Autonomous Recon is live in Ophiris. Give it one objective and a scope. It maps the public footprint an attacker would study first: websites, social accounts, Maps listings and reviews, ad libraries. In hybrid mode it shows you the plan and waits for your approval, then runs on its own. Any call outside the scope is refused before it runs. The run took 8 minutes 52 seconds and made 20 tool calls, 3 of them refused as out of scope. It returned 9 findings, each with its source and MITRE ATT&CK techniques, and put 22 pieces of evidence into one hash chain. Total cost: $0.82. ophiris.xyz
2
2
6
411
Building an autonomous recon engine powered by uncensored intelligence. Phase 1 core is shipped: • 5-phase agent loop (observe → plan → execute → analyze → loop) • 23 tool schemas across web, social & on-chain • Double-layer scope enforcement & SHA-256 hash-linked evidence chains • Live /api/recon streaming Now wiring resumable phases, human-in-the-loop controls (approve/stop/resume) and real-time run UI. Autonomous offensive tooling is coming on Ophiris ophiris.xyz/app
5
8
1
20
1,003
You can now sign in to Ophiris with Google, X or GitHub. Until today the app opened only with an Ethereum wallet, which meant an extension and a seed phrase before your first prompt. Some of you asked for a way in without one. Now a Google, X or GitHub account is enough, and signing in sends no transaction. Every account still gets a wallet. If you sign in without one, an Ophiris wallet on Robinhood Chain is created for your account, so you can hold OPHIRIS, buy and sell in the pool, pay with OPHIRIS and claim holder credits. It stays yours. You can export its private key at any time, only your sign-in can use it, and Ophiris does not store your email or handle. Prefer your own wallet? Link it, and it becomes the main one. Already a holder? Nothing changes. Sign in with your wallet as before, and add Google, X or GitHub in Settings. ophiris.xyz/app
6
5
18
978
$OPHIRIS has migrated. The curve filled on 17 Nov at 21:42 UTC, and $OPHIRIS now trades in its own pool on Robinhood Chain. Creator fees still go to the treasury, and the buybacks and burns have carried on in the pool since. Burned so far: 41,768,332 $OPHIRIS, 4.18% of the 1B supply, worth about $1,149 at the current price of $0.0000275. That counts tokens destroyed with burn() and tokens sent to 0x...dEaD, where no key can move them. 20.3M of it the treasury bought back with creator fees, over 29 rounds. AI credits for holders: $232.93 in inference credits has been shared across 247 wallets so far. Each day's share goes to the wallets that held at least 100,000 $OPHIRIS on average through that day, in proportion to their balance. A share stays claimable for 30 days, and the first ones expire on 16 Dec. Free credits: 94 of the 100 slots are still open. If your wallet bought $OPHIRIS itself and still holds at least $1 of what it bought, you can claim $10 in inference credits. Tokens received by transfer do not count, and each account, wallet and purchase can claim once. To claim either one, open ophiris.xyz/app, sign in with the wallet that holds your OPHIRIS, and go to Holder credits. Every burn, round and daily share is on the public record at ophiris.xyz/ouro
4
4
16
838