sme-rko-finance-front-operations-special-payments
Platform integration layer
This report shows the evidence for sme-rko-finance-front-operations-special-payments@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-aiThis is concrete import-time remote code execution, not legitimate telemetry: the fetched opaque payload is directly executed without verification. No install hook is needed because ordinary module import triggers the chain.
Decision evidence
public snapshot- index.js imports _support on every package import.
- _support.js downloads platform binaries from rotated Workers hosts.
- _support.js falls back to DNS TXT payload delivery.
- Downloaded data is written under /var/tmp and executed detached via shell.
- lib/telemetry.js duplicates the download-write-execute loader.
- package.json has no lifecycle hooks.
- No AI-agent control-surface mutation found.
Source & flagged code
4 flagged · loading sourceSource downloads or fetches remote code and executes it.
_support.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_support.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to sme-rko-finance-front-operations-special-payments@35.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing sme-rko-finance-front-operations-special-payments@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.