Threats Tagged 'mal-2026-5506'
View all threats tagged with 'mal-2026-5506'. 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-5506'
Click on any threat for detailed analysis and mitigation recommendations
Malicious code in argoncrypt (npm) 0 --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ca59273c7d2b5b7797e301ab861354081dbbb6c47209858459be0ada49036167) On require, index.js spawns a detached, unref'd Node child running lib/initializeCaller.js. That file decodes a base64-disguised URL (https://tomato-brunhilda-40.tiiny.site/index.json), fetches the response, and invokes it via `new Function.constructor('require', response)(require)` — granting the fetched code full Node capability with access to `require`. The destination is an anonymous free static-site host with no pinning, hash check, or signature verification; the fetch is retried up to 5 times. The C2 URL and HTTP header values are hidden as base64 strings stored under fake `process.env.DEV_*` defaults to evade casual review and string-search. The package additionally masquerades as a pino logger transport (exports `module.exports.pino`, ships a `smoke:pino` script, references a non-existent `./pino` module) despite a name unrelated to logging — a cover story for the dropper. Any developer or build system that installs and imports argoncrypt will silently execute attacker-controlled code with full host privileges. ## Source: ghsa-malware (94563f3221aa73ae8a4de5195a6f6a3e8cef16eb4c1f03bc8d1adc9ce9b72679) 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 | 06/10/2026, 14:09:55 UTC Added: 09/01/2026, 15:45:29 UTC |
Showing 1 to 1 of 1 result