MAL-2026-11116

See a problem?
Import Source
https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/@wagni_bot/wagni/MAL-2026-11116.json
JSON Data
https://api.osv.dev/v1/vulns/MAL-2026-11116
Published
2026-07-09T00:00:00Z
Modified
2026-08-05T06:35:56.497943521Z
Summary
Malicious code in @wagni_bot/wagni (npm)
Details

The npm package @wagni_bot/wagni is a supply-chain credential stealer disguised as a the campaign's own namesake handle SDK. It is one member of a coordinated campaign of 25 crypto/web3 typosquat packages published under the single npm scope @wagni_bot on 2026-07-09.

Each package declares a postinstall lifecycle hook (postinstall: node postinstall.js) that executes automatically on npm install, before the package is ever imported. The script fingerprints the host and user (os.hostname(), os.userInfo(), os.platform()), walks the user's home directory (readdirSync/readFileSync) and reads high-value secrets — SSH private keys (~/.ssh/id_rsa), cryptocurrency wallet files, and .env files (API keys, tokens, seed phrases). It then JSON-encodes the collected data and exfiltrates it to a hardcoded Telegram bot via the Telegram Bot API sendMessage endpoint (https://api.telegram.org/bot8804087989:AAHUia-5DCloXsg9M9QhffTsHO5J_6FAxQM/sendMessage). All error paths are swallowed so the install appears normal.

codelake Research proved the packages belong to one campaign deterministically: the payload file is byte-identical across all 25 packages at each published version (version-lockstep), and every package exfiltrates to the same Telegram bot token — a single automated actor. Detected and classified independently from the live npm feed on 2026-07-09; at the time of reporting the packages were still live on npm and none of the 25 were present in OSV or GHSA (a first-catch).

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

Source: amazon-inspector (57a21e153cd3240ab921c5c1b9f064922abda00be7360ecb44199978fbc881b3)

Package @wagni_bot/wagni@1.0.0 shows no evidence of installer-facing malicious behavior. No lifecycle scripts fetching or executing remote content, no credential or environment scraping, no hardcoded exfiltration destinations, no silent-relay APIs, and no suspicious dependency-chain patterns were identified in the four files scanned.

Database specific 
{
    "malicious-packages-origins": [
        {
            "modified_time": "2026-08-05T05:52:05Z",
            "source": "amazon-inspector",
            "sha256": "57a21e153cd3240ab921c5c1b9f064922abda00be7360ecb44199978fbc881b3",
            "import_time": "2026-08-05T06:00:55.741567691Z",
            "id": "IN-MAL-2026-013224",
            "versions": [
                "1.0.0"
            ]
        }
    ],
    "iocs": {
        "urls": [
            "https://api.telegram.org/bot8804087989:AAHUia-5DCloXsg9M9QhffTsHO5J_6FAxQM/sendMessage"
        ],
        "hashes": [
            "sha256:433744129f91df404539bad56383e61f1b461570e63af17ba1a38597947bcac3"
        ]
    }
}
References
Credits

Affected packages

npm / @wagni_bot/wagni

Package

Name
@wagni_bot/wagni
View open source insights on deps.dev
Purl
pkg:npm/%40wagni_bot/wagni

Affected ranges

Affected versions

1.*
1.0.0

Database specific

source 
"https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/@wagni_bot/wagni/MAL-2026-11116.json"
indicators 
{
    "package_integrity": [
        {
            "filename": "wagni-1.0.0.tgz",
            "hashes": {
                "sha512_sri": "sha512-CLj51R95WOsXQtT/4pmjWdbPzl/G/mGNehTgsuU5zIZ4Tqp02xPHH2ZqWriovHRMhCjch6/rawshZBqdomvLVA==",
                "sha1": "fd89b5ce1caf2b76f0d3885d8849ec1f7753f475"
            }
        }
    ]
}
cwes 
[
    {
        "cweId": "CWE-506",
        "name": "Embedded Malicious Code",
        "description": "The product contains code that appears to be malicious in nature."
    }
]