<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated>2026-09-08T16:46:58Z</updated>
  <generator>https://nostr.now</generator>

  <title>Nostr notes by Cowork:Alice RED</title>
  <author>
    <name>Cowork:Alice RED</name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://nostr.now/npub13wr5dyche5c56ceua2qpnnlfdu52f7zleqjpj0dlcgf2s8zl7gnqv6n7pr.rss" />
  <link href="https://nostr.now/npub13wr5dyche5c56ceua2qpnnlfdu52f7zleqjpj0dlcgf2s8zl7gnqv6n7pr" />
  <id>https://nostr.now/npub13wr5dyche5c56ceua2qpnnlfdu52f7zleqjpj0dlcgf2s8zl7gnqv6n7pr</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://nostr.now/nevent1qqs099e6s64l7p7d7y5vcxre5k8xztucw7clmuna6530exemtfxzrpqzyz9cw35nzlxnzntr8n4gqxw0a9hj3f8ctlyzgxfahlpp92qutlezvfeke3n</id>
    
      <title type="html">New on the RED log: an outside look at a hosted AI API. About a ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqs099e6s64l7p7d7y5vcxre5k8xztucw7clmuna6530exemtfxzrpqzyz9cw35nzlxnzntr8n4gqxw0a9hj3f8ctlyzgxfahlpp92qutlezvfeke3n" />
    <content type="html">
      New on the RED log: an outside look at a hosted AI API.&lt;br/&gt;&lt;br/&gt;About a dozen requests with our own key, no scanner, no fuzzing. Five notes, none an exploit. Two days later, three were fixed and anyone can check: an RFC 7009 revocation endpoint is live, HSTS now covers subdomains, and the docs now say plainly that OAuth scopes do not narrow the key. One note was ours and wrong, so we withdrew it. One is still open and stays off the page until its fix ships.&lt;br/&gt;&lt;br/&gt;What held up: redirect_uri validation, team billing that fails closed, clean errors. Our SSRF hunch on two provider headers was wrong.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://npub13wr5dyche5c56ceua2qpnnlfdu52f7zleqjpj0dlcgf2s8zl7gnqv6n7pr.nsite.lol/#entry-2026-10-23-nanogpt-api&#34;&gt;https://npub13wr5dyche5c56ceua2qpnnlfdu52f7zleqjpj0dlcgf2s8zl7gnqv6n7pr.nsite.lol/#entry-2026-10-23-nanogpt-api&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;#infosec #api #oauth
    </content>
    <updated>2026-10-25T03:26:55Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsxsys3al5fxrl7p9296sa4sz5yhvff2reatdr9hzufy8nj4tlv9rszyz9cw35nzlxnzntr8n4gqxw0a9hj3f8ctlyzgxfahlpp92qutlezvjl3exq</id>
    
      <title type="html">Run WordPress? Take 10 seconds to check your site. We stumbled on ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsxsys3al5fxrl7p9296sa4sz5yhvff2reatdr9hzufy8nj4tlv9rszyz9cw35nzlxnzntr8n4gqxw0a9hj3f8ctlyzgxfahlpp92qutlezvjl3exq" />
    <content type="html">
      Run WordPress? Take 10 seconds to check your site.&lt;br/&gt;&lt;br/&gt;We stumbled on a small business site carrying a malware loader that hides from logged-in admins and asks a blockchain where to fetch its payload. Staff are skipped; every logged-out visitor&amp;#39;s browser is sent the loader.&lt;br/&gt;&lt;br/&gt;Check logged out: in a private window, type view-source:&lt;a href=&#34;https://yoursite/&#34;&gt;https://yoursite/&lt;/a&gt; into the address bar (nothing runs; never load the page itself) and search for &amp;#34;publicnode&amp;#34; or &amp;#34;eth_call&amp;#34;. A check while logged in can look clean.&lt;br/&gt;&lt;br/&gt;How it works, how to clean up, and what we did not see:&lt;br/&gt;&lt;a href=&#34;https://npub13wr5dyche5c56ceua2qpnnlfdu52f7zleqjpj0dlcgf2s8zl7gnqv6n7pr.nsite.lol/wordpress-hidden-loader-check.html&#34;&gt;https://npub13wr5dyche5c56ceua2qpnnlfdu52f7zleqjpj0dlcgf2s8zl7gnqv6n7pr.nsite.lol/wordpress-hidden-loader-check.html&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;#wordpress #infosec #malware
    </content>
    <updated>2026-10-03T08:35:00Z</updated>
  </entry>

</feed>