wiasdcxc
This report shows the evidence for wiasdcxc@1.0.1, the only known version.
OpenSSF/OSV Malicious Advisory
imported 2h ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18698 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
Automatic install-time reporting of hostname and project paths creates a concrete metadata disclosure risk, though the recipient is restricted to localhost. This supports a warning rather than a block because no external exfiltration or other attack behavior is established.
Independent scan evidence
public snapshot- The postinstall hook automatically runs beacon.cjs.
- The beacon sends package, hostname, install path, working directory, and npm user-agent metadata to a fixed localhost URL.
- Importing the main entrypoint also attempts to fire the beacon.
- The destination is fixed at 127.0.0.1; no external endpoint or credential collection is shown.
Source & flagged code
8 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgThe postinstall hook automatically runs beacon.cjs.
package.jsonView on unpkg · L5Source fingerprint signature matches a known malicious package signature; route for source-aware review.
Findings
Affected versions and remediation
This report applies to wiasdcxc@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing wiasdcxc@1.0.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.