registry / Remote code execution / @biz44/id95-client
@biz44/id95-client
embedded module for device information collection. Educational and enterprise use.
This report shows the evidence for @biz44/id95-client@1.1.96, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe complete remote-code execution path is present in the published source and activates on ordinary import. Detached execution and PID tracking add 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 @biz44/id95-client or explicitly invoking its initializer.
Impact
Remote code can run with the importing application's Node permissions and persist as a detached process.
Mechanism
Detached remote payload loader using Function evaluation.
Attack narrative
The package runs initialization on import. It spawns a detached Node process, stores its PID, then the loader fetches a JSON field from api.npoint.io, base64-decodes it, and evaluates it with access to require and package path values. This gives a remote operator arbitrary Node code execution in the consumer environment without a source update.
AI rationale
The complete remote-code execution path is present in the published source and activates on ordinary import. Detached execution and PID tracking add persistence behavior.
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 entry automatically starts initialization.
- Initialization creates a detached background Node process and records its PID in .pid.
- The loader downloads a base64 program from api.npoint.io and runs it with Function, exposing require and file paths.
- The remote program can use child-process facilities because the loader modifies child_process loading behavior.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- The inspected local source does not itself enumerate or transmit credentials.
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 @biz44/id95-client@1.1.96.
The versions list below shows the verdict for each recorded version.
- Avoid installing @biz44/id95-client@1.1.96. 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.