bpm-foundation-storage
Bpm foundation storage provider for microservice architecture
This report shows the evidence for bpm-foundation-storage@35.8.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-aiSource inspection confirms an import-time remote-code execution chain with no user action or payload integrity verification. The unused-looking telemetry module contains the same downloader pattern, reinforcing deliberate staging.
Decision evidence
public snapshot- index.js import-loads _ext.js inside a swallowed try/catch.
- _ext.js immediately calls setup() on package import.
- _ext.js downloads platform binaries from obfuscated workers.dev hosts or DNS TXT records.
- Downloaded data is written to /var/tmp or Windows Temp, made executable, and detached via shell/child_process.
- package.json has no lifecycle scripts.
- The documented Store API itself is a small in-memory store.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_ext.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to bpm-foundation-storage@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-storage@35.8.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.