Jacob Ayokunle

Agentic Engineer, ex-CTO @IndicinaCo. Investor, Tech Builder, Talented and Gifted. #Exboy #Programmer #Tech

[Jacob Ayokunle @jayrobzy]

Hard work pays but smart work pays better. 😉

[Jacob Ayokunle @jayrobzy]

Software has always been about learning to use tools and patterns and I don't that has changed with AI. I always found curiosity to individually learn as the key quality of a software engineer.

[Jacob Ayokunle @jayrobzy]

@seunosewa Instead of building you could also invest. You own nairaland. You can start by ads credits as a way to help tech companies grow. If you start a platform to discuss startups and their challenges it would also go a long way. It's just one step at a time

[Jacob Ayokunle @jayrobzy]

@namzo Have you tried it? Care to share link or guide.

[Jacob Ayokunle @jayrobzy]

AI chats needs to be full of dynamic UI to make it quicker to understand and make decisions.

[Jacob Ayokunle @jayrobzy]

@arcinternet Buy Arc... So sad that you gave up

[Jacob Ayokunle @jayrobzy]

@LyalinDotCom I am sure this will merged with agy in the next few months.
Too many tools is confusing Google

[Jacob Ayokunle @jayrobzy]

@heyandras I thought the rule is avoid Friday deploys.

[Jacob Ayokunle @jayrobzy]

@syntaxfm @sentry @ThePledge Thanks for doing this. This should be done more in our industry

[Jacob Ayokunle @jayrobzy]

@TheHackersNews The vulnerabilities never end. Keep them coming...

[Jacob Ayokunle @jayrobzy]

@heyandras @theo I hope it's Rust

[LiteLLM (YC W23) @LiteLLM]

Hello,

At 6:32 a.m. PDT we became aware of malicious LiteLLM 1.107.0 artifacts published to PyPI, Docker Hub, and GHCR, which were published at approximately 4:40 a.m. PDT. Enterprise deployments pulling only from our private registry are unaffected by this incident.

We are coordinating communication around this incident in this GitHub issue (https://t.co/JQ6nlZ9XXE).

We have removed the malicious releases and images. If you installed or ran them, please follow the remediation guidance in the above-linked issue and treat credentials accessible to those deployments as exposed.

Sincerely,
Oliver Jensen
Director of Security - LiteLLM

[Jacob Ayokunle @jayrobzy]

@TheHackersNews

[Jacob Ayokunle @jayrobzy]

Oct 21 will be remembered in history

[Jacob Ayokunle @jayrobzy]

@githubstatus Not today of all days that we are all patching security issues

[FBI Cyber Division @FBICyberDiv]

Two critical vulnerabilities have been identified in PHP, a widely used programming language that powers websites and web applications. These vulnerabilities (CVE-2026-109618 and CVE-2026-109619) could allow malicious cyber actors to remotely execute code in PHP core, potentially compromising sensitive data and networks.

The FBI urges organizations to take the following steps now:

➡️ If an immediate update is not feasible it is recommended that organizations take the system offline until it can be fully mitigated.

➡️ Immediately update affected PHP installations following the guidance on https://t.co/rDrPSxB3zX. Inventory where PHP runs in your environment, prioritizing internet-facing systems and vendor products that bundle PHP.

➡️ Monitor web servers for suspicious activity, including PHP processes unexpectedly launching command shells or downloading files. Ensure appropriate process-monitoring capabilities are in place to help identify potential exploitation.

➡️ If you find signs of compromise, isolate affected systems, preserve your web server and PHP logs, and report it to your local FBI field office or https://t.co/iqgVZIbCru. Those reports help us identify the actors involved and warn other organizations before they become victims.

For the latest information, follow PHP’s announcement on https://t.co/rDrPSxB3zX, CERT-EU Security Advisory 2026-018, and CISA’s Known Exploited Vulnerabilities catalog.

[Jacob Ayokunle @jayrobzy]

Security nightmare. Patching...

[Andras Bacsai @heyandras]

Here is a full list of what you can do NOW for PHP2Shell (CVE-2026-109618 / CVE-2026-109619) as a temporary mitigation.

(generated and validated by LLM)

1️⃣ Do this first. In php.ini or the FPM pool, set:
session.upload_progress.enabled = 0
Reload PHP-FPM, then update PHP right after the release (21 Oct, 14:00 UTC).

2️⃣ Edge block until you patch. It blocks the PHPSESSID cookie and query (also lowercase and URL-encoded), and all multipart/form-data requests.
⚠️ File uploads stop working until you remove it.

☁️ Cloudflare (WAF custom rule, action Block):
(lower(url_decode(http.cookie)) contains "phpsessid") or (lower(url_decode(http.request.uri.query)) contains "phpsessid") or (any(lower(http.request.headers["content-type"][*])[*] contains "multipart/form-data"))

🟩 nginx (http {} context):
map "$http_cookie|$args|$content_type" $block_php2shell {
default 0;
"~*(?:p|%[57]0)(?:h|%[46]8)(?:p|%[57]0)(?:s|%[57]3)(?:e|%[46]5)(?:s|%[57]3)(?:s|%[57]3)(?:i|%[46]9)(?:d|%[46]4)" 1;
"~*multipart/form-data" 1;
}
In each server {} block:
if ($block_php2shell) { return 403; }

🔒 Caddy:
@php2shell expression `{header.Cookie}.matches("(?i)(?:p|%[57]0)(?:h|%[46]8)(?:p|%[57]0)(?:s|%[57]3)(?:e|%[46]5)(?:s|%[57]3)(?:s|%[57]3)(?:i|%[46]9)(?:d|%[46]4)") || {query}.matches("(?i)(?:p|%[57]0)(?:h|%[46]8)(?:p|%[57]0)(?:s|%[57]3)(?:e|%[46]5)(?:s|%[57]3)(?:s|%[57]3)(?:i|%[46]9)(?:d|%[46]4)") || {header.Content-Type}.matches("(?i)multipart/form-data")`
respond @php2shell 403

🚦 Traefik v3 (Coolify: Server > Proxy > Dynamic Configurations). Add this to the https router and also to a copy for the http entrypoint:
http:
routers:
block-php2shell:
rule: "HeaderRegexp(`Cookie`, `(?i)(?:p|%[57]0)(?:h|%[46]8)(?:p|%[57]0)(?:s|%[57]3)(?:e|%[46]5)(?:s|%[57]3)(?:s|%[57]3)(?:i|%[46]9)(?:d|%[46]4)`) || QueryRegexp(`PHPSESSID`, `.*`) || HeaderRegexp(`Content-Type`, `(?i)multipart/form-data`)"
priority: 100000
entryPoints: [https]
middlewares: [deny-all]
service: noop@internal
tls: {}
middlewares:
deny-all:
ipAllowList:
sourceRange: ["255.255.255.255/32"]

✅ Test:
curl -s -o /dev/null -w '%{http_code}\n' -H 'Cookie: PHPSESSID=x' https://your-app → 403
curl -s -o /dev/null -w '%{http_code}\n' -F a=b https://your-app → 403

The edge block does not protect direct origin access. Disable upload_progress and patch PHP.

[Jacob Ayokunle @jayrobzy]

@RobertJBye Interested

[Jacob Ayokunle @jayrobzy]

Are people still paying for Jetbrains IDE?

[Jacob Ayokunle @jayrobzy]

How do companies manage AI access for staff members? People are just connecting tools to anything possible