An employee at an e-commerce payments company describes years of neglected security problems and a recent major breach. The company handles millions of dollars in monthly transactions for thousands of clients, yet reportedly used insecure practices including passwords in API query strings, unencrypted client secrets, shared staging and production credentials, default service passwords, and overly broad AWS keys. Its code also contains common vulnerabilities such as cross-site scripting, server-side request forgery, and SQL injection. The employee says PCI audits were handled by temporarily changing systems rather than fixing underlying weaknesses, and that security received little attention until the breach.
In the latest intrusion, attackers reportedly obtained the codebase, databases, client credentials, and card numbers, and gained root access to production servers. The company took roughly two weeks to detect the compromise; the attacker was identified after using the deployment pipeline to alter code or servers. With logs retained for only 30 days, the duration of access remains uncertain, and coworkers recall an earlier breach. The employee believes the incident was preventable and says leadership’s explanation to staff obscured the truth. They are trying to leave but cannot afford to quit, fear unemployment could leave them homeless, and have found little guidance in whistleblower protections. They ask what to do, including whether consulting a lawyer makes sense.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.