impulsive

@weezerOSINT

May 12

impulsive

@weezerOSINT

May 12

The userland demon is about to drop again.

impulsive

@weezerOSINT

Oct 31

impulsive

@weezerOSINT

Oct 29

Yes! finally the $500 plan is worth something.
went from 0% usage left to 50%

impulsive

@weezerOSINT

Oct 31

vx-underground

@vxunderground

Oct 31

> be me
> have PC
> 64gb of RAM
> need more power for goop
> lookup stuff for good goop machine
> cost easily exceeding $5,000

Yeah, I'm killing myself tonight

impulsive

@weezerOSINT

Oct 30

Chrome Jesus

@manipulate

Oct 29

someone lock $100 with me that the binance hack is social engineering at its finest.

i know everyone is banking on some kind of exploit or zero day but i'm going to lock money that it's an insider who helped.

impulsive

@weezerOSINT

Oct 30

Binance

@binance

Oct 30

Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private a detailed technical post-mortem once the investigation is complete and the facts are fully verified.

The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.

As an immediate precaution, Binance has:

- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.

Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.

Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.

binance.com/en/support/ann…

impulsive

@weezerOSINT

Oct 29

Tibo

@thsottiaux

Oct 29

Day 25/

We are doubling all usage limits for all Pro 100/200/500 tiers and Business Premium, effective today.

We heard your kind feedback and won’t be reducing usage limits for Pro 200, so your Work and Codex usage will stay the same. We’re also going to continue offering extended limits for dots for now, and usage of your dot will still continue to be separate from your default usage.

And we'll of course also keep shipping better models and other efficiency improvements that increase your effective usage over time.

impulsive

@weezerOSINT

Oct 25

s1r1us

@S1r1u5_

Oct 25

the stealmybitcoin[.]com (php2shell) challenge is shit, and everyone already predisposed to dismissing ai's cyber capabilities is jumping on the bandwagon to call the bug unexploitable and overhyped.

like bro, did you even try to solve it?

i think the challenge can be solved in er made stealmybitcoin just slopped it up like crazy, wasting an insane amount of people's time and tokens because of their sloppiness.

just from a blackbox perspective, for the first ~10 hours, they seemed to be serving something like index.html through a wildly uncommon setup:

nginx -> proxy_pass -> php -S -> index.html

if you look at the PHP CLI server code, without a router, it doesn't even initialize php for static files, so you can't trigger the vulnerable multipart parser in the first place.

after @LiveOverflow called this out, they updated the server to expose an actual PHP endpoint:

stealmybitcoin.com/php-version.php

this is still a crazy setup, running php's single-threaded development server behind nginx, but apparently the exploit works reliably now.

except everyone who wanted to prove php2shell was fake made the challenge go viral, and the server basically got dosed by everyone else who want to solve. now you can barely even make a request to it.

impulsive

@weezerOSINT

Oct 24

Keystone Hardware Wallet

@KeystoneWallet

Oct 24

We owe you an apology.

On October 20, we detected unauthorized access to our official website. After verifying API activity with Shopify, we confirmed on October 23 that a third party obtained customer shipping information. You trusted us with those details, and we're sorry we didn't keep them safe.

Exposed: names, contact details, shipping addresses, and order details (items and prices).
Not exposed: payment card or bank details, recovery phrases, private keys, or wallet passwords.

We've blocked access, fixed the vulnerability, opened an investigation, and are emailing affected customers.

Scammers may pose as Keystone by phone, text, email, or mail, offering refunds, replacement devices, or "fixes" for your order or address. None of it is from us.

NEVER share your recovery phrase or private keys, and NEVER enter your recovery phrase into a device you didn't order. We will never ask for them. Don't click links in unexpected messages. Type keyst.one yourself.

A detailed report is coming soon.

Until then, trust only our official channels. If anything feels off, email support@keyst.one. We'd rather hear from you than have you take a chance.

Again, we're truly sorry to everyone affected.

impulsive

@weezerOSINT

Oct 24

solst/ICE of Astarte

@IceSolst

Oct 24

I predict CVP will become a paid tier. They’ll make cyber rejections even more common until you are forced to pay for cyber access + KYC (upload your ID).

Lmk what’s your best way around this bs.

impulsive

@weezerOSINT

Oct 24

Max Blade

@_MaxBlade

Oct 23

i spent $400 on kimi k3.1 pro subs today

to send 4 prompts

the worst part is if i just paid via api it would have been $29 total. The 5 hour limit is completely broken.

wow..

Lets talk about the output quality though, here is kimi vs opus. which do you prefer?

impulsive

@weezerOSINT

Oct 23

Calif

@calif_io

Oct 23

CC @pwnlambda

Tibo

@thsottiaux

Oct 21

OpenAI Developers

@OpenAIDevs

Oct 20

You can now choose 12-hour prompt caching in the API.

Persistent agents, like dots, reuse context throughout the day.

You can keep shared instructions, tools, and context cached longer and pay the lower cached-input rate, even when requests are hours apart.

impulsive

@weezerOSINT

Oct 18

Theo - t3.gg

@theo

Oct 18

I think about this one every once in awhile. Honestly it’s one of the more artful takes on the delusional hater archetype. His ability to lie about every single thing he knows is honestly impressive!