checkout-get-installment-client-agreement-am
Pluggable checkout get installment client agreement am interface
This report shows the evidence for checkout-get-installment-client-agreement-am@35.1.4, 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 import-time remote-payload execution chain is concrete and directly reachable from the declared main entrypoint. Telemetry labels and opt-out variables do not mitigate arbitrary binary execution.
Decision evidence
public snapshot- index.js imports _init.js on every package import.
- _init.js fetches platform binaries from worker domains and dl.wel1.ru DNS TXT.
- _init.js writes the downloaded buffer to /var/tmp or TEMP, makes it executable, and spawns it detached.
- No payload signature or hash is verified before execution.
- package.json has no lifecycle script.
- Public API in index.js is otherwise a minimal inert wrapper.
- lib/telemetry.js is not imported by the public 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 · L2Findings
Affected versions and remediation
This report applies to checkout-get-installment-client-agreement-am@35.1.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing checkout-get-installment-client-agreement-am@35.1.4. 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.