Which versions of syntaxlogger are malicious?

The following PyPI versions of syntaxlogger are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate syntaxlogger if I installed it?

syntaxlogger is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed syntaxlogger — how do I know if it already compromised me?

If syntaxlogger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is syntaxlogger part of a known attack campaign?

Yes — syntaxlogger is associated with the 2026-05-syntaxlogger campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find syntaxlogger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for syntaxlogger (5 malicious versions).

Malicious package

syntaxloggerPyPI

Advisory published May 13, 2026Updated May 13, 2026

syntaxlogger is a confirmed malicious PyPI package (MAL-2026-3697) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in syntaxlogger (PyPI)

MAL-2026-3697

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall syntaxlogger

What this malware does

When using the provided functionality, code silently downloads archives with executables to a location excluded from A scanning, and then executes them. The remote content appears to be a legitimate application manipulated via DLL poisoning to perform malicious actions.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-05-syntaxlogger

Reasons (based on the campaign):

Downloads and executes a remote executable.
action-hidden-in-lib-usage
malware

Malicious versions

5 flagged

0.1.00.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

ebc8a65895fc09c10b6e6bf23926076ec575582e80e084616e6779b091df947d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for syntaxlogger (5 malicious versions).
If you installed it — respond
syntaxlogger is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If syntaxlogger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. syntaxlogger on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-syntaxlogger

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks syntaxlogger-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database