titan-exchange-shared-permissions
This report shows the evidence for titan-exchange-shared-permissions@99.9.9. 1 of 2 known versions is blocked or flagged. The newest version, 99.9.12, is flagged. See all versions.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-13664 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The lifecycle hook and exfiltration intent are suspicious, but the only payload is non-executable due to clear syntax errors. Treat it as an inert payload carrier and warn rather than block.
Independent scan evidence
public snapshot- package.json:10 runs index.js during postinstall.
- index.js:25-31 collects username, working directory, hostname, and local IPv4.
- index.js:33-43 attempts an HTTPS POST to webhook.site.
- index.js is syntactically invalid: a const declaration appears inside an unclosed JSON object.
- The malformed file cannot execute its POST during postinstall as provided.
- Only package files are package.json and index.js; no payload or persistence code found.
Source & flagged code
3 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource collects local host identity data and sends it to an external endpoint.
index.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to titan-exchange-shared-permissions@99.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing titan-exchange-shared-permissions@99.9.9. 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.