MalwarePublished 23 Sep 2026

memoryos (PyPI) · Malicious Code

Affects memoryosSource GCVE Database

Malicious package : remove memoryos and rotate any secrets on hosts that installed it.

Data as of 24 Sep 2026, 06:54 UTC

Classification

Malicious package

Published to PyPI · OSV MAL-2026-16475

What to do

Remove memoryos from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
PyPImemoryos	Affected =2.0.34	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A malicious version 2.0.34 of the MemoryOS Python package on PyPI was published containing a Go-based implant named sckit. This implant runs a background binary that collects various credential files from the user's home directory and exfiltrates them to attacker-controlled servers under skyleen.fr. It also includes functionality to propagate itself into other repositories and packages accessible with the stolen credentials. The implant uses encrypted communication with its command-and-control servers and deletes itself after execution. Additionally, the package's build backend can steal CI environment publishing tokens, enabling further compromise of downstream package publishing.

Impact

The implant steals a wide range of sensitive credentials from the user's home directory, including package manager credentials, Git credentials, SSH private keys, vault tokens, and cached tokens. These stolen credentials are sent to attacker-controlled infrastructure, enabling further compromise of developer environments and potentially other repositories and packages. The CI environment token theft allows attackers to hijack downstream package publishing workflows, increasing the scope of the supply-chain compromise. The implant's self-deletion and encrypted communications make detection and analysis more difficult.

Defensive guidance

Users should immediately stop using version 2.0.34 of the MemoryOS package and remove it from their environments. Audit and revoke any potentially compromised credentials, including package manager tokens, SSH keys, and CI environment tokens. Review CI/CD pipelines for unauthorized environment variable modifications or payload executions. Monitor for suspicious network connections to the indicated attacker domains. Check the vendor advisory or PyPI for updates or fixed versions before resuming use.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Sep 2026, 06:54 UTC

Technical details

References

Community reviews