Alaeddine Mesbahi retweeted
New in Ostorlab Threat Center: detection for PHP2Shell (CVE-2026-109618, CVE-2026-109619).
Ostorlab scans flag web servers that report an affected PHP version, without sending any exploit.
If you're affected, update to the 21 October PHP release.
Alaeddine Mesbahi retweeted
Reverse engineer anything with agents, from app behavior down to native binaries.
github.com/morluto/rea
Alaeddine Mesbahi retweeted
Why did the US ban this number in 2001? It sounds insane, but 25 years ago, the Motion Picture Association of America was genuinely trying to delete this number from the internet.
You see, back in 1999, a teenager in Norway named Jon Lech Johansen wrote a piece of code called DeCSS.
It cracked CSS, the encryption on DVDs. Suddenly, anyone could copy a movie with the click of a button. It was a nightmare for the movie studios.
They went nuclear. They sued the hacker magazine 2600: The Hacker Quarterly.
They threatened Slashdot, and their lawyers fired out cease-and-desist letters to anyone hosting the code. They called it a digital burglary tool.
But the internet found a loophole.
A computer scientist named Phil Carmody realized that computer code is just binary ones and zeros.
And you can treat that string of binary as a single number. That way, you get a really, really big integer—which is the illegal code.
But Carmody knew that just finding any number wasn’t going to be enough, because the government could still ban a random number.
So he needed a number that science would be forced to protect. He needed a prime number.
You see, the University of Tennessee maintains a prestigious academic database called the Prime Pages.
It records the 5,000 largest known prime numbers. Carmody realized that if he could turn the illegal code into a record-breaking prime number, the university would have to publish it.
His first attempt was 1,401 digits long. It was prime, but too small.
It didn’t crack the top 5,000 list. It wasn’t mathematically interesting enough to save.
So, he hacked the math.
Use this formula:
K × 256^N + B
Now, K is the illegal code part. 256^N is the mathematical equivalent of adding useless zeros at the end—like making a book longer by adding blank pages. It doesn’t change the actual content inside.
So, he kept adding “blank pages,” shifting the number, until he hit a mathematical jackpot—a 1,959-digit monster.
This wasn’t just illegal code anymore. It became the 10th largest ECP prime number ever discovered at the time.
It was checkmate.
The number was immediately added to the university database. For the MPAA to ban the code now, they would have to order a university to delete a scientific record.
You can’t censor mathematics.
Alaeddine Mesbahi retweeted
A baby with brittle bones plays a sliding game on the bed with his mother…
This will make you Cry. Every human deserves a chance to live
Alaeddine Mesbahi retweeted
Zhu Youfang, a rural teacher in Hubei, kept teaching despite spinocerebellar ataxia, using a rope for support as her mobility declined.
Her resilience and dedication to her students are truly inspiring.
Alaeddine Mesbahi retweeted
How could this level of blatant fraud make it past a VC firm led by this executive team?
Delve, a YC-backed compliance startup that raised $32 million, has been accused of systematically faking SOC 2, ISO 27001, HIPAA, and GDPR compliance reports for hundreds of clients. According to a detailed Substack investigation by DeepDelver, a leaked Google spreadsheet containing links to hundreds of confidential draft audit reports revealed that Delve generates auditor conclusions before any auditor reviews evidence, uses the same template across 99.8% of reports, and relies on Indian certification mills operating through empty US shells instead of the "US-based CPA firms" they advertise. Here's the breakdown:
> 493 out of 494 leaked SOC 2 reports allegedly contain identical boilerplate text, including the same grammatical errors and nonsensical sentences, with only a company name, logo, org chart, and signature swapped in
> Auditor conclusions and test procedures are reportedly pre-written in draft reports before clients even provide their company description, which would violate AICPA independence rules requiring auditors to independently design tests and form conclusions
> All 259 Type II reports claim zero security incidents, zero personnel changes, zero customer terminations, and zero cyber incidents during the observation period, with identical "unable to test" conclusions across every client
> Delve's "US-based auditors" are actually Accorp and Gradient, described as Indian certification mills operating through US shell entities. 99%+ of clients reportedly went through one of these two firms over the past 6 months
> The platform allegedly publishes fully populated trust pages claiming vulnerability scanning, pentesting, and data recovery simulations before any compliance work has been done
> Delve pre-fabricates board meeting minutes, risk assessments, security incident simulations, and employee evidence that clients can adopt with a single click, according to the author
> Most "integrations" are just containers for manual screenshots with no actual API connections. The author describes the platform as a "SOC 2 template pack with a thin SaaS wrapper"
> When the leak was exposed, CEO Karun Kaushik emailed clients calling the allegations "falsified claims" from an "AI-generated email" and stated no sensitive data was accessed, while the reports themselves contained private signatures and confidential architecture diagrams
> Companies relying on these reports could face criminal liability under HIPAA and fines up to 4% of global revenue under GDPR for compliance violations they believed were resolved
> When clients threaten to leave, Delve reportedly pairs them with an external vCISO for manual off-platform work, which the author argues proves their own platform can't deliver real compliance
> Delve's sales price dropped from $15,000 to $6,000 with ISO 27001 and a penetration test thrown in when a client mentioned considering a competitor
Alaeddine Mesbahi retweeted
Dan says he's got Qwen 3.5 397B-A17B - a 209GB on disk MoE model - running on an M3 Mac at ~5.7 tokens per second using only 5.5 GB of active memory (!) by quantizing and then streaming weights from SSD (at ~17GB/s), since MoE models only use a small subset of their weights for each token
Alaeddine Mesbahi retweeted
CVE-2025-68461: Roundcube Webmail SVG XSS sanitizer bypass (CVSS 7.2 High). Affects <1.5.12 and <1.6.12. Trick: attributeName="xlink:href" slips past naive comparisons → stored XSS path. Fix: normalize/strip namespace prefix.
blog.ostorlab.co/cve-2025-68…
#XSS #CVE #Roundcube #AppSec
Alaeddine Mesbahi retweeted
🚀 We’re launching Agentic Deep Scan
Our next-generation vulnerability scanner for web, APIs, and mobile apps (iOS, Android, soon HarmonyOS).
We’re the first and only platform delivering deep agentic scanning for mobile, while also covering web & APIs, helping security teams go beyond traditional scans with greater confidence and control.
Alaeddine Mesbahi retweeted
AWS sent me a $47 bill. I haven't used AWS in 8 months.
Logged in to shut it down. Found one EC2 instance running. Micro. $0.0058 per hour. Someone spun it up in February using my old credentials I forgot to rotate.
I was about to terminate it. Then opened the logs.
A bot. Running 24/7 since February. Connected to Binance WebSocket and a prediction platform API. Executing trades every 3 minutes.
I followed the wallet address from the config file.
0x732F1. $339,140 profit. 38,945 predictions. Joined February 2026. Bio: there are no socials/websites related to this profile.
→ Wallet: t.me/PolyGunSniperBot?start=…
Someone used my forgotten $47/month server to run a bot that made $339K.
38,945 trades. 800 per day. BTC moves on Binance. Platform lags 25 seconds. Bot buys old price. Collects $1. Repeat.
The code was 26 lines of Python. Clean. No comments. No readme. Just a WebSocket listener, a price comparison and a buy function with a 15 second sleep timer.
$339K profit on a $47 monthly server bill. ROI on the server alone: 721,574%.
I checked the SSH login history. One IP address. Vietnam. Logged in once in February. Never again. Set the bot. Left.
Someone halfway across the world found my exposed credentials, didn't steal my data, didn't mine anything. Just quietly parked a 26 line script on my cheapest server and let it print.
I didn't terminate the instance. Changed the password. Sat there reading the logs for 2 hours.
The bot is still running. The wallet is still active. $113K in open positions right now.
My $47 AWS bill just became the most profitable invoice I never meant to pay.
Readers added context they thought people might want to know
@marlowxbt has posted several nearly identical fictional 'discovery' stories recently using different hooks (AWS EC2, Replit, Claude, Cursor). The linked Polymarket wallet has legitimate profits, but the personal story is fabricated content for engagement.
x.com/marlowxbt
Alaeddine Mesbahi retweeted
You can now fine-tune Qwen3.5 with our free notebook! 🔥
You just need 5GB VRAM to train Qwen3.5-2B LoRA locally!
Unsloth trains Qwen3.5 1.5x faster with 50% less VRAM.
GitHub: github.com/unslothai/unsloth
Guide: unsloth.ai/docs/models/qwen3…
Qwen3.5-4B Colab: colab.research.google.com/gi…
Alaeddine Mesbahi retweeted
Mardi 10 mars, c'est la conférence JSSI 2026 organisée par l'OSSIR !
Une journée d'échanges autour de la sécurité de la chaine d'approvisionnement logiciel :
ossir.org/conference/jssi-20…
RDV dans les nouveaux locaux de l'ESIEA à Ivry-sur-Seine (au pied du RER C), dès 8h30.
Alaeddine Mesbahi retweeted
DORA compliance for mobile releases, without the regulatory noise.
Part 2 of our 4-part BFSI mobile and AppSec series is live. This one is the practical bit: a simple controls baseline, a clear PASS or FAIL verdict model, and how to handle exceptions without turning every release into a negotiation.
Read Article 2: blog.ostorlab.co/dora-compli…
#DORA #MobileSecurity #AppSec #BFSI
Alaeddine Mesbahi retweeted
Are one-way trusts really one way? @lowercase_drm sums up how the TDO password lets you turn a one-way AD forest trust into bidirectional access, and releases a new tool to remotely extract these secrets.
offsec.almond.consulting/tru…
Alaeddine Mesbahi retweeted
🚨 Saltcorn (≤1.5.0-beta.19) has a critical 1-click RCE: reflected XSS + backup command injection.
An admin clicking a link is all it takes.
We tested a PoC to show the full chain. How would you handle this in production?
Full breakdown & fix in our article : blog.ostorlab.co/ghsa-cr3w-c…
Alaeddine Mesbahi retweeted
#Podcast #Cybersécurité
Épisode #534 consacré au ver "Shai-Hulud", avec @christophetd
nolimitsecu.fr/shai-hulud/
Alaeddine Mesbahi retweeted
We work with mobile apps every day, and over time, we’ve found 10 tools that make our penetration testing faster, smarter, and more effective.
Here are the 10 tools worth knowing in 2026.
Alaeddine Mesbahi retweeted
🔴Live: Mobile Hacking Conference | Day 2
youtube.com/watch?v=CfioCImy…
Alaeddine Mesbahi retweeted
🚨 SSRF Alert in LangChain!
CVE-2026-26019: A naive startsWith() check in RecursiveUrlLoader lets attackers bypass crawl restrictions and reach internal network assets, turning a single injected link into SSRF.
We cover the root cause, exploitation, and the patch.
Full breakdown 👇
blog.ostorlab.co/cve-2026-26…
Alaeddine Mesbahi retweeted
DORA compliance for mobile teams, without the regulatory noise.
We wrote a 4-part series that covers everything a BFSI mobile or AppSec team needs to know.
→ Article 1: Scope and what you actually need to do
→ Article 2: Controls baseline, verdicts, and exceptions
→ Article 3: Resilience drills for critical mobile journeys
→ Article 4: Third-party risk, SDKs, and evidence packs
Article 1 is live.
blog.ostorlab.co/understandi…
#DORA #MobileSecurity #AppSec #BFSI





























