I have never had a real vacation. Closest things to a vacation I've had are cyber/tech conferences. The way things are looking, I'm not likely to ever get a vacation moving forward. If all contingencies are met, I'll get a start date for a new job. From there I'll have 8mos on a trial work period to get off of disability. If my medical issues interfere with the job, I'm back to square one. If the contingencies are not met, the job offer is rescinded, and I'm back to square one.
I told my mom my bookshelf is falling apart. She didn't bother asking how many books I had, she just sent me the link for the strongest shelf she could find 🤣
Someone emailed me PDF goop that apparently takes over the entire Gmail account.
I didn't open said goop, but I tried to forward to @vxgiveaways and make it VERY CLEAR that it is goop.
Gmail refused to send it to vxug but didn't block it from coming to me (-_-)
> be me
> get dm from friend @malwrhunterteam
> "smelly i found goop"
> wtf i love goop (malware)
> @smica83, funny sounding name man shares
> flagged as goop from north korea (maybe)
> wtf i love north korea (they dont steal monies)
> download
> look inside
> .msc file
> Microsoft Management Console file
> file thingie for sysadmins to open
> big ass fuck off obfuscated code
> wtf
> javascript encoded as html decimal thingies
> decode
> obfuscated javascript
> weird comments inside the javascript code
> comment about BangBus (porno?)
> ??? bros like BangBus ???
> does a bunch of dumb obfuscation
> eventually pulls out giant blob of data from .msc file
> look inside
> base64 encoded OLE stream
> what year is it?
> look inside OLE stream
> ocx_streamorstorage
> look inside
> 21,486 lines of obfuscated javascript
> simple bullshit tho, just embedded a bunch of goop
> base64 encoded and split up a bunch
> put back together
> fails
> oh its also compressed
> decompress
> works
> XLST with microsoft jscript executor
> ok
> XLST jscript uses a bunch of .net stuff
> .net makes another XML
> what the fuck is this fucking piece of shit
> .net reads XML it made
> eventually find 32bit position independent shellcode
> the shellcode is stored in the balls
> jk was stored in "Resource Directory:b:Array:QrJVY"
> shellcode never seen before on VirusTotal
> open shellcode in IDA PRO (thank u hexrays ily omg)
> look inside
> lots of stuff, have lots of work to do
THIS IS AN ACTUAL F*CKING GOLDMINE
Anthropic just shared one of the best tricks for Claude Code.
The idea: run Sonnet, Haiku 5.5 and Opus 5.5 at once, each one doing only the job it's best at.
Better results and way fewer tokens, because every task lands on the right model.
You just launch Claude Code like this:
claude --model sonnet --advisor opus
here's the split:
→ Sonnet 5.5 runs the session, writes the code and applies the fixes
→ Haiku 5.5 swarms the repo in parallel: search, grep and diff audits
→ Opus 5.5 stays on call as advisor for the big calls and signs off on the diff
→ you stop burning Opus context on work that doesn't need it
Opus only steps in at three moments:
→ before a plan locks
→ when the same error shows up twice
→ before calling it done
Sonnet builds. Haiku swarms. Opus reviews.
JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split
the full tree
> Sonnet 5.5 runs the main session and coordinates the work
> search maps the repo on Haiku 5.5, read-only
> grep finds call sites on Haiku 5.5 in its own context
> audit checks the diff on Haiku 5.5 in a throwaway worktree
> Opus 5.5 on call as advisor, reviews the synthesized diff before sign-off
> JEV routes micro-forks in milliseconds
paste the tree and this prompt into Claude Code ↓
"Reconfigure my Claude Code setup around this tree:
1. Run the main session on Sonnet 5.5 with Opus 5.5 as advisor.
2. Create three Haiku 5.5 subagents in .claude/agents: search (maps the repo), grep (finds call sites), audit (checks the diff).
3. Set isolation: worktree on audit so its checks never touch my working branch.
4. Add one rule to CLAUDE.md: delegate every repo search and test run to the Haiku 5.5 subagents to keep the main context small.
5. Route fast deterministic forks (tool choice, path selection, retries) through JEV.
Show me every change as a diff first. No edits until I say go."
↳ https://t.co/YqkjQiqRGv
save it, it'll come in handy.
Of course my car goes into the shop today 🤦🏻♀️ shocks, rear tires, and rear bearings are all bad. Sitting across the street in a Publix eating popcorn chicken from their deli until @CorpsTigris comes to pick me up...