registry / Remote code execution / process-lhpm
process-lhpm
Utilities for working with runtime and system information.
This report shows the evidence for process-lhpm@1.1.79, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package executes an opaque remotely supplied payload automatically on import through a detached background process. Although it has no install hook, this is concrete remote code execution and persistence behavior.
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
Importing index.js or invoking the exported initializer.
Impact
A remote operator can run arbitrary Node code in the importing application's context.
Mechanism
Detached remote payload loader with dynamic code execution.
Attack narrative
A normal import calls initialize, which spawns a detached loader and writes .pid. That loader requests a remote JSON response, decodes its code field from base64, and runs it through Function with require, module paths, and exports available. This provides remote arbitrary code execution without a user command and persists a background process.
AI rationale
The package executes an opaque remotely supplied payload automatically on import through a detached background process. Although it has no install hook, this is concrete remote code execution and persistence behavior.
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 automatically starts the initializer.
- The initializer launches a detached Node process and records its PID.
- The loader downloads base64 code from a remote endpoint and executes it with require access.
- The loader globally intercepts child-process module loading and hides Windows child processes.
Evidence against
- package.json contains no npm install lifecycle hook.
- The remote payload is not bundled, so its specific actions cannot be determined statically.
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-lhpm@1.1.79.
The versions list below shows the verdict for each recorded version.
- Avoid installing process-lhpm@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.