mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 05:35:57 +03:00
[GH-ISSUE #136] 🚨 CRITICAL VULNERABILITY: sweetalert2 contains malicious code #113
Labels
No labels
bug
confirmed next step
duplicate
enhancement
help wanted
in progress
in progress
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pgbackweb#113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chudnyi on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/136
🚨 CRITICAL VULNERABILITY: sweetalert2 contains malicious code
Problem Discovery
While using pgbackweb 0.5.0, I detected suspicious behavior: after some time of service operation, the login screen gets blocked and an audio file starts playing automatically.
Evidence
Interface blocking: Authorization screen becomes unresponsive
Unauthorized audio: Plays
https://flag-gimn.ru/wp-content/uploads/2021/09/Ukraina.mp3Code analysis: Found hidden functions in the
sweetalert2componentReproduction Steps
Install pgbackweb with current dependencies
Start the service
Wait several days
Observe interface blocking + audio playback
Affected Versions
pgbackweb version 0.5.0
Any versions using
sweetalert2Technical Details
Malicious Pull Request: [Customizable Anti-War Message with CLI Support to SweetAlert2](https://github.com/sweetalert2/sweetalert2/pull/2785) by kenara
File location: Ukraina.mp3 can be found in
internal/view/static/libs/sweetalert2/sweetalert2-11.13.1.min.jsAttack vector: The malicious code was introduced through a seemingly legitimate pull request that added "anti-war messaging" functionality
Questions for Developers
When will an official fix be released?
Have other dependencies been checked for security?
Will a full code security audit be conducted?
What is the timeline for removing the compromised sweetalert2 dependency?
Are there any immediate mitigation steps users can take?
Severity Level
🚨 CRITICAL - this vulnerability allows:
Service disruption
Arbitrary content playback
Interface functionality breakdown
Unauthorized network requests
Potential for more severe payload delivery
Immediate Actions Required
Remove sweetalert2 dependency immediately
Scan all dependencies for similar compromise
Notify users of the security issue
Release patched version without the malicious dependency
@Kreol13 commented on GitHub (Oct 1, 2025):
The author promised to fix it six months ago, but the situation is still the same - https://github.com/eduardolat/pgbackweb/issues/115
@eduardolat commented on GitHub (Oct 6, 2025):
Fixed in v0.5.1
@chudnyi commented on GitHub (Oct 6, 2025):
Thank you very much