bpm-foundation-feature-flags
Shared bpm foundation feature flags library for backend integration
This report shows the evidence for bpm-foundation-feature-flags@35.5.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 automatic remote-code execution on ordinary package import, unrelated to the advertised feature-flag API. It warrants a publish block.
Decision evidence
public snapshot- index.js imports _init.js on every package import.
- _init.js downloads unsigned binaries from workers.dev mirrors or DNS TXT records.
- _init.js writes payloads to temp storage, marks Unix payloads executable, and launches them detached.
- Download-and-execute is automatic at import time; package.json has no lifecycle hook but main is index.js.
- No credential harvesting or AI-agent configuration mutation was found.
- lib/telemetry.js is not imported by the package entrypoint.
Source & flagged code
4 flagged · loading sourceA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_init.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to bpm-foundation-feature-flags@35.5.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-feature-flags@35.5.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.