Urgent.News

What's breaking now, across thousands of outlets.

Tech

Rig of Troy: A Suspicious Recovery Script Hidden Inside Roblox Toolbox Models

An investigation into suspicious R6 models, hidden GUIs, remote code loading, and a possible social engineering attack. 1. It Started With an Animation R6 models and animations in the Roblox Toolbox. Everything seemed normal until I inspected one of the models more closely. Inside the character's Right Arm , I found something unexpected: a script called Runtime.lua , accompanied by a complex…

An investigation revealed a hidden script inside Roblox Toolbox models. Developers found suspicious R6 models and animations in the Toolbox. One model had a script called Runtime.lua in its Right Arm object. Further analysis showed similar structures in multiple models from different creators. The script installed an interface inside the PlayerGui, hiding it under MovementElevateAction.

The interface displayed instructions encouraging the execution of an external command. The hidden script also contained a fingerprinting mechanism and checked conditions that could stop the installation. The investigation did not confirm the final payload's purpose, but it raised concerns about the trustworthiness of Roblox Toolbox assets.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

We Dropped Harbor for Large Images. A Traefik Default Was the Cause.

I stopped pushing large images to Harbor because the pushes kept failing. The cause was a default in Traefik, which I had adopted only because ingress-nginx was retired.

  • Large images (over 100 MB) failed to push due to Traefik's default readTimeout
  • 60-second readTimeout cut off parts of large image uploads, causing 504 errors
  • Adjusting Traefik entrypoint's readTimeout to 10 minutes resolved large image pushes

nexus studioQA 14

A red test can mean three very different things: the application broke, the network blinked, or the site showed a bot challenge.

  • SECURE verdict indicates test passed on its own
  • BREACHED verdict signifies application has broken, resulting in bug report
  • Other failures suggest environment or harness is at fault, not a fixed defect

The pause before the action: how Sakupa's confirmation step works

A quick disclosure first: I am not Sakupa's developer. I came across this MCP server while looking into how AI agents publish websites, and this post only organizes facts from its official site and…

  • Sakupa pauses before website changes to show proposed modifications to users.
  • The confirmation step serves to validate edits, prevent errors, and maintain workflow consistency.
  • Designed for static sites, Sakupa lacks dynamic features like databases or login capabilities.

More from Wednesday 4 November →