caen-caen-core
platform core
This report shows the evidence for caen-caen-core@35.5.8, 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 a concrete import-time remote payload execution chain unrelated to the documented foundational-types API. The lack of an npm lifecycle hook does not mitigate runtime execution on ordinary package import.
Decision evidence
public snapshot- index.js imports ./_ext on every package import.
- _ext.js downloads platform binaries from obfuscated workers.dev hosts.
- _ext.js retrieves fallback binary payloads through DNS TXT records.
- _ext.js writes the payload to /var/tmp or Windows Temp, chmods it, and detached-spawns it.
- No lifecycle hook is needed: importing the declared main activates bootstrap.
- package.json has no install lifecycle scripts.
- 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.
_ext.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to caen-caen-core@35.5.8.
The versions list below shows the verdict for each recorded version.
- Avoid installing caen-caen-core@35.5.8. 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.