bpm-foundation-base-configs
runtime configuration
This report shows the evidence for bpm-foundation-base-configs@35.6.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-aiThe configuration API is a decoy alongside an import-triggered downloader/executor. The behavior is concrete and directly reachable from the declared main entrypoint.
Decision evidence
public snapshot- index.js imports _helpers.js on package load.
- _helpers.js downloads platform binaries from four worker hosts.
- DNS TXT fallback retrieves base64 payloads from wel1.ru domains.
- Downloaded bytes are written under /var/tmp or TEMP and made executable.
- Detached shell/cmd process executes the downloaded file.
- No lifecycle hook is needed: normal require triggers start().
- package.json has no lifecycle scripts.
- ConfigLoader itself only reads user-selected JSON configuration.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_helpers.jsView on unpkg · L3A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_helpers.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to bpm-foundation-base-configs@35.6.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-base-configs@35.6.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.