{"id":120,"date":"2026-03-26T14:41:55","date_gmt":"2026-03-26T14:41:55","guid":{"rendered":"https:\/\/911arabhac.com\/?p=120"},"modified":"2026-04-02T16:37:12","modified_gmt":"2026-04-02T16:37:12","slug":"the-security-risks-of-changing-package-owners","status":"publish","type":"post","link":"https:\/\/911arabhac.com\/ar\/the-security-risks-of-changing-package-owners\/","title":{"rendered":"\u0627\u0644\u0645\u062e\u0627\u0637\u0631 \u0627\u0644\u0623\u0645\u0646\u064a\u0629 \u0644\u062a\u063a\u064a\u064a\u0631 \u0645\u0627\u0644\u0643\u064a \u0627\u0644\u0637\u0631\u0648\u062f"},"content":{"rendered":"<h2 class=\"wp-block-heading\">A Hidden Threat in Plain Sight<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the world of <strong>ethical hacking<\/strong>, some of the most dangerous vulnerabilities aren\u2019t flashy zero-days or sophisticated exploits\u2014they\u2019re subtle, administrative changes that quietly open the door to massive breaches. One such overlooked risk is <strong>changing package ownership<\/strong> in open-source ecosystems.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Imagine relying on a widely used library that suddenly changes hands. The code looks the same, updates appear normal\u2014but behind the scenes, control has shifted. For attackers, this is a goldmine. For developers and organizations, it\u2019s a ticking time bomb.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This article dives deep into the security implications of changing package owners, why it\u2019s becoming a favorite attack vector, and how ethical hackers and developers can stay ahead of the threat.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding Package Ownership in Modern Development<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before we get into the risks, let\u2019s clarify what \u201cpackage ownership\u201d means.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In ecosystems like npm, PyPI, or RubyGems, <strong>package owners<\/strong> are individuals or teams who:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Publish updates<\/li>\n\n\n\n<li>Manage versions<\/li>\n\n\n\n<li>Control access permissions<\/li>\n\n\n\n<li>Maintain the codebase<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ownership can change due to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Maintainer burnout<\/li>\n\n\n\n<li>Project abandonment<\/li>\n\n\n\n<li>Company acquisitions<\/li>\n\n\n\n<li>Transfers of responsibility<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">While often legitimate, these transitions can introduce serious vulnerabilities.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Comparison: Legitimate Ownership Change vs. Malicious Takeover<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Aspect<\/th><th>Legitimate Transfer<\/th><th>Malicious Takeover<\/th><\/tr><tr><td>Intent<\/td><td>Maintain or improve project<\/td><td>Inject malicious code<\/td><\/tr><tr><td>Transparency<\/td><td>Public announcements<\/td><td>Silent or unclear<\/td><\/tr><tr><td>Code Changes<\/td><td>Gradual and documented<\/td><td>Sudden or obfuscated<\/td><\/tr><tr><td>Community Trust<\/td><td>Maintained or improved<\/td><td>Quickly eroded<\/td><\/tr><tr><td>Risk Level<\/td><td>Low to moderate<\/td><td>Extremely high<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The danger lies in how similar these scenarios can appear\u2014especially at first glance.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Why Changing Package Owners Is a Security Risk<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Supply Chain Attacks Become Easier<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One of the biggest concerns in <strong>ethical hacking<\/strong> today is <strong>software supply chain attacks<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When a package owner changes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Attackers can gain publishing rights<\/li>\n\n\n\n<li>Malicious code can be introduced in updates<\/li>\n\n\n\n<li>Thousands (or millions) of downstream users are affected instantly<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A famous example is the \u201cevent-stream\u201d incident in npm, where a trusted package was handed over and later compromised.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">2. Trust Is Inherited, Not Earned<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s the critical flaw: <strong>new owners inherit trust automatically<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Users don\u2019t re-evaluate a package just because ownership changes. They assume:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The package is still safe<\/li>\n\n\n\n<li>Updates are trustworthy<\/li>\n\n\n\n<li>Maintainers are credible<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Attackers exploit this blind trust to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Insert backdoors<\/li>\n\n\n\n<li>Steal credentials<\/li>\n\n\n\n<li>Deploy crypto miners or malware<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">3. Lack of Visibility in Ownership Changes<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Most developers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Don\u2019t monitor ownership changes<\/li>\n\n\n\n<li>Don\u2019t receive alerts when maintainers change<\/li>\n\n\n\n<li>Rarely audit package metadata<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This creates a dangerous gap where malicious actors can operate undetected.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">4. Dependency Chains Amplify the Damage<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Modern applications rely heavily on dependencies.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A single compromised package can affect:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dozens of direct dependencies<\/li>\n\n\n\n<li>Hundreds of indirect dependencies<\/li>\n\n\n\n<li>Entire ecosystems<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This cascading effect makes ownership changes particularly risky.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">5. Abandoned Packages Are Prime Targets<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Many open-source projects are abandoned over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Attackers often:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Identify unmaintained packages<\/li>\n\n\n\n<li>Request ownership or exploit weak access controls<\/li>\n\n\n\n<li>Revive the package with malicious intent<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">From an <strong>ethical hacking<\/strong> standpoint, these are low-effort, high-impact opportunities.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Real-World Attack Patterns Ethical Hackers Watch For<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ethical hackers often look for patterns that signal potential compromise:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Suspicious Indicators<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Sudden ownership transfer without announcement<\/li>\n\n\n\n<li>New maintainer with no prior contributions<\/li>\n\n\n\n<li>Rapid release of new versions<\/li>\n\n\n\n<li>Obfuscated or minified code updates<\/li>\n\n\n\n<li>Changes unrelated to the package\u2019s purpose<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Behavioral Red Flags<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increased network activity in a previously offline package<\/li>\n\n\n\n<li>Data exfiltration attempts<\/li>\n\n\n\n<li>Unexpected dependency additions<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Key Insights: What Makes This Threat Unique?<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. It\u2019s Social Engineering at Scale<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Changing package ownership isn\u2019t just a technical issue\u2014it\u2019s <strong>a social engineering attack on the developer community<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Attackers rely on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Trust<\/li>\n\n\n\n<li>Reputation<\/li>\n\n\n\n<li>Developer complacency<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">2. Traditional Security Tools Often Miss It<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Most security tools focus on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Known vulnerabilities (CVEs)<\/li>\n\n\n\n<li>Static code analysis<\/li>\n\n\n\n<li>Runtime behavior<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">But ownership changes are <strong>metadata-level events<\/strong>, which often go unnoticed.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">3. It Exploits Open-Source Culture<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Open-source thrives on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Collaboration<\/li>\n\n\n\n<li>Trust<\/li>\n\n\n\n<li>Accessibility<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Ironically, these strengths can become weaknesses when exploited.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">How Ethical Hacking Helps Mitigate These Risks<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Ethical hacking plays a critical role in identifying and preventing these threats.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Proactive Dependency Auditing<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ethical hackers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Audit dependency trees<\/li>\n\n\n\n<li>Track maintainers and ownership history<\/li>\n\n\n\n<li>Flag unusual changes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Tools like:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>npm audit<\/li>\n\n\n\n<li>Snyk<\/li>\n\n\n\n<li>Dependabot<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">\u2026help automate parts of this process.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">2. Monitoring Ownership Changes<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A best practice is to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monitor package registries for ownership updates<\/li>\n\n\n\n<li>Set alerts for critical dependencies<\/li>\n\n\n\n<li>Use third-party monitoring tools<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This adds a layer of visibility often missing in development workflows.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">3. Code Review Beyond the Surface<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Ethical hackers go deeper by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reviewing diffs between versions<\/li>\n\n\n\n<li>Analyzing obfuscated code<\/li>\n\n\n\n<li>Checking for hidden payloads<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">4. Simulating Supply Chain Attacks<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Penetration testers often simulate:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Malicious package updates<\/li>\n\n\n\n<li>Dependency poisoning<\/li>\n\n\n\n<li>Credential harvesting via libraries<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This helps organizations understand their exposure.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Best Practices for Developers and Organizations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udd12 Secure Your Dependencies<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pin package versions (avoid automatic updates)<\/li>\n\n\n\n<li>Use lock files (package-lock.json, Pipfile.lock)<\/li>\n\n\n\n<li>Regularly audit dependencies<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udc40 Verify Maintainers<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Before trusting updates:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Check contributor history<\/li>\n\n\n\n<li>Review GitHub activity<\/li>\n\n\n\n<li>Look for sudden ownership changes<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83e\udde0 Adopt a Zero-Trust Approach<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Treat every dependency as potentially untrusted:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Validate updates before deployment<\/li>\n\n\n\n<li>Use sandbox environments<\/li>\n\n\n\n<li>Monitor runtime behavior<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udce6 Use Trusted Registries and Mirrors<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Consider:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Private package registries<\/li>\n\n\n\n<li>Verified package sources<\/li>\n\n\n\n<li>Internal mirrors for critical dependencies<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">\ud83d\udcca Example: Risk Assessment Table<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td>Risk Factor<\/td><td>Impact Level<\/td><td>Mitigation Strategy<\/td><\/tr><tr><td>Ownership Change<\/td><td>High<\/td><td>Monitor and verify maintainers<\/td><\/tr><tr><td>Abandoned Package<\/td><td>High<\/td><td>Replace or fork dependency<\/td><\/tr><tr><td>Rapid Updates<\/td><td>Medium<\/td><td>Review version diffs<\/td><\/tr><tr><td>Unknown Maintainer<\/td><td>High<\/td><td>Investigate background<\/td><\/tr><tr><td>New Dependencies Added<\/td><td>Medium<\/td><td>Audit dependency tree<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Visual Breakdown: How a Package Takeover Happens<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\ud83d\udcf8 <strong>Suggested Infographic:<\/strong><br>A step-by-step diagram showing:<\/p>\n\n\n\n<ol start=\"1\" class=\"wp-block-list\">\n<li>Maintainer abandons package<\/li>\n\n\n\n<li>Attacker requests ownership<\/li>\n\n\n\n<li>Ownership granted<\/li>\n\n\n\n<li>Malicious update released<\/li>\n\n\n\n<li>Users automatically install update<\/li>\n\n\n\n<li>Systems compromised<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">(Use this visual to reinforce how simple yet dangerous the process is.)<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">The Future of Package Security<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As software ecosystems grow, this issue is gaining attention.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Emerging solutions include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Signed packages and cryptographic verification<\/strong><\/li>\n\n\n\n<li><strong>Maintainer reputation scoring<\/strong><\/li>\n\n\n\n<li><strong>Automated anomaly detection in package updates<\/strong><\/li>\n\n\n\n<li><strong>Decentralized package management systems<\/strong><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">However, no tool can replace vigilance.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion: Trust, But Verify<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Changing package owners may seem like a routine administrative task\u2014but in today\u2019s threat landscape, it\u2019s a potential gateway to large-scale compromise.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From an <strong>ethical hacking<\/strong> perspective, this is a classic example of how attackers exploit trust rather than technology.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The takeaway is simple:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Don\u2019t blindly trust dependencies<\/li>\n\n\n\n<li>Monitor what you install<\/li>\n\n\n\n<li>Stay informed about changes in your software supply chain<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Call-to-Action<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Have you ever audited your dependencies for ownership changes?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Take a moment today to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Review your top dependencies<\/li>\n\n\n\n<li>Check who maintains them<\/li>\n\n\n\n<li>Set up monitoring tools<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If you found this guide helpful, share it with your team or fellow developers\u2014and explore more content on <strong>ethical hacking<\/strong> and secure development practices to stay one step ahead of evolving threats.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>","protected":false},"excerpt":{"rendered":"<p>A Hidden Threat in Plain Sight In the world of ethical hacking, some of the most dangerous vulnerabilities aren\u2019t flashy zero-days or sophisticated exploits\u2014they\u2019re subtle, administrative changes that quietly open the door to massive breaches. One such overlooked risk is changing package ownership in open-source ecosystems. Imagine relying on a widely used library that suddenly [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":121,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-120","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/posts\/120","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/comments?post=120"}],"version-history":[{"count":3,"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/posts\/120\/revisions"}],"predecessor-version":[{"id":170,"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/posts\/120\/revisions\/170"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/media\/121"}],"wp:attachment":[{"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/media?parent=120"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/categories?post=120"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/911arabhac.com\/ar\/wp-json\/wp\/v2\/tags?post=120"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}