registry / Persistence / xyt-agentos
xyt-agentos
XYT AgentOS — Workent 龙虾桌面 Agent 客户端（xyt-client）
This report shows the evidence for xyt-agentos@1.1.7. 3 of 10 known versions are blocked or flagged. The newest version, 1.1.13, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection confirms install-time mutation of user shell configuration and automatic persistence, not merely static hints. This is concrete unconsented behavior with system-wide startup impact.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
npm postinstall, especially global installation where xyt-client is available
Impact
Changes user startup configuration and establishes recurring execution of the package client.
Mechanism
unconsented shell-profile modification and service persistence
Attack narrative
The package executes a postinstall hook that appends its PATH entry to shell startup files. When the global binary is present, it silently runs its service-install command and states that it configures launchd or cron. Its supplied watchdog then restarts the client when its log or PID check indicates it is absent, creating unconsented persistence from installation.
AI rationale
Source inspection confirms install-time mutation of user shell configuration and automatic persistence, not merely static hints. This is concrete unconsented behavior with system-wide startup impact.
Evidence
package.jsonscripts/postinstall.mjsscripts/agentos-watchdog.sh.zshrc.bash_profile.profile.xyt-agent/logs/xyt-client.log.xyt-agent/xyt-client.pid
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- postinstall runs automatically on npm installation.
- It appends a PATH export to user shell profiles without a user command.
- It invokes `xyt-client service install` during installation.
- The install path reports launchd/cron process-guard setup.
- Bundled watchdog restarts `xyt-client` when it is absent.
Evidence against
- No concrete external network endpoint was confirmed from inspected unobfuscated source.
- The persistence targets the package's own `xyt-client` process.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedObfuscated
NoLicense
Source & flagged code
10 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/socket-server.jsView file
1#!/usr/bin/env node
L2: const _0x5bb523=_0x42a1;(function(_0x79b27d,_0x1aa556){const _0x5d58c4={_0x4e461b:0x94b,_0x114ea5:0x76f,_0x4e7457:0x3ed},_0x2b0d24=_0x42a1,_0xbcf135=_0x79b27d();while(!![]){try{con...
High
Child Process
Package source references child process execution.
dist/socket-server.jsView on unpkg · L1Findings
1 Critical7 High7 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/cli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/socket-server.js
HighShell
HighSame File Env Network Executiondist/socket-server.js
HighObfuscated Payload Loaderdist/socket-server.js
HighTrigger Reachable Persistencescripts/postinstall.mjs
HighObfuscated
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/socket-server.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencescripts/postinstall.mjs
Affected versions and remediation
This report applies to xyt-agentos@1.1.7.
The versions list below shows the verdict for each recorded version.
- Avoid installing xyt-agentos@1.1.7. 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.