Malicious code in jsf-utils (npm)
The npm package jsf-utils versions 1.3.1 and 0.3.1 contains malicious code that executes a remote JavaScript payload at import time. This payload is fetched from a mutable anonymous paste service and executed with full access to the installer's environment, enabling arbitrary code execution. The package impersonates a legitimate utility by reusing metadata from a trusted author and conceals the malicious logic inside a seemingly benign string helper module. The malicious code also spawns a detached Node.js process to maintain persistence beyond the initial import. Systems with this package installed should be considered fully compromised.
AI Analysis
Technical Summary
The jsf-utils npm package (versions 1.3.1 and 0.3.1) includes a top-level asynchronous immediately-invoked function expression (IIFE) in lib/string/pathcase.js that fetches and executes a remote JavaScript payload from https://jsonkeeper.com/b/BPB86 using Function.constructor. This execution occurs with access to the installer's require function, allowing extensive control over the environment. The malicious code is concealed within a file intended as a trivial string helper, with the original benign code commented out. Additionally, the package spawns a detached Node.js child process running the fetched script, enabling execution persistence beyond the initial import. The package falsely claims to be authored by jonschlinkert and reuses legitimate metadata to disguise its malicious nature. Because the payload is hosted on a mutable anonymous paste service, the attacker can change the executed code at any time without republishing the package.
Potential Impact
Any system that installs or runs jsf-utils versions 1.3.1 or 0.3.1 is fully compromised due to remote code execution with access to the installer's environment. This can lead to complete system takeover, including unauthorized access to secrets and keys stored on the machine. The malicious child process spawned by the package can persist beyond the initial execution, making removal of the package insufficient to guarantee system cleanup.
Mitigation Recommendations
No official patch or fix is currently available. Immediate removal of the jsf-utils package versions 1.3.1 and 0.3.1 is strongly recommended. Because the package grants full control to an attacker, all secrets and keys stored on the affected system should be considered compromised and rotated from a different, trusted machine. Monitor for any suspicious child processes or unexpected network activity related to Node.js. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Malicious code in jsf-utils (npm)
Description
The npm package jsf-utils versions 1.3.1 and 0.3.1 contains malicious code that executes a remote JavaScript payload at import time. This payload is fetched from a mutable anonymous paste service and executed with full access to the installer's environment, enabling arbitrary code execution. The package impersonates a legitimate utility by reusing metadata from a trusted author and conceals the malicious logic inside a seemingly benign string helper module. The malicious code also spawns a detached Node.js process to maintain persistence beyond the initial import. Systems with this package installed should be considered fully compromised.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The jsf-utils npm package (versions 1.3.1 and 0.3.1) includes a top-level asynchronous immediately-invoked function expression (IIFE) in lib/string/pathcase.js that fetches and executes a remote JavaScript payload from https://jsonkeeper.com/b/BPB86 using Function.constructor. This execution occurs with access to the installer's require function, allowing extensive control over the environment. The malicious code is concealed within a file intended as a trivial string helper, with the original benign code commented out. Additionally, the package spawns a detached Node.js child process running the fetched script, enabling execution persistence beyond the initial import. The package falsely claims to be authored by jonschlinkert and reuses legitimate metadata to disguise its malicious nature. Because the payload is hosted on a mutable anonymous paste service, the attacker can change the executed code at any time without republishing the package.
Potential Impact
Any system that installs or runs jsf-utils versions 1.3.1 or 0.3.1 is fully compromised due to remote code execution with access to the installer's environment. This can lead to complete system takeover, including unauthorized access to secrets and keys stored on the machine. The malicious child process spawned by the package can persist beyond the initial execution, making removal of the package insufficient to guarantee system cleanup.
Mitigation Recommendations
No official patch or fix is currently available. Immediate removal of the jsf-utils package versions 1.3.1 and 0.3.1 is strongly recommended. Because the package grants full control to an attacker, all secrets and keys stored on the affected system should be considered compromised and rotated from a different, trusted machine. Monitor for any suspicious child processes or unexpected network activity related to Node.js. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6921
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-2jff-wp39-wgch"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba8768715ace43581c15
Added to database: 07/10/2026, 09:25:27 UTC
Last enriched: 07/10/2026, 10:05:11 UTC
Last updated: 07/27/2026, 03:11:06 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.