MalwarePublished 13 Jul 2026

node-fsagent (npm) · Malicious Code

Affects node-fsagentSource GCVE Database

Malicious package : remove node-fsagent and rotate any secrets on hosts that installed it.

Data as of 26 Oct 2026, 15:56 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10506

What to do

Remove node-fsagent from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmnode-fsagent	Affected 1.0.0 – 1.2.2 9 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The node-fsagent npm package contains malicious code that archives the host's /root/.codex directory, splits the archive into chunks, and exfiltrates the data by publishing these chunks as sequential npm package versions using a reconstructed npm registry authentication token. The token is embedded and reconstructed at runtime, granting publish rights to the attacker's npm account. The package's main entry is empty and does not auto-execute the malicious script; the harmful behavior occurs only if the archive-sender.js script is run directly. The package has no legitimate functionality and serves solely as a covert data exfiltration and credential distribution tool.

Impact

The malicious package enables covert exfiltration of potentially sensitive data from the host's /root/.codex directory by publishing it in chunks to the public npm registry. Additionally, the embedded authentication token grants publish rights to the attacker's npm account, allowing them to republish the node-fsagent package or other packages owned by that account, potentially facilitating further supply chain attacks or malicious package updates. There is no automatic execution of the malicious code upon installation or require, limiting exploitation to manual invocation of the script.

Defensive guidance

Users should avoid installing or using the node-fsagent package in any of the affected versions. Since the malicious behavior only triggers when the archive-sender.js script is run directly, not on install or require, avoid executing any scripts from this package. Review and revoke any npm registry tokens that may have been compromised due to this package. Monitor npm accounts for unauthorized publishing activity.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2026, 09:47 UTC

Technical details

References

Community reviews