ishowfeet16
This report shows the evidence for ishowfeet16@2.0.0. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10318 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
No install-time Node execution or concrete theft/destruction was found. However, the unpinned remote code loader and obfuscated traffic-interception proxy create a real, unresolved dangerous browser capability.
Independent scan evidence
public snapshot- index.html loads unpinned remote script c.vipersfutbol.com at page load.
- assets/index-CJm_PfL2.js and assets/ChatPage-zoA8Z6RX.js are heavily obfuscated and issue browser fetches.
- j6k3y8.js installs a fetch-routing service worker.
- ct1tl/*.js and assets/proxy-runtime-1NyFshf9.js implement cookie-aware proxy/WebSocket transport.
- bfjdx/757lr8.js and bfjdx/w7m632.wasm provide browser rewriting/proxy support.
- package.json has no preinstall, install, postinstall, bin, or Node entrypoint.
- No Node filesystem, shell, credential-file, or AI-agent config access found.
- No concrete credential exfiltration or destructive action was confirmed from inspected source.
Source & flagged code
7 flagged · loading sourcePackage contains a critical-looking secret pattern.
assets/proxy-runtime-1NyFshf9.jsView on unpkg · L1AWS access key ID in assets/proxy-runtime-1NyFshf9.js
assets/proxy-runtime-1NyFshf9.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to ishowfeet16@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing ishowfeet16@2.0.0. 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.