Malicious code in buttoncontent (npm)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm buttoncontent
- Affected
- every version
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18339 lists affected ranges: npm buttoncontent >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (e9d44a5a2d3a96bab51870b046a7d474991b20c52e850f7e5639281ba8bff80e) Package buttoncontent@0.0.0-stage contains two files with no install-time lifecycle scripts, no network activity, no filesystem reads of installer-secret paths, and no execution of fetched or obfuscated content. The version coordinate (0.0.0-stage) and minimal file count are consistent with a placeholder or staging publication rather than a functional library. No exfiltration, dropper, backdoor, silent-relay, or credential-distribution mechanism is present.
Source: ghsa-malware (18ee43e64a2d1a1e6de6c6dce2b7be4032731042b6ab27f86bdde5ffee1c9689) Any 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. The package should be removed, but as full control of the computer may have been given to an…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record MAL-2026-18339
- Revision 1 · created ·
Published from osv record MAL-2026-18339
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-6crh-vwr2-4qfp Advisory: Malicious code in buttoncontent (npm) IDs: GHSA-6crh-vwr2-4qfp Record: https://patchnext.com/advisories/mal-2026-18339 (revision 2, source checked 30 Oct 2026, 06:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm buttoncontent: affected every version ## Suggested inspection (read-only) - `npm ls buttoncontent --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on buttoncontent. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/MAL-2026-18339 (OSV record MAL-2026-18339 lists affected ranges: npm buttoncontent >=0) Commands are suggestions: review each one before running it.
Loading voting…