Malicious code in agentenact (npm)
- Product
- agentenact (npm)
- Affected
- agentenact 0.2.0
- Fixed in
- No fix yet
Last verified against sources: October 28, 2026
Am I affected?
agentenact (npm): affected agentenact 0.2.0. No fix has been reported yet.
- Check your version: run
npm ls agentenact. Versions 0.2.0 of agentenact are affected. [1]
What to do now
- Remove the package if it is installed: run
npm uninstall agentenact. [1] - Remove the package. [1]
- Rotate all secrets and keys stored on that computer immediately from a different computer. [1]
- Consider any computer that has this package installed or running fully compromised. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
Impact
What was done
Sources
- MAL-2026-18346 — OSV (Open Source Vulnerabilities)
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
Malicious code in agentenact (npm)
Product: agentenact (npm) | Affected: agentenact 0.2.0 | Fixed in: No fix yet
Summary: Malicious code in agentenact (npm).
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/10/mal-2026-18346-agentenact-npmCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for agentenact (npm)
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.