Threats Tagged 'mal-2026-15671'
View all threats tagged with 'mal-2026-15671'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'mal-2026-15671'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in quartz-core (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8f59477bf2399742c785aa97d80d04b4800f66446ae3635167ba173d96080a91) On npm install, the package's preinstall hook (package.json scripts.preinstall = `node index.js`) executes index.js, which reads the installer's OS username (os.userInfo().username), hostname (os.hostname()), and current working directory (process.cwd()), then issues a DNS A-record query for a subdomain of the attacker-controlled domain oob.algamil7x.xyz of the form `selftest.<username>.<hostname>.<cwd>.<timestamp>.oob.algamil7x.xyz` via dns.Resolver.resolve4. The tarball ships no other functionality: package.json has an empty description and author, no dependencies, and no runtime code beyond the beacon. The name `quartz-core` at the elevated version 99.1.9 is consistent with a dependency-confusion reconnaissance probe designed to identify internal build environments where a private package name resolves to this public one. ## Source: ghsa-malware (f2f763d82e760eded4c7415a92f07bf478beeee2ac94ee8e8af73292194b7f42) 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. Join the discussion | GCVE Database | 09/01/2026, 01:03:21 UTC Added: 09/02/2026, 15:48:51 UTC |
Showing 1 to 1 of 1 result