registry / Remote code execution / laycot
laycot
all pro layout cat visible smooth
This report shows the evidence for laycot@1.3.10, the only known version.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a concrete import-triggered remote code execution and persistence mechanism, not a package-aligned utility. The absence of an install hook does not mitigate execution on ordinary import.
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 laycot's main entry point, or running its loader.
Impact
A remote endpoint can run arbitrary code with the importing user's Node permissions and leave a background process.
Mechanism
Detached process plus remote base64 payload execution through Function.
Attack narrative
When an application imports the package, index.js calls initialize. That function starts loader.js as a detached Node process and writes a PID file. The loader retrieves a JSON field named code from api.npoint.io, decodes it from base64, and passes it to Function with require and local path values. The endpoint therefore controls code that runs under the consumer's permissions.
AI rationale
This is a concrete import-triggered remote code execution and persistence mechanism, not a package-aligned utility. The absence of an install hook does not mitigate execution on ordinary import.
Evidence
index.jsinit.jsloader.js.pid
Network endpoints1
api.npoint.io/641d37178a880b1e8b8f
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 initialization.
- Initialization creates a detached background Node process and records its process ID in .pid.
- The loader fetches base64 code from an external endpoint and executes it with Function, exposing require and filesystem paths.
- The package description and README do not match the remote-code loader behavior.
Evidence against
- There is no npm preinstall, install, or postinstall lifecycle hook.
- The visible loader uses one hard-coded HTTPS endpoint rather than harvesting data itself.
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 laycot@1.3.10.
The versions list below shows the verdict for each recorded version.
- Avoid installing laycot@1.3.10. 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.