Codeberg/Community
54
325
Fork
You've already forked Community
12

New Issue email notification, but can not see issue in repository #1955

Closed
opened 2025年05月29日 08:28:36 +02:00 by derReparierer · 3 comments

Comment

i regularly receive email notifications, that someone has opened a new issue, e.g. this one:
grafik

When trying to answer this issues (or mark them as resolved after a fix), i am not able to see the issue anymore on codeberg. The issue list is empty, the view on codeberg link in the email runs into Page not Found. Even as logged in user. Also tried on another device and another browser. Here are some Page not Found examples:
derReparierer/derReparierer#6
derReparierer/derReparierer#7
derReparierer/derReparierer#8

In the past, there have been some issues as my user name contains case sensitive characters (Codeberg-CI/feedback#221). Could it be, that there is a similar problem? Or is this related to any other problem?

corresponding repository: https://codeberg.org/derReparierer/derReparierer

### Comment i regularly receive email notifications, that someone has opened a new issue, e.g. this one: ![grafik](/attachments/ffe1d853-3192-45f7-b68f-fb8fdbae5662) When trying to answer this issues (or mark them as resolved after a fix), i am not able to see the issue anymore on codeberg. The issue list is empty, the `view on codeberg` link in the email runs into `Page not Found`. Even as logged in user. Also tried on another device and another browser. Here are some `Page not Found` examples: https://codeberg.org/derReparierer/derReparierer/issues/6 https://codeberg.org/derReparierer/derReparierer/issues/7 https://codeberg.org/derReparierer/derReparierer/issues/8 In the past, there have been some issues as my user name contains case sensitive characters (https://codeberg.org/Codeberg-CI/feedback/issues/221). Could it be, that there is a similar problem? Or is this related to any other problem? corresponding repository: https://codeberg.org/derReparierer/derReparierer
7.5 KiB

I am 90% sure this is part of a deliberate spam attack and the reported issue is a complete fake, i.e. text generated by some kind of LLM.

Codeberg (and me personally) already had the questionable pleasure with other fake issues. The text LOOKS real but if you go into the details, some things don’t really make logical sense. I just got two fake issues today again. What’s scary is that they sound more and more plausible.

Another thing that seems to give the game away (apart from logical contradictions) is the somewhat wordy moralizing or catastrophizing tone in all of those spam issues. OK, real people might act up as well, but it’s a writing style I noticed among all those fake issues. This suggests the text might be coming from the same single LLM.

Codeberg continously deletes those spam accounts and their issues (thank you, Codeberg!). So you only see the e-mail notification while the issue is already deleted.

That’s just my guess tho, this is NOT an official confirmation!

I am 90% sure this is part of a deliberate spam attack and the reported issue is a complete fake, i.e. text generated by some kind of LLM. Codeberg (and me personally) already had the questionable pleasure with other fake issues. The text LOOKS real but if you go into the details, some things don’t really make logical sense. I just got two fake issues today again. What’s scary is that they sound more and more plausible. Another thing that seems to give the game away (apart from logical contradictions) is the somewhat wordy moralizing or catastrophizing tone in all of those spam issues. OK, real people might act up as well, but it’s a writing style I noticed among all those fake issues. This suggests the text might be coming from the same single LLM. Codeberg continously deletes those spam accounts and their issues (thank you, Codeberg!). So you only see the e-mail notification while the issue is already deleted. That’s just my guess tho, this is NOT an official confirmation!

Facing the same issue on one repository. I can nevertheless agree with @Wuzzy 's guess, as the issue texts are pretty much catastrophizing and formally well structured (which is far from the usual issues we get in our communities) and seems to be aimed at demoralizing the developer with such sentences:

"I mean, it should be relatively straightforward to replicate, right?"

or

"If this issue is already known, can we please get some updates on when it might be addressed? If it's not, I insist it should be prioritized. This is a fundamental aspect of the application that needs immediate improvement."

My guess would be either that this is a spam attack or someone thinking she/he could do a study on such issues and developer responses, which is - I would say - far worse as it makes clear a failure on ethics.

Facing the same issue on one repository. I can nevertheless agree with @Wuzzy 's guess, as the issue texts are pretty much catastrophizing and formally well structured (which is far from the usual issues we get in our communities) and seems to be aimed at demoralizing the developer with such sentences: > "I mean, it should be relatively straightforward to replicate, right?" or > "If this issue is already known, can we please get some updates on when it might be addressed? If it's not, I insist it should be prioritized. This is a fundamental aspect of the application that needs immediate improvement." My guess would be either that this is a spam attack or someone thinking she/he could do a study on such issues and developer responses, which is - I would say - far worse as it makes clear a failure on ethics.
Owner
Copy link

Especially since there were multiple issues, this was most likely related to spam attacks. We have seen them on a daily basis around the time when you reported the problem (end of May to early June).

We delete the content as soon as possible. However, there is no way to undo sent emails.

We are trying to avoid generating the email notifications in the first place.

Especially since there were multiple issues, this was most likely related to spam attacks. We have seen them on a daily basis around the time when you reported the problem (end of May to early June). We delete the content as soon as possible. However, there is no way to undo sent emails. We are trying to avoid generating the email notifications in the first place.
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#1955
Reference in a new issue
Codeberg/Community
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?