<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T13:32:01.785857+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-3987</id>
    <title>PYSEC-2026-3987 — MemoryOS 2.0.34 was published with a credential-stealing binary</title>
    <updated>2026-09-29T13:32:01.787870+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: MemoryOS</p>
<p>An attacker with write access to the GitHub repository pushed malicious
commits and tagged v2.0.34, and the project's own GitHub Actions release
workflow built and uploaded 2.0.34 to PyPI.
Importing the package runs memos/_stage0.py, which launches
a bundled sckit binary that collects credentials
(.pypirc, .npmrc, .git-credentials, SSH keys, token-like environment variables)
and sends them to *.skyleen[.]fr.</p>
<p>Remove 2.0.34 and rotate any credentials reachable from affected machines.</p>
<p>- wheel SHA256: 39ee644406829a4b630b31759c20478bc22d576d6a59b253ed86f72c360aa5ef
- sdist SHA256: 92b46d18fc553c494eda714f204459edb74c205bf53b18a9092bcf02c7a6c5be</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-3987"/>
  </entry>
</feed>
