registry / Data exfiltration / sysdo
sysdo
System binary configuration tool
This report shows the evidence for sysdo@1.0.0, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is concrete runtime data exfiltration through automatic clipboard collection and remote POSTs, supplemented by screenshot upload capability. The absence of lifecycle hooks does not remove the malicious user-execution attack surface.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
User runs the sysdo CLI.
Impact
Sensitive clipboard text and screenshots can be sent off-device without per-item consent.
Mechanism
Hidden clipboard monitoring and screenshot upload via remote HTTP POST.
Attack narrative
The package has no install hook, but its declared CLI executes pointer.py. That program repeatedly reads clipboard changes and POSTs them to iq-sec.vercel.app while its UI is not hidden. It also registers a screen-capture hotkey that captures the primary monitor, encodes it, and uploads it to the same endpoint. Stealth hide/show controls conceal the application.
AI rationale
This is concrete runtime data exfiltration through automatic clipboard collection and remote POSTs, supplemented by screenshot upload capability. The absence of lifecycle hooks does not remove the malicious user-execution attack surface.
Evidence
package.jsonindex.jspointer.pystart_tool.vbs%TEMP%\python-3.12.3-amd64.exe
Network endpoints1
iq-sec.vercel.app/api
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- The CLI entrypoint launches pointer.py after installing Python and its dependencies.
- pointer.py continuously reads changed clipboard text while visible and submits it to a remote API.
- It can capture the full primary monitor, base64-encode the image, and upload it to that API.
- The package provides stealth hide/show hotkeys and an invisible UI, concealing this collection activity.
Evidence against
- package.json contains no preinstall, install, or postinstall lifecycle hook.
- Screen capture is initiated by a registered hotkey; the clipboard monitor is automatic after launch.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
HighEntropyStringsUrlStrings
Source & flagged code
3 flagged · loading sourcepointer.pyView file
•path = pointer.py
kind = build_helper
sizeBytes = 31787
magicHex = [redacted]
Medium
index.jsView file
•matchType = normalized_sha256
matchedPackage = syspo@1.0.1
matchedPath = index.js
matchedIdentity = npm:c3lzcG8:1.0.1
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
index.jsView on unpkg•matchType = malicious_source_fingerprint_signature
signature = dcd6e9f81522be69
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = syspo@1.0.1
matchedPath = index.js
matchedIdentity = npm:c3lzcG8:1.0.1
similarity = 1.000
shingleOverlap = 1
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Findings
2 High3 Medium4 Low
HighKnown Malware Source Similarityindex.js
HighKnown Malware Source Fingerprint Signatureindex.js
MediumEnvironment Vars
MediumShips Build Helperpointer.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to sysdo@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing sysdo@1.0.0. 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.