IMMA

426 posts

IMMA banner
IMMA

IMMA

@IMMANUX2160

Tech lover Passionate about Machine Learning and Artificial Intelligence. Currently learning and exploring the exciting world of ML/AI through Python libraries.

Katılım Nisan 2022
575 Takip Edilen81 Takipçiler
IMMA
IMMA@IMMANUX2160·
@idriz_agunlofi @olumuyiwaayo Hey sir, can I slide into your dm to ask about the enquiries on how you got the admission, I’d really appreciate
English
1
0
0
31
AGUNLOFI IDRIS A.
AGUNLOFI IDRIS A.@idriz_agunlofi·
@olumuyiwaayo Hello Doc What would you advise to do about the USA school admission? I got an offer from Ohio university but not funded yet and was told to wait till a student declines
English
3
0
0
451
IMMA
IMMA@IMMANUX2160·
@JIgwede @genius_excell @nonnydam @heisdania @victorosimhen9 Hey man, you could just point out to an argument you don’t seem to agree, I’ve actually had great conversations with the authors of the tweets I replied, no one is forming “I too know”, it’s a constructive argument and it’s subjective
English
0
0
1
47
Daniel
Daniel@heisdania·
hi dad 😭 @victorosimhen9 they say a closed mouth is a closed destiny i lost my father at a very young age, still yet to go to the university please can you adopt me dad so i can get to the uni, i registered for JAMB this year from the money i saved🙏😭
Daniel tweet media
English
212
1K
6.7K
395.1K
IMMA
IMMA@IMMANUX2160·
@genius_excell @abijayofficial @nonnydam @heisdania @victorosimhen9 Yes, that’s true, that’s even what I’m trying to lean my argument upon the theory and practical gap, mathematics won’t be very much applied here because it’s basically abstract, it was a fun conversation tho my boss🙌🏽
English
0
0
2
41
Genius Excel
Genius Excel@genius_excell·
@IMMANUX2160 @abijayofficial @nonnydam @heisdania @victorosimhen9 Okay. The argument is not even based on local vs intl. standards. I used that to point out why almost every NG CS student end up as self taught. To answer your question, Mathematics has no standard way of being taught. The bone of contention is theory against practical in NG uni.
English
1
0
0
37
IMMA
IMMA@IMMANUX2160·
@nonnydam @genius_excell @abijayofficial @heisdania @victorosimhen9 I beg to differ, well thank God you put close, ‘cause my friends wey Dey study am no suppose Dey complain about the standard, I remember one telling me how they had to on phone torch light when they were learning some surgical procedures on a live human
English
0
0
0
39
IMMA
IMMA@IMMANUX2160·
@genius_excell @abijayofficial @nonnydam @heisdania @victorosimhen9 Thank you for pointing it out, I’ve checked out CS50 before, it’s not the same way we were being taught, now lemme now ask which courses are being taught same with an international standard here in Nigeria?, please just mention one, I promise you, you won’t find any.
English
2
0
0
90
IMMA
IMMA@IMMANUX2160·
@abijayofficial @genius_excell @nonnydam @heisdania @victorosimhen9 Exactly my point my bro, currently I’m in my final years studying computer science, what I’m doing to make money is totally different which is cybersecurity, and it’s very easy for me to cross that gap, just because of some prerequisite, even the top best in tech are self taught
English
1
0
1
209
Genius Excel
Genius Excel@genius_excell·
@IMMANUX2160 @nonnydam @heisdania @victorosimhen9 Lol 😂 dem dey tell you reality you dey distinguish between SWE and CS major. Bro said it’s theoretical and would rather study something else as he can learn what you want to go and study in 6 months. What you fail to understand is being employable after completion.
English
5
0
7
563
5STAR💈
5STAR💈@5starbarber_1·
20 courses you’ll regret studying in Nigeria if you don’t have a clear plan; 1. Political science 2. Sociology 3. Economics 4. Chemistry 5. Physics 6. Philosophy 7. All educational courses 8. Animal science 9. Crop science 10. Soil science 11. Sport science 12. Mass communication 13. History & international relations 14. Nigerian languages( Yoruba, Hausa, Igbo) 15. Estate management 16. Economics again 17. Fishery 18. Agricultural science 19. Computer science 20. Microbiology
English
441
64
1K
127.1K
IMMA
IMMA@IMMANUX2160·
@Dv_sol1 @lonelysloth_sec @bangjelkoski @injective you could as well read this and next time try not to be biased when it comes to rational thinking, x.com/al_f4lc0n/stat…
f4lc0n@al_f4lc0n

the figures referenced in the post are entirely misleading. There was no impact realized from this issue. Zero user funds were affected and zero addresses were compromised. My response: Are you suggesting I should have actually exploited the bug and caused real damage before coming to talk to you? For the stated vulnerability to work in practice, it would require execution of several suspicious transactions that would have an extraordinarily limited impact. My response: You should know better than anyone that on a Cosmos-based chain, a single transaction can pack multiple messages. Just one transaction is more than enough to completely drain multiple whale accounts. Injective has dynamic rate limiting functionalities which are applied automatically based on our live monitoring systems. This functionality has been live on mainnet since last year and is publicly available in our code base. My response: First, this has nothing to do with the vulnerability itself. Rate limiting doesn't stop attackers from stealing funds. It only slows them down when they try to bridge those funds over to Ethereum. Second, when I submitted my report, the mainnet configuration for this feature was not set. In other words, this feature wasn't even turned on! In addition to all of the above, this report was reviewed against the clearly defined terms of our Immunefi program. Based on those terms, issues such as those raised in this report that DO NOT impact block production or consensus are categorized outside of the Blockchain/DLT tier and carry a maximum payout of $50,000. My response: First, Immunefi has always put the impact of direct fund theft at the very top of its priority list. This is a fact that everyone knows. Second, you changed your bug bounty page after I submitted my report. Here’s the snapshot from November 8, 2025: web.archive.org/web/2025110816… . And now, there’s an extra line added to your bug bounty page: “IMPORTANT: Within the Assets in Scope table, the injective-core folder is listed for both Blockchain/DLT and Web/App due to overlap between the two within the same folder. However, for a report to be categorized as Blockchain/DLT, the resulting impact has to be directly involved with the block production process or with consensus failures. All reports not dealing directly with either of these are to be categorized as Web/App.” I’d really like to know when this line was added. and do you really value chain consensus more than users' funds? We remain committed to fair, transparent, and consistent handling of all reports, and to maintaining the highest standards of security for the ecosystem. Injective has done so since its mainnet inception in 2021 and will continue to do so in perpetuity, always putting builders and security first. My response: You never even replied to my messages, and now you’re blaming me for not requesting mediation? I can post the original report if you agree. I left many messages, but you haven't replied to a single one. ---------- Finally: Stop making excuses from every angle and trying to use technical jargon to confuse people who aren't developers. That doesn’t work anymore these days. Anyone can just ask an AI to fact-check what both of us are saying. I have no ill intentions toward your project. All I'm asking is for you to be honest and handle this transparently.

English
0
0
2
355
Bojan Angjelkoski
Bojan Angjelkoski@bangjelkoski·
Security is paramount at @injective and we take our bug bounty program very seriously. First and foremost, the figures referenced in the post are entirely misleading. There was no impact realized from this issue. Zero user funds were affected and zero addresses were compromised. For the stated vulnerability to work in practice, it would require execution of several suspicious transactions that would have an extraordinarily limited impact. Injective has dynamic rate limiting functionalities which are applied automatically based on our live monitoring systems. This functionality has been live on mainnet since last year and is publicly available in our code base. In addition to all of the above, this report was reviewed against the clearly defined terms of our Immunefi program. Based on those terms, issues such as those raised in this report that DO NOT impact block production or consensus are categorized outside of the Blockchain/DLT tier and carry a maximum payout of $50,000. If the poster had requested a mediation we would explain to him the dynamic rate limiters and monitoring systems we have in place and why his stated figures are misleading. However, he did not do so. We always follow the procedures set forth by the Immunefi program and expect the submitter to do so as well. We remain committed to fair, transparent, and consistent handling of all reports, and to maintaining the highest standards of security for the ecosystem. Injective has done so since its mainnet inception in 2021 and will continue to do so in perpetuity, always putting builders and security first.
f4lc0n@al_f4lc0n

I Saved Injective's $500M. They Pay Me $50K. I like hunting bugs on @immunefi . I'm decent at it. - #1 — Attackathon | Stacks - #2 — Attackathon | Stacks II - #1 — Attackathon | XRPL Lending Protocol - 1 Critical and 1 High from bug bounties (not counting this one) Life was good. Then I found a Critical vulnerability in @injective . This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk. I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity. Then — silence. For 3 months. No follow up. No technical discussion. Nothing. A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either. I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten. I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve. Full Technical Report: github.com/injective-wall…

English
74
37
188
182.4K
IMMA
IMMA@IMMANUX2160·
@Anh084879445581 @LZ_security Hey man, seems you have an ideal knowledge detecting web2 vulnerabilities, do you mostly apply this mentality/methodology to web3 vulnerabilities?
English
0
0
0
15
anh_iu
anh_iu@Anh084879445581·
@LZ_security It's a common bug pattern in web2: processing a signed request/message without proper verifcation. Improper saml, jwt verification issues are somewhat similar to this also.
English
1
0
1
97
LZ_security
LZ_security@LZ_security·
For hunters looking for bugs in blockchain infra (DLT), this is a great case study. Not complex, but very effective.
f4lc0n@al_f4lc0n

I Saved Injective's $500M. They Pay Me $50K. I like hunting bugs on @immunefi . I'm decent at it. - #1 — Attackathon | Stacks - #2 — Attackathon | Stacks II - #1 — Attackathon | XRPL Lending Protocol - 1 Critical and 1 High from bug bounties (not counting this one) Life was good. Then I found a Critical vulnerability in @injective . This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk. I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity. Then — silence. For 3 months. No follow up. No technical discussion. Nothing. A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either. I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten. I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve. Full Technical Report: github.com/injective-wall…

English
1
0
19
2K
daktus05
daktus05@bieg_david·
@IMMANUX2160 @IsaiahOdekina @smartnakamoura there's a reason its computer SCIENTIST and so many people dont understand it... Even people who choose to study it. Experience it daily from CS students at my uni complaining about "we dont even code that much" on the uni subreddit...
English
1
0
0
29
Smart👨‍💻 | Software Engineer
Nigerian uni is giving us C programming in 2026. Not React. Not cloud. Not even basic web dev. C for that matter omoo who are we building for 😭
English
247
23
412
241.8K