Malicious code in agentenact (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 agentenact
- Affected
- >= 0.2.0, <= 0.2.0
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18346 lists affected ranges: npm agentenact >=0.2.0 <=0.2.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 (07db0f79773c0790dd0cda967228203b58861c89d78540a25c8ff7ac28152f29) Review of agentenact@0.2.0 (npm) surfaced no evidence of credential theft, install-time or import-time remote code execution, silent-relay of caller data to a non-first-party destination, backdoor, dropper behavior, or self-propagation. No lifecycle hooks fetching or executing remote content, no reads of installer-secret paths (~/.aws, ~/.ssh, ~/.npmrc, browser or wallet stores), no whole-environment scraping, and no hardcoded attacker C2 endpoints were observed in the package's shipped files.
Source: ghsa-malware (069f1dacd0464661f41d72bc99c21b659368fcefcccac68d349cc7d62cb1cca4) 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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record MAL-2026-18346
- Revision 1 · created ·
Published from osv record MAL-2026-18346
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-7p7m-8jmq-qp93 Advisory: Malicious code in agentenact (npm) IDs: GHSA-7p7m-8jmq-qp93 Record: https://patchnext.com/advisories/mal-2026-18346 (revision 2, source checked 30 Oct 2026, 06:15 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 agentenact: affected >= 0.2.0, <= 0.2.0 ## Suggested inspection (read-only) - `npm ls agentenact --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 agentenact. - 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-18346 (OSV record MAL-2026-18346 lists affected ranges: npm agentenact >=0.2.0 <=0.2.0) Commands are suggestions: review each one before running it.
Loading voting…