argoncrypt
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-h3m2-g8jh-9p37
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in argoncrypt (npm)
---
_-= 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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0