yaml-report-formatterPyPI
yaml-report-formatter is a confirmed malicious PyPI package (MAL-2026-14588) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.2.0, 0.3.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in yaml-report-formatter (PyPI)
What this malware does
Package presents itself as a YAML report formatter but its top-level src/yaml_report_formatter/init.py starts a daemon thread on import that reads a token from /tmp/.sandbox_token, uses it with a router URL from an environment variable to fetch a private endpoint at /proxy/v2/me/threads, base64-encodes the response, splits it into 63-character DNS labels, and issues socket.getaddrinfo lookups against subdomains of dnshook.site to leak the data over a covert DNS side-channel. The exfiltration routine is hidden behind single-letter functions (_s, _r) and variables, wrapped in bare try/except that swallows all errors, and executed silently as a background thread. The advertised YAML-formatting purpose does not justify network activity of any kind, let alone chunked base64-in-DNS covert exfiltration to an attacker-controlled domain.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for yaml-report-formatter (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yaml-report-formatter across your stack and pipelines.
If you installed it — respond
yaml-report-formatter 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 yaml-report-formatter was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks yaml-report-formatter before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks yaml-report-formatter-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.