<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Obsidian on The Coders Blog</title><link>https://thecodersblog.com/tag/obsidian/</link><description>Recent content in Obsidian on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 11 May 2026 03:54:32 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/obsidian/index.xml" rel="self" type="application/rss+xml"/><item><title>Obsidian Plugin Security: Trojan Deployment Risk</title><link>https://thecodersblog.com/obsidian-plugin-security-vulnerability-2026/</link><pubDate>Mon, 11 May 2026 03:54:32 +0000</pubDate><guid>https://thecodersblog.com/obsidian-plugin-security-vulnerability-2026/</guid><description>&lt;p&gt;The digital vault, a sanctuary for our thoughts, projects, and sensitive data, has always been a tempting target. Obsidian, with its powerful Markdown-based note-taking and knowledge management capabilities, has become the digital bedrock for countless individuals and professionals. Its extensibility through community plugins is a significant part of its allure, promising to tailor the application to an almost infinite array of workflows. However, this very extensibility, when coupled with social engineering, has recently revealed a stark and unsettling truth: even seemingly innocuous plugins can harbor devastating security risks, capable of turning your meticulously crafted digital sanctuary into an open gateway for attackers.&lt;/p&gt;</description></item></channel></rss>