bpm-foundation-nest-keycloak-connect
Reusable bpm foundation nest keycloak connect components
This report shows the evidence for bpm-foundation-nest-keycloak-connect@35.8.6, 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 hidden loader is reachable on ordinary import and executes unauthenticated remote payloads. Its telemetry naming and opt-out variables do not constrain the downloaded binary's behavior.
Decision evidence
public snapshot- index.js imports _shim.js on every package import.
- _shim.js downloads binary payloads over HTTPS and DNS TXT fallback.
- _shim.js writes payloads to /var/tmp or Windows Temp, chmods, then detached-spawns them.
- Remote hosts and wel1.ru DNS domains are hard-coded and obscured by string joining.
- package.json has no lifecycle hook; activation is import-time instead.
- No credential harvesting or AI-agent configuration writes found.
- lib/telemetry.js remote-execution path is exported but 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.
_shim.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to bpm-foundation-nest-keycloak-connect@35.8.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing bpm-foundation-nest-keycloak-connect@35.8.6. 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.