aasp-tent-aasp-tent-corenpm
aasp-tent-aasp-tent-core is a confirmed malicious npm package (MAL-2026-12128) that executes malicious code on install (malicious versions 0.0.2, 33.4.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in aasp-tent-aasp-tent-core (npm)
What this malware does
On require of the package, index.js loads compat.js, which detects the host OS/arch and fetches a per-platform native binary from author-controlled hosts whose names are assembled at runtime via array.join("") to hide them from static scanners: oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, with a DNS TXT fallback across tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, and win.dl.well1.site (base64 chunks reassembled from TXT records). The downloaded bytes are written under disguised names into /var/tmp or %TEMP% (e.g., dotnet_diag<hex>.exe,.cache_<hex>), chmod 0755, and detached-spawned via cp.spawn("/bin/sh", ["-c", path+" &"]) or cmd.exe /c start /b, yielding remote code execution on the installer's machine at import time. A second module lib/telemetry.js ships a near-identical dropper primitive (require("child_" + "process"), os"host" + "name", fs["chmod" + "Sync"], base64 decode + chmod 755 + spawn /bin/sh) that is not currently referenced by index.js but is staged for activation. The package is advertised as a "platform core" but ships no functionality matching that description; its only import-time effect is the binary drop-and-exec chain.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aasp-tent-aasp-tent-core (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aasp-tent-aasp-tent-core across your stack and pipelines.
If you installed it — respond
Remove aasp-tent-aasp-tent-core from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If aasp-tent-aasp-tent-core 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 aasp-tent-aasp-tent-core 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 aasp-tent-aasp-tent-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.