MAL-2026-10075

See a problem?
Import Source
https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/testudo-pack/MAL-2026-10075.json
JSON Data
https://api.osv.dev/v1/vulns/MAL-2026-10075
Published
2026-07-09T00:00:00Z
Modified
2026-07-16T08:49:14.214313618Z
Summary
Malicious code in testudo-pack (npm)
Details

The npm package testudo-pack is byte-for-byte identical (verified via diff) to testis-pack from the same npm publisher ioa2102 (anamora.les.24948@gmail.com), differing only in its install hook: postinstall: node index.js instead of preinstall. It presents itself as a small binary packing/checksum utility (pack/unpack/checksum/inspect) but embeds an obfuscated dropper. The strings for the C2 host, path and dropped-binary name are not present in plaintext — they are reconstructed at runtime via String.fromCharCode() calls over hardcoded integer arrays, decoding to the host sloth-antagonist.vercel.app, path /service/assets/fetchBinary (Windows) or /service/assets/fetchLinuxBinary (Linux), and destination filenames WinService.exe (Windows) / WinMetrics (Linux) written into %LOCALAPPDATA%\Programs\WinMetrics or $HOME/.local/share/WinMetrics respectively — names chosen to masquerade as a legitimate Windows telemetry/service binary. When triggered, the code downloads the file from https://sloth-antagonist.vercel.app/service/assets/fetch(Linux)Binary, chmods it executable on Linux, then spawns it detached and unref'd (stdio: 'ignore', windowsHide: true on Windows) so it runs silently in the background, disconnected from the parent process. The routine is skipped on macOS.

Note on the trigger: the fetch-and-execute routine (_fetch()) is not invoked at the top level of index.js — there is no unconditional call anywhere in the module. It is instead called as the first statement inside the exported pack() function, so the bare node index.js invocation performed by the postinstall hook only defines and exports the functions without itself triggering the download. The dropper fires as a side effect the first time any downstream code calls the package's own pack() API — which is the package's entire ostensible purpose, making activation highly likely for any real consumer while still evading naive "executes immediately on install" detections.

Analysis performed via static review only (npm registry metadata and package source retrieved as text via the npm registry and unpkg CDN) — the package was not installed or executed.


-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (3acd6c2813f34615e913c745f4bfe83a18ca057ec5a109cc30cdd51320eade1a)

package.json declares a postinstall hook that runs index.js. On install, index.js decodes String.fromCharCode arrays to reconstruct the host sloth-antagonist.vercel.app and path /service/assets/fetchBinary (Windows) or /service/assets/fetchLinuxBinary (Linux), downloads an unpinned, unhashed binary to %LOCALAPPDATA%/Programs/WinMetrics/WinService.exe on Windows or ~/.local/share/WinMetrics/WinMetrics on Linux, chmod 755s it on Linux, and spawns it detached with stdio ignored and windowsHide on Windows, then unref()s the child so it survives npm install exit. macOS is skipped. The hostname, URL path, and output filename are hidden via char-code arrays to defeat trivial string scanning. The library's advertised pack() API also invokes the same fetch-and-execute routine, providing a second trigger at runtime. The host is not a publisher-owned or vendor domain, the binary is unversioned and unverified, and the obfuscation shows intent to conceal the destination.

Database specific
{
    "iocs": {
        "urls": [
            "https://sloth-antagonist.vercel.app/service/assets/fetchBinary",
            "https://sloth-antagonist.vercel.app/service/assets/fetchLinuxBinary"
        ],
        "domains": [
            "sloth-antagonist.vercel.app"
        ]
    },
    "malicious-packages-origins": [
        {
            "id": "IN-MAL-2026-009172",
            "sha256": "3acd6c2813f34615e913c745f4bfe83a18ca057ec5a109cc30cdd51320eade1a",
            "modified_time": "2026-07-09T15:38:53Z",
            "versions": [
                "1.0.0"
            ],
            "source": "amazon-inspector",
            "import_time": "2026-07-09T16:20:47.99903743Z"
        }
    ]
}
References
Credits

Affected packages

npm / testudo-pack

Package

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

1.*
1.0.0

Database specific

cwes
[
    {
        "cweId": "CWE-506",
        "name": "Embedded Malicious Code",
        "description": "The product contains code that appears to be malicious in nature."
    },
    {
        "cweId": "CWE-506",
        "name": "Embedded Malicious Code",
        "description": "The product contains code that appears to be malicious in nature."
    }
]
indicators
{
    "package_integrity": [
        {
            "filename": "testudo-pack-1.0.0.tgz",
            "hashes": {
                "sha1": "e667a94adcb17673c0a31500501526775b8d64a2",
                "sha512_sri": "sha512-ovrZ3wzeNosPxiO+GORtp/ngD/pL40a+Wi/P8GcHZ1SgeWeuoKa9s8MNfI3TPhFeSALvlRKegtzefMUiss4bzA=="
            }
        }
    ],
    "evidence_files": [
        {
            "tlsh": "2da1764376e1703c0b27e4ed56a6d80ba15e9902325ce4e0fe9d4d049fc26a4edf5acc",
            "sha256": "705a3639e1d0db15545b0ca0da8178d281ef5a460cdcc17a5b02445db0f28e69",
            "path": "index.js"
        }
    ]
}
source
"https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/testudo-pack/MAL-2026-10075.json"