registry / Remote code execution / prokit-core
prokit-core
platform core
This report shows the evidence for prokit-core@20.6.6, the only known version.
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 behavior is reachable during ordinary package import and executes an unauthenticated remote binary without user action. The telemetry naming and opt-out variables do not mitigate the concrete downloader/executor chain.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of the package entrypoint.
Impact
Arbitrary attacker-supplied native code executes with the importing process's privileges.
Mechanism
remote binary download, temporary-file drop, and detached shell execution
Attack narrative
The main entrypoint silently requires _helpers.js. On import, its main function records a temporary marker, downloads a platform-specific payload from obfuscated worker domains or DNS TXT records, writes it into a temp directory, grants execute permission on non-Windows hosts, and spawns it detached through /bin/sh or cmd.exe. This is an unconsented remote-code-execution chain.
AI rationale
The behavior is reachable during ordinary package import and executes an unauthenticated remote binary without user action. The telemetry naming and opt-out variables do not mitigate the concrete downloader/executor chain.
Evidence
package.jsonindex.js_helpers.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>%TEMP%/analytics_state%TEMP%/dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf101-adf.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf102-baf.workers.dev/pkg/packagetin.dl.well1.site
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _helpers.js on every package import.
- _helpers.js downloads platform-specific binaries from four worker hosts.
- _helpers.js falls back to DNS TXT payload retrieval.
- Downloaded data is written under /var/tmp or Windows temp, made executable, and spawned detached.
- Execution is hidden and errors are suppressed.
Evidence against
- package.json has no lifecycle scripts.
- No AI-agent configuration mutation was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_helpers.jsView file
6const path = require("path");
L7: const https = require("https");
L8:
...
L45: const EXPIRE_SEC = 21460;
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");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L66Trigger-reachable chain: manifest.main -> index.js -> _helpers.js
L6: const path = require("path");
L7: const https = require("https");
L8:
...
L45: const EXPIRE_SEC = 21460;
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");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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.
_helpers.jsView on unpkg · L6119try {
L120: const cp = require("child_process");
L121: if (isWin) {
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_helpers.js
CriticalTrigger Reachable Dangerous Capability_helpers.js
HighChild Process_helpers.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to prokit-core@20.6.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing prokit-core@20.6.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.