Takeaway: Automated scanners are essential for flagging capabilities, but manual verification is the only way to determine intent.
We acted quickly in hopes of preventing harms, but in this case, we were mistaken.
We've removed the post to avoid any confusion (sorry!).
Earlier today, we flagged a VS Code extension (rphlmr.vscode-drizzle-orm) based on 21 critical YARA hits from vsix-audit.
After manual inspection and deeper analysis, inspecting the .vsix, and reversing the WASM binaries, we’ve confirmed this is a False Positive.
- The SOL wallet identified was actually a character property table in the Oniguruma regex engine.
- The "Dropper" patterns were standard Emscripten/LLHTTP boilerplate.
- The "Stealer" hits were bundled dotenv and undici dependencies.
1/ I've been doing some research into how Unity Packages (similar to Node or Pip packages) could be weaponized for malware delivery
Let me tell you, it doesn't exactly look good... 🧵
Links:
CVE-2025-31201: Apple
CVE-2025-31200: Apple and Google Threat Analysis Group
macOS Sequoia 15.4.1:
https://t.co/t3r8hndiDn
iOS 18.4.1 and iPadOS 18.4.1:
https://t.co/su6XCE0N23
visionOS 2.4.1:
https://t.co/GY4t0NIJWu
No excuses.
These are live use, not theoretical CVEs.
Apple doesn’t push same-day cross-platform updates and delete vulnerable code unless the stakes are real.
Stay sharp. Patch everything. Watch your traffic. 🧙♂️
Two #CVE's, patched across every Apple platform, both marked as actively exploited in the wild:
#Apple just released:
- macOS 15.4.1,
- iOS 18.4.1
- iPadOS 18.4.1
- tvOS 18.4.1
- visionOS 2.4.1
— and you should stop what you're doing and update now.
July 2023 #TornadoCash exit worth 1,400 ETH ($2.6M)
Exit via 100 ETH Contract, swaps for USDC, heads out over the Synapse bridge, to Polygon 0xc09d3c2 and get gambled away at @Stake. I see this fairly often when analysing TC.
Tool: @MetaSleuth
Community Alert: There is currently a fake @Ledger Live app on the official @Microsoft App Store which was resulted in 16.8+ BTC ($588K) stolen
Scammer address
bc1qg05gw43elzqxqnll8vs8x47ukkhudwyncxy64q
Unfortunate but true, web3 sees security as something you pay for once prior to your contract deployment. Brand protection gets sidelined in favor of keeping hype perpetually alive. Not to mention, those who do help, very often get nothing in return, so there's little incentive for professionals, albeit rife with opportunity to improve security across the board. We hardly have a name for the position though, so it can certainly be and feel overwhelming.
That said, its always appreciable seeing the builders and the devs and security techs that are here, reaching out and making such efforts. This has been a constant in the space for years despite any market or trends otherwise. There's a sense of purpose to the whole thing because of this, and it certainly brings a level of quality and enthusiasm that you can't rightly find elsewhere.
Nice post - cheers.
@PeckShieldAlert This is another MakerDAO deposit. Now, I dont understand the exact mechanics of this, but after a bit of digging, funds seem to get withdrawn from Maker as USDC and deposited into Coinbase
https://t.co/sAI8lsi5aO
It's release time 🎃
- Responses can now be intercepted and modified
- Delete requests from HTTP History
- [Pro] Import/export your projects using our new "backups" page
- [Pro] Add shell commands to your convert workflows with the new "Shell" node
https://t.co/5zKo9NF31G