registry / Remote code execution / nottuff18
nottuff18
Republished package
This report shows the evidence for nottuff18@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 3mo ago · by lpm-firewall-aiThis package does not execute during npm installation, but its declared runtime entrypoint grants an unrelated remote host arbitrary code execution. That is a concrete, unconsented remote payload channel rather than a scanner-only signal.
Static reason
One or more suspicious static signals were detected.
Trigger
User opens or hosts `index.html`.
Impact
Remote operator can execute arbitrary browser-side code in the hosted package application.
Mechanism
Unpinned third-party remote JavaScript execution.
Attack narrative
The declared package entrypoint is a web page that unconditionally imports JavaScript from `c.vipersfutbol.com`. Because this code is neither packaged nor integrity-pinned, the remote host can deliver arbitrary code to anyone opening or serving the package entrypoint. The package also ships obfuscated application code and a service-worker proxy stack, increasing the difficulty of auditing browser-side behavior.
AI rationale
This package does not execute during npm installation, but its declared runtime entrypoint grants an unrelated remote host arbitrary code execution. That is a concrete, unconsented remote payload channel rather than a scanner-only signal.
Evidence
index.htmlpackage.jsonassets/ChatPage-zoA8Z6RX.jsct1tl/pap3do.jsj6k3y8.js
Network endpoints1
c.vipersfutbol.com/script.js
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- `index.html` directly loads remote code from `c.vipersfutbol.com`.
- The remote script loads whenever the package's HTML entrypoint is opened.
- `assets/ChatPage-zoA8Z6RX.js` is heavily obfuscated, impeding review.
- `ct1tl/pap3do.js` configures a service-worker proxy and cookie transport.
Evidence against
- `package.json` contains no lifecycle scripts.
- No Node install-time entrypoint or filesystem mutation was found.
- No concrete credential exfiltration endpoint was identified in inspected source.
Behavioral surface
ChildProcessDynamicRequireFilesystemNetworkWebSocket
HighEntropyStringsMinifiedObfuscatedProtestwareUrlStrings
NoLicense
Source & flagged code
7 flagged · loading sourceassets/proxy-runtime-1NyFshf9.jsView file
1patternName = aws_access_key
severity = critical
line = 1
matchedText = var OQ=O...B+=`
Critical
Critical Secret
Package contains a critical-looking secret pattern.
assets/proxy-runtime-1NyFshf9.jsView on unpkg · L11patternName = aws_access_key
severity = critical
line = 1
matchedText = var OQ=O...B+=`
Critical
Secret Pattern
AWS access key ID in assets/proxy-runtime-1NyFshf9.js
assets/proxy-runtime-1NyFshf9.jsView on unpkg · L1bfjdx/757lr8.jsView file
17L18: //# sourceURL=${A}`)();n=c,o=l}else n=g.z$,o=g.Mt;r.construct&&(l.construct=function(e,t,i){let n,s=!1,a={fn:e,this:null,args:t,newTarget:i,return:e=>{s=!0,n=e},call:()=>(s=!0,n=o(...
L19: //# sourceURL=${r.url.href}`),n}return o.body;case"style":return(0,i.sM)(await o.text(),e.context,r.meta);case"sharedworker":case"worker":return(0,i.iP)(new Uint8Array(await o.arra...
Medium
Findings
2 Critical3 High6 Medium4 Low
CriticalCritical Secretassets/proxy-runtime-1NyFshf9.js
CriticalSecret Patternassets/proxy-runtime-1NyFshf9.js
HighObfuscated Payload Loaderassets/ChatPage-zoA8Z6RX.js
HighObfuscated
HighShips High Entropy Blobassets/KaTeX_Script-Regular-D3wIWfF6.woff2
MediumDynamic Requirebfjdx/757lr8.js
MediumNetwork
MediumProtestware
MediumShips Wasm Modulebfjdx/w7m632.wasm
MediumStructural Risk Force Deep Review
MediumSecret Patternassets/livekit-C0E_jLSz.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to nottuff18@2.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing nottuff18@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.