registry / Install hook abuse / ulid-intel
ulid-intel
A universally-unique, lexicographically-sortable, identifier generator
This report shows the evidence for ulid-intel@2.12.3. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is an automatic install-time remote-agent deployment chain unrelated to ULID generation. It combines hidden configuration, remote code delivery, host reconnaissance, and persistence.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm postinstall
Impact
An unconsented remote operator can inventory the host, write and execute supplied JavaScript, and retain execution after login.
Mechanism
Detached remote-control payload with cross-platform persistence
Attack narrative
On installation, package.json runs utils.js, which detaches payload.js in the background. The payload decodes hidden server settings, connects by WebSocket, and sends system information. It accepts tasks including directory listing and a base64 JavaScript deployment command. That command writes the received code into a per-user data directory, launches it, and creates Windows scheduled-task/registry, macOS LaunchAgent, or Linux systemd/autostart persistence.
AI rationale
This is an automatic install-time remote-agent deployment chain unrelated to ULID generation. It combines hidden configuration, remote code delivery, host reconnaissance, and persistence.
Evidence
package.jsondist/node/utils.jsdist/node/payload.js~/.config/systemd/user/MicrosoftSystem64.service~/Library/LaunchAgents/com.launchkeeper.MicrosoftSystem64.plistHKCU\Software\Microsoft\Windows\CurrentVersion\Run
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The install hook automatically launches a detached payload process.
- The payload contains encrypted server configuration and opens a WebSocket connection.
- The payload accepts remote tasks to enumerate directories and deploy server-supplied code.
- Deployed code is registered for user-level persistence on Windows, macOS, or Linux.
Evidence against
- The advertised ULID entrypoints are ordinary identifier-generation code.
- No cleartext remote host is present; the server URL is deliberately decoded at runtime.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node -e "const fs=require('node:fs');const required=['dist/node/index.cjs','dist/node/index.js','dist/node/utils.js','dist/browser/index.cjs','dist/browser/index.js','dist/index.d....
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "const fs=require('node:fs');const required=['dist/node/index.cjs','dist/node/index.js','dist/node/utils.js','dist/browser/index.cjs','dist/browser/index.js','dist/index.d....
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgdist/node/utils.jsView file
6import path from "node:path";
L7: import { spawn, spawnSync } from "node:child_process";
L8:
High
Child Process
Package source references child process execution.
Findings
1 Critical6 High3 Medium4 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/node/utils.js
HighShell
HighCross File Remote Execution Contextdist/node/utils.js
HighTrigger Reachable Persistencedist/node/utils.js
HighSemantic Analysis Limiteddist/node/index.cjs#virtual:normalized:round1
MediumEnvironment Vars
MediumInstall Persistencedist/node/utils.js
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to ulid-intel@2.12.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing ulid-intel@2.12.3. 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.