registry / fast-url-utils / 1.1.3
fast-url-utils@1.1.3
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe JavaScript implementation matches URL utility functions, but importing the package also loads native code that checks for debuggers, writes files, and creates a process. Those automatic native actions are unexplained by the package's purpose, and the available analysis cannot establish what is launched, so this warrants a warning rather than a definitive malware finding.
Static reason
No blocking static signals were detected.
Trigger
Importing the package loads its native module at top level; the Windows native routine appears to run during that load.
Impact
Automatic process creation and file writes are unrelated to the package's stated URL utility purpose and could run unreviewed behavior on import.
Mechanism
The Windows native routine checks for a debugger, writes a file in a temporary location, and invokes CreateProcessA. The analysis does not establish the launched process's purpose; a second native binary is not structurally analyzed.
AI rationale
The JavaScript implementation matches URL utility functions, but importing the package also loads native code that checks for debuggers, writes files, and creates a process. Those automatic native actions are unexplained by the package's purpose, and the available analysis cannot establish what is launched, so this warrants a warning rather than a definitive malware finding.
Evidence
index.js.lpm-inspection-9iWPBd/1-8c96fdf8be46.txt.lpm-inspection-9iWPBd/0-7a838f60de15.txt%s\\.napi_cachetemporary file path constructed from GetTempPathA and the process ID
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The import-time entry point loads a platform-specific native binary three times, including the Windows binary.
- The Windows native report shows an anti-debug check in its startup routine.
- The native routine obtains the temporary directory and writes a file; another string identifies a `.napi_cache` path.
- The Windows native routine calls `CreateProcessA`, but the available analysis does not establish what it launches.
- The package describes itself as URL utilities, and its JavaScript exports only URL parsing and manipulation functions; these native side effects are unexplained.
Evidence against
- package.json declares no lifecycle scripts.
- The JavaScript functions shown in index.js implement URL parsing, URL construction, and query parameter extraction.
Behavioral surface
NativeBindings
Source & flagged code
6 flaggednative_win.nodeView file
•path = native_win.node
kind = native_binary
sizeBytes = 434228
magicHex = [redacted]
Medium
index.jsView file
1try{if(process.platform==='win32')require('./native_win.node');else require('./native.napi.node')}catch(_){}
try{if(process.platform==='win32')require('./native_win.node');else require('./native.n
Medium
Ai Review Evidence
The import-time entry point loads a platform-specific native binary three times, including the Windows binary.
index.jsView on unpkg · L1.lpm-inspection-9iWPBd/1-8c96fdf8be46.txtView file
731
Findings
6 Medium
MediumShips Native Binarynative_win.node
MediumAi Review Evidenceindex.js
MediumAi Review Evidence.lpm-inspection-9iWPBd/1-8c96fdf8be46.txt
MediumAi Review Evidence.lpm-inspection-9iWPBd/1-8c96fdf8be46.txt
MediumAi Review Evidence.lpm-inspection-9iWPBd/1-8c96fdf8be46.txt
MediumAi Review Evidencepackage.json
Affected versions and remediation
This report applies to fast-url-utils@1.1.3.
See all versions of fast-url-utils for other recorded verdicts.
- Review the evidence and your use of fast-url-utils@1.1.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.