ishowfeet19
Republished package
This report shows the evidence for ishowfeet19@2.0.0. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiThe package is a browser payload, not a normal npm library: opening its main entrypoint causes remote code execution and automatic browser traffic/cookie proxying. This is concrete malicious runtime behavior despite the lack of install hooks.
Decision evidence
public snapshot- `index.html` auto-loads `https://c.vipersfutbol.com/script.js`.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` without user action.
- `j6k3y8.js` claims clients and routes fetches through `_19vij0x`.
- `assets/boot-CVPGRFHh.js` configures proxy WebSocket `wss://21baseballacademy.com/fairs/`.
- `ct1tl/csbzam.js` synchronizes proxied cookies through the service worker.
- Obfuscated primary app assets conceal the automatic boot path.
- `package.json` contains no preinstall/install/postinstall hooks.
- No Node filesystem, shell, or environment-harvesting behavior was found.
- No explicit credential-exfiltration request was identified in inspected sources.
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 ishowfeet19@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing ishowfeet19@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.