{"id":3962,"date":"2026-08-05T10:00:21","date_gmt":"2026-08-05T09:00:21","guid":{"rendered":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/"},"modified":"2026-08-05T10:00:23","modified_gmt":"2026-08-05T09:00:23","slug":"chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm","status":"publish","type":"post","link":"https:\/\/www.whysecurity.it\/en\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/","title":{"rendered":"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm"},"content":{"rendered":"<p>Microsoft Threat Intelligence has identified a large-scale supply chain attack impacting over 400 npm packages, including critical ecosystem dependencies like keyv and flat-cache. The campaign leverages a sophisticated, self-propagating worm variant dubbed &#8216;Mini Shai-Hulud&#8217;, which utilizes heavily obfuscated Bun-based JavaScript payloads.<\/p>\n<h3>Attack Methodology<\/h3>\n<p>The malware functions by exploiting npm preinstall lifecycle hooks, executing malicious code on developer workstations and CI\/CD runners before security checks can initiate. Once active, the worm performs several critical tasks:<\/p>\n<ul>\n<li><strong>Credential Theft:<\/strong> Scans local environments for npm, GitHub, cloud (AWS), Kubernetes, and HashiCorp Vault secrets.<\/li>\n<li><strong>Propagation:<\/strong> Uses stolen tokens to automatically download packages, inject the malicious payload, increment version numbers, and republish the compromised packages to the npm registry.<\/li>\n<li><strong>Persistence:<\/strong> Injects malicious configurations into Claude and Visual Studio Code settings within repositories to ensure re-infection.<\/li>\n<li><strong>Exfiltration:<\/strong> Data is encrypted and exfiltrated via HTTPS, with GitHub repositories serving as a fallback channel.<\/li>\n<\/ul>\n<h3>Impact and Mitigation<\/h3>\n<p>Organizations should treat any environment where these packages were installed as compromised. This includes developer workstations and automated build pipelines.<\/p>\n<p><strong>Recommended actions for remediation:<\/strong><\/p>\n<ul>\n<li><strong>Rotate Credentials:<\/strong> Immediately revoke and rotate all secrets that were accessible to the affected systems.<\/li>\n<li><strong>Clean Rebuilds:<\/strong> Purge npm\/yarn caches and rebuild infrastructure from trusted, known-good sources.<\/li>\n<li><strong>Hardening:<\/strong> Update to npm CLI v12 to utilize &#8216;min-release-age&#8217; features and review GitHub Actions OIDC publishing permissions to prevent unauthorized automated releases.<\/li>\n<li><strong>Detection:<\/strong> Microsoft Defender XDR provides specific detections for &#8216;ShaiLoader&#8217;, &#8216;MalBun&#8217;, and &#8216;ShaiWorm&#8217;. Security teams should monitor for the identified Indicators of Compromise (IOCs), such as the setup.mjs loader and connections to domains like npm-cache[.]com.<\/li>\n<\/ul>\n<p>This incident highlights the critical need for robust CI\/CD security and proactive monitoring of supply chain dependencies to prevent widespread, automated propagation of malicious code.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft Threat Intelligence has identified a large-scale supply chain attack impacting over 400 npm packages, including critical ecosystem dependencies like keyv and flat-cache. The campaign leverages a sophisticated, self-propagating worm variant dubbed &#8216;Mini Shai-Hulud&#8217;, which utilizes heavily obfuscated Bun-based JavaScript payloads. Attack Methodology The malware functions by exploiting npm preinstall lifecycle hooks, executing malicious code [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3963,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3962","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cybersecurity"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm - CyberSecurity Experts<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.whysecurity.it\/en\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm - CyberSecurity Experts\" \/>\n<meta property=\"og:description\" content=\"Microsoft Threat Intelligence has identified a large-scale supply chain attack impacting over 400 npm packages, including critical ecosystem dependencies like keyv and flat-cache. The campaign leverages a sophisticated, self-propagating worm variant dubbed &#8216;Mini Shai-Hulud&#8217;, which utilizes heavily obfuscated Bun-based JavaScript payloads. Attack Methodology The malware functions by exploiting npm preinstall lifecycle hooks, executing malicious code [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.whysecurity.it\/en\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/\" \/>\n<meta property=\"og:site_name\" content=\"CyberSecurity Experts\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/whysec\" \/>\n<meta property=\"article:published_time\" content=\"2026-08-05T09:00:21+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-08-05T09:00:23+00:00\" \/>\n<meta name=\"author\" content=\"whysecurity\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"whysecurity\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/\"},\"author\":{\"name\":\"whysecurity\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#\\\/schema\\\/person\\\/aa3b7e95e9fd51fd7f39d48911fdfe0a\"},\"headline\":\"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm\",\"datePublished\":\"2026-08-05T09:00:21+00:00\",\"dateModified\":\"2026-08-05T09:00:23+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/\"},\"wordCount\":293,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.whysecurity.it\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/immagine-2.jpg\",\"articleSection\":[\"Cybersecurity\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/\",\"url\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/\",\"name\":\"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm - CyberSecurity Experts\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.whysecurity.it\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/immagine-2.jpg\",\"datePublished\":\"2026-08-05T09:00:21+00:00\",\"dateModified\":\"2026-08-05T09:00:23+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.whysecurity.it\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/immagine-2.jpg\",\"contentUrl\":\"https:\\\/\\\/www.whysecurity.it\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/immagine-2.jpg\",\"width\":940,\"height\":627},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.whysecurity.it\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#website\",\"url\":\"https:\\\/\\\/www.whysecurity.it\\\/\",\"name\":\"WhySecurity\",\"description\":\"Cyber Security Network Services\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.whysecurity.it\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#organization\",\"name\":\"WhySecurity\",\"url\":\"https:\\\/\\\/www.whysecurity.it\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/tempnewweb.whysecurity.it\\\/wp-content\\\/uploads\\\/2025\\\/10\\\/logo_white.png\",\"contentUrl\":\"https:\\\/\\\/tempnewweb.whysecurity.it\\\/wp-content\\\/uploads\\\/2025\\\/10\\\/logo_white.png\",\"width\":500,\"height\":91,\"caption\":\"WhySecurity\"},\"image\":{\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/whysec\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.whysecurity.it\\\/#\\\/schema\\\/person\\\/aa3b7e95e9fd51fd7f39d48911fdfe0a\",\"name\":\"whysecurity\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ca59ad0cd8de5b2222178a2dfd751991a577b51363cd53356ed10b18f5c54a2c?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ca59ad0cd8de5b2222178a2dfd751991a577b51363cd53356ed10b18f5c54a2c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ca59ad0cd8de5b2222178a2dfd751991a577b51363cd53356ed10b18f5c54a2c?s=96&d=mm&r=g\",\"caption\":\"whysecurity\"},\"sameAs\":[\"https:\\\/\\\/whysecurity.it\"],\"url\":\"https:\\\/\\\/www.whysecurity.it\\\/en\\\/author\\\/whysecurity\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm - CyberSecurity Experts","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.whysecurity.it\/en\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/","og_locale":"en_US","og_type":"article","og_title":"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm - CyberSecurity Experts","og_description":"Microsoft Threat Intelligence has identified a large-scale supply chain attack impacting over 400 npm packages, including critical ecosystem dependencies like keyv and flat-cache. The campaign leverages a sophisticated, self-propagating worm variant dubbed &#8216;Mini Shai-Hulud&#8217;, which utilizes heavily obfuscated Bun-based JavaScript payloads. Attack Methodology The malware functions by exploiting npm preinstall lifecycle hooks, executing malicious code [&hellip;]","og_url":"https:\/\/www.whysecurity.it\/en\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/","og_site_name":"CyberSecurity Experts","article_publisher":"https:\/\/www.facebook.com\/whysec","article_published_time":"2026-08-05T09:00:21+00:00","article_modified_time":"2026-08-05T09:00:23+00:00","author":"whysecurity","twitter_card":"summary_large_image","twitter_misc":{"Written by":"whysecurity","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/#article","isPartOf":{"@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/"},"author":{"name":"whysecurity","@id":"https:\/\/www.whysecurity.it\/#\/schema\/person\/aa3b7e95e9fd51fd7f39d48911fdfe0a"},"headline":"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm","datePublished":"2026-08-05T09:00:21+00:00","dateModified":"2026-08-05T09:00:23+00:00","mainEntityOfPage":{"@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/"},"wordCount":293,"commentCount":0,"publisher":{"@id":"https:\/\/www.whysecurity.it\/#organization"},"image":{"@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/#primaryimage"},"thumbnailUrl":"https:\/\/www.whysecurity.it\/wp-content\/uploads\/2026\/08\/immagine-2.jpg","articleSection":["Cybersecurity"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/","url":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/","name":"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm - CyberSecurity Experts","isPartOf":{"@id":"https:\/\/www.whysecurity.it\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/#primaryimage"},"image":{"@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/#primaryimage"},"thumbnailUrl":"https:\/\/www.whysecurity.it\/wp-content\/uploads\/2026\/08\/immagine-2.jpg","datePublished":"2026-08-05T09:00:21+00:00","dateModified":"2026-08-05T09:00:23+00:00","breadcrumb":{"@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/#primaryimage","url":"https:\/\/www.whysecurity.it\/wp-content\/uploads\/2026\/08\/immagine-2.jpg","contentUrl":"https:\/\/www.whysecurity.it\/wp-content\/uploads\/2026\/08\/immagine-2.jpg","width":940,"height":627},{"@type":"BreadcrumbList","@id":"https:\/\/www.whysecurity.it\/chaindrop-supply-chain-compromise-anatomy-of-a-self-propagating-worm\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.whysecurity.it\/"},{"@type":"ListItem","position":2,"name":"ChainDrop Supply Chain Compromise: Anatomy of a Self-Propagating Worm"}]},{"@type":"WebSite","@id":"https:\/\/www.whysecurity.it\/#website","url":"https:\/\/www.whysecurity.it\/","name":"WhySecurity","description":"Cyber Security Network Services","publisher":{"@id":"https:\/\/www.whysecurity.it\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.whysecurity.it\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.whysecurity.it\/#organization","name":"WhySecurity","url":"https:\/\/www.whysecurity.it\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.whysecurity.it\/#\/schema\/logo\/image\/","url":"https:\/\/tempnewweb.whysecurity.it\/wp-content\/uploads\/2025\/10\/logo_white.png","contentUrl":"https:\/\/tempnewweb.whysecurity.it\/wp-content\/uploads\/2025\/10\/logo_white.png","width":500,"height":91,"caption":"WhySecurity"},"image":{"@id":"https:\/\/www.whysecurity.it\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/whysec"]},{"@type":"Person","@id":"https:\/\/www.whysecurity.it\/#\/schema\/person\/aa3b7e95e9fd51fd7f39d48911fdfe0a","name":"whysecurity","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/ca59ad0cd8de5b2222178a2dfd751991a577b51363cd53356ed10b18f5c54a2c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/ca59ad0cd8de5b2222178a2dfd751991a577b51363cd53356ed10b18f5c54a2c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ca59ad0cd8de5b2222178a2dfd751991a577b51363cd53356ed10b18f5c54a2c?s=96&d=mm&r=g","caption":"whysecurity"},"sameAs":["https:\/\/whysecurity.it"],"url":"https:\/\/www.whysecurity.it\/en\/author\/whysecurity\/"}]}},"_links":{"self":[{"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/posts\/3962","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/comments?post=3962"}],"version-history":[{"count":1,"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/posts\/3962\/revisions"}],"predecessor-version":[{"id":3964,"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/posts\/3962\/revisions\/3964"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/media\/3963"}],"wp:attachment":[{"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/media?parent=3962"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/categories?post=3962"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whysecurity.it\/en\/wp-json\/wp\/v2\/tags?post=3962"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}