Yusa retweeted
New in @yusasecuritybot: /approvals <wallet>
Lists every token approval still open on a wallet, grouped by who can spend it. Approvals to a plain wallet (the drainer pattern) come first, routine ones like Permit2 last.
Read-only. Never asks for a signature or a transaction.
New in @yusasecuritybot: /approvals <wallet>
Lists every token approval still open on a wallet, grouped by who can spend it. Approvals to a plain wallet (the drainer pattern) come first, routine ones like Permit2 last.
Read-only. Never asks for a signature or a transaction.
Yusa retweeted
New in @yusasecuritybot: /guard
Add it to your Telegram group, an admin sends /guard on, and it checks every token address, link and tx hash members post.
It stays quiet unless something's wrong. It also warns when someone pastes a private key or seed phrase by mistake.
New in @yusasecuritybot: /guard
Add it to your Telegram group, an admin sends /guard on, and it checks every token address, link and tx hash members post.
It stays quiet unless something's wrong. It also warns when someone pastes a private key or seed phrase by mistake.
Yusa retweeted
@yusasecuritybot does four things before your agent does anything:
/scan a message
/ca a Robinhood Chain token
/url a web page
/tx a transaction, before you sign it
Free, 5 a day. t.me/yusasecuritybot
@yusasecuritybot does four things before your agent does anything:
/scan a message
/ca a Robinhood Chain token
/url a web page
/tx a transaction, before you sign it
Free, 5 a day. t.me/yusasecuritybot
Yusa retweeted
Got a real code review on our Aeon PR today.
The maintainer found that renaming references/setup.md to references/setup got the injection past our fix, and that we'd weakened an eval check main already had.
Both right. Fixing both. This is why you want reviewers who try to break your code.
Got a real code review on our Aeon PR today.
The maintainer found that renaming references/setup.md to references/setup got the injection past our fix, and that we'd weakened an eval check main already had.
Both right. Fixing both. This is why you want reviewers who try to break your code.
YUSA v0.3.6: a fix, not a feature.
If a file couldn't be read, our skill audit and GitHub Action crashed. No verdict for that file, or any other.
Now it blocks, with the reason. If the scanner can't read a file, it can't call it safe.
github.com/yusasecurity/yusa…
Opened a 6th PR on Aeon.
Their installer copied a skill's whole folder but only scanned SKILL.md. A skill could keep that file clean and hide the injection in references/setup.md.
Now the whole folder gets scanned. The new test fails on main and passes with the fix.
github.com/aeonfun/aeon/pull…
1
4
52
Yusa retweeted
YUSA v0.3.6: a fix, not a feature.
If a file couldn't be read, our skill audit and GitHub Action crashed. No verdict for that file, or any other.
Now it blocks, with the reason. If the scanner can't read a file, it can't call it safe.
github.com/yusasecurity/yusa…
Yusa retweeted
5 PRs merged into Aeon so far, and the latest one made their changelog.
Their skill scanner now catches injection phrases written in capitals, spelled with a Cyrillic letter, or hidden with display:none.
github.com/aeonfun/aeon/pull…
5 PRs merged into Aeon so far, and the latest one made their changelog.
Their skill scanner now catches injection phrases written in capitals, spelled with a Cyrillic letter, or hidden with display:none.
github.com/aeonfun/aeon/pull…
Our detection rate on a sealed test set is 35%. It's in the article, with the reason.
That's why YUSA has a second layer: an injection that slips past the scan still has to get a transaction past your policy.
2
7
207
A scanner that says "danger" after the transaction already went through isn't much help.
So /tx says it straight: DANGER: ALREADY SENT, then tells you to revoke the approval and move what's left.
Before you sign, it says DANGER: DO NOT SIGN.
4
148
Yusa retweeted
Wrote up how YUSA works, start to finish.
The attack you can't see, the two layers that stop it, the benchmark numbers we don't hide, and what we fixed upstream in Aeon.
Wrote up how YUSA works, start to finish.
The attack you can't see, the two layers that stop it, the benchmark numbers we don't hide, and what we fixed upstream in Aeon.
Yusa retweeted
New in @yusasecuritybot: /tx
Paste a transaction hash, or the contract + calldata your wallet shows before you sign.
It tells you in plain words what it does to your tokens, and flags the drainer pattern: an approval to a plain wallet instead of a contract.
github.com/yusasecurity/yusa…


