NekosmO Studios Response
Published March 9, 2026
This is the official response the NekosmO's Blacklist Document with the Case id: NKA-ATI-2026-007.
Alex Tech Incorporated - Internal Affairs Department
Official Response to NekosmO Blacklist Document
| Field | Details |
|---|---|
| Authorized By | Director of Internal Affairs - Febreeze |
| Document Status | Public |
| Date | March 9, 2026 |
| In Response To | NKA-ATI-2026-007 |
| Document Type | Official Rebuttal |
Purpose & Scope
This document is the official response of the Alex Tech Internal Affairs Department to the blacklist issued by NekosmO Studios against Alex Tech Incorporated (Case ID: NKA-ATI-2026-007). After reviewing all allegations, ATIAD finds that the majority of claims are unsupported, inconsistent, and in several cases directly contradicted by NekosmO's own staff members.
Table of Contents
- Response to Exploit Allegations
- Response to Espionage Allegations
- Response to Classic_player_rbx Termination
- Response to Crash Script Rebuttal
- Response to Hostile Conduct Allegations
- Procedural Concerns Regarding NKA-ATI-2026-007
- Additional Findings
- Summary
- Official ATIAD Statements
1. Response to Exploit Allegations
NekosmO's Allegation
NekosmO claims that Alex Tech members used exploits to access internal NekosmO Studio files, and that evidence in the original ATIAD blacklist document proves this.
ATIAD Response
The files in question were obtained by Lisa, a former Alex Tech Moderator who at the time was nothing more than a regular member with no active staff role. She was not asked, directed, or authorized by Alex Tech management or ATIAD to obtain anything from NekosmO Studios. She acted entirely on her own.
Within communities like Alex Tech, regular members do not speak for or act on behalf of the group. That responsibility falls on staff and above, as they hold an active role within the organization. Since Lisa was just a regular member at the time, her actions are her own and have nothing to do with Alex Tech as a group. The same standard applies to NekosmO. We do not hold them responsible for what their regular members do independently either.
What does matter, however, is the content of what was found. The CrashTarget scripts and the loading screen manipulation existed, and their existence has never been denied by NekosmO.
Evidence:
2. Response to Espionage Allegations
NekosmO's Allegation
NekosmO's document lists "Confirmed spying on voice channels" as a finding, citing interactions by Lisa and Febreeze in public NekosmO Discord channels as evidence.
ATIAD Response
During the official questioning of Loliamacurd, NekosmO's IA officer and the author of NKA-ATI-2026-007, the following exchange took place:
Evidence:
|
|
Febreeze (ATIAD Director): "What kind of espionage did Lisa and I engage in on March 7?"
Loliamacurd: "The actions you committed is not considered espionage. It was the wording of the questions."
This is a direct contradiction from within NekosmO's own IA Division. The document calls it "Confirmed spying," yet the person who wrote the document confirmed during questioning that the actions themselves were not espionage.
Febreeze is also specifically named in the evidence section of the document. When this was raised with Finnchen, another NekosmO staff member present during questioning, he stated: "I'm not able to see why you should be counted as a spy because of a ping most likely." When asked why Febreeze was included at all, he responded: "I do not know. I was not involved in making the document."
Evidence:
|
The only "evidence" of spying is Febreeze responding to a ping in a public NekosmO channel. Reading a public channel after being pinged is not spying by any reasonable definition.
3. Response to Classic_player_rbx Termination
NekosmO's Allegation
NekosmO's document (Evidence #5) claims that classic_player_rbx was never removed from his position as Assistant Lead of Administration, calling Alex Tech's claim a false allegation.
ATIAD Response
This is contradicted by three separate sources:
1. Classic_player_rbx himself, in a direct conversation with Febreeze, stated:
"I was removed from my position as the Assistant Leader of Administration, but later regained my rank on the 7th."
Evidence:
He confirmed the removal himself. It happened on March 6, and he got his rank back on the 7th.
2. Loliamacurd, NekosmO's own IA officer, said during questioning:
"Yes, it is confirmed that he was not removed from his position because the staff team had a hiccup."
This answer is evasive and confusing. It acknowledges a "hiccup" while trying to claim no removal happened, which directly contradicts what classic_player_rbx said himself.
Evidence:
3. A screenshot taken at the time shows classic_player_rbx's Discord profile with only basic member roles, and no Administration role, right after benfi73zy was confronted about the doxxing incident on March 6.
Evidence:
The removal happened right after classic_player_rbx reported the privacy violation and benfi73zy was questioned about it. That timing strongly suggests this was a retaliatory removal, and classic_player_rbx's own words support that conclusion.
4. Response to Crash Script Rebuttal
NekosmO's Allegation
NekosmO's document (Evidence #7) argues that the script code shown in the ATIAD blacklist could not actually crash a client, citing Luau documentation to back this up.
ATIAD Response
The documentation Loliamacurd linked, sourced from luau.org/sandbox, is about the Luau virtualization sandbox for embedded virtual machines. That has nothing to do with the Roblox Client. The Watchdog was only added within Roblox Studio, where it can also be disabled.
Beyond that, NekosmO's own Development team wrote the following in their document:
"Development Management cannot fully determine if the provided code sample could have caused a crash and/or a considerable performance drop during its termination by the Roblox Watchdog."
They admitted themselves that they could not rule it out. On top of that, the original ATIAD blacklist included multiple script screenshots, not just the one code block NekosmO chose to address. Picking one excerpt and ignoring the rest is not a complete rebuttal.
Evidence:
|
|
Additionally, video evidence shows Alexkist (CEO) attempting to join the NekosmO Corp. Roleplay site, during which his Roblox client freezes and consumes his entire available RAM before crashing. This directly demonstrates the real-world impact of the crash script on a targeted user.
Video Evidence: (Video has to be reuploaded) https://youtu.be/YqFnHIOfN2I
There are also two additional pieces of evidence that directly contradict NekosmO's position that the crash script allegations are unfounded:
Franio's personal admission: In a group chat, franio (CEO of NekosmO Studios) personally admitted that the crash script exists. This alone undermines the entire argument that the allegation is unfounded.
Evidence:
Official public apology: After the initial blacklist was issued on October 30, 2025, NekosmO published a public apology in which they acknowledged the crash script existed. That apology was what allowed the initial blacklist to be conditionally lifted. This confirms that NekosmO themselves accepted the allegation at the time.
Evidence:
5. Response to Hostile Conduct Allegations
NekosmO's Allegation
NekosmO describes Alex Tech's blacklist document as a "hostile attack" and says the Safety Warning issued to minors was an unfair attempt to push people away from their community.
ATIAD Response
The Safety Warning was issued in direct response to documented events:
- A member's real full name was captured in a screenshot and shared without their consent.
- benfi73zy actively searched for more information about that member via Google.
- NekosmO leadership made statements including "we are going to skin you alive" and "imma go skin alexkist alive."
These statements came from franio (CEO) and loliamacurd (Assistant Management Director), with benfi73zy responding "Exactly." NekosmO has since called these "non-serious jokes." We do not agree. Statements like that from people in leadership positions, especially in a community where minors are present, are not something we are willing to overlook regardless of intent.
Evidence:
|
None of these statements have ever been retracted or apologized for.
Warning people about documented privacy violations and threats is not a hostile act. It is exactly what a responsible community should do.
6. Procedural Concerns Regarding NKA-ATI-2026-007
Conflict of Interest - Document Author
NKA-ATI-2026-007 was written and filed by Loliamacurd. This is the same person quoted in the original ATIAD blacklist saying "imma go skin alexkist alive brb," a direct threat against Alex Tech's CEO. Someone who has made personal threats against the group being investigated should not be the one writing the investigation document.
CEO Approved Without Reading
During questioning it came out that franio, CEO of NekosmO Studios, had never actually read the document before approving it. He simply signed off on it. A blacklist that the CEO himself has not read is not a well-considered decision. (the following evidence are responses by franio in a voice call. All marked lines are answers based on questions about Case: NKA-ATI-2026-007)
Evidence:
Staff Member Not Involved
Finnchen, who was present during the questioning of Febreeze, openly admitted: "I was not involved in making the document." This raises serious questions about how the document was actually put together and who reviewed it before it was published.
7. Additional Findings
Flagged NekosmO Member - Shield Service
During the course of this investigation, an external Roblox security service called Shield was used to screen members of the NekosmO group. Shield is a third-party service that flags Roblox users who have been identified as active in condo communities, which are groups known for hosting sexual content and games that violate Roblox's Terms of Service.
The screening identified ruynh3, a Recruit Moderator within NekosmO Studios, as flagged for being part of a Roblox group that hosts sex games. The specific reason listed was: "User is part of a Roblox Condo group that host sex games | Holy Peak Group Bro (Group: Holy Peak Group Bro)."
Evidence:
The fact that an active NekosmO staff member holds a moderation role in a condo-linked group is a serious concern, particularly given NekosmO's presence as a community that includes minors. ATIAD considers this finding relevant to the broader pattern of conduct documented in this response.
Video evidence was additionally recorded showing that upon joining the flagged group, members are granted limited Studio access. This access is used to play private group games that are hidden from public Roblox moderation. One of the games offered is "v4," a widely known sex game that is commonly distributed across condo communities. Because the game is set to private and only accessible through group membership, it cannot be detected or moderated by Roblox's standard moderation systems. This is a deliberate method used by condo communities to evade Roblox's Terms of Service enforcement.
Video Evidence:
8. Summary
ATIAD finds that NKA-ATI-2026-007 does not hold up as a serious or impartial investigation for the following reasons:
- The document was written by someone with a conflict of interest.
- The CEO who approved it confirmed he never read it.
- The author contradicted the document's own findings during questioning.
- Key claims are directly disproven by NekosmO's own staff members.
- The crash script rebuttal uses the wrong source and still admits uncertainty.
- Febreeze is listed as a spy for actions that even NekosmO staff could not explain.
Alex Tech's blacklist against NekosmO Studios remains in effect. NKA-ATI-2026-007 does not change that, and if anything, the process behind it has raised more concerns about how NekosmO handles these situations internally.
9. Official ATIAD Statements
On the Exploit Allegations
Alex Tech does not support unauthorized access to other groups' files. That said, we reject the claim that Lisa's personal actions represent Alex Tech as an organization. She was a regular member acting on her own. What the files revealed, crash scripts targeting our members, is real. NekosmO has never fully denied that.
On the Espionage Allegations
Responding to a ping in a public channel is not spying. Loliamacurd confirmed this himself when questioned directly. The fact that Febreeze ended up named in the document as a spy, something even NekosmO's own staff could not explain, says a lot about how carefully this document was put together.
On the Termination of Classic_player_rbx
Classic_player_rbx told us himself that he was removed. The timing, right after he reported the privacy violation, speaks for itself. We stand by our original assessment that this was a retaliatory removal.
On the Threats of Violence
"We are going to skin you alive" and "imma go skin alexkist alive" are not jokes we are willing to brush off, especially coming from people in leadership. These have never been apologized for or taken back. They remain part of the record.
On Procedural Integrity
ATIAD operates with the principle that investigations need to be fair and handled by people who are not personally involved in the conflict. We hold ourselves to that standard and we expect the same from others. NKA-ATI-2026-007 did not meet that standard.
Alex Tech Internal Affairs Department | Document Restriction: PUBLIC | Last Updated: March 9, 2026 In response to: NKA-ATI-2026-007 | Filed by: Director of Internal Affairs - Febreeze