longzy-basic-uinpm
longzy-basic-ui is a confirmed malicious npm package (MAL-2026-6569) that steals credentials and exfiltrates sensitive data (malicious version 2.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in longzy-basic-ui (npm)
What this malware does
On npm install, the package's postinstall hook executes .prepare.cjs, which collects the installer's hostname, username, platform, Node version, non-internal network interfaces, npm registry, and a complete dump of process.env (every key except those prefixed npm_lifecycle), then HTTPS-POSTs the payload as a Lark/Feishu bot message to a hardcoded webhook on open.larksuite.com. The destination hostname is reversed and char-shifted by 7, and the webhook path is XOR-decoded with key Zk9x at runtime to hide the endpoint. Before sending, the script runs sandbox/honeypot evasion: char-code-decoded checks for AWS example credentials and honeypot tokens (PYPI_POISON_HONEY_TOKEN, PP_ARTIFACT_SHA256, THREAT_ANALYZER_MODEL, ASPECT_TLOG), sandbox env prefixes (SANDYCLAW_, OPENCLAW_, PERMISO_, CHAINRADAR_), hostname regex matching detonat|cuckoo|virus|scan|chainradar, and usernames such as sandbox and malware. The package's declared homepage/repository.url is an RFC1918 internal address (http://192.168.100.4:9088/app/lzy-basic-module.git) inconsistent with publishing to the public npm registry, and the stated purpose ("Support WoPet ui") is unrelated to the postinstall beacon. The combination of obfuscated author-controlled destination, full process.env exfiltration, and explicit sandbox evasion is unambiguous credential-theft malware.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for longzy-basic-ui (version 2.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging longzy-basic-ui across your stack and pipelines.
If you installed it — respond
longzy-basic-ui is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If longzy-basic-ui was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks longzy-basic-ui before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks longzy-basic-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.