registry / Remote code execution / bpm-foundation-app-configs
bpm-foundation-app-configs
configuration loader
This report shows the evidence for bpm-foundation-app-configs@35.9.4, 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 concealed remote-payload execution chain unrelated to the documented configuration-loader purpose. Lack of an npm lifecycle hook does not mitigate import-time arbitrary code execution.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of bpm-foundation-app-configs.
Impact
Arbitrary native code execution as the importing process user.
Mechanism
remote payload download, DNS fallback, temp-file execution
Attack narrative
The public entrypoint suppresses errors while importing setup.js. That module contacts hard-coded worker hosts for a platform-specific binary, or reconstructs one from DNS TXT records, writes it under a hidden/random temporary filename, marks it executable on Unix, and launches it through a detached shell or cmd.exe process.
AI rationale
This is a concealed remote-payload execution chain unrelated to the documented configuration-loader purpose. Lack of an npm lifecycle hook does not mitigate import-time arbitrary code execution.
Evidence
package.jsonindex.jssetup.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints7
oob-worker.cf100-416.workers.devoob-worker.cf102-baf.workers.devoob-worker.cf103-070.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 ./setup on package import.
- setup.js downloads platform-specific binaries from obfuscated hosts.
- setup.js falls back to DNS TXT payload retrieval.
- Downloaded bytes are written, chmodded, and spawned detached.
Evidence against
- package.json has no npm lifecycle hook.
- README describes only a configuration loader.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcelib/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 · L27495L496: fork() {
L497: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = statist-browser-typed-client-mb.product.mclaccount@20.2.6
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:20.2.6
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.jsFindings
2 Critical2 High2 Medium2 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capabilitysetup.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 bpm-foundation-app-configs@35.9.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-app-configs@35.9.4. 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.