{"answers":{"affected":"1 open source package ship an affected version, including aiocpa.","exploited":"There is no known exploitation of PYSEC-2024-152 in the wild and no public exploit code.","fix":"No fix has been published for PYSEC-2024-152 yet. Limit exposure of the affected software until one is available.","what":"PYSEC-2024-152 is a vulnerability in aiocpa, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for PYSEC-2024-152 and fix it if it is affected.\n\nWhat it is: PYSEC-2024-152 is a vulnerability in aiocpa, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of PYSEC-2024-152 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aiocpa (PyPI): affected all versions; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/PYSEC-2024-152/ (Markdown: https://insights.sbomify.com/PYSEC-2024-152/index.md)","id":"PYSEC-2024-152","markdown":"https://insights.sbomify.com/PYSEC-2024-152/index.md","name":"PYSEC-2024-152","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"end_of_life","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Python color gradient library","requires_auth":"none","summary":"Malicious code in aiocpa library steals Crypto Pay credentials and sends them to a remote bot, requiring immediate removal of the package.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"aiocpa is a user-facing library for generating color gradients of text.\nVersion 0.1.13 introduced obfuscated, malicious code targeting\nCrypto Pay users, forwarding client credentials to a remote Telegram bot.\nAll versions have been removed from PyPI.","ecosystems":["PyPI"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"aiocpa 0.1.13 contains credential harvesting code","id":"PYSEC-2024-152","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"supply_chain","year":"2024"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"aiocpa","purl":"pkg:pypi/aiocpa","source":"PYSEC-2024-152"}],"products":null,"published":"2024-11-25","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Malicious code in aiocpa library steals Crypto Pay credentials and sends them to a remote bot, requiring immediate removal of the package.","url":"https://insights.sbomify.com/PYSEC-2024-152/"}