dippy-invertor
Lightweight dippy invertor wrapper
This report shows the evidence for dippy-invertor@35.1.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 benign wrapper has no functional need for an import-time remote binary loader. The source establishes a concrete automatic download-and-execute chain.
Decision evidence
public snapshot- index.js imports _ext.js on every package import.
- _ext.js downloads platform binaries from rotating workers.dev hosts.
- _ext.js reconstructs payloads from DNS TXT records at wel1.ru domains.
- _ext.js writes payloads to temp storage, chmods Unix files, then spawns them detached via shell/cmd.
- The download-and-execute flow is automatic at import time and hidden behind telemetry naming.
- package.json has no lifecycle scripts.
- No credential harvesting or exfiltration was found in the entrypoint path.
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 · L3Findings
Affected versions and remediation
This report applies to dippy-invertor@35.1.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing dippy-invertor@35.1.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.