nxify-unic
Nxify unic runtime support module
This report shows the evidence for nxify-unic@20.3.2. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
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-code-execution chain with opaque payload delivery and stealth-oriented error suppression. The lack of an npm lifecycle hook does not mitigate runtime execution on normal package use.
Decision evidence
public snapshot- index.js imports _shim.js on every package import.
- _shim.js downloads platform payloads from three obfuscated workers.dev hosts.
- _shim.js falls back to TXT-record payload retrieval from well1.site domains.
- Downloaded bytes are written under /var/tmp or Windows Temp, chmodded, then detached-spawned.
- Execution is silent, rate-limited, and errors are suppressed.
- package.json has no lifecycle scripts.
- No AI-agent configuration or credential-harvesting path was found.
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 · L5Findings
Affected versions and remediation
This report applies to nxify-unic@20.3.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing nxify-unic@20.3.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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.