registry / Malware / @hydranium/glsp-client-theia

@hydranium/glsp-client-theia

Theia-coupled client primitives for GLSP heads built on @hydranium/glsp-server. Provides the diagram widget, manager, client contribution and connection-handler bases that Theia-based adopters extend, and binds @hydranium/glsp-client's host-neutral classe

This report shows the evidence for @hydranium/glsp-client-theia@1.0.0-next.391. 6 of 165 known versions are blocked or flagged. The newest version, 1.0.0-next.421, is allowed. See all versions.

AI Security Review

scanned 3d ago · by lpm-firewall-ai

The package manifest contains repeated, unusually specific review-directed defenses of package behaviors, which indicates an attempt to influence security review. The inspected runtime code appears consistent with the package’s stated Theia/GLSP purpose, but that does not remove the malicious review manipulation.

Static reason

No blocking static signals were detected.

Trigger

Reviewing package.json; the text is present in the published manifest.

Impact

Could manipulate automated or human review into overlooking package risks.

Mechanism

Nonstandard // metadata fields provide unsolicited defenses of the exports, peer dependency, prepack hook, and CSS import.

Attack narrative

The manifest contains multiple unsolicited // fields that explain away review-relevant package behavior, including the prepack hook and module imports. This is deliberate review-directed manipulation. The inspected JavaScript and stylesheet show ordinary package functionality, with no separate runtime attack identified.

AI rationale

Evidence

package.json

Decision evidence

public snapshot

AI called this Malicious at 86.0% confidence as Malware with low false-positive risk.

Evidence for block

package.json contains nonstandard // fields that argue how reviewers should interpret the exports, peer dependency, prepack hook, and stylesheet side effect.
The prepack note explicitly dismisses install concerns, while the other notes frame the package’s behavior as harmless; together these are review-directed attempts to preempt scrutiny.

Evidence against

The declared lifecycle scripts contain no install, preinstall, or postinstall hook.
The inspected entry points export Theia/GLSP modules, and the diagram widget imports the package’s loading stylesheet; no unrelated runtime action was identified.

Behavioral surface

SourceNo risky source behavior triggered.

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 32 file(s), 155 KB of source

Source & flagged code

3 flagged

style/diagram-loading.cssView file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

style/diagram-loading.cssView on unpkg

package.jsonView file

101"//exports": "The stylesheet key is an ASSET entry, not a module subpath, and it is spelled as the exact filename rather than `./style/*` so nothing becomes reachable automatically — the same no-wildcard property every other key here has. It exists because the widget's own import is package-RELATIVE, which `exports` does not gate, so the map's silence broke nobody inside the package while blocking every adopter who wants to `@import` the sheet, re-bundle it or override it by specifier; that failure reads as \"not exported under the conditions\" rather than as a missing entry. `tsc` emits n

High

Suspicious Dependency Evidence

package.json contains nonstandard // fields that argue how reviewers should interpret the exports, peer dependency, prepack hook, and stylesheet side effect.

package.jsonView on unpkg · L101

103"//prepack": "The publish guard, a `prepack` rather than a `prepare`: `prepack` runs only when a tarball is made (`npm pack`, `npm publish`) and never on install, so it cannot break the install it has no business touching. What it defends against: `files` lists `lib`, `lib` is gitignored, and a `files` entry matching nothing is skipped SILENTLY — so `npm publish` from an unbuilt tree emits a tarball of `src` and

High

Ai Review Evidence

The prepack note explicitly dismisses install concerns, while the other notes frame the package’s behavior as harmless; together these are review-directed attempts to preempt scrutiny.

package.jsonView on unpkg · L103

Findings

3 High1 Low

HighSemantic Analysis Limitedstyle/diagram-loading.css

HighSuspicious Dependency Evidencepackage.json

HighAi Review Evidencepackage.json

LowScripts Present

Affected versions and remediation

This report applies to @hydranium/glsp-client-theia@1.0.0-next.391.

The versions list below shows the verdict for each recorded version.

Avoid installing @hydranium/glsp-client-theia@1.0.0-next.391. 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: 2026-11-02 02:07:57.604Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

165 known versions

Showing the 100 most recent of 165 known versions.

registry / Malware / @hydranium/glsp-client-theia

@hydranium/glsp-client-theia

This report shows the evidence for @hydranium/glsp-client-theia@1.0.0-next.391. 6 of 165 known versions are blocked or flagged. The newest version, 1.0.0-next.421, is allowed. See all versions.

AI Security Review

scanned 3d ago · by lpm-firewall-ai

Static reason

No blocking static signals were detected.

Trigger

Reviewing package.json; the text is present in the published manifest.

Impact

Could manipulate automated or human review into overlooking package risks.

Mechanism

Nonstandard // metadata fields provide unsolicited defenses of the exports, peer dependency, prepack hook, and CSS import.

Attack narrative

AI rationale

Evidence

package.json

Decision evidence

public snapshot

AI called this Malicious at 86.0% confidence as Malware with low false-positive risk.

Evidence for block

package.json contains nonstandard // fields that argue how reviewers should interpret the exports, peer dependency, prepack hook, and stylesheet side effect.
The prepack note explicitly dismisses install concerns, while the other notes frame the package’s behavior as harmless; together these are review-directed attempts to preempt scrutiny.

Evidence against

The declared lifecycle scripts contain no install, preinstall, or postinstall hook.
The inspected entry points export Theia/GLSP modules, and the diagram widget imports the package’s loading stylesheet; no unrelated runtime action was identified.

Behavioral surface

SourceNo risky source behavior triggered.

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 32 file(s), 155 KB of source

Source & flagged code

3 flagged

style/diagram-loading.cssView file

•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1

High

Semantic Analysis Limited

A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.

style/diagram-loading.cssView on unpkg

package.jsonView file

High

Suspicious Dependency Evidence

package.json contains nonstandard // fields that argue how reviewers should interpret the exports, peer dependency, prepack hook, and stylesheet side effect.

package.jsonView on unpkg · L101

High

Ai Review Evidence

The prepack note explicitly dismisses install concerns, while the other notes frame the package’s behavior as harmless; together these are review-directed attempts to preempt scrutiny.

package.jsonView on unpkg · L103

Findings

3 High1 Low

HighSemantic Analysis Limitedstyle/diagram-loading.css

HighSuspicious Dependency Evidencepackage.json

HighAi Review Evidencepackage.json

LowScripts Present

Affected versions and remediation

This report applies to @hydranium/glsp-client-theia@1.0.0-next.391.

The versions list below shows the verdict for each recorded version.

Avoid installing @hydranium/glsp-client-theia@1.0.0-next.391. 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: 2026-11-02 02:07:57.604Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

165 known versions

Showing the 100 most recent of 165 known versions.

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

AI Security Review

Decision evidence

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

More from @hydranium

Other malware packages

Related packages

More from @hydranium

Other malware packages