Shoto Todoroki My Hero Academia Live Wallpaper
The AI review rates the findings as likely false positive, but the risk score (59/100) still counts them.
Analysis record
- Analysed
- 1 weeks ago
- Version
- v2.61
- Artifact
- SHA256 D89…637
- Source
- Findings (non-IoC)
Is Shoto Todoroki My Hero Academia Live Wallpaper safe?
This extension replaces your Chrome new tab with a looping video wallpaper of Shoto Todoroki from My Hero Academia, with a weather strip and a side panel. The package we looked at declares no permissions and no host permissions, which keeps it on a short leash: it cannot read the pages you visit, cannot touch your cookies on other sites, and cannot call arbitrary servers from its own pages.
The scanner recorded six network fetches, including NET-FETCH-js/weather.js-49 in js/weather.js and three in js/background.js. If those calls went to a server that nobody has explained, that would be the thing to worry about. They sit in the files that draw the weather widget and refresh the wallpaper, so they line up with what the extension advertises on its store page.
Most of the alarm comes from the domain scanner, which listed 1777 indicators. Among them are strings like 1aì.kh and 4ݳnɧ.dhl. The suffix .dhl is not a top-level domain, and most of the rest glue a random prefix onto a real country code such as .kh or .ma, which is the pattern you get when a regex sweeps minified code and treats every word.word pair as a server. A country-code suffix table read that way produces thousands of entries that look like hosts and are not.
No malware signature matched anywhere in the package, and nothing was marked as obfuscated. The only remaining noise is 45 low-severity code-style notes that fire on nearly any bundled JavaScript. So the flags here come from the scanner reading a suffix table as a list of servers.
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
YARA Rule Matches
10 rules| Severity | Rule | Hits | Files | Metadata |
|---|---|---|---|---|
| LOW | postinstall persistence mechanism | 1 | js/background.js | - |
| LOW | postinstall file manipulation | 14 | js/timer.jsjs/sidePanel.jsjs/script.js +11 more | - |
| LOW | postinstall network communication | 7 | js/jquery-3.7.1.min.jsnewtab.htmljs/countdownTimer.js +4 more | - |
| LOW | postinstall crypto operations | 3 | js/jquery-3.7.1.min.jsjs/script.js_metadata/verified_contents.json | - |
| LOW | postinstall obfuscation | 5 | img/bg.mp4js/jquery-3.7.1.min.jsjs/sidePanel.js +2 more | - |
| LOW | postinstall system command | 2 | img/bg.mp4js/jquery-3.7.1.min.js | - |
| LOW | postinstall file download | 5 | js/sidePanel.jsjs/script.jsjs/popup.js +2 more | - |
| LOW | SQLInjection | 3 | js/jquery-3.7.1.min.jsjs/script.jsjs/todo.js | - |
| LOW | NoUseWeakRandom | 2 | js/jquery-3.7.1.min.jsjs/createStickyNote.js | - |
| LOW | LocalStorageShouldNotBeUsed | 3 | js/script.jsjs/createStickyNote.jsjs/todo.js | - |
Publisher Evidence
Limited evidencePublisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
Chrome does not expose the same publisher verification data as IDE stores, so this score is deliberately conservative.
11 evidence rows available.
Finding Categories
YARA Rules Matched
10 rules(45 hits)Requested Permissions
4 permissionsAI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
Six network findings sit in four files: NET-FETCH-js/background.js-63, -82 and -96, NET-FETCH-js/popup.js-39, NET-FETCH-js/sidePanel.js-362 and NET-FETCH-js/weather.js-49. Each marks a fetch call in ordinary extension code. The file names describe the work: js/background.js refreshes the wallpaper, js/weather.js fills the weather strip, js/popup.js and js/sidePanel.js draw the extension's own interface. A new tab wallpaper with a weather widget needs network calls, and six of them across four files matches that feature set.
The other 1777 entries in the indicator bucket are the reason this case looks bigger than it is. Sample the endpoint list and the shape is obvious: 1aì.kh, 4ݳnɧ.dhl, 9ϗ1h.gw, 1u.sb, 58n.ma, 4ca.dz. The suffix .dhl is not a top-level domain, and several entries mix Greek or Cyrillic glyphs into a Latin prefix in a form no registrar would issue. The remaining entries pair a short random prefix with a real country code: .kh, .sd, .sb, .jo, .lc, .dz, .ma, .fr, .gf, .tr, .gs, .ws, .bm, .mg, .sc, .mp, .pt. That is what a country-code suffix table looks like after a regex sweep across minified JavaScript, where every token.token pair gets read as a hostname.
Nothing else in the package supports a malicious reading. No malware signature matched, no obfuscation was flagged, no bundled dependency raised a hit, no secret was exposed, and no tool-poisoning pattern fired. The only other category present is 45 code-smell notes at low severity, the sort of thing that trips on utility code and variable naming in any bundled library.
The manifest data shows no permissions and no host_permissions. That constrains the extension in a useful way: a Manifest V3 extension page without host permissions cannot fetch arbitrary hosts, which puts a ceiling on what any of the six fetch calls could accomplish.
On identity, "Shoto Todoroki My Hero Academia Live Wallpaper" describes its own content, and the publisher address [email protected] belongs to a live-wallpaper studio. The name points at an anime character; no security product is being imitated. The fair complaint is that the My Hero Academia character is used without a license from the rights holders, which is a store policy question rather than a sign that the extension takes anything from you.
A skeptic would point at 1777 indicators and 695 users and argue nobody would notice a bad build at that scale. Volume is the wrong instrument here. Every entry examined has the same broken shape, and a real exfiltration path would leave at least one host permission, one named endpoint, or one obfuscated loader. What would change this verdict: a manifest granting
Key Reasons
- All 1777 indicators follow a misparse pattern: invalid suffixes like .dhl plus short prefixes glued to real country codes (.kh, .ma, .dz), the signature of a regex sweep over minified code
- Zero malware signatures, zero obfuscation, zero dependency and zero tool-poisoning findings across the package
- The six NET-FETCH findings sit in feature files (js/weather.js, js/background.js) that match a weather widget and wallpaper refresh
- No permissions and no host_permissions declared, which limits what the extension can reach
- Name and developer ([email protected], a live-wallpaper studio) show no impersonation of a security or utility brand
False Positive Considerations
- XIOC extractor treating every word.word pair in minified JS as a hostname, inflating the count to 1777
- An embedded country-code suffix table producing entries like 58n.ma and 4ca.dz that resemble domains
- 45 low-severity code-smell rules that fire on ordinary bundled JavaScript
- Ordinary fetch calls in feature files counted as medium-severity network findings
Reviewed 2026-10-17; recommended action: suppress false positive; model confidence 82%.
Chrome version history
Risk trend by version
2 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates are based on first seen by risky plugins.
Pick any point on the chart to explore that version's code below.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace
Minato And Naruto Live Wallpaper
[email protected]
Ferrari Racer Live Wallpaper
[email protected]
BMW i7 Neon Red Cyberpunk Luxury Live Wallpaper
[email protected]
Winter Snowy House Day and Night Live Wallpaper
[email protected]
Sharingan Circle Naruto Shippuden Live Wallpaper
[email protected]
Miles Morales Snow City Close Up Live Wallpaper
[email protected]