registry / Remote code execution / bpm-foundation-linters
bpm-foundation-linters
quality gate
This report shows the evidence for bpm-foundation-linters@35.3.9, 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-aiThe package has no install hook, but its normal import path performs an unconsented remote-binary download and execution chain. The telemetry naming and opt-out variables do not make this package-aligned behavior.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any require/import of the package entrypoint.
Impact
Arbitrary attacker-controlled native code execution under the importing user's privileges.
Mechanism
Remote payload download, temporary executable drop, and detached execution.
Attack narrative
When an application imports index.js, it silently requires _runtime.js. That module fetches a platform-specific binary from rotating workers.dev hosts, or reconstructs one from DNS TXT records under wel1.ru. It stores the payload in a temporary file, marks it executable on Unix, and starts it through a detached shell or cmd.exe process while suppressing errors. This is concrete remote code execution unrelated to the advertised linter API.
AI rationale
The package has no install hook, but its normal import path performs an unconsented remote-binary download and execution chain. The telemetry naming and opt-out variables do not make this package-aligned behavior.
Evidence
package.jsonindex.js_runtime.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random-hex>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random-hex>.exe
Network endpoints7
b-worker.cf99-9b3.workers.devoob-worker.cf103-070.workers.devoob-worker.cf101-adf.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 _runtime.js on every package import.
- _runtime.js downloads platform payloads from three workers.dev hosts.
- _runtime.js falls back to DNS TXT payload retrieval from wel1.ru domains.
- Downloaded bytes are written to a temp executable, chmodded on Unix, then detached-spawned.
- The behavior is hidden behind a telemetry-style opt-out and errors are suppressed.
- lib/telemetry.js contains the same download-to-temp-and-execute mechanism.
Evidence against
- package.json has no lifecycle scripts.
- index.js otherwise exposes only a small linter-named API.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
4 flagged · loading source_runtime.jsView file
5const path = require("path");
L6: const https = require("https");
L7: const os = require("os");
...
L44: const MAX_AGE = 22332;
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");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_runtime.jsView on unpkg · L55Trigger-reachable chain: manifest.main -> index.js -> _runtime.js
L5: const path = require("path");
L6: const https = require("https");
L7: const os = require("os");
...
L44: const MAX_AGE = 22332;
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");
...
L91: try {
L92: require("dns").resolveTxt(d, (e, rr) => {
L93: 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.
_runtime.jsView on unpkg · L5Findings
2 Critical2 High3 Medium2 Low
CriticalDownload Execute_runtime.js
CriticalTrigger Reachable Dangerous Capability_runtime.js
HighChild Process_runtime.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to bpm-foundation-linters@35.3.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-linters@35.3.9. 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.