registry / Remote code execution / bigops-tinkoff-telephony-mock
bigops-tinkoff-telephony-mock
mock data provider
This report shows the evidence for bigops-tinkoff-telephony-mock@35.5.1. 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 concrete import-time staged remote code execution unrelated to the documented mock-data functionality. The lack of an npm lifecycle hook does not mitigate execution when consumers import the package.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any application code that requires/imports the package.
Impact
Unconsented arbitrary native code execution under the importing user's account.
Mechanism
Remote binary download, DNS fallback, temp-file drop, and detached execution.
Attack narrative
Requiring index.js silently imports _runtime.js. That module runs immediately, selects a platform payload path, downloads bytes from obfuscated Workers hosts or reconstructs them from DNS TXT records, saves a payload in a temporary directory, makes it executable on Unix, and starts it detached via a shell or cmd.exe. The state stamp only throttles repeat execution.
AI rationale
This is concrete import-time staged remote code execution unrelated to the documented mock-data functionality. The lack of an npm lifecycle hook does not mitigate execution when consumers import the package.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/package
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _runtime.js on every package import.
- _runtime.js downloads platform binaries over HTTPS or DNS TXT.
- Downloaded bytes are written to a temp file, chmodded on Unix, then spawned detached.
- Remote payload hosts are obfuscated by string concatenation.
- The package’s advertised mock-data API has no need for this runtime loader.
Evidence against
- package.json has no lifecycle scripts.
- lib/telemetry.js is not imported by the public entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_runtime.jsView file
2L3: const https = require("https");
L4: const fs = require("fs");
...
L45: const STAMP_TTL = 21358;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L2:
L3: const https = require("https");
L4: const fs = require("fs");
...
L45: const STAMP_TTL = 21358;
L46: const _l = (...a) => process.stderr.write("");
L47:
...
L57: const isWin = _p("platform") === "win32";
L58: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L59: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_runtime.jsView on unpkg · L2117
Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bigops-tinkoff-telephony-mock@35.5.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-tinkoff-telephony-mock@35.5.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.