{"answers":{"affected":"2 open source packages ship an affected version, including epress.","exploited":"There is no known exploitation of GHSA-vf8q-pw7h-r2x2 in the wild and no public exploit code.","fix":"No fix has been published for GHSA-vf8q-pw7h-r2x2 yet. Limit exposure of the affected software until one is available.","what":"GHSA-vf8q-pw7h-r2x2 is a vulnerability in epress, published on 11 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-vf8q-pw7h-r2x2 and fix it if it is affected.\n\nWhat it is: GHSA-vf8q-pw7h-r2x2 is a vulnerability in epress, published on 11 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-vf8q-pw7h-r2x2 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- epress (npm): affected all versions; no fix listed\n- epress (npm): 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/GHSA-vf8q-pw7h-r2x2/ (Markdown: https://insights.sbomify.com/GHSA-vf8q-pw7h-r2x2/index.md)","id":"GHSA-vf8q-pw7h-r2x2","markdown":"https://insights.sbomify.com/GHSA-vf8q-pw7h-r2x2/index.md","name":"GHSA-vf8q-pw7h-r2x2","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"workaround","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"npm package","requires_auth":"none","summary":"Malicious npm package executes cryptocurrency miner code upon installation, requiring users to remove the package and check for miner processes.","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":"Version 4.13.2 of `epress` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.\n\n## Recommendation\n\nRemove the package from your environment and verify whether your system is running the cryptocurrency miner.","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 epress","id":"GHSA-vf8q-pw7h-r2x2","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"],"last_affected":[],"package":"epress","purl":null,"source":"GHSA-vf8q-pw7h-r2x2"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":[],"package":"epress","purl":"pkg:npm/epress","source":"GHSA-vf8q-pw7h-r2x2"}],"products":null,"published":"2020-09-11","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 executes cryptocurrency miner code upon installation, requiring users to remove the package and check for miner processes.","url":"https://insights.sbomify.com/GHSA-vf8q-pw7h-r2x2/"}