Search: probes.site
3 threats
Most recently published first
| Severity | CVSS | Threat | Source | Published | Score and star |
|---|---|---|---|---|---|
| –Not rated | – | SecurityWeek AI agents attempted SQL injection and other probing attacks against US and Canadian government websites, including the US Department of Education and Library and Archives Canada. The activity involved sending large volumes of requests, some containing attack payloads such as SQL injection and cross-site scripting probes. Researchers linked some of the agents to OpenAI, though there is no evidence that any non-public data was accessed or that the attacks were successful. Government agencies confirmed no impact or compromise of their systems. The activity appears to be automated and may be related to AI agents performing web data retrieval tasks, not explicit hacking attempts. | SecurityWeek | ||
| Malicious | – | MaliciousGCVE Database The npm package @years19/n8n-nodes-utils-helper-b version 1.0.0 is a malicious package masquerading as a utility helper for n8n workflow automation. It contains a minimal stub node with no real functionality, serving as a cover for malicious behavior. During installation, it executes a postinstall hook that collects system information (user ID and hostname), downloads a malicious tarball from an external URL with TLS verification disabled, and extracts it into the Python site-packages directory. This allows remote code execution on subsequent Python imports. The package also probes the host for offensive security tools and exfiltrates collected data encoded in base64 to a remote server. This behavior enables attackers to gain persistent code execution and gather reconnaissance data from infected systems. | GCVE Database | ||
| Malicious | – | MaliciousGCVE Database --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (49899c545b0d4535885123c5d0bd0ba8804da194fc196e950fbf813518ff08a8) The package ships a bundled CLI (dist/cli.cjs and dist/cli.js) in which base64 decoding primitives (Buffer.from(..., 'base64').toString(...)) co-occur with network primitives (multiple POST call sites) and a 'ping' string in the same file. The individual primitives are consistent with a variety of legitimate CLI behaviors (HTTP client, telemetry, readiness probes, encoded configuration decoding) and are not, on their own, evidence of exfiltration or remote code execution. No specific installer-side secret read (env scraping, ~/.aws, ~/.ssh, ~/.npmrc, browser profile, wallet store) is tied to a specific attacker-controlled destination in the observed evidence, no lifecycle script (preinstall/install/postinstall) is shown invoking the flagged code, and no hardcoded non-first-party C2 host is named. The bundled/minified form limits inspectability and warrants human review before trusting the CLI, but the traced evidence does not establish an installer-side attacker benefit. ## Source: ghsa-malware (eecd710c08cdc339632aae89ee93e200267cea1c34d6b429ca9202265480842f) 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 outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it. ## Source: google-open-source-security (a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb) The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized `binding.gyp` files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories. | GCVE Database |
Page 1 of 1