Scary Baby in Yellow Unblocked πΆπ Play & Track Your Escapes extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) β not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: djaffceijldfkemglkmfpolnjfnmagkg
Permissions (2)
- Store local data
- Schedule tasks
Related extensions
Tomb Escaper Unblocked GameLifestyle
Noob Escape Plan Unblocked ποΈ Play & Track Your EscapesLifestyle
Purrrification Unblocked π₯οΈπβ Instant Play & Save Your ResultsLifestyle
Granny Unblocked: Play Online for Free (No Download)Lifestyle
Granny Unblocked GameLifestyle
The Baby In YellowLifestyle
Frequently asked questions
Is Scary Baby in Yellow Unblocked πΆπ Play & Track Your Escapes safe to use?
Our latest automated scan rates the Chrome listing of Scary Baby in Yellow Unblocked πΆπ Play & Track Your Escapes at 89/100 (low risk) β malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Scary Baby in Yellow Unblocked πΆπ Play & Track Your Escapes require?
Scary Baby in Yellow Unblocked πΆπ Play & Track Your Escapes requests 2 permissions. The most significant: Store local data, Schedule tasks. See the full breakdown in the security report.
Who develops Scary Baby in Yellow Unblocked πΆπ Play & Track Your Escapes?
Scary Baby in Yellow Unblocked πΆπ Play & Track Your Escapes is published by MAGBEI GAMES. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 1.1
- Current listed version
- 1.1
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 0 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisherβs servers. A low-risk result is not a guarantee of safety. How our checks work.