Federal prosecutors bust suspects in violent Apple delivery heist


Federal prosecutors arrested three men accused of carrying out the robbery.

Federal prosecutors say three men pulled off a violent hijacking of an Apple delivery truck outside a New York shopping center and escaped with more than a million dollars worth of iPhones, MacBooks, and other products.

The armed January robbery reportedly netted more than $1.2 million worth of stolen Apple products, including iPhone, MacBooks, iPads, Apple Watch, and accessories. Authorities described the robbery as a coordinated operation where suspects forced delivery workers into a truck at gunpoint before relocating the cargo to another vehicle.

The suspects were identified as Alan Christhofer Cedeno-Ferrer, Michael Mejia-Nunez, and Ennait Alexis Sirett-Padilla. Delivery workers unloading Apple merchandise outside the shopping center in Manhasset were intercepted by masked men armed with handguns.

A black Honda Accord pulled up beside the truck, and the men approached the victims before forcing them to a nearby location. One worker was restrained with zip ties in the back of the truck during the robbery.

Another worker was forced into the driver’s seat and ordered to drive less than half a mile to a secluded parking area behind an office building. The suspects later confined both workers inside the cargo area while they transferred Apple products into a second vehicle.

Prosecutors describe a coordinated cargo theft operation

The robbery operation used a second truck staged for the merchandise transfer. Surveillance footage allegedly showed a Home Depot box truck following the hijacked Apple delivery vehicle to a nearby secondary location.

The suspects aligned the rear cargo compartments so they could quickly move Apple products between the trucks out of public view.

Once the transfer was complete, the suspects shut the cargo doors with the victims still inside and fled the scene. One worker later managed to free himself and call 911.

The defendants later pleaded not guilty in federal court. They were ordered held without bail pending trial.

Apple shipments remain attractive targets for organized theft rings

ABC News first reported the arrests and details of the alleged Apple delivery truck hijacking.

A single shipment headed to a busy Apple Store can contain hundreds of devices ready for immediate sale. Organized theft crews increasingly target consumer electronics shipments before products ever reach retail stores.

Two slim smartphones stacked side by side, black phone on top of a blue phone, showing their side buttons against a soft purple background on a gray surfaceInvestigators said the suspects used a second truck to move the stolen Apple products.

Apple products have repeatedly been tied to large product heists because they carry high resale value in relatively compact packages.

Even with protections such as Activation Lock and device management systems, stolen Apple hardware can still retain value through unauthorized resale channels and parts harvesting operations.

The suspects also appeared to minimize visibility near the shopping center itself by relocating the truck to a quieter secondary site before transferring merchandise into another enclosed vehicle.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Vibe coding has taken the development world by storm—and it truly is a modern marvel to behold. The problem is, the vibe coding rush is going to leave a lot of apps broken in its wake once people move on to the next craze. At the end of the day, many of us are going to be left with apps that are broken with no fixes in sight.

A lot of vibe “coders” are really just prompt typers

And they’ve never touched a line of code

An AI robot using a computer with a prompt field on the screen. Credit: Lucas Gouveia / How-To Geek

Vibe coding made development available to the masses like never before. You can simply take an AI tool, type a prompt into a text box, and out pops an app. It probably needs some refinement, but, typically, version one is still functional whenever you’re vibe coding.

The problem comes from “developers” who have never written a line of code. They’re just using vibe coding because it’s cool or they think they can make a quick buck, but they really have no knowledge of development—or any desire to learn proper development.

Think of those types of vibe coders as people who realize they can use a calculator and online tools to solve math problems for them, so they try to build a rocket. They might be able to make something work in some way, but they’ll never reach the moon, even though they think they can.

Anyone can vibe code a prototype

But you really need to know what you’re doing to build for the long haul

For those who don’t know what they’re doing, vibe coding is a fantastic way to build a prototype. I’ve vibe coded several projects so far, and out of everything I’ve done, I’ve realized one thing—vibe coding is only as good as the person behind the keyboard. I have spent more time debugging the fruits of my vibe coding than I have actually vibe coding.

Each project that I’ve built with vibe coding could have easily been “viable” within an hour or two, sometimes even less time than that. But, to make something of actual quality, it has always taken many, many hours.

Vibe coding is definitely faster than traditional coding if you’re a one-man team, but it’s not something that is fast by any means if you’re after a quality product. The same goes for continued updates.

I’ve spent the better part of three months building a weather app for iPhone. It’s a simple app, but it also has quite a lot of complex things going on in the background.

It recently got released in the App Store—no small feat at all. But, I still get a few crash reports a week, and I’m constantly squashing bugs and working on new features for the app. This is because I’m planning on supporting the app for a long time, not just the weekend I released it, and that takes a lot more work.

Vibe coders often jump from app to app without thinking of longevity

The app was a weekend project, after all

A relaxed man lounging on an orange beanbag watches as a friendly yellow robot works on a laptop for him, while multiple red exclamation-mark warning icons float around them. Credit: Lucas Gouveia/How-To Geek | ViDI Studio/Shutterstock

I’ve seen it far too often, a vibe coder touting that they built this “complex app” in 48 hours, as if that is something to be celebrated. Sure, it’s cool that a working version of an app was up and running in two days, but how well does it work? How many bugs are still in it? Are there race conditions that cause a random crash?

My weather app has a weird race condition right now I’m tracking down. It crashes, on occasion, when opened from Spotlight on an iPhone. Not every time does that cause a crash, just sometimes.

If a vibe coder’s only goal is to build apps in short amounts of time so they can brag about how fast they built the app, they likely aren’t going to take the time to fix little things like that.

I don’t vibe code my apps that way, and I know many other vibe coders that aren’t that way—but we all started with actual coding, not typing a prompt.


Anyone can be a vibe coder, but not all vibe coders are developers

“And when everyone’s super… no one will be.” – Syndrome, The Incredibles. It might be from a kids’ movie, but it rings true in the era of vibe coding. When everyone thinks they can build an app in a weekend, everyone thinks they’re a developer.

By contrast, not every vibe coder is actually a developer, and that’s the problem. It’s hard to know if the app you’re using was built by someone who has plans to support the app long-term or not—and that’s why there’s going to be a lot of broken apps in the future.

I can see it now, the apps that people built in a weekend as a challenge will simply go without updates. While the app might work for the first few weeks or months just fine, an API update comes along and breaks the app’s compatibility. It’s at that point we’ll see who was vibe coding to build an app versus who was vibe coding just for online clout—and the sad part is, consumers will lose out more often than not with broken apps.



Source link