backupsitetuff9
Republished package
This report shows the evidence for backupsitetuff9@2.0.0. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiAlthough npm installation itself has no lifecycle hook, the declared `index.html` entrypoint immediately imports remote code and ships a service-worker proxy to an external transport. The source establishes a concrete runtime attack surface and offers no package-aligned justification.
Decision evidence
public snapshot- `index.html` automatically loads remote code from `https://c.vipersfutbol.com/script.js`.
- `assets/boot-CVPGRFHh.js` registers `j6k3y8.js` as a service worker and configures a proxy controller.
- The proxy boot code hard-codes `wss://21baseballacademy.com/fairs/` as its transport endpoint.
- `assets/ChatPage-zoA8Z6RX.js` is deliberately obfuscated while containing credential-oriented sign-in/sign-up API flows.
- `package.json` has no npm lifecycle scripts.
- No Node filesystem, child-process, or environment-variable harvesting was confirmed.
- No install-time execution path was found.
Source & flagged code
9 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 backupsitetuff9@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing backupsitetuff9@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.