registry / Remote code execution / id79-client
id79-client
embedded module for device information collection. Educational and enterprise use.
This report shows the evidence for id79-client@1.1.79, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is an import-triggered remote code execution chain with persistence-like detached execution, not a package-aligned client feature.
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 id79-client.
Impact
The remote endpoint can run arbitrary code under the importing application's user account and leave a background process running.
Mechanism
Detached remote payload download and Function-based execution.
Attack narrative
When an application imports the package, index.js invokes initialize. It starts loader.js as a detached process and stores a PID file. The loader fetches JSON from api.npoint.io, decodes its code field from base64, and evaluates it using Function with require and local path variables. This provides the remote endpoint arbitrary code execution in the consumer environment.
AI rationale
This is an import-triggered remote code execution chain with persistence-like detached execution, not a package-aligned client feature.
Evidence
index.jsinit.jsloader.js.pid
Network endpoints1
api.npoint.io/24c12c4b66a29747764f
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 calls its initializer.
- The initializer launches loader.js as a detached background Node process and records its PID.
- The loader downloads a base64 code field and executes it with Function while exposing require and filesystem paths.
Evidence against
- No npm install lifecycle hook is declared; activation occurs when the package is imported.
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 id79-client@1.1.79.
The versions list below shows the verdict for each recorded version.
- Avoid installing id79-client@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.