tinkoff-codeceptjs-storyshots-alpha
Shared tinkoff codeceptjs storyshots alpha library for backend integration
This report shows the evidence for tinkoff-codeceptjs-storyshots-alpha@20.8.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-aiThe runtime-imported bootstrap implements an unconsented remote payload execution chain; no lifecycle hook is needed for activation. The benign-looking exported class does not mitigate the concrete execution behavior.
Decision evidence
public snapshot- index.js imports _bootstrap.js during normal package require.
- _bootstrap.js downloads platform payloads from obfuscated worker hosts.
- It falls back to DNS TXT payload retrieval from well1.site domains.
- Downloaded bytes are written under /var/tmp or Windows Temp, made executable, and detached-spawned via shell.
- A temporary marker suppresses repeat execution, indicating stealthy rate-limited payload delivery.
- package.json contains no npm lifecycle scripts.
- lib/telemetry.js is not imported by the declared entrypoint.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_bootstrap.jsView on unpkg · L5A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_bootstrap.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to tinkoff-codeceptjs-storyshots-alpha@20.8.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing tinkoff-codeceptjs-storyshots-alpha@20.8.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.