Now we’ll try to set up the node using bitcoin. I followed the instructions to download the file. I would like to check the release signature before installing. First done:

someone@somewhere:~/Downloads$ gpg --recv-keys 01EA5486DE18A882D4C2684590C8019E36C2E964
gpg: key 90C8019E36C2E964: public key "Wladimir J. van der Laan (Bitcoin Core binary release signing key) <(email protected)>" imported
gpg: Total number processed: 1
gpg:               imported: 1

That seemed okay. I’d like to confirm that it was signed after this SHA256SUMS.asc This is the file I downloaded before, but I’ll get it.

someone@somewhere:~/Downloads$ gpg --verify SHA256SUMS.asc 
gpg: no signed data
gpg: can't hash datafile: No data

What am I doing wrong?

Despite Oracle denying a breach of its Oracle Cloud federated SSO login servers and the theft of account data for 6 million people, BleepingComputer has confirmed with multiple companies that associated data samples shared by the threat actor are valid.

Last week, a person named ‘rose87168’ claimed to have breached Oracle Cloud servers and began selling the alleged authentication data and encrypted passwords of 6 million users. The threat actor also said that stolen SSO and LDAP passwords could be decrypted using the info in the stolen files and offered to share some of the data with anyone who could help recover them.

The threat actor released multiple text files consisting of a database, LDAP data, and a list of 140,621 domains of companies that were allegedly impacted by the breach. It should be noted that some of the company domains look like tests, and there are multiple domains per company.

In addition to the data, rose87168 shared an Archive.org URL with BleepingComputer for a text file hosted on the “login.us2.oraclecloud.com” server that contained their email address. This file indicates that the threat actor could create files on Oracle’s server, indicating an actual breach.

However, Oracle has denied that it suffered a breach of Oracle Cloud and has refused to respond to any further questions about the incident.

“There has been no breach of Oracle Cloud. The published credentials are not for the Oracle Cloud. No Oracle Cloud customers experienced a breach or lost any data,” the company told BleepingComputer last Friday.

This denial, however, contradicts findings from BleepingComputer, which received additional samples of the leaked data from the threat actor and contacted the associated companies.

Representatives from these companies, all who agreed to confirm the data under the promise of anonymity, confirmed the authenticity of the information. The companies stated that the associated LDAP display names, email addresses, given names, and other identifying information were all correct and belonged to them.

The threat actor also shared emails with BleepingComputer, claiming to be part of an exchange between them and Oracle.

One email shows the threat actor contacting Oracle’s security email (secalert_us@oracle.com) to report that they hacked the servers.

“I’ve dug into your cloud dashboard infrastructure and found a massive vulnerability that has handed me full access to info on 6 million users,” reads the email seen by BleepingComputer.

Another email thread shared with BleepingComputer shows an exchange between the threat actor and someone using a ProtonMail email address who claims to be from Oracle. BleepingComputer has redacted the email address of this other person as we could not verify their identity or the veracity of the email thread.

In this email exchange, the threat actor says someone from Oracle using a @proton.me email address told them that “We received your emails. Let’s use this email for all communications from now on. Let me know when you get this.”

Cybersecurity firm Cloudsek has also found an Archive.org URL showing that the “login.us2.oraclecloud.com” server was running Oracle Fusion Middleware 11g as of February 17, 2025. Oracle has since taken this server offline after news of the alleged breach was reported.

This version of the software was impacted by a vulnerability tracked as CVE-2021-35587 that allowed unauthenticated attackers to compromise Oracle Access Manager. The threat actor claimed that this vulnerability was used in the alleged breach of Oracle’s servers.

BleepingComputer has emailed Oracle numerous times about this information but has not received any response.

XRP Must Move Past $3.40 To Retain Market Interest

Popular market analyst Egrag Crypto has shared an intriguing analysis of the XRP market. In an X post on February 14, the crypto expert states that the third-largest cryptocurrency must achieve a strong close above $2.75 (marked in green) to sustain its current upward trend.

Based on historical data, $2.75 has presented a significant resistance level. If XRP can close and hold above this price zone on its 4-hour trading chart,  it would indicate that buyers are gaining control of the market following a month of major price loss.

Thereafter, the altcoin must attain another price close above $2.94 (marked in yellow)  which would suggest a higher bullish momentum with significant potential for new highs such as $3.22. For the XRP market, each confirmed close above these specified price levels strengthens the present bullish momentum. 

However, Egrag Crypto warns that all price movement below the current bull rally peak of $3.40 will remain merely “noise” in the long run. The analyst warns that XRP must break above this psychological price level to confirm a certain trend shift in the upward direction.

XRP Market Overview 

At press time, XRP trades at $2.73 following an aggregate 6.43% gain in the past 24 hours. The asset’s trading volume is up by 66.61% indicating a high level of interest from market participants. On its 7-day chart, XRP boasts 13.78% gains, reducing its monthly loss to around 8.39%. 

Amidst its recent price retracement, community sentiments in the XRP market remain highly bullish, especially with the advancement of a potential XRP ETF. By acknowledging Grayscale’s ETF application, the SEC is allowed an initial review period of 45 days – potentially extensible to 240 days – to approve or reject the proposed ETF.

With the implementation of the pro-crypto agenda of Donald Trump, investors are highly positive about an approval suggesting a potential influx of institutional capital as seen with the Bitcoin Spot ETFs.