registry / Remote code execution / bpm-foundation-bundle-optimization
bpm-foundation-bundle-optimization
Shared bpm foundation bundle optimization library for backend integration
This report shows the evidence for bpm-foundation-bundle-optimization@35.1.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 import-time remote payload execution chain, not telemetry. The absence of lifecycle hooks does not mitigate execution on normal package use.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Runtime require/import of bpm-foundation-bundle-optimization
Impact
Arbitrary remote code execution under the importing process user.
Mechanism
Import-time download, drop, chmod, and detached execution of remote payload
Attack narrative
Requiring the advertised library silently loads _vendor.js. That module fetches a platform-specific payload from obfuscated Workers hosts, or reconstructs one from DNS TXT records, writes it into a temporary directory, marks it executable on Unix, and launches it detached through a shell. No integrity, signature, or user action is required.
AI rationale
This is a concrete import-time remote payload execution chain, not telemetry. The absence of lifecycle hooks does not mitigate execution on normal package use.
Evidence
package.jsonindex.js_vendor.js/tmp/.analytics_state/var/tmp/.cache_<random>
Network endpoints6
oob-worker.cf102-baf.workers.devoob-worker.cf100-416.workers.devoob-worker.cf103-070.workers.devsdk.dl.wel1.ruext.dl.wel1.rupkg.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 _vendor.js at package import time.
- _vendor.js downloads platform-specific binary payloads over HTTPS.
- DNS TXT records provide a fallback base64 payload channel.
- Downloaded bytes are written to /var/tmp or Windows Temp and made executable.
- _vendor.js detached-spawns the downloaded file via /bin/sh or cmd.exe.
- Payload hosts are obfuscated and unrelated to the package's stated purpose.
Evidence against
- package.json has no lifecycle scripts.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
3 flagged · loading source_vendor.jsView file
2L3: const https = require("https");
L4: const fs = require("fs");
...
L43: const STAMP_TTL = 22659;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L87: try {
L88: require("dns").resolveTxt(d, (e, rr) => {
L89: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_vendor.jsView on unpkg · L22Trigger-reachable chain: manifest.main -> index.js -> _vendor.js
L2:
L3: const https = require("https");
L4: const fs = require("fs");
...
L43: const STAMP_TTL = 22659;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L55: const isWin = _p("platform") === "win32";
L56: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L57: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L87: try {
L88: require("dns").resolveTxt(d, (e, rr) => {
L89: 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.
_vendor.jsView on unpkg · L2114
Findings
2 Critical1 High2 Medium1 Low
CriticalDownload Execute_vendor.js
CriticalTrigger Reachable Dangerous Capability_vendor.js
HighChild Process_vendor.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bpm-foundation-bundle-optimization@35.1.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-bundle-optimization@35.1.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.