Which versions of sap-quarterly-report are malicious?

The following PyPI versions of sap-quarterly-report are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate sap-quarterly-report if I installed it?

sap-quarterly-report 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 sap-quarterly-report — how do I know if it already compromised me?

If sap-quarterly-report 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 sap-quarterly-report part of a known attack campaign?

Yes — sap-quarterly-report is associated with the 2026-08-ekx-report-utils 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 sap-quarterly-report across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sap-quarterly-report (version 1.0.0).

Malicious package

sap-quarterly-reportPyPI

Advisory published Aug 27, 2026Updated Aug 27, 2026

sap-quarterly-report is a confirmed malicious PyPI package (MAL-2026-14556) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sap-quarterly-report (PyPI)

MAL-2026-14556

Immediate action

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

pip uninstall sap-quarterly-report

What this malware does

During import, the package collects sensitive information and exfiltrates it using DNS queries.

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

Campaign: 2026-08-ekx-report-utils

Reasons (based on the campaign):

targetted-attack
exfiltration-generic
exfiltration-credentials

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2235bdf8263c08fede094c665d2fbc4e023a0f0c5e99631d70ae0685567b37ec

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for sap-quarterly-report (version 1.0.0).
If you installed it — respond
sap-quarterly-report 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 sap-quarterly-report 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. sap-quarterly-report on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-08-ekx-report-utils

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks sap-quarterly-report-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