{"answers":{"affected":"2 open source packages ship an affected version, including leetlog.","exploited":"There is no known exploitation of GHSA-gfm8-g3vm-53jh in the wild and no public exploit code.","fix":"No fix has been published for GHSA-gfm8-g3vm-53jh yet. Limit exposure of the affected software until one is available.","what":"GHSA-gfm8-g3vm-53jh is a vulnerability in leetlog, published on 3 Sep 2020."},"fix_prompt":"Check this codebase for GHSA-gfm8-g3vm-53jh and fix it if it is affected.\n\nWhat it is: GHSA-gfm8-g3vm-53jh is a vulnerability in leetlog, published on 3 Sep 2020. \nExploitation: There is no known exploitation of GHSA-gfm8-g3vm-53jh in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- leetlog (npm): affected from 0.1.2; no fix listed\n- leetlog (npm): affected from 0.1.2; 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/GHSA-gfm8-g3vm-53jh/ (Markdown: https://insights.sbomify.com/GHSA-gfm8-g3vm-53jh/index.md)","id":"GHSA-gfm8-g3vm-53jh","markdown":"https://insights.sbomify.com/GHSA-gfm8-g3vm-53jh/index.md","name":"GHSA-gfm8-g3vm-53jh","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"unknown","non_default_config":false,"product_category":"npm logging library","requires_auth":"none","summary":"Malicious npm package adds hardcoded SSH key, granting attackers full system access and requiring immediate credential rotation.","user_interaction":"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":"Versions 0.1.2 and 0.1.3 of `leetlog` contain malicious code. The package adds an arbitrary hardcoded SSH key identified as `hacker@evilmachine` to the system's `authorized_keys`\n\n## Recommendation\n\nAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.\n\nThe package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Malicious Package in leetlog","id":"GHSA-gfm8-g3vm-53jh","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"supply_chain","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0.1.2"],"last_affected":[],"package":"leetlog","purl":null,"source":"GHSA-gfm8-g3vm-53jh"},{"ecosystem":"npm","fixed":[],"introduced":["0.1.2"],"last_affected":[],"package":"leetlog","purl":"pkg:npm/leetlog","source":"GHSA-gfm8-g3vm-53jh"}],"products":null,"published":"2020-09-03","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Malicious npm package adds hardcoded SSH key, granting attackers full system access and requiring immediate credential rotation.","url":"https://insights.sbomify.com/GHSA-gfm8-g3vm-53jh/"}