runtimedev-link
Pure Node.js telemetry for RuntimeDev platform
This report shows the evidence for runtimedev-link@1.0.11. 11 of 13 known versions are blocked or flagged. The newest version, 1.0.14, is flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms user-level persistence, remote command execution, and arbitrary path upload behavior that is not limited to benign package functionality. The absence of npm lifecycle hooks reduces install-time blast radius but does not mitigate the malicious runtime payload.
Decision evidence
public snapshot- bin/cli.js runs installPersistence() during normal CLI startup, not only explicit install.
- lib/persistence.js registers autostart via systemd user units, crontab, launchd, or Windows Task Scheduler.
- lib/transport.js polls /api/telemetry/poll-command and executes server-supplied commands through lib/exec.js execSync.
- lib/download.js zips arbitrary requested file/directory paths and lib/transport.js posts them to /api/telemetry/upload-download.
- lib/transport.js reports hostname, username, OS info, directory tree, public IP, and Chrome extension inventory.
- package.json has no npm lifecycle scripts, so install alone does not execute code.
- Network API base is supplied by token or environment rather than hardcoded, except api.ipify.org for public IP lookup.
Source & flagged code
2 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version.
lib/persistence.jsView on unpkgSource writes installer persistence such as shell profile or service configuration.
lib/persistence.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to runtimedev-link@1.0.11.
The versions list below shows the verdict for each recorded version.
- Avoid installing runtimedev-link@1.0.11. 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.