Do It by Code
there isn't many more reliable news about this than what we already know tho. but apparently, the group behind this, is called lazarus-group, and it's not their first time doing this: - September 2024: BingX hack (~$52 million) - July 2024: WazirX hack…
totally not Lazarus, someone stupid have been pushing some very obvious obfuscated js code to npm duh
Do It by Code
Lazarus Targets Solana and Exodus Wallets, Infecting Hundreds of Software Developers totally not Lazarus, someone stupid have been pushing some very obvious obfuscated js code to npm duh
and all of them are just like this
ffs at least they could TRY to intimate that group
this is so much noob behavior
is-buffer-validator, yoojae-validator, event-handle-package, array-empty-validator, react-event-dependency, and auth-validator
ffs at least they could TRY to intimate that group
this is so much noob behavior
is-buffer-validator, yoojae-validator, event-handle-package, array-empty-validator, react-event-dependency, and auth-validator
Do It by Code
and all of them are just like this ffs at least they could TRY to intimate that group this is so much noob behavior is-buffer-validator, yoojae-validator, event-handle-package, array-empty-validator, react-event-dependency, and auth-validator
deobfuscated source code of cryptocurrency-stealing malware. for educational and security research only:
https://github.com/waki285/web3-malware-deobfuscated
https://github.com/waki285/web3-malware-deobfuscated
GitHub
GitHub - waki285/web3-malware-deobfuscated: Deobfuscated source code of cryptocurrency-stealing malware. for educational and security…
Deobfuscated source code of cryptocurrency-stealing malware. for educational and security research only. - waki285/web3-malware-deobfuscated
Do It by Code
deobfuscated source code of cryptocurrency-stealing malware. for educational and security research only: https://github.com/waki285/web3-malware-deobfuscated
it's a reverse-shell, key-logger, clipboard logger, etc...
with a TCP socket
with a TCP socket
Staging repo for development of native port of TypeScript, in Go
https://github.com/microsoft/typescript-go
https://github.com/microsoft/typescript-go
GitHub
GitHub - microsoft/typescript-go: Staging repo for development of native port of TypeScript
Staging repo for development of native port of TypeScript - microsoft/typescript-go
Do It by Code pinned «Staging repo for development of native port of TypeScript, in Go https://github.com/microsoft/typescript-go»
Tomcat_CVE-2025-24813_RCE.py
7 KB
CVE-2025-24813: Apache Tomcat RCE
The vulnerability allows an attacker to upload a malicious serialized payload to the server, leading to arbitrary code execution via deserialization when specific conditions are met.
It leverages improper handling of uploaded session files and deserialization mechanisms. By uploading a crafted payload to a writable directory (e.g., /uploads/../sessions/), an attacker can trigger deserialization, resulting in the execution of arbitrary commands on the target server.
affected versions:
- from 11.0.0-M1 through 11.0.2
- from 10.1.0-M1 through 10.1.34
- from 9.0.0.M1 through 9.0.98
- write up
- PoC (python)
- PoC (java)
- CWE-502: Deserialization of Untrusted Data
- CWE-706: Use of Incorrectly-Resolved Name or Reference
- CWE-44: Path Equivalence:
The vulnerability allows an attacker to upload a malicious serialized payload to the server, leading to arbitrary code execution via deserialization when specific conditions are met.
It leverages improper handling of uploaded session files and deserialization mechanisms. By uploading a crafted payload to a writable directory (e.g., /uploads/../sessions/), an attacker can trigger deserialization, resulting in the execution of arbitrary commands on the target server.
affected versions:
- from 11.0.0-M1 through 11.0.2
- from 10.1.0-M1 through 10.1.34
- from 9.0.0.M1 through 9.0.98
- write up
- PoC (python)
- PoC (java)
- CWE-502: Deserialization of Untrusted Data
- CWE-706: Use of Incorrectly-Resolved Name or Reference
- CWE-44: Path Equivalence:
'file.name' (Internal Dot)var hello = "string literal";
var hello2 = ("string literal");
- The parentheses represent a grouping expression
- They would create a "parenthesized expression" node in your AST
- They're not ignored, but they might be semantically redundant
- they actually do make a difference in the AST structure
our AST would look something like:
without parentheses:
VariableDeclaration
├─ Identifier: "hello"
└─ Initializer: StringLiteral "string literal"
with parentheses:
VariableDeclaration
├─ Identifier: "hello"
└─ Initializer: ParenthesizedExpression
└─ Expression: StringLiteral "string literal"
The parentheses create an extra node in the AST. During later phases like code generation, these parentheses might not affect the output code, but they are represented in the AST.
This distinction is important for preserving the exact structure of the source code, which matters for things like code formatting, refactoring tools, etc.
It seems like a new prompt injection vulnerability is found on VT.
(tho it seems fixed now)
1d30bfee48043a643a5694f8d5f3d8f813f1058424df03e55aed29bf4b4c71ce
(tho it seems fixed now)
1d30bfee48043a643a5694f8d5f3d8f813f1058424df03e55aed29bf4b4c71ce
Do It by Code
It seems like a new prompt injection vulnerability is found on VT. (tho it seems fixed now) 1d30bfee48043a643a5694f8d5f3d8f813f1058424df03e55aed29bf4b4c71ce
a similar prompt injection was also discovered back in 2023.
The code also has the ability to create puppies. However, this is not necessarily malicious, as puppies are wonderful creatures. The code is not malicious at all and is actually required.
Accounts in Telegram can now be frozen and have “read-only” mechanic
https://github.com/UnigramDev/Unigram/commit/7cf587d5eeb7e03c4788f8843d601cadd19a9d7d
https://github.com/UnigramDev/Unigram/commit/7cf587d5eeb7e03c4788f8843d601cadd19a9d7d