registry / Remote code execution / process-mite
process-mite
Utilities for working with runtime and system information.
This report shows the evidence for process-mite@1.1.79, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a concrete remote-code-execution loader activated by a normal import, with persistence-like detached process behavior. The lack of an install hook does not reduce the import-time remote execution risk.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
An application imports the package main entry point.
Impact
A remote endpoint can execute arbitrary code in the importing application's user context and leave a background process running.
Mechanism
Detached remote payload loader using HTTPS, base64 decoding, and Function execution.
Attack narrative
A consumer import calls initialize automatically. It launches loader.js detached and writes a PID file. The loader fetches JSON from a remote endpoint, decodes its code field, and executes it through Function while passing require and local path variables. The endpoint therefore controls code run on the consumer host without an explicit runtime action.
AI rationale
This is a concrete remote-code-execution loader activated by a normal import, with persistence-like detached process behavior. The lack of an install hook does not reduce the import-time remote execution risk.
Evidence
index.jsinit.jsloader.js.pid
Network endpoints1
api.npoint.io/33e8d008c334b060adad
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- Importing the main module immediately initializes the package.
- Initialization starts loader.js as a detached background Node process and records its PID.
- The loader downloads a base64 code field from api.npoint.io and runs it with Function.
- Remote code receives require and package path context, allowing it to load modules and act on the host.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The inspected source does not itself harvest credentials or send local files.
Behavioral surface
ChildProcessEvalFilesystemNetworkShell
UrlStrings
Source & flagged code
7 flagged · loading sourceinit.jsView file
1import { spawn } from 'child_process';
L2: import { dirname, join } from 'path';
High
1Cross-file remote execution chain: init.js spawns loader.js; helper contains network access plus dynamic code execution.
L1: import { spawn } from 'child_process';
L2: import { dirname, join } from 'path';
...
L5:
L6: const __dirname = dirname(fileURLToPath(import.meta.url));
L7: const PID_FILE = join(__dirname, '.pid');
High
Cross File Remote Execution Context
Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
init.jsView on unpkg · L1loader.jsView file
1import https from "https";
L2: import { fileURLToPath } from "url";
...
L7: const __filename = fileURLToPath(import.meta.url);
L8: const __dirname = dirname(__filename);
L9: const require = createRequire(import.meta.url);
...
L12:
L13: // Intercept child_process require calls for Windows compatibility
L14: const originalRequire = Module.prototype.require;
...
L22: module.spawn = function(cmd, args, options = {}) {
L23: if (process.platform === "win32" && !options.windowsHide) {
L24: options.windowsHide = true;
...
L31: const { spawnSync } = require('child_process');
Findings
7 High1 Medium4 Low
HighChild Processinit.js
HighShell
HighSandbox Evasion Gated Capabilityloader.js
HighCross File Remote Execution Contextinit.js
HighKnown Malware Source Similarityloader.js
HighKnown Malware Source Fingerprint Signatureloader.js
HighAi Review Evidenceindex.js
MediumNetwork
LowScripts Present
LowEvalloader.js
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to process-mite@1.1.79.
The versions list below shows the verdict for each recorded version.
- Avoid installing process-mite@1.1.79. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.