Prevents normal page interaction and forces disruptive audio playback.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The published browser bundle contains an automatic, locale- and domain-targeted disruption: it blocks page interaction and plays external audio after a delay. This is protestware and warrants blocking the version.
Importing the browser bundle on a matching site when the browser language starts with ru, after the stored initiation date is more than three days old.
Mechanism
Top-level code disables body pointer events and automatically appends and plays a looping anthem loaded from flag-gimn.ru.
Attack narrative
When the browser entry bundle is imported on a matching domain by a Russian-language browser, it records the first visit and waits until that date is over three days old. It then blocks pointer interaction and automatically plays a looping anthem fetched from flag-gimn.ru. This targeted disruption is unrelated to a document-template library's purpose.
Evidence
dist/index.jsdist/index.mjs
Network endpoints1
flag-gimn.ru
Decision evidence
public snapshot
Evidence for block
The browser entry bundle checks for a Russian browser language and a host ending in .ru, .su, .by, or .xn--p1ai, then stores an initiation date in localStorage.
After that date is more than three days old, the bundle disables page interaction and adds a looping audio element sourced from flag-gimn.ru; it attempts to play the audio automatically.
Reachable file contains a blocking source-risk pattern.
High
AI review evidence
The browser entry bundle checks for a Russian browser language and a host ending in .ru, .su, .by, or .xn--p1ai, then stores an initiation date in localStorage.
After that date is more than three days old, the bundle disables page interaction and adds a looping audio element sourced from flag-gimn.ru; it attempts to play the audio automatically.
Avoid installing es-document-template@0.0.67. 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.