registry / Remote code execution / bpm-foundation-date-range
bpm-foundation-date-range
Reusable bpm foundation date range components
This report shows the evidence for bpm-foundation-date-range@35.4.2, 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, concealed import-time remote code execution unrelated to the advertised date-range library. The similarly capable telemetry file reinforces the intent but is not required for the verdict.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Runtime import/require of the package
Impact
Arbitrary remote code executes with the importing process's privileges.
Mechanism
import-time remote binary download, drop, and execution
Attack narrative
The normal CommonJS entrypoint suppresses errors while requiring _polyfill.js. That file immediately runs setup(), contacts randomized worker hosts for an OS-specific binary, falls back to base64 DNS TXT reconstruction, drops the resulting payload into a temporary directory, makes it executable on Unix, and starts it through a detached shell or cmd.exe process.
AI rationale
This is concrete, concealed import-time remote code execution unrelated to the advertised date-range library. The similarly capable telemetry file reinforces the intent but is not required for the verdict.
Evidence
package.jsonindex.js_polyfill.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf100-416.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packagesdk.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 _polyfill on every require
- _polyfill.js downloads platform binaries from obfuscated hosts
- DNS TXT fallback reconstructs a binary payload
- Downloaded payload is written, chmodded, then detached-spawned
Evidence against
- package.json has no lifecycle scripts
- index.js exposes a minimal date-range API
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
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 · L27490L491: fork() {
L492: const child = new Scope();
High
•matchType = normalized_sha256
matchedPackage = boxy-scroll-providers@35.5.1
matchedPath = lib/telemetry.js
matchedIdentity = npm:Ym94eS1zY3JvbGwtcHJvdmlkZXJz:35.5.1
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 High3 Medium3 Low
CriticalDownload Executelib/telemetry.js
CriticalTrigger Reachable Dangerous Capability_polyfill.js
HighChild Processlib/telemetry.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowWeak Cryptolib/telemetry.js
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bpm-foundation-date-range@35.4.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-date-range@35.4.2. 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.