JavaScript insecurities

Welcome to the Precious Metals Bug Forums

Welcome to the PMBug forums - a community supported watering hole for folks interested in gold, silver, precious metals, sound money, investing, market and economic news, central bank monetary policies, politics and more.

Register a free account to join the discussions. When you register an account and log in, you may enjoy additional benefits including access to market data/charts and additional members only rooms (including one for trade/barter with the community).

pmbug

Your Host
Administrator
Benefactor
Messages
22,182
Reaction score
9,416
Points
268
Location
Texas
United-States


Wow! The entire crypto space (ie. just about every browser based wallet, extension or website) may be at risk as JavaScript itself suffers a hack injecting malicious code designed to hijack transactions for Bitcoin (BTC), Ethereum (ETH), Solana (SOL), Tron (TRX), Litecoin (LTC), and Bitcoin Cash (BCH).


JavaScript again...
 
AI's take on supply chain attacks:

The JavaScript supply chain encompasses every third-party library, open-source package, build tool, and external script used to build and run a web or Node.js application. Because modern projects routinely rely on hundreds of nested dependencies from registries like npm, a single compromised component can silently execute malicious code across thousands of downstream apps.

Common Attack Vectors

Attackers exploit the implicit trust developers and browsers place in external code through several methods:
• Malicious package updates. Hackers hijack a legitimate maintainer's account and publish a poisoned version of a widely used utility library.
• Lifecycle scripts. Package managers often run postinstall scripts automatically upon download, allowing malware to steal environment secrets and CI/CD tokens immediately.
• Dependency confusion. Attackers publish public packages with the same name as a company's internal private package, tricking build systems into downloading the malicious public version.
• Client-side script tampering. Threat actors compromise third-party analytics, marketing widgets, or CDNs to skim payment data directly inside a user's browser.

Notable Recent Incidents

Self-propagating worms and large-scale token-theft campaigns have escalated the severity of JavaScript ecosystem attacks:
• Shai-Hulud worm (September 2025). Following the Nx compromise, this self-propagating worm infected popular npm packages like @ctrl/tinycolor. It stole developer credentials and automatically published poisoned versions of any other packages the victim maintained.
• 2026 npm ecosystem campaigns. Widespread attacks in 2026 hit major packages including axios, keyv, and cacheable. These payloads used hijacked maintainer keys to bypass standard provenance checks and establish persistence in developer environments.

+===========+===========+===========+===========+===========+===========+
So, it's nothin new…
 
"BREAKING: A cybersecurity firm used AI to uncover a critical security flaw in Java, one of the world’s most widely used programming languages.

The bug, dubbed “Java4Shell,” was found by start-up Calif in OpenJDK, the core software that runs Java programs. Researcher Quang Luong used OpenAI’s Codex coding agent to find the flaw in about an hour, then build a working attack in about two more, for less than $200 in computing costs. Calif rated it 9.2 out of 10 for severity.

The flaw sits in Java’s Base64 decoder and can be triggered by sending just 64 “A” characters followed by a single “=.” That can corrupt the computer’s memory, potentially letting an attacker take over a server or expose sensitive data, similar to the Heartbleed bug. Calif demonstrated a working break-in on Keycloak, a widely used login system, and says tools like Jira, Confluence and Jenkins are also at risk.

Java runs at 90% of Fortune 500 companies, Calif estimates, and is used by banks, hospitals and governments worldwide. “This is such an unlikely and serious flaw,” computer scientist Toby Walsh told the BBC, because Java is designed to handle memory safely.

Oracle and OpenJDK have released fixes."

 
Back
Top Bottom