registry / Data exfiltration / @ory/cursor
@ory/cursor
Ory plugin for Cursor: scaffolding rules, a local Ory instance, and authentication, authorization, and audit for every tool call
This report shows the evidence for @ory/cursor@1.8.1. 2 of 21 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe dependency's postinstall automatically transmits the Git email domain from `~/.gitconfig` to the configured telemetry endpoint. This is install-time transmission of identifying Git information without an install-time consent prompt, so the package is malicious under the install-time contact rule.
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
Installing @ory/cursor when its reova dependency's postinstall runs, unless a global opt-out is set.
Impact
Exposes identifying organizational information from Git configuration during installation without an install-time consent prompt.
Mechanism
reova discovers the dependent package, collects package and system details plus the Git email domain, then POSTs the payload to the configured endpoint.
Attack narrative
During installation, reova's postinstall runs automatically. Because @ory/cursor enables it and configures telemetry.reo.dev, the tracker reads the installer's Git email domain from ~/.gitconfig, includes it with install metrics, and sends the payload to that endpoint unless the user has set a global opt-out.
AI rationale
The dependency's postinstall automatically transmits the Git email domain from `~/.gitconfig` to the configured telemetry endpoint. This is install-time transmission of identifying Git information without an install-time consent prompt, so the package is malicious under the install-time contact rule.
Evidence
package.json.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/package.json.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/index.js.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/src/collector.js.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/src/tracker.js.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/src/sender.js~/.gitconfig
Network endpoints
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package enables `reova` and configures `https://telemetry.reo.dev/data`.
- The resolved `reova` dependency runs `node index.js` in its postinstall hook, which starts tracking.
- The collector reads the Git email from `~/.gitconfig` and adds its domain to install analytics.
- The tracker sends collected install data to the configured endpoint using an HTTP POST.
- Tracking proceeds when the package is enabled and an endpoint is configured; neither requires an install-time user prompt.
Evidence against
- The package itself declares no lifecycle scripts.
- The collector sends the Git email domain rather than the full email address.
- `reova` honors global `REOVA_ANALYTICS=false` and `DO_NOT_TRACK` opt-outs.
Behavioral surface
Filesystem
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggeddist/cli/main.jsView file
•matchType = normalized_sha256
matchedPackage = @ory/cursor@1.8.0
matchedPath = dist/cli/main.js
matchedIdentity = npm:QG9yeS9jdXJzb3I:1.8.0
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.
dist/cli/main.jsView on unpkg•matchType = malicious_source_fingerprint_signature
signature = b2ded14fc8480242
signatureType = suspicious_hashes
sourceLabel = final_verdict:malicious
matchedPackage = @ory/cursor@1.8.0
matchedPath = dist/cli/main.js
matchedIdentity = npm:QG9yeS9jdXJzb3I:1.8.0
similarity = 1.000
shingleOverlap = 6
summary = package final verdict is malicious
High
Known Malware Source Fingerprint Signature
Source fingerprint signature matches a known malicious package signature; route for source-aware review.
dist/cli/main.jsView on unpkgdist/cli/setup.jsView file
Findings
8 High4 Low
HighKnown Malware Source Similaritydist/cli/main.js
HighKnown Malware Source Similaritydist/cli/setup.js
HighKnown Malware Source Fingerprint Signaturedist/cli/main.js
HighAi Review Evidencepackage.json
HighSuspicious Lifecycle Evidence.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/package.json
HighSuspicious Lifecycle Evidence.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/index.js
HighAi Review Evidence.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/src/collector.js
HighAi Review Evidence.lpm-dependency-evidence-7a02f6da-f581-4eb9-b1e0-94afb46d6470/1/npm-linux/src/collector.js
LowScripts Present
LowFilesystem
Low
Affected versions and remediation
This report applies to @ory/cursor@1.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ory/cursor@1.8.1. 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.