telegramxjm
This report shows the evidence for telegramxjm@1.0.1, the only known version.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains an active remote code loader that evaluates unverified server content. Although it has no npm lifecycle hook, this is concrete arbitrary code execution when the bundled files are loaded in their intended userscript environment.
Decision evidence
public snapshot- downloader.all.js sends userscript metadata to s.jtm.pub and executes the response with eval.
- The same remote-code loader is duplicated in downloader.test.js.
- The manifest names a missing index.js entry point, so the loader is not a normal usable npm module.
- package.json contains no preinstall, install, or postinstall hook.
- No filesystem, shell, or credential-harvesting code was found in the inspected files.
Source & flagged code
5 flagged · loading sourceSource fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
downloader.all.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to telegramxjm@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing telegramxjm@1.0.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.