Malicious Package

Overview @brick-v2/core is a malicious package. This package contains malicious code, and its content was removed from the official package manager. While this package might be attempting to impersonate a valid organization, there is no connection between that organization and this package...

Malicious code in @brick-v2/core (npm)

Source: amazon-inspector 90c1fd9505ce4256620f9cb647e3a57a5af52539aa1e717a3eecb0485dec8c83 The package's main entry index.js loads a prebuilt native binary at prebuilds/-/metrics.node inside a top-level try/catch, executing native code within the Node process as soon as the module is required. The...

MAL-2026-17715 Malicious code in @brick-v2/core (npm)

@brick-v2/core is a dependency confusion package published to npm on 2026-10-09 by the account s4yhii, targeting the internal @galicia-toolkit- / @brick-v2 package namespaces with inflated versions e.g. 999.0.x. Early versions resolve ..dc.oob.s4yhii.com via DNS to beacon the victim's hostname...

Malicious code in @brick-v2/core (npm)

@brick-v2/core is a dependency confusion package published to npm on 2026-10-09 by the account s4yhii, targeting the internal @galicia-toolkit- / @brick-v2 package namespaces with inflated versions e.g. 999.0.x. Early versions resolve ..dc.oob.s4yhii.com via DNS to beacon the victim's hostname...

Excessive Iteration

Overview Affected versions of this package are vulnerable to Excessive Iteration in the PullImage process. An attacker can cause excessive CPU and memory consumption by supplying a crafted OCI image index with deeply nested or heavily fanned-out descriptor graphs, leading to prolonged stalls and...

Malware in twitch.dashboard-v2.core

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outsid...

MAL-2024-1600 Malicious code in v2-core (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 51e0286004b6b184a7ae2c0a7110095cd51122ae1c9ccc69db8d1bfd7380dfed Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

Malware in v2-core

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outsid...

Malicious code in v2-core (npm)

--- -= Per source details. Do not edit below this line.=- Source: ghsa-malware 51e0286004b6b184a7ae2c0a7110095cd51122ae1c9ccc69db8d1bfd7380dfed Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be...

Two pairs can have same tokens

Handle sirhashalot Vulnerability details Impact The createLPoolPair function in ControllerV1.sol tries to prevent a pair from being create if it already exists. It does this with the statement requirelpoolPairstoken0token1.lpool0 == address0 || lpoolPairstoken1token0.lpool0 == address0, 'pool pai...

Hardcoded seed phrase in sherlock-v2-core repo

Handle cryptphi Vulnerability details Impact The hardcoded mnemonic can lead to account compromise. Proof of Concept There exists hardcoded credentials in line This credentials can be used to takeover the wallet address used. Tools Used Github Recommended Mitigation Steps Avoid hardcoding...