registry / Remote code execution / engin1
engin1
Utilities for working with runtime and system information.
This report shows the evidence for engin1@1.3.99, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package contains an import-time detached remote-code execution chain unrelated to its advertised utility purpose. This is concrete malicious behavior even without an npm lifecycle hook.
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 engin1 through its main entry point.
Impact
Remote operators can run arbitrary Node.js code in the importing user's environment.
Mechanism
Detached remote payload download and dynamic execution.
Attack narrative
A normal import calls initialize(), which creates an unreferenced detached Node process running loader.js. The loader retrieves JSON from api.npoint.io, base64-decodes its code field, and passes it to new Function along with require and filesystem-location values. This gives the remote endpoint control of code executed on the consumer machine and leaves a background loader tracked by .pid.
AI rationale
The package contains an import-time detached remote-code execution chain unrelated to its advertised utility purpose. This is concrete malicious behavior even without an npm lifecycle hook.
Evidence
index.jsinit.jsloader.js.pid
Network endpoints1
api.npoint.io/24c25d5f5fcbb0992a4f
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 initializes the package.
- Initialization starts a detached background loader and records its process ID.
- The loader downloads base64 content from a remote endpoint and executes it with Node module access.
- The advertised runtime-information purpose does not match the remote-code loader.
Evidence against
- package.json has no preinstall, install, or postinstall hook.
- No credential collection is present in the inspected source.
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 engin1@1.3.99.
The versions list below shows the verdict for each recorded version.
- Avoid installing engin1@1.3.99. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.