
Bald Black Christian Conservative Contributor @BoringSecurity Experiment: https://xitter.cf/t.co/dm7nihfbu7 shields@x2x | cryptoshields.eth
Canada
Joined February 2021
- Tweets75.5K
- Following2K
- Followers6K
- Likes16.9K
1/ Working in Web3 can be a real mental challenge, especially for people who are offering Public good services.
We spend our time, our money to build, offer and push products and services NOBODY ever asked for. Hoping that they will pay attention and eventually support us.
You invite a woman on a date
You better be ready to pat for her
And no, she doesn’t have to sleep with you because you paid.
Learn to be a gentleman or go eat alone
If your ENS name is below, you may have tokens sitting unclaimed in the official Arbitrum bridge (if you did not claim them yet)
You started a withdrawal from Arb to Eth but never did the final claim step.
Nobody needs to DM you about this. Anyone who does is a scammer.
What if everything you thought an NFT collection could be was just the beginning? 👀
We're not just changing where NFTs live. We're expanding what they can do for you.
🐛 Bugz Minters' Bonus: Get rewarded for minting.
💰 DIVIT: Earn crypto rewards for helping your community thrive.
🌐 UnVaulting: Take your NFTs wherever you want, whenever you want, for whatever reason.
🔥 Lower Marketplace Fees: Keep more of your money where it belongs. In your pocket.
More freedom. More opportunities. More rewards.
And this is just the beginning.
Welcome to UnVault. 🚀
Just another day in Crypto
Official Statement | Security Incident Update
TL;DR: No private keys were compromised, unaffected wallets are safe, and all affected users will be fully reimbursed by Bloom.
Following our investigation, we have identified the exact attack vector and confirmed the scope of the incident.
The attack exploited a third-party module through a complex Remote Code Execution (RCE) vulnerability. No private keys were accessed or compromised, and we have ruled out broader exposure of users' wallets.
Incident Overview
Affected: 49 wallet addresses belonging to 9 users.
• Total losses: Approximately 9,408 SOL ($947,000).
• Root cause: Exploited third-party module enabling an RCE vulnerability.
• Refunds: Bloom will fully reimburse 100% of the stolen funds directly to secure wallets designated by the affected users.
• We are also working to trace the stolen funds, explore recovery and freezing options, and identify the attacker.
Our team has been developing software since 2018 and operating in crypto since 2021. We are an established team, committed to building for the long term and protecting the trust of our users.
Security threats are an unfortunate reality of this industry, even with extensive precautions in place. Our commitment to user safety, transparency, and business continuity remains unchanged.
The Bloom Team
Your Ledger Nano X says "Battery problem: charging stopped"? You are not alone.
I opened mine to check for spy implants.
Instead, I found out why it wouldn't charge.
Spoiler alert: The battery wasn't dead.
Full video in the first reply. 🔋
Ok Let’s shut down the internet
🚨 PHP warns of another unpatched remote code execution risk; CVE-2026-115560
The newly disclosed vulnerability is separate from the two PHP2Shell flaws patched earlier this week and is not fixed by PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35.
⠀
PHP says exploitation requires an unusual configuration where an application:
• Uses php_binary or php_serialize as its session serializer
• Changes the serializer to php at runtime before session_start()
• Has session upload progress enabled
⠀
PHP considers the risk unlikely and plans to release a fix during its next regular update cycle.
Until then, administrators with affected configurations should set:
session.upload_progress.enabled=0
Applications that do not change the session serializer at runtime are not exposed through this path.
No exploitation has been reported.
Source:
php.net/
















