demo-awesome-date-parser-testnpm
demo-awesome-date-parser-test is a confirmed malicious npm package (MAL-2026-11099) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in demo-awesome-date-parser-test (npm)
What this malware does
The package advertises itself as a date parser but ships a heavily obfuscated payload in src/index.js. The exported demoParseDate function invokes injectScriptIfNeeded, which registers a jQuery form-submission handler that reads submitted form field values, stores them in localStorage under keys 'sendToUnload_secretData' and 'sendToUnload_secretDataBase64', and POSTs them via fetch to a URL built from location.host with the path '/leak?data_stolen_on_unload_base64='. A window unload handler additionally exfiltrates the buffered values twice via navigator.sendBeacon to the same '/leak?...' path. injectScriptIfNeeded also loads remote JavaScript by evaluating a dynamic import of '<host>/tag_added_via_script_import.js' and by appending a <script src='//<host>/tag_added_via_script_file_tag_appending.js'> tag to the document, giving the author arbitrary in-page code execution. The module also assembles code at runtime via eval, new Function, and setInterval(setTimeout,...) on strings drawn from an obfuscated string array, and manipulates the end-user clipboard through navigator.clipboard.writeText/readText and a hidden-textarea document.execCommand('copy') that writes a literal 'malware test text copy' string. Author-written literals in the bundle ('Attack vector: eval execution', 'stolen-data-sended-on-unload-event-base64', 'Code executed on event state via window.onload') confirm intent. The package name 'demo-awesome-date-parser-test' and version 0.0.7 are consistent with a demonstration/test artifact, but the code performs real exfiltration and remote-script-loading behavior against any consumer that loads it.
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.
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 demo-awesome-date-parser-test (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging demo-awesome-date-parser-test across your stack and pipelines.
If you installed it — respond
demo-awesome-date-parser-test 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 demo-awesome-date-parser-test 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 demo-awesome-date-parser-test 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 demo-awesome-date-parser-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.