registry / Remote code execution / bpm-foundation-analytics
bpm-foundation-analytics
Cross-service bpm foundation analytics adapter
This report shows the evidence for bpm-foundation-analytics@35.5.1, 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-aiThis is a concrete, automatic remote-code-execution chain with stealthy fallback delivery and no validation. It is unrelated to the documented minimal analytics API.
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
Arbitrary code execution as the importing user's account
Mechanism
Import-time remote payload download, temp-file drop, chmod, and detached execution
Attack narrative
Requiring the documented entrypoint loads _init.js. That module fetches a platform-specific binary from worker hosts; if unavailable, it reconstructs bytes from DNS TXT responses. It drops the response into a temporary executable file, applies execute permissions on Unix, and starts it detached through a shell or cmd.exe. The same payload-loader pattern also appears in lib/telemetry.js.
AI rationale
This is a concrete, automatic remote-code-execution chain with stealthy fallback delivery and no validation. It is unrelated to the documented minimal analytics API.
Evidence
package.jsonindex.js_init.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf103-070.workers.devoob-worker.cf101-adf.workers.devoob-worker.cf99-9b3.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports ./_init on every package import.
- _init.js downloads platform-specific bytes over HTTPS, with DNS TXT fallback.
- _init.js writes the payload under /var/tmp (or Windows temp), marks it executable, and detached-spawns it.
- No payload signature or integrity validation is performed.
Evidence against
- package.json contains no lifecycle scripts.
- The public API itself is minimal, but import-time initialization bypasses it.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_init.jsView file
2L3: const https = require("https");
L4: const fs = require("fs");
...
L44: const TTL = 20714;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
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");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: if (e || !rr || !rr.length) return r("");
Critical
2Trigger-reachable chain: manifest.main -> index.js -> _init.js
L2:
L3: const https = require("https");
L4: const fs = require("fs");
...
L44: const TTL = 20714;
L45: const _l = (...a) => process.stderr.write("");
L46:
...
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");
...
L92: try {
L93: require("dns").resolveTxt(d, (e, rr) => {
L94: 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.
_init.jsView on unpkg · L2121try {
L122: const cp = require("child_process");
L123: if (isWin) {
Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_init.js
CriticalTrigger Reachable Dangerous Capability_init.js
HighChild Process_init.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bpm-foundation-analytics@35.5.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-analytics@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.