GCVE-110-OSM-2026-12072

Malicious Python package containing an encrypted DNS payload loader. This package is part of the "lurves-agent" campaign along with other PyPI packages like openaii and transfomers. The existing package report identifies a PTH file that triggers the loader during Python initialization. When invoked, the loader retrieves an encrypted Python stage from DNS TXT records, authenticates and decrypts it, and executes it in memory. The remote stage was not retrieved, so its final behavior remains unknown. Static analysis of platform-telemetry-client.payload (5,145 bytes, 121 lines); no sample code was executed and no payload infrastructure was contacted. The existing package report records PTH-based startup execution; the standalone artifact defines bootstrap() but does not call it, and the PTH file was not supplied for this analysis. Lines 14-19 encode the payload domain and a 32-byte key using Base64 plus XOR 0x5A. Lines 71-92 implement DNS TXT queries over IPv4 UDP port 53 to a hardcoded public resolver, using transaction ID 0x1a2b and a six-second per-query timeout. The public resolver is legitimate infrastructure, not a verified malicious IOC. Lines 94-108 query the n-prefixed payload domain for a decimal chunk count, then query zero-based decimal-index subdomains and concatenate the first TXT answer from each available response. The assembled Base64 data consists of a 12-byte nonce, ciphertext, and a trailing 16-byte authentication tag. The embedded AES-256-GCM implementation authenticates and decrypts the payload without additional authenticated data, then decodes it as UTF-8. Lines 110-121 resolve builtins.exec through character codes and execute nonempty plaintext with __name__ set to __main__, inside a daemon thread started by bootstrap(). Missing or invalid count records, no chunks, authentication failure, and UTF-8 failure terminate retrieval without execution. Missing individual chunks are skipped; malformed DNS/Base64, network errors, and ordinary execution exceptions are suppressed by the worker. No retry, fallback transport, platform branch, subprocess, local dropped file, host-data collection, upload, or blockchain activity is present in this artifact. This is an additional payload download through DNS directly into memory, not merely configuration retrieval. Path ledger: uninvoked bootstrap has no network activity; invoked bootstrap reaches DNS retrieval; failed retrieval/decryption terminates; valid nonempty plaintext reaches arbitrary Python execution. Unresolved: the PTH caller was not inspected and the DNS-delivered stage was not retrieved; subsequent downloads, persistence, exfiltration, and other remote-stage behavior remain unknown. Domain registration or live status was not checked; historical availability and campaign attribution in the older report are not independently verified by this analysis.