<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Yeti Journal on Yeti.Security — Pen-testing &amp; security consulting</title><link>https://yetisecurity.cz/journal/</link><description>Recent content in The Yeti Journal on Yeti.Security — Pen-testing &amp; security consulting</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://yetisecurity.cz/journal/index.xml" rel="self" type="application/rss+xml"/><item><title>Crampon-7: credential-stuffing wave targeting fleet-management SaaS</title><link>https://yetisecurity.cz/journal/crampon-7-credential-stuffing/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://yetisecurity.cz/journal/crampon-7-credential-stuffing/</guid><description>&lt;div class="callout crit">&lt;span class="label">// TLP:AMBER · limited distribution&lt;/span>
This brief contains active-campaign indicators. Share inside your organization
and with trusted partners only. Do not redistribute publicly.
&lt;/div>

&lt;p>A coordinated credential-stuffing campaign is targeting US-based
fleet-management platforms. Yeti has observed activity against three customers
in the last 72 hours. Recommended actions are at the bottom of this post.&lt;/p>
&lt;p>&lt;span class="stat-inline">
&lt;span class="v">HIGH&lt;/span>
&lt;span class="l">severity&lt;/span>
&lt;/span>

&lt;span class="stat-inline">
&lt;span class="v">11&lt;/span>
&lt;span class="l">known victims&lt;/span>
&lt;/span>

&lt;span class="stat-inline">
&lt;span class="v">~3%&lt;/span>
&lt;span class="l">success rate&lt;/span>
&lt;/span>

&lt;span class="stat-inline">
&lt;span class="v">05.04&lt;/span>
&lt;span class="l">first seen&lt;/span>
&lt;/span>
&lt;/p>
&lt;h2 id="summary">Summary&lt;/h2>
&lt;p>Threat actor &lt;strong>CRAMPON-7&lt;/strong> is replaying credentials harvested from a 2025
unrelated SaaS breach against fleet-management login endpoints. Distributed
across approximately 4,200 residential proxies; rate-limited at 1.5
requests/second per IP — well below typical naive rate-limiting thresholds.&lt;/p></description></item><item><title>The first six findings we see, every time</title><link>https://yetisecurity.cz/journal/first-six-findings/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://yetisecurity.cz/journal/first-six-findings/</guid><description>&lt;p>Eighteen months in, we&amp;rsquo;ve completed 38 engagements. They span fintechs, fleet-
management SaaS, two robotics companies, and a healthtech firm we can&amp;rsquo;t name.
Different stacks, different teams, very different threat models.&lt;/p>
&lt;p>And yet — the same six findings appear in roughly the same order, every time.&lt;/p>
&lt;p>Treat this list as a &lt;strong>pre-emptive remediation roadmap&lt;/strong>. If you can knock
these out before our next visit (or, ideally, before someone else&amp;rsquo;s first
visit), the rest of the engagement is materially more useful.&lt;/p></description></item><item><title>Northstar Robotics: fixing twelve findings before the report shipped</title><link>https://yetisecurity.cz/journal/northstar-case-study/</link><pubDate>Sun, 22 Mar 2026 00:00:00 +0000</pubDate><guid>https://yetisecurity.cz/journal/northstar-case-study/</guid><description>&lt;p>In Q2 2026 we ran a four-week penetration test against &lt;strong>Northstar Robotics&lt;/strong>,
a fleet-management SaaS for autonomous logistics vehicles. The engagement
covered their production web app, the operator mobile apps (iOS + Android),
and their customer-facing API.&lt;/p>
&lt;p>We found 28 issues — two critical, four high, nine medium, eight low, five
informational. None of those numbers are unusual. The unusual part: by the
time we sent the final report, &lt;strong>20 of the 28 were already fixed&lt;/strong>. Six more
had open PRs. Two were deferred deliberately, with a documented exception.&lt;/p></description></item></channel></rss>