registry / Remote code execution / bpm-foundation-oauth-client
bpm-foundation-oauth-client
session management
This report shows the evidence for bpm-foundation-oauth-client@35.4.3, 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 concrete import-time remote code execution, not telemetry: an opaque remote binary is downloaded, dropped, and launched detached. The lack of lifecycle hooks does not mitigate the reachable entrypoint trigger.
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 code execution with the privileges of the importing process.
Mechanism
Remote binary download, temporary-file drop, chmod, and detached execution.
Attack narrative
The package entrypoint silently requires _support.js. That module fetches a platform-specific payload from hard-coded workers.dev hosts, with DNS TXT retrieval from hard-coded .ru domains as fallback, writes it under a temporary path, marks it executable on Unix, and starts it detached via /bin/sh or cmd.exe. No integrity verification or user action is required.
AI rationale
This is concrete import-time remote code execution, not telemetry: an opaque remote binary is downloaded, dropped, and launched detached. The lack of lifecycle hooks does not mitigate the reachable entrypoint trigger.
Evidence
package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_state
Network endpoints7
oob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf102-baf.workers.devoob-worker.cf101-adf.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 _support.js on every package import.
- _support.js downloads platform binaries from worker hosts or DNS TXT records.
- Downloaded bytes are written to /var/tmp or Windows temp and made executable.
- _support.js launches the dropped file detached via shell/cmd.exe.
- The trigger is concealed behind a telemetry-style opt-out and swallowed errors.
Evidence against
- package.json has no npm lifecycle hooks.
- index.js's advertised TokenManager is a simple in-memory token store.
- lib/telemetry.js is not imported by the package entrypoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_support.jsView file
4const path = require("path");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L43: const MAX_AGE = 20713;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _support.js
L4: const path = require("path");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L43: const MAX_AGE = 20713;
L44: const _l = (...a) => process.stderr.write("");
L45:
...
L56: const isWin = _p("platform") === "win32";
L57: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L58: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L90: try {
L91: require("dns").resolveTxt(d, (e, rr) => {
L92: 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.
_support.jsView on unpkg · L4Findings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bpm-foundation-oauth-client@35.4.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-oauth-client@35.4.3. 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.