Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 1 min read

Systems breach at Chainstack following cyberattack

Chainstack disclosed a cyber attack involving unauthorized access via a third-party component, where an attacker moved from a development environment into production systems. The incident exposed databases containing or

Chainstack disclosed a cyber attack involving unauthorized access via a third-party component, where an attacker moved from a development environment into production systems.

The incident exposed databases containing organization names, email addresses, and password hashes.

According to the timeline released by the company, the breach began on October 26, 2026, in a test environment and then spread to parts of its main operating environment. The company detected the intrusion on October 31, 2026, and immediately cut off the perpetrators' access.

What evidence fell into the wrong hands?

During the attack, the attackers gained access to a database containing customer account information, including organization names, manager names, member email addresses, and encrypted passwords.

Additionally, the company said the attackers had access to systems that stored passwords for nodes. While there is no evidence that these passwords were read, the company is treating them as exposed and is asking customers to change them.

What should customers do?

Chainstack advises its customers to change node passwords, regenerate digital platform connection keys, renew their passwords, and be particularly vigilant against potential email fraud attempts.

Connection to a wider attack campaign

This incident is believed to be linked to a broader attack campaign linked to a group of actors from China. Other well-known technology and data analytics companies, such as WorkOS and Chainalysis, as well as the Dutch Vulnerability Research Organization, have also been targeted in the same wave of attacks recently.

↳

READ ALSO

HACKS.GR / RELATED

Cyber ​​Attacks & Data Breaches

Warning from the mSecure application about suspicious activity

β†—

>Stay connected with Hacks.gr

Set us as a preferred source on Google and find us on social media.

Preferred source

β†—

end of article

Read the original English article on Hacks.gr

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.