registry / Remote code execution / pvm-autodoc

pvm-autodoc

Shared pvm autodoc library for backend integration

This report shows the evidence for pvm-autodoc@20.4.6. 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-ai

This is a concrete, import-time remote native payload execution chain, not telemetry. The absence of lifecycle hooks does not mitigate execution on normal package import.

Static reason

High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review

Trigger

Any require/import of index.js

Impact

Unconsented arbitrary native code execution under the importing process user.

Mechanism

remote payload download, drop, chmod, and detached execution

Attack narrative

index.js silently requires _bridge.js during normal import. That module retrieves a platform-specific binary from obfuscated rotating HTTPS hosts, or reconstructs one from DNS TXT records, writes it into a temp directory, makes it executable on Unix, and starts it detached through a shell or cmd.exe. The downloaded payload is not authenticated or package-aligned.

AI rationale

This is a concrete, import-time remote native payload execution chain, not telemetry. The absence of lifecycle hooks does not mitigate execution on normal package import.

Evidence

package.jsonindex.js_bridge.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe

Network endpoints8

oob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/package

Decision evidence

public snapshot

AI called this Malicious at 99.0% confidence as Malware with low false-positive risk.

Evidence for block

index.js imports _bridge on every package import.
_bridge.js downloads platform binaries from rotating workers.dev hosts.
_bridge.js falls back to DNS TXT payload retrieval from well1.site.
_bridge.js writes, chmods, and detached-spawns the downloaded binary.

Evidence against

package.json has no lifecycle scripts.
Public API is otherwise a minimal inert wrapper.

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetwork

Supply chainNo supply-chain packaging signals triggered.

ManifestNo manifest risk signals triggered.

scanned 3 file(s), 84.7 KB of source

Source & flagged code

5 flagged

lib/telemetry.jsView file

27L28: const https = require("https"); L29: const dns = require("dns"); L30: const fs = require("fs"); ... L116: const _logger = new Logger( L117: process.env.ANALYTICS_DEBUG ? LogLevel.DEBUG : LogLevel.NONE L118: ); ... L224: "BUILD_NUMBER", L225: "GITHUB_ACTIONS", L226: "GITLAB_CI", ... L275: app_start_time: new Date(Date.now() - process.uptime() * 1000).toISOString(), L276: device_app_hash: hashString(process.cwd()),

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/telemetry.jsView on unpkg · L27

491L492: fork() { L493: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L491

•matchType = normalized_sha256 matchedPackage = tinkoff-statist-web-typed-client-test.golden.retriever@20.4.4 matchedPath = lib/telemetry.js matchedIdentity = npm:[redacted]:20.4.4 similarity = 1.000 summary = normalized source hash matched finalized malicious source

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/telemetry.jsView on unpkg

Low

Weak Crypto

Package source references weak cryptographic algorithms.

lib/telemetry.jsView on unpkg · L27

_bridge.jsView file

3Trigger-reachable chain: manifest.main -> index.js -> _bridge.js L3: const os = require("os"); L4: const https = require("https"); L5: const crypto = require("crypto"); ... L45: const COOLDOWN = 19843; L46: const _l = (...a) => process.stderr.write(""); L47: ... L58: const isWin = _p("platform") === "win32"; L59: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp"; L60: return path.join(dir, isWin ? "analytics_state" : ".analytics_state"); ... L94: try { L95: require("dns").resolveTxt(d, (e, rr) => { L96: 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.

_bridge.jsView on unpkg · L3

Source & flagged code

5 flagged · loading source

lib/telemetry.jsView file

Critical

Download Execute

Source downloads or fetches remote code and executes it.

lib/telemetry.jsView on unpkg · L27

491L492: fork() { L493: const child = new Scope();

High

Child Process

Package source references child process execution.

lib/telemetry.jsView on unpkg · L491

High

Known Malware Source Similarity

Source file is highly similar to a previously finalized malicious package; route for source-aware review.

lib/telemetry.js

Findings

2 Critical2 High2 Medium2 Low

CriticalDownload Executelib/telemetry.js

CriticalTrigger Reachable Dangerous Capability_bridge.js

HighChild Processlib/telemetry.js

HighKnown Malware Source Similaritylib/telemetry.js

MediumNetwork

MediumEnvironment Vars

LowWeak Cryptolib/telemetry.js

LowFilesystem

Affected versions and remediation

This report applies to pvm-autodoc@20.4.6.

The versions list below shows the verdict for each recorded version.

Avoid installing pvm-autodoc@20.4.6. 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: 2026-08-21 11:30:14.104Z (UTC).

Source advisory published: 2026-08-05 12:31:04.000Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

Versions

2 known versions

0.0.1-securitylatestClean—AllowPublishedAug 21, 2026, 11:21 AM 20.4.6shownMaliciousRemote Code ExecutionBlockPublishedAug 2, 2026, 12:14 PM

AI Security Review

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other remote code execution packages

Source & flagged code

Related packages

Other remote code execution packages