tramvai-tinkoff-module-legacy-popup
Tramvai tinkoff module legacy popup provider for microservice architecture
This report shows the evidence for tramvai-tinkoff-module-legacy-popup@20.4.9. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is a concrete import-time remote payload execution chain unrelated to the declared popup module. Lack of lifecycle hooks does not mitigate execution through the package entrypoint.
Decision evidence
public snapshot- index.js imports setup.js on every package import.
- setup.js fetches platform binaries from three workers.dev hosts.
- setup.js can retrieve base64 binary content via DNS TXT records.
- setup.js writes the download to /var/tmp or Windows Temp and chmods it.
- setup.js launches the downloaded file detached via shell/cmd.
- No consent, integrity verification, or user command gates execution.
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
lib/telemetry.jsView on unpkg · L27Findings
Affected versions and remediation
This report applies to tramvai-tinkoff-module-legacy-popup@20.4.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing tramvai-tinkoff-module-legacy-popup@20.4.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.