<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss.xsl" type="text/xsl"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Feed | Moskic</title><description>Project, notes, links, and thoughts from my corner of the internet</description><link>http://feed.moskic.com</link><item><title>Recently I’ve been learning ESP32 development and made a voice recorder firmware that runs on the Cardputer ADV. Maybe it’s the most powerful recorder firmware for the Cardputer ADV? （Since nobody else seems to have made one XD）</title><link>http://feed.moskic.com/posts/7</link><guid isPermaLink="true">http://feed.moskic.com/posts/7</guid><pubDate>Fri, 19 Jun 2026 11:57:23 GMT</pubDate><content:encoded>Recently I’ve been learning ESP32 development and made a voice recorder firmware that runs on the Cardputer ADV. Maybe it’s the most powerful recorder firmware for the Cardputer ADV? （Since nobody else seems to have made one XD）&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;https://github.com/Moskic/cardputer-adv-recorder&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot; title=&quot;https://github.com/Moskic/cardputer-adv-recorder&quot;&gt;https://github.com/Moskic/cardputer-adv-recorder&lt;/a&gt;&lt;a class=&quot;tgme_widget_message_link_preview&quot; href=&quot;https://github.com/Moskic/cardputer-adv-recorder&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot; title=&quot;A voice recorder and WAV player firmware for the M5Stack Cardputer ADV - Moskic/cardputer-adv-recorder&quot;&gt;
  
  &lt;div class=&quot;link_preview_site_name accent_color&quot;&gt;GitHub&lt;/div&gt;
  &lt;img class=&quot;link_preview_image&quot; alt=&quot;GitHub - Moskic/cardputer-adv-recorder: A voice recorder and WAV player firmware for the M5Stack Cardputer ADV&quot; src=&quot;/static/https://cdn4.telesco.pe/file/pfrHkKkft44FR4yY9kYN6RLs1kGPVUHMH97wXQ5Cz1rPWALpNPyLDcZwb60G5A1RBoVxskQXo_FHAzwfItxAVUeOXroAwEqTCyVMtxmLLvz1L5xTAO085kohQdJ2DjkC6tTm1G8RQ0ERQ8oQTEWXl0-mmlv3krUHEMdI-cihvhX_hQLf9tXM8OJBAwBTuaWxM2XagN-cxMBwHHa3d5196486XT2RqsNntUFch1-YSel7pDKWTqqQ5bGCCcl5b561K3uoijb6saQWSmLQPGDmuoQkNPvxf0-ekslgJkY8OUgY_mUC8J3h4kr_EuUIEnCgupusBcUvyVLv7GPZdi0b2g.jpg&quot; width=&quot;1200&quot; height=&quot;630&quot; loading=&quot;eager&quot; /&gt;
  &lt;div class=&quot;link_preview_title&quot;&gt;GitHub - Moskic/cardputer-adv-recorder: A voice recorder and WAV player firmware for the M5Stack Cardputer ADV&lt;/div&gt;
  &lt;div class=&quot;link_preview_description&quot;&gt;A voice recorder and WAV player firmware for the M5Stack Cardputer ADV - Moskic/cardputer-adv-recorder&lt;/div&gt;
&lt;/a&gt;</content:encoded></item><item><title>My global guidance for Codex: LinkInspired by andrej-karpathy-skills</title><link>http://feed.moskic.com/posts/6</link><guid isPermaLink="true">http://feed.moskic.com/posts/6</guid><pubDate>Wed, 17 Jun 2026 08:50:32 GMT</pubDate><content:encoded>My &lt;b&gt;global guidance&lt;/b&gt; for Codex: &lt;a href=&quot;https://raw.githubusercontent.com/Moskic/scripts/main/Codex/AGENTS.md&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot; title=&quot;Link&quot;&gt;&lt;b&gt;Link&lt;/b&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Inspired by &lt;a href=&quot;https://github.com/multica-ai/andrej-karpathy-skills&quot; target=&quot;_blank&quot; rel=&quot;noopener&quot; title=&quot;andrej-karpathy-skills&quot;&gt;andrej-karpathy-skills&lt;/a&gt;</content:encoded></item><item><title>I recently handled a security incident involving an old Nezha Dashboard instance.The root cause was a critical Nezha vulnerability: GHSA-5c25-7vpj-9mqh. My dashboard was running v2.0.7, which was affected.Attack flow:1. Attacker accessed:/dashboard../data/config.yaml2. Dashboard config was exposed3. JWT / agent secrets were leaked4. Attacker forged admin access5. Malicious cron jobs were created through Nezha6. All connected agents started scanning servers for secrets7. Results were sent to external webhook endpointsSuspicious commands looked like:grep -rn &apos;AKIA|sk-ant|sk-proj|AIzaSy|github_pat_&apos; /root /home /opt /etc /app /var /data /tmpcurl </title><link>http://feed.moskic.com/posts/4</link><guid isPermaLink="true">http://feed.moskic.com/posts/4</guid><pubDate>Tue, 16 Jun 2026 01:10:13 GMT</pubDate><content:encoded>I recently handled a security incident involving an old Nezha Dashboard instance.&lt;br /&gt;&lt;br /&gt;The root cause was a critical Nezha vulnerability: GHSA-5c25-7vpj-9mqh. My dashboard was running v2.0.7, which was affected.&lt;br /&gt;&lt;br /&gt;Attack flow:&lt;br /&gt;&lt;br /&gt;1. Attacker accessed:&lt;code&gt;&lt;br /&gt;/dashboard../data/config.yaml&lt;br /&gt;&lt;/code&gt;&lt;br /&gt;2. Dashboard config was exposed&lt;br /&gt;&lt;br /&gt;3. JWT / agent secrets were leaked&lt;br /&gt;&lt;br /&gt;4. Attacker forged admin access&lt;br /&gt;&lt;br /&gt;5. Malicious cron jobs were created through Nezha&lt;br /&gt;&lt;br /&gt;6. All connected agents started scanning servers for secrets&lt;br /&gt;&lt;br /&gt;7. Results were sent to external webhook endpoints&lt;br /&gt;&lt;br /&gt;Suspicious commands looked like:&lt;br /&gt;&lt;code&gt;&lt;br /&gt;grep -rn &apos;AKIA|sk-ant|sk-proj|AIzaSy|github_pat_&apos; /root /home /opt /etc /app /var /data /tmp&lt;br /&gt;&lt;br /&gt;curl http://169.254.169.254/...&lt;br /&gt;&lt;/code&gt;&lt;br /&gt;Impact:&lt;br /&gt;&lt;br /&gt;• Nezha JWT and agent secrets should be considered leaked  &lt;br /&gt;• All connected nodes should be treated as exposed  &lt;br /&gt;• Any API keys, cloud credentials, SSH keys, TLS keys, or tokens on those servers should be rotated  &lt;br /&gt;&lt;br /&gt;Recommendations:&lt;br /&gt;&lt;br /&gt;• Upgrade Nezha immediately, at least to v2.0.13+  &lt;br /&gt;• Stop all old agents  &lt;br /&gt;• Re-register every node with new secrets  &lt;br /&gt;• Do not reuse old config.yaml, SQLite DB, agent secret, or UUIDs  &lt;br /&gt;• Do not expose the dashboard directly to the public Internet  &lt;br /&gt;• Rotate passwords, SSH keys, API tokens, and TLS certificates  &lt;br /&gt;&lt;br /&gt;Lesson learned:&lt;br /&gt;&lt;br /&gt;A monitoring dashboard with remote command execution is not “just a dashboard”. Treat it like critical infrastructure.</content:encoded></item><item><title>Hello World 🌍</title><link>http://feed.moskic.com/posts/2</link><guid isPermaLink="true">http://feed.moskic.com/posts/2</guid><pubDate>Mon, 15 Jun 2026 12:07:22 GMT</pubDate><content:encoded>Hello World &lt;i class=&quot;emoji&quot;&gt;&lt;b&gt;🌍&lt;/b&gt;&lt;/i&gt;</content:encoded></item></channel></rss>